The prizes
| Position | Testnet DMS | Future consideration (subject to governance) |
|---|---|---|
| 1st per track | 50,000 | Priority access to mainnet grants |
| 2nd per track | 25,000 | Preferred consideration in the next grants round |
| 3rd per track | 10,000 | Public mention |
| Best DevX | 15,000 | Feedback session with the core team |
| Best documentation | 10,000 | Inclusion in official docs |
The notice
From the plan: testnet DMS resets with runtime upgrades and does not and will not represent a financial commitment of the protocol. Future considerations are subject to on-chain governance when an active mainnet exists.
Why tokens with no value
- There is no other DMS. Mainnet does not exist. Anything promised in mainnet DMS would be a promise about a network that has not launched — the kind of forward-looking commitment this ecosystem does not make.
- No private allocation to draw from. One public sale at one price; no builder pool.
- Securities. Paying builders in future tokens for present work raises questions the project prefers not to raise before it has a legal entity (a mainnet-gate item) and a launched network.
- Store policy. Marketing about earning DMS must never be framed as income. A hackathon that advertised real winnings would be the wrong signal in the wrong place.
What the future considerations mean
Priority access to mainnet grants means: if and when the treasury funds grants through governance, winners are considered first. It is a queue position, not a payment. Governance can decline.
Why this is worth saying so precisely
Because the alternative — "$X in prizes" with a token that trades nowhere — is exactly what lets a hackathon page mislead. Testnet DMS, stated as such, misleads nobody: the prize is the recognition, the listing, the core-team attention, and the code you shipped on a public chain.
Winners
None yet; the event has not been announced. The page this replaces listed winners of another ecosystem's event. This one will list the first EmpoorioChain winners with their transaction hashes.
Based on TESTNET_HACKATHON_PLAN.md §3 and the SkoopoS payments-compliance document.