420Docs context
Skip to content

420 Arbitration developer integration

Open and consume disputes only through registered domains and exact origin identifiers. Treat finalized rulings as bounded inputs, not privileged calls into the rest of the ecosystem.

Before consuming a ruling, verify expected domain/origin, case parties if relevant, finalized arbitration state, ruling/remedy commitment, required chain finality and replay protection.