@NewtonProtocol $NEWT #Newt
i keep getting stuck on one small ugly part of Newton.
not the Rego policy. not even the pass / fail attestation. the thing before that.
the Gateway.
because i think most people, me too at first, read Newton like it already has the canonical PolicyData sitting there and then just checks whether an intent should pass or fail against it. neat story. too neat maybe.
but that is not really what starts happening.
on Newton, first the Gateway pulls in PolicyData, WASM data oracle outputs, all the external signals the policy needs. then operators look at them. compare them. narrow them down until quorum can live with one canonical input for policy evaluation. not perfect truth. not divine truth. just enough agreement to let pre-settlement enforcement keep moving.
that part matters more than i expected.
because then Newton stops feeling like compliance middleware to me and starts feeling more like an authorization layer that forces competing oracle outputs into PolicyData the PolicyClient can actually verify before settlement.
and that bothers me in a good way.
because once you see it like that, the Newton Rego policy is not the first judgment anymore. the first judgment is earlier. which oracle outputs count. which external signals count. how much disagreement still fits inside quorum. what gets medianed down into something the Aggregator can package into a BLS aggregate signature and send forward like the operator set has one mind.
does it really have one mind though or just a quorum-shaped truce.
maybe that is the deeper thing here.
onchain people keep talking like execution is the event. Newton keeps dragging my attention backward. toward the earlier moment where operators have to stop disagreeing and hand the chain one canonical PolicyData input the PolicyClient will accept.
by the time the attestation arrives, the harder judgment already happened.
$CRWD $TLM
i keep getting stuck on one small ugly part of Newton.
not the Rego policy. not even the pass / fail attestation. the thing before that.
the Gateway.
because i think most people, me too at first, read Newton like it already has the canonical PolicyData sitting there and then just checks whether an intent should pass or fail against it. neat story. too neat maybe.
but that is not really what starts happening.
on Newton, first the Gateway pulls in PolicyData, WASM data oracle outputs, all the external signals the policy needs. then operators look at them. compare them. narrow them down until quorum can live with one canonical input for policy evaluation. not perfect truth. not divine truth. just enough agreement to let pre-settlement enforcement keep moving.
that part matters more than i expected.
because then Newton stops feeling like compliance middleware to me and starts feeling more like an authorization layer that forces competing oracle outputs into PolicyData the PolicyClient can actually verify before settlement.
and that bothers me in a good way.
because once you see it like that, the Newton Rego policy is not the first judgment anymore. the first judgment is earlier. which oracle outputs count. which external signals count. how much disagreement still fits inside quorum. what gets medianed down into something the Aggregator can package into a BLS aggregate signature and send forward like the operator set has one mind.
does it really have one mind though or just a quorum-shaped truce.
maybe that is the deeper thing here.
onchain people keep talking like execution is the event. Newton keeps dragging my attention backward. toward the earlier moment where operators have to stop disagreeing and hand the chain one canonical PolicyData input the PolicyClient will accept.
by the time the attestation arrives, the harder judgment already happened.
$CRWD $TLM