The Hardest Part of a Policy Is Agreeing on Reality
While reading Newton’s whitepaper, I assumed the difficult part would be writing the policy itself.
“Block the transaction if APY falls below 5%” sounds straightforward.
Then I noticed a deeper problem: what if five operators check the same market at the same moment and see five slightly different APYs?
One sees 5.12%. Another sees 5.04%. A third sees 4.98%.
Now the policy is no longer the hard part. Reality is.
This matters because Newton’s operators need to sign the same result before a BLS aggregate signature can be created. If every operator evaluates a different data value, they may all follow the policy correctly and still fail to agree.
Newton’s answer is a two-phase consensus process.
First, in the Prepare phase, operators independently fetch external data through sandboxed WASM providers. That could be oracle prices, sanctions feeds, risk scores, or market data. The Gateway then computes a canonical dataset, using median-based consensus for numeric fields.
Second, in the Evaluate phase, every operator runs the same Rego policy against that same canonical data, signs the result, and the Aggregator exits once the required stake-weighted quorum is reached.
That design changed how I think about policy systems.
A rule can be perfectly written and still produce useless outcomes if the network cannot agree on the inputs.
For DeFi vaults, that difference is critical. A leverage cap, APY threshold, or oracle-health rule is only enforceable if operators share a consistent view of the market before capital moves.
The real innovation is not simply “policy as code.”
It is turning messy, time-sensitive external data into one verifiable decision that a smart contract can trust.
The hardest part of a policy is not deciding the rule.
It is agreeing on what is true right now.
@NewtonProtocol $NEWT #Newt
While reading Newton’s whitepaper, I assumed the difficult part would be writing the policy itself.
“Block the transaction if APY falls below 5%” sounds straightforward.
Then I noticed a deeper problem: what if five operators check the same market at the same moment and see five slightly different APYs?
One sees 5.12%. Another sees 5.04%. A third sees 4.98%.
Now the policy is no longer the hard part. Reality is.
This matters because Newton’s operators need to sign the same result before a BLS aggregate signature can be created. If every operator evaluates a different data value, they may all follow the policy correctly and still fail to agree.
Newton’s answer is a two-phase consensus process.
First, in the Prepare phase, operators independently fetch external data through sandboxed WASM providers. That could be oracle prices, sanctions feeds, risk scores, or market data. The Gateway then computes a canonical dataset, using median-based consensus for numeric fields.
Second, in the Evaluate phase, every operator runs the same Rego policy against that same canonical data, signs the result, and the Aggregator exits once the required stake-weighted quorum is reached.
That design changed how I think about policy systems.
A rule can be perfectly written and still produce useless outcomes if the network cannot agree on the inputs.
For DeFi vaults, that difference is critical. A leverage cap, APY threshold, or oracle-health rule is only enforceable if operators share a consistent view of the market before capital moves.
The real innovation is not simply “policy as code.”
It is turning messy, time-sensitive external data into one verifiable decision that a smart contract can trust.
The hardest part of a policy is not deciding the rule.
It is agreeing on what is true right now.
@NewtonProtocol $NEWT #Newt