POLICY REGISTRY
Policies
One policy is one Rego module and at most one WASM module, published by CID and immutable at its address. Composition is not here: a policy client composes up to eight of these and requires every one to allow, so the same policy can be picked off the shelf by several clients at different parameters.
8
POLICIES LIVE
0
WITH WASM
8
PURE REGO
0
REUSED
| Policy | Address | Chain | WASM | Clients | Tasks 24h | Solo allow | Published |
|---|---|---|---|---|---|---|---|
| 0xea71306356d455acfb192f1533c38aacc0e22f85 | 0xea71…2f85 | Ethereum | pure Rego | 1 | 0 | — | |
| 0x3b753ee8eb688dc1d01dd6baa48c181e29823d2e | 0x3b75…3d2e | Ethereum | pure Rego | 1 | 0 | — | |
| 0x5aebd7388777b938647570f7f827da1518ced812 | 0x5aeb…d812 | Ethereum | pure Rego | 1 | 0 | — | |
| 0x06f725e1fa95b4fe92e92b344676dcde261bc10b | 0x06f7…c10b | Ethereum | pure Rego | 1 | 0 | — | |
| 0xdeffd83760a963c9368f2337b26ac979ae285cb5 | 0xdeff…5cb5 | Ethereum | pure Rego | 1 | 0 | — | |
| 0xab434a206165b8b1db8d53734a3350c1523942a8 | 0xab43…42a8 | Ethereum | pure Rego | 1 | 0 | — | |
| 0x70887a6015c9d058531e93ee742c1a6f5b4fcef5 | 0x7088…cef5 | Ethereum | pure Rego | 1 | 0 | — | |
| 0x1bb3b7c84cf1e2168a1041687019043fecea28fb | 0x1bb3…28fb | Ethereum | pure Rego | 0 | 0 | — |
Solo allow is a policy’s allow rate over the tasks where it was the only policy in the set, and — everywhere else. TaskResponse.allowed is a single boolean for the whole set, and no record says which policy denied — so a per-policy rate inside a multi-policy set would be invention. The rate you probably want is on the client, where the set’s verdict is the whole story.