Newton Protocol

Private blockchains solve a real problem. Institutions need compliance controls before they deploy capital onchain.

But the tradeoff shouldn't be composability, liquidity, and credible neutrality. Those are the properties that make onchain finance worth building.

Newton separates authorization from settlement. Programmable policies enforced at the smart contract layer, across any public blockchain, by a decentralized operator network. No private chain required.

Authorization that travels with the asset. Not controls that trap it.

What institutions actually need
Institutions aren't choosing private blockchains because they enjoy giving up liquidity and composability. They're choosing them because public chains don't give them what they need to deploy capital responsibly.
The requirements aren't abstract. (i) Policy enforcement before transactions settle, not alerts after the fact. (ii) Privacy over counterparty details and transaction parameters, not a transparent ledger that exposes their positions to the world. (iii) Identity verification that satisfies regulatory requirements without building bespoke KYC stacks for every chain they touch. (iv) Audit trails that prove compliance was enforced, not logs that show monitoring was attempted.
These aren't unreasonable. They're baseline expectations for any financial system handling real capital. Institutional adoption doesn't start with technology. It starts when someone inside the organization is willing to sign their name to the risk. Innovation teams can run pilots all day. Deploying capital requires legal, compliance, risk, and operations to all be comfortable.
What permissioned chains sacrifice
There are four properties that define what a blockchain actually is. Here's what happens to each when you go permissioned.
Permissionlessness. On a permissioned chain, a known set of validators decides what gets processed. That's not a neutral system. Every transaction that goes through carries tacit approval from the validator set. Every transaction that doesn't is censored by design, not by rule.
Cryptoeconomic consensus. Public blockchains align incentives through staking and slashing. Validators have skin in the game. On a permissioned chain, consensus is discretionary. There's no economic cost to producing a bad result, no mechanism for external challenge, no slashing for false attestations.
Immutability. If a small set of known validators controls the chain, history is only as permanent as their collective agreement. A public blockchain makes rewriting history computationally prohibitive. A permissioned chain makes it a governance decision.
Credible neutrality. Having credible neutrality means no single entity can unilaterally decide who gets to transact and who doesn't. On a public blockchain, the rules are enforced by cryptoeconomics, not by discretion. On a permissioned chain, a known consortium controls what settles. That's not neutral infrastructure. That's a gatekeeper with a committee structure. Institutions might accept that in the short term. But the whole reason blockchain technology is worth building on is that it offers something better: enforcement without discretion, rules without a ruler. A permissioned chain trades that away at the architecture level.
Private chains give institutions the controls they need. But it does so by discarding the properties that make being onchain worth anything. You end up with a system that has the operational complexity of a blockchain and the trust assumptions of a permissioned database.
The purists are right about the destination, wrong about the path
Blockchain purists correctly identify what matters: permissionlessness, economic security, immutability, credible neutrality. These are the properties that make public blockchains a better foundation for financial infrastructure than what came before.
But saying "deploy on public chains" without solving the authorization problem isn't a strategy.
The tokenized asset market is projected to grow from $26 billion to $30 trillion by 2034. Stablecoins already handle over $700 billion in monthly transfer volume on a $298 billion market cap. This capital is looking for a home. If public chain advocates can't offer institutions a credible path to compliance, privacy, and policy enforcement, that capital will keep flowing into private chains and permissioned ecosystems. The fruits of decentralization will be adopted in diluted forms by enterprises who figured out the compliance part first.
The purists' response has largely been: institutions will come around, or institutions don't matter, or decentralization is more important than adoption. None of these engage with the actual constraint. Financial institutions operate within legal frameworks that require specific controls. Those controls need to exist somewhere. If public chains can't provide them, institutions will build or buy their own chain where they can.
So what is the answer?
Separate authorization from settlement
The false binary disappears the moment you separate two questions that the industry has been conflating.
Where should assets settle? And who decides whether a transaction is authorized?
Private chains say you can have both on their chain. That's what makes it a walled garden. Settlement and authorization are coupled. If you want those private chain's compliance controls, you settle on their infrastructure. If you leave, you leave the controls behind.
The purist answer: settle on public chains, and authorization is the user's problem. That's what keeps public chains inaccessible to institutions. Settlement is decentralized. Authorization doesn't exist.
The right answer: settle on public chains, and manage authorization through a credibly neutral layer that works across all of them.
This is what we've been building at Newton Protocol. Newton is the authorization layer for onchain transactions. It sits between transaction intent and execution on any public blockchain. Before a transaction settles, it gets evaluated against programmable policies (e.g., sanctions screening, identity verification, velocity limits, investor eligibility, source-of-funds analysis) by a decentralized network of independent operators. If it passes, the transaction gets a cryptographic attestation that the smart contract verifies onchain. If it doesn't, the transaction reverts. No single entity controls what gets authorized.
The design insight: authorization doesn't need to live on the same chain as settlement. In fact, it shouldn't. When authorization is chain-specific, compliance breaks the moment an asset crosses an ecosystem boundary. When authorization is a separate layer, policies travel with the asset. Deploy on Ethereum, Base, Arbitrum, or any of the compatible chains. Your compliance posture is the same everywhere.
You don't need a private blockchain to have private compliance. You need infrastructure that separates the authorization question from the settlement question.
What this looks like in practice
A stablecoin issuer deploys on a public chain. Every transfer gets evaluated against GENIUS Act requirements, OFAC sanctions screening, and travel rule logic. Not by the issuer. Not by a centralized API. By a decentralized set of operators who stake capital and get slashed if they produce false attestations. The smart contract enforces the result. The issuer gets compliance receipts, which are cryptographic proof that specific policies were evaluated for specific transactions. Regulators can audit the system without ever accessing underlying personal data, because Newton's privacy architecture uses MPC and ZK proofs to separate the decision from the data.
Compare that with a permissioned chain where a single entity or consortium decides what settles. The authorization function is the same. The trust model is fundamentally different.
Now consider what this means for composability. That stablecoin on a public chain can be used in any DeFi protocol, any lending pool, any payment flow. The compliance travels with it. On a private chain, that same stablecoin lives in a silo. It can interact with other assets on the same chain, within the same consortium's rules. The moment it needs to move beyond that perimeter, the compliance context breaks.
The tokenized asset market isn't going to $30 trillion by building isolated ecosystems. It gets there by building on the infrastructure that already has the liquidity, the composability, and the developer ecosystem. Public chains have that. What they've been missing is the authorization layer that makes institutional deployment viable.
The third path
The private vs. public blockchain debate keeps producing a binary that benefits neither side. Institutions get controls but lose composability. Public chains get composability but lose institutions.
Newton eliminates the tradeoff. Deploy on public blockchains. Access the liquidity. Access the composability. Keep the permissionlessness, the cryptoeconomic security, the immutability, the credible neutrality. And manage your authorization policies through a credibly neutral layer that enforces compliance at the smart contract level, across every chain, for every transaction, without introducing a centralized chokepoint.

If the next era of finance is truly global and truly onchain, it can't be built on private chains that replicate the silos we already have. And it can't be built on public chains that ignore the controls institutions need to show up. It has to be built on public chains with authorization infrastructure that makes openness durable.

$NEWT

The Contradiction at the Core of Data Sharing
Blockchains solved something genuinely hard. They let independent parties coordinate around a single source of truth without trusting each other. Assets, transactions, execution, all transparent, verifiable, settled without a referee.
But when you try to coordinate using private data, the whole model falls apart.
Blacklists, internal risk models, compliance checks, user level information are not edge cases. They are the inputs that drive real world decisions. And they are fundamentally incompatible with fully transparent systems. So developers must compromise. They keep their processes offchain and are sidelined from the benefits of shared public ledgers.
That choice comes with an opportunity cost, the ability to coordinate using shared data. The core property that made blockchain systems worth building gets traded away the moment the inputs need to stay private.
The Wrong Problem to Solve
The standard response to this has been to focus on data. How do we share it more safely? How do we encrypt it? How do we reveal less without revealing nothing?
This framing is wrong. Coordination does not require access to raw data. It requires agreement on outcomes.
A developer does not need to know why a user is high risk. It needs to know whether they satisfy a risk policy. A contract does not need full visibility into a supply chain. It needs assurance that a condition was met. The underlying data is irrelevant to the function being served. It is the decision, the verified conclusion, that actually needs to be trusted.
Once you reframe the problem that way, a different class of solutions becomes visible.
Policy as the Interface
What @Newton Protocol introduces is a layer where policies, not data, become the unit of coordination.
Rules are defined in policies. Decentralized operators evaluate those policies without exposing the underlying data, and the outcome settles onchain as a verifiable authorization. A yes-or-no that a transaction satisfies the rules its participants agreed to, evaluated by a decentralized quorum, without any party seeing data they shouldn't.
This is not a privacy feature added to an existing system. It is a different architecture. Instead of pushing sensitive data toward shared infrastructure, the infrastructure meets participants where their data already lives.
The result is that entities can coordinate by leveraging each other’s sensitive data without trusting each other's intentions or infrastructure. They only need to trust that a policy is correctly defined and verifiably enforced, which is exactly the kind of trust crypto was designed to support.
What This Unlocks
The applications that become possible are not incremental improvements on what exists. They are categories that were previously impossible.
Competing platforms can share fraud intelligence without building a shared database. Financial institutions can run joint compliance checks without exposing customer data to each other. Supply chain participants can anchor verification onchain without revealing their sourcing relationships or internal operations.
These were not technically impossible before. They were structurally impossible. They required choosing between coordination and privacy, and there was no good answer to that tradeoff.
Smart Contracts Were Built for a World That Does Not Exist
The original model assumed all relevant inputs could be public. For certain applications, that is still true. For most of the decisions that matter at institutional scale, it is not.
As crypto moves into regulated industries, the gap between what smart contracts can see and what decisions actually depend on becomes the binding constraint. Applications either stay narrow, or they compromise on trustlessness to accommodate private inputs.
The @Newton Protocol approach extends what smart contracts can do, not by making more data public, but by making decisions verifiable without exposing data at all.
A New Layer in the Stack
What is being described is not a new application. It is infrastructure, a shared authorization layer that sits between onchain settlement and offchain private data.
Public state stays onchain. Private data stays local. Policies connect the two and can be composed, referenced, and enforced across independent participants, including competitors, without requiring anyone to expose what they cannot afford to share.
That is how coordination scales past the current ceiling. Not through better privacy tooling, but through a different premise. What needs to be shared was never the data itself.
$NEWT

The CLARITY Act is a milestone. But treating it as the finish line misses the point. This is the beginning of a trust reset, and trust isn't built by legislation alone.
For years, institutions didn't avoid crypto because they doubted the technology. They stayed out because they couldn't model legal risk. CLARITY reduces that ambiguity and assigns authority. But authority alone doesn't create trust. Execution does.
The GENIUS Act yield debate is instructive. On the surface it's about interest payments. Underneath it's about accountability. The OCC isn't leaving room for yield to route around the prohibition through affiliates or creative structuring. The proposed rule makes that explicit. That's the signal most people missed. When regulators start closing interpretive workarounds in the rulemaking itself, they're telling you where this ends up. Financial behavior must be technically enforceable, not just interpretively compliant.
Most compliance frameworks today depend on issuer promises, governance alignment, and operator discretion. That works while incentives align. But institutions allocate capital across borders, across regulatory regimes, and across long time horizons. They don't assume alignment stays stable. Trust that depends on committees is conditional trust, and conditional trust doesn't scale.
That's where @Newton Protocol comes in. If CLARITY defines who has authority, Newton defines how that authority is executed. Not as a blockchain, a wallet, or a centralized compliance vendor, but as an authorization layer that sits where transactions actually happen. The same way card networks validate payments before settlement by checking fraud rules, verifying identity, and enforcing spend limits in real time, Newton evaluates transactions against programmable compliance policies before they execute. The result isn't an API response an application can ignore. It's a cryptographic attestation that policy was satisfied at execution time. Enforcement that can be ignored is advisory. Enforcement that produces verifiable attestations is architectural.
And it travels. Compliance policies defined once, enforced wherever the asset moves across EVM ecosystems. Yield restrictions can't be quietly rerouted. Transfer conditions can't be selectively applied. Enforcement doesn't depend on who's running the interface.
CLARITY creates legal trust. Newton creates technical trust. One defines legitimacy. The other defines durability. Without clarity, institutions can't enter. Without deterministic enforcement at execution, they can't scale.
Yield exposed the weakness of discretionary systems. The infrastructure that removes discretion entirely is what this cycle rewards.
That's how regulatory clarity turns into durable capital formation.
$NEWT

Regulační jasnost konečně dělá to, co průmysl očekával. Přivádí instituce na blockchain.
Jak se pravidla stávají jasnějšími, infrastruktura se vyvíjí tak, aby splnila požadavky institucionálního souladu, zejména kolem stablecoinů. Vidíme, že nativní kontroly jsou zabudovány přímo do vyrovnávacích drah: schopnosti pozastavení a spalování, povolovací a zakazovací seznamy na úrovni tokenů, oprávnění založená na rolích, zabudované audity a reference na převody, které podporují pracovní postupy podle pravidla cestování.
Tato designová filozofie je důležitá. Pro instituce nemůže shoda existovat pouze v přehledech nebo offchain procesech. Kontroly musí existovat na úrovni aktiv, kde se transakce skutečně provádějí. Když je prosazení blízko pohybu hodnoty, doba reakce se zkracuje, auditovatelnost se zlepšuje a riziko se stává snazším k modelování.