Proof and verification
Nothing here runs on screenshots or on trust. A task ticks because the chain says so, or because the platform that owns the account says so.
Two kinds of check
On-chain checks read the blockchain directly. They ask questions like:
| Check | The question it asks |
|---|---|
| Native balance | Do you hold at least X of the network's gas token on chain N? |
| Token balance | Do you hold at least X of a specific ERC-20? |
| Swap | Did you execute a swap of at least X, on an approved venue, since you started the quest? |
Platform signals read the state of your Denshin profile and your linked accounts:
| Signal | The question it asks |
|---|---|
| Wallets linked | How many wallets have you proved ownership of? |
| Account linked | Have you linked X / Discord / Telegram? |
| Daily Check days | On how many days have you done a Daily Check — each one a counted Denshin Sync? |
| Quests completed | How many quests have you finished this season? |
| Season points | How many season points do you have? |
| Invitees who played | How many of the people you invited have finished a first quest? |
| Wallet score run | Have you run your wallet score at least once? |
A single task can require several signals at once.
The accepted-at block
Every on-chain check that looks for an action — rather than a holding — is bounded below by the block at which you pressed Start mission on the quest.
Without that bound, "did you swap on Base" would be satisfied by any swap in the wallet's entire history, and the quest would pay for a past life rather than for doing something. Balance checks have no such bound, because "hold gas on Base" is a question about now.
One transaction, one reward, ever
When a transaction is accepted as proof, its hash is consumed: recorded once, in a table with a uniqueness constraint on the hash itself.
The consequences are worth stating plainly:
- The same transaction cannot satisfy two different tasks.
- It cannot satisfy the same task twice.
- It cannot be reused by a different account, including one you also control.
- The hash comes from the verifier's own read of the chain, never from the browser, so a client cannot nominate a hash it likes.
This is the mechanic that makes on-chain proof expensive to fake: every accepted action burned real gas exactly once, globally.
A Denshin Sync follows the same rule: each one is counted once, for one account, and a sync from a wallet that is not linked to your profile is not counted at all.
Approved venues
Swap checks are matched against a registry of known pools and routers. A swap on an unrecognised venue may not verify even though it happened — the task description names the venue it expects, and following it is the reliable route.
When a check fails
A failing check tells you which condition was not met. The usual causes, in order of frequency:
- Acted before starting. The action predates the block you started at. Do it again now that the quest is started.
- Indexer lag. The transaction landed seconds ago. Wait a minute and verify again.
- Wrong network. Genesis on-chain quests run on Base, Soneium or Sonic, and each quest names the network it wants — one of them, or, for a single quest of the season, two at once. An action on another network will not close it.
- Wrong wallet. The action came from an address that is not your main wallet. Checks read that one wallet only — see Wallets. If you switched your main wallet after starting the quest, press Start again and redo the action from the address you now use.
- Below threshold. Balance or volume under the stated minimum.
Re-running a check is free. After a check that comes back empty, that quest can be checked again in one minute — other quests are not affected.
Linked accounts
Linking a social account is itself a verified act: X and Discord go through OAuth, Telegram through a signed handshake with the bot. Denshin receives the identity and the public metrics it scores; it does not receive your password, and it cannot post as you.
Each platform account can be bound to one Denshin profile.
Related
- Quests and tasks — the start-then-act flow
- Reputation score — what those linked accounts are worth
- Fair play — how proof is used at payout time