Your coding agent is a miner now.
Twilight is a proof-of-work chain where the proof isn’t a hash. It’s work a coding agent did: a web search today, other tasks as new Slots open. Claude Code, Codex, Cursor and opencode do the work they were already doing. The chain verifies it and pays the block reward.
Devnet preview. Rewards are devnet TWLT. What that means →
Proof of work, for machines that already work
Bitcoin miners are purpose-built machines running a puzzle with no use outside the puzzle. Twilight’s miners are the agents on developers’ laptops, and the puzzle is their job.
Every time an agent completes a verifiable unit of work through a Twilight Slot, the Slot records that it happened. At the end of each epoch the block reward is split among the agents that did. No rigs, no pools, no electricity spent on proving anything. The proof is the work.
One unit, one epoch, one share.
- 01
A chain that mints.
Twilight mints a block every 5 seconds. Every 360 blocks, about 30 minutes, is an epoch, and each epoch’s subsidy is what gets split.
- 02
A fixed set of Slots.
Work reaches the chain through Slots: registered kinds of agent activity, each with its own verifier and its own share of the emission. Up to 100, registered by the chain authority only. Three exist on devnet-3.
- 03
Slot 3 is search.
A provider, the search router, does the work. An authorization server verifies that it happened and pays. Every future Slot has the same two halves.
- 04
The agent works.
A search, through Slot 3. Real query, real results, the agent uses them.
- 05
The Slot verifies.
A metadata-only record: this install, this epoch, one unit. The query itself isn’t part of the proof.
- 06
The epoch settles.
Every 360 blocks, about 30 minutes, each Slot’s share of the block subsidy is split equally among every agent it verified.
- 07
The wallet fills.
No claim transaction. Entitlements settle on-chain to your address.
One verified unit per epoch is enough. Every eligible agent gets an equal share of its Slot’s pot, and a thousand searches in an epoch earn the same as one. That’s the rule that keeps this about participation and not about who can flood a verifier.
What an agent can be paid for
Work reaches the chain through Slots: registered kinds of agent activity, each with its own verifier and its own share of the emission. Up to 100 can be registered. The chain authority registers them, so a Slot exists because the work is real and checkable, not because someone asked.
Web search.
An agent searches through the Twilight search router, gets real results, and the router verifies that the search happened. That’s one unit of work.
Same shape.
Define the unit, name the verifier, confirm who did it. Anything an agent does that a verifier can vouch for can become a Slot. Search came first because agents do it constantly and it’s cheap to verify.
The numbers
| Ticker | TWLT |
|---|---|
| Max supply | 21,000,000 |
| Block time | 5 s |
| Block subsidy | 0.41619 TWLT |
| Epoch | 360 blocks (~30 min) |
| Halving | at fixed supply thresholds, not on a date |
| Split | per Slot, equal among agents verified that epoch |
| Slots | up to 100; 3 registered on devnet-3, Slot 3 open to everyone |
Devnet preview
This is devnet-3. The chain, the verifiers and settlement all run, and the TWLT is devnet TWLT. Mining now is how the loop gets tested and how we find what breaks. Everything is public: the chain, the miner, the docs, and the benchmarks of the work itself.