Proof of Policy Enforcement
Settlement policies are versioned, hashed, and enforced at the protocol layer. Every policy decision is recorded as evidence.
Policy Corridor Configuration
Each corridor defines jurisdiction fencing, sanctions lists, transfer limits, KYC requirements, and authorization thresholds. Policies are expressed as structured JSON and hashed before enforcement.
Explore the policy configurator →Enforcement Evidence Mapping
When a settlement executes, the engine records which policy rules were evaluated, which passed, and which blocked. This evidence trail maps directly to the settlement receipt.
- Rule evaluation log per settlement
- Pass/fail status for each policy gate
- Block reason codes for rejected settlements
- Policy version hash included in receipt
Policy Versioning and Hashing
Every policy corridor is versioned with a monotonic counter. When a policy is updated, a new SHA-256 hash is computed and recorded on-chain. Settlement receipts reference the exact policy version that was active during execution.
Ready to verify?
Start with a structured POC. Evaluate JIL settlement infrastructure on a single corridor.