Building Before the Rules Are Final
The Rules Aren't Final but the Infrastructure Still Has to Be Built.
The CLARITY Act vote failed. There was an expectation that clearer legislation, together with future rulemaking from agencies, would accelerate the need for onchain policy enforcement.
That need hasn't gone away.
Institutions that want to operate onchain still care about risk management, compliance and policy enforcement. Those requirements don't disappear because legislation takes longer than expected.
The infrastructure still has to be built.
For years, financial compliance has happened surrounding the transaction. A provider screens an address. A compliance team reviews a counterparty. A risk system produces a signal. The transaction is then approved or rejected somewhere in the process.
Onchain finance changes the mechanics. Transactions can execute automatically, across applications and across networks. If a policy is supposed to constrain that transaction, there needs to be infrastructure capable of enforcing it at execution.
That's the authorization problem.
Newton can take inputs from whatever systems an institution already uses. An AML provider, credential system, sanctions oracle, risk engine, internal compliance system or another onchain application can provide the relevant signal.
The authorization layer evaluates those inputs against a programmable policy and determines whether the transaction is allowed to proceed.
That makes it input-agnostic. Institutions don't need to replace the systems they already use. Their existing compliance and risk infrastructure can become inputs into an enforceable onchain policy.
The policy itself is programmable. Requirements can change without requiring the underlying asset or application to be rebuilt. Different assets can have different policies. Different counterparties can have different permissions. External signals can change the outcome of a transaction.
This becomes even more important as financial activity becomes multichain.
An institution won't necessarily issue an asset, trade it, finance it and settle it on the same network. Assets will move between environments. Applications will interact with each other. Collateral will move wherever liquidity is available.
The policy needs to keep working when that happens.
Otherwise every new environment becomes another compliance integration, and the promise of open financial infrastructure starts looking a lot like the closed systems it was supposed to improve.
There is also a question of verification. Institutions need to know more than a transaction that happened to pass a compliance process. They need to be able to establish that the relevant policy was evaluated and that the transaction was authorized according to that policy.
That is where programmable and verifiable authorization becomes infrastructure.
The CLARITY Act may take another vote, or it may never pass during this term because of how partisan it has become. Agencies and regulators in other countries, however, will continue to develop rules. The exact requirements will change.
We don't need to wait for all of that to be finished before building the systems that will enforce those requirements.
The institutions coming onchain will care about risk management and compliance either way.
Newton gives them an input-agnostic authorization layer for turning those requirements into programmable policies and enforcing them before transactions execute.
We're building that infrastructure now.