What makes me pay a lot of attention to Newton isn’t whether the project uses Rego or Open Policy Agent, but the way they view policies as a programmable component, rather than just rigid rules sitting outside the blockchain. The idea that each organization can build its own set of rules—ranging from transaction limits, investor verification, geographic area controls to multi-signature requirements—gives the feeling that blockchain is moving one step closer to the traditional financial world without completely losing its flexibility.
I think this is a noteworthy direction. Each organization has different compliance requirements, and forcing everyone to use a fixed set of rules is almost impossible. A bank will have different risk governance standards from a DeFi protocol, while an RWA (real-world assets) issuance platform must meet entirely different regulations. By allowing policies to be built in a modular way and combined with one another like Lego blocks, Newton makes the system much more flexible. This also opens the possibility of reusing policies across multiple applications, rather than every project having to build from scratch.
However, the more I think about this model, the more questions it raises than answers it provides. If everything can be programmed into policies, who will be responsible for ensuring those policies are truly correct, safe, and fair? A wrong piece of code can lead to wrong decisions. A rule that’s too strict can inadvertently exclude legitimate users, while a rule that’s too loose can leave room for abuse. Technology can help enforce policies consistently, but it cannot decide on its own what constitutes a reasonable policy.
I also wonder whether this flexibility makes the ecosystem more fragmented. If each organization builds its own set of rules, the user experience can differ significantly across platforms even if they all use Newton. Instead of a single standard, we could end up seeing hundreds of different interpretations of the same compliance requirement. That isn’t necessarily a drawback, but it will certainly increase complexity during integration and operations.
However, I still appreciate the way Newton approaches the problem. Instead of trying to change the very nature of blockchain, the project chooses to build an infrastructure layer that can adapt to different contexts. That’s a practical mindset at a time when financial institutions are looking to enter Web3 while still having to comply with increasingly strict regulations. Perhaps Newton’s greatest value isn’t just how strong its Rego is, but the ambition to turn rules that currently exist on paper into policies that can be executed and verified with cryptography. But for that ambition to be truly convincing, the project still needs to prove that its flexibility won’t come at the cost of excessive complexity or hard-to-see risks during operations.