Expand description
Client-Side Validation Engine
The client receives consignments and seal consumption proofs from peers, verifies them locally, and accepts or rejects state transitions.
§Flow
Client receives consignment from peer:
│
├─ Bitcoin anchor? → Map UTXO spend → Right(id, commitment, owner, nullifier=None)
├─ Sui anchor? → Map object deletion → Right(id, commitment, owner, nullifier=None)
├─ Aptos anchor? → Map resource destruction → Right(id, commitment, owner, nullifier=None)
└─ Ethereum anchor? → Map nullifier registration → Right(id, commitment, owner, nullifier=Some(hash))
│
▼
Client validates uniformly:
1. Each Right.verify() passes
2. Commitment chain integrity (genesis → present)
3. No seal double-consumption (cross-chain registry)
4. Accept or reject the consignmentStructs§
- Seal
Consumption Event - Seal consumption event — the atomic unit of client-side validation.
- Validation
Client - Client-side validation engine.
Enums§
- Validation
Error - Errors that can occur during consignment validation.
- Validation
Result - Result of consignment validation.