NEWTON PROTOCOL · POLICY CLIENT
0xfa2b…2880revision 5 · superseded
0xfa2b8f045eb50cc6f8e13e82e10a41ef45732880 · 1 of 8 policies · Sepolia
Revision 5 is superseded. Every attestation minted against 0xd7ac151e…89d4 was revoked when revision 6 landed on 2026-10-18 — regardless of its expiry block, because the client’s policyId no longer matches. Tasks created under it still replay correctly: each one carries this exact set as its own frozen snapshot. See revision 6, the current set →
POLICY ID
REVISION
5 of 6
POLICIES
1 of 8
DISTINCT
1
RESPONSE EXPIRY
300 blocks
CHAIN
Sepolia
TASKS · 24H
—
ALLOW RATE
—
Policies — 1
one Rego + WASM pair per slot- 00x9ea65507248bf0f6d37dad6162df64cc632b9d6c0x9ea6…9d6cnot in factory registry300 blocksbounds set expiryhooknot in schema0xfa2b8f045eb50cc6f8e13e82e10a41ef45732880sheetnot in schemahttps://docs.google.com/spreadsheets/d/1lT3cmztG7dxTgnNDiVZjbE84UHtKogH07W6XWnbJd2Y/gviz/tq?tqx=out:csvmax_age_snot in schema600swap_selectornot in schema0x9d555cf7threshold_hexnot in schema0000000000000000000000000000000000000000000000000000000000000000deposit_selectornot in schema0xf08a814e
policyParams — 327 bytes on chain
0x7b22737761705f73656c6563746f72223a2230783964353535636637222c226465706f7369745f73656c6563746f72223a2230786630386138313465222c227468726573686f6c645f686578223a2230303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030222c227368656574223a2268747470733a2f2f646f63732e676f6f676c652e636f6d2f7370726561647368656574732f642f316c5433636d7a744737647854676e4e4469565a6a624538345548744b6f67483037573658576e624a6432592f6776697a2f74713f7471783d6f75743a637376222c22686f6f6b223a22307866613262386630343565623530636336663865313365383265313061343165663435373332383830222c226d61785f6167655f73223a3630307d
Each module is evaluated against its own input — {"params": <this slot’s policyParams>, "wasm": <this slot’s WASM output>}. There is no shared data.wasm object and no cross-slot namespace, so slot 1 cannot read slot 0’s WASM output and a policy cannot be written to depend on its neighbours.
Tasks under revision 5
no tasksExport CSVJSONNo tasks match this scope yet.
The export carries one row per task with the frozen policy set in slot order, and it is the complete filtered history rather than this page. It has no per-policy verdict column: TaskResponse.allowed is a single boolean for the whole set, so which policy denied a task is in no record.