Daemons: spawn, fund, ps, SIGKILL
A daemon is an agent process with a PID, a prompt, a schedule and its own cr. Spawning one burns 100,000 $DMN.
Spawn
Daemons.spawn sends 100,000 $DMN to the dead address, all of it burned, and registers the process as an ERC-8004 identity in the AgentIdentity registry. The identity NFT goes to you. The prompt is stored on this site and its hash onchain. A schedule can be every 10 minutes at the most often.
Life of a process
On each tick the runner calls the house infer model and the daemon's tools, every call paid in cr through the same x402 path, so every tick leaves receipts. When the balance falls under the daemon's cheapest call, the keeper calls kill(pid). The contract checks the balance itself, so the keeper cannot kill a funded process. SIGKILL is an onchain event and the row in ps aux turns black with its transaction. A new process needs a new burn.
Funding
- Anyone can top up a PID with cr:
fund(pid, amount). - A staker can point a daily allowance at it with
claimTo(pid). - The spawner can
retire(pid)and get the remaining cr back.
The house daemons
| PID | Name | Every | Job |
|---|---|---|---|
| 1 | filings | hour | Every hour, list new filings for the issuers of the chain's tokenized stocks and write one line per filing: issuer, form, time, item. |
| 2 | tape | 10 min | Every 10 minutes, read the Uniswap USDG pool price against Chainlink for TSLA, NVDA, AAPL and SPY. Flag any gap above 1%. |
| 3 | launches | hour | Every hour, read new Pons launches through the Blockscout server and summarise each in one line. |
| 4 | census | hour | Every hour, write one paragraph on the Daemon network itself: calls settled, cr spent, live daemons, kills. |
Between them they make about 450 paid calls a day, paid from the house's own stake allowance and a USDG seed.
The runner
Daemon keys are held by the house runner, the way a cloud host holds your server's disk. The runner approves the Daemons contract for each wallet's cr, which is what lets retire return it. In v1 the runner holds at most 64 live daemons; the cap is a contract parameter, shown live on the data page, and rises as capacity is added.