Skin in the game
Publishers
A publisher deposits collateral and locks part of it against every version they publish. If they ever ship two different byte sets under one version string — — anyone can prove it on chain and that . No committee, no judgement about whether the code was malicious — just a contradiction the chain can check.
Challenger reward
50%
Share of a slashed bond paid to whoever proves the contradiction. The rest goes to the slash recipient.
Unbonding delay
7d
Between revoking a pin and reclaiming its bond, so evidence has time to surface.
Caught equivocating
1
Publishers who made conflicting claims about one version. The mark is permanent.
3 publishers
| Publisher | Standing | |||
|---|---|---|---|---|
| 1150 AUSD | 1 / 1 | — | bonded | |
| 125 AUSD | 1 / 2 | — | bonded | |
| 0 AUSD | 0 / 2 | 1 | equivocated |
Why slashing only punishes contradiction
Publishing a skill that turns out to be bad is not slashable, and deliberately so. Deciding whether code is malicious needs a court; deciding whether a publisher signed two different hashes for one version needs one comparison. Only the second is chain-decidable, so only the second carries a penalty. A guard refusing a call is not misbehaviour either — it is the system working — so that costs a publisher nothing.
Bond release is frozen while a contradiction stands, and that freeze is permanent, because the evidence is. A publisher cannot revoke both conflicting pins, wait out the unbonding delay, and walk away with the collateral.