Newton needed a way for curators to write onchain policies. It didn't invent a new crypto language.
It reached for Rego, the Open Policy Agent standard that platform teams already use to guard cloud systems and APIs.
That choice says something.
@NewtonProtocol isn't courting people who want a novel DSL. It's meeting institutions where they already are, with a language their engineers have written for years.
Lower learning curve, faster to trust.
But Rego was built to gate API calls and server clusters, not money that settles with finality and can't be clawed back.
Familiar and fit-for-purpose aren't the same thing.
The pragmatism here is the part I respect about $NEWT . I'm just not sure a language designed for reversible systems carries cleanly into one where mistakes are permanent.
Newton is worth watching for how that holds up under real load.
#Newt
It reached for Rego, the Open Policy Agent standard that platform teams already use to guard cloud systems and APIs.
That choice says something.
@NewtonProtocol isn't courting people who want a novel DSL. It's meeting institutions where they already are, with a language their engineers have written for years.
Lower learning curve, faster to trust.
But Rego was built to gate API calls and server clusters, not money that settles with finality and can't be clawed back.
Familiar and fit-for-purpose aren't the same thing.
The pragmatism here is the part I respect about $NEWT . I'm just not sure a language designed for reversible systems carries cleanly into one where mistakes are permanent.
Newton is worth watching for how that holds up under real load.
#Newt
