Perfil de Mavis Evan | Binance Square

·

--

Artigo

Ver tradução

IT'S NOT ABOUT MAKING EVERYONE AGREE. IT'S ABOUT MAKING ENFORCEMENT CRYPTOGRAPHICALLY SOUNDLook, I’ll be honest. When I saw "another AVS" pop up in my feed, my eyes glazed over. We’ve all watched this cycle play out. New verification network. Grand claims about bridging offchain and onchain. Token launch. Then radio silence. Newton Protocol could absolutely be that. But policy engines? That part actually got my attention. Here’s the real problem with onchain finance right now. It’s exploding. Stablecoins alone are pushing $300 billion in circulation. Monthly transfer volumes? Over $700 billion. Tokenized real-world assets sit north of $21 billion and climbing. But the infrastructure to enforce compliance at the transaction level is basically nonexistent. Or worse, it’s centralized and opaque, which defeats the whole point of putting this stuff onchain in the first place. Smart contracts lack context, and that’s a genuine vulnerability. Wallets call contracts directly. AI agents hallucinate transactions. Sanctions lists change faster than governance can keep up. These aren’t manufactured problems. So why does Newton feel different? Because it isn’t trying to replace your compliance stack. It enhances it. Policy evaluation happens offchain, but the result a cryptographic attestation gets enforced onchain. Smart contracts actually require it at execution time. That’s the critical distinction between this and the typical "trust us, we checked" API approach. You get a verifiable proof that a policy was evaluated and satisfied, not just a JSON response an application could ignore. It works. Period. The architecture reads clean. BLS attestations. Privacy commitments. Composable SDK. You submit an intent, get a decision from an operator quorum. Standard stuff, but applied to a real pain point. The policy engine runs Rego, which enterprises already use for cloud-native policy. You write standard rules sanctions screening, KYC, source-of-funds, velocity limits, investor eligibility and Newton makes it cryptographically verifiable. You don’t need to understand the zero-knowledge stuff on the backend. Honestly, that’s where the magic is. The Rego evaluator compiles down to RISC-V and runs inside a ZK virtual machine. The proof certifies that given this specific policy and input data, you got exactly this output. No side effects. No external state. Pure determinism. And determinism? That’s what makes this trustless. Anyone can challenge an attestation. Not just operators. A compliance auditor, a competing app, or some automated bot can all submit challenges. You catch a discrepancy between what operators attested and your independent evaluation? You generate a ZK proof showing the policy produces a different output, submit it onchain within the dispute window, and if the proof verifies, the operators who signed the incorrect attestation get slashed. That’s not governance voting. That’s not multi-sig approval. It’s just math. The economics are straightforward too — the cost of attacking Newton scales with total stake. You can’t just compromise a few nodes and call it a day. Privacy gets tricky, and I appreciate how Newton handles it. The blockchain never sees identity data. Encrypted references stored in the IdentityRegistry, decryption requiring a quorum of operators. There’s also the Newton Privacy Envelope using HPKE, which enables stuff like sealed-bid auctions where no one not even operators can see individual bids before the evaluation window closes. Encrypted bids get evaluated collectively, results attested via BLS signatures without revealing losing bids. That eliminates front-running and information leakage in a way onchain auctions have never really solved. The friction? Predictable. Latency on policy evaluation. Operator network costs. Yet another layer for developers to learn. Enterprise adoption needs regulatory comfort that decentralized attestations might not provide. And then there’s the token. Always the token. The incentive design risks drifting toward speculation rather than genuine policy enforcement. I’ve seen this before. But the use cases are broad. Stablecoin issuers embedding policy evaluation at the transfer level. Tokenized securities with investor eligibility checks that can’t be bypassed even if someone compromises the admin key. Institutional DeFi access without permissioned forks. AI agents with programmatic guardrails. Cross-border payments with verifiable compliance receipts that satisfy regulators without exposing identity. Even fraud mitigation with non-custodial 2FA a compromised private key alone isn't enough to move funds. Applications submit intents through Newton’s Gateway API, get back an aggregate BLS signature, pass that to the smart contract. The contract validates against the TaskManager, confirms it’s valid and unexpired, and executes. Alice signs once. Compliance receipt stays onchain as proof that sanctions, KYC, velocity, and source-of-funds policies were evaluated and passed. Honestly? This is infrastructure we’ve needed for a while. Not some massive blockchain rearchitecture. Not a centralized compliance vendor. Not another proprietary protocol with vendor lock-in. Just neutral, auditable infrastructure that serves diverse participants with diverse requirements. A regulated European bank and a permissionless DeFi protocol can both use Newton, each with policies appropriate to their context, without being constrained by each other’s requirements. That’s the architectural bet. It’s not about making everyone agree on the same rules. It’s about making enforcement cryptographically sound so you don’t have to trust the intermediary. #Newt $NEWT $BIRB $TAIKO {future}(VELVETUSDT) {future}(RPLUSDT) {future}(ALLOUSDT)

IT'S NOT ABOUT MAKING EVERYONE AGREE. IT'S ABOUT MAKING ENFORCEMENT CRYPTOGRAPHICALLY SOUND

Look, I’ll be honest. When I saw "another AVS" pop up in my feed, my eyes glazed over. We’ve all watched this cycle play out. New verification network. Grand claims about bridging offchain and onchain. Token launch. Then radio silence. Newton Protocol could absolutely be that. But policy engines? That part actually got my attention.
Here’s the real problem with onchain finance right now. It’s exploding. Stablecoins alone are pushing $300 billion in circulation. Monthly transfer volumes? Over $700 billion. Tokenized real-world assets sit north of $21 billion and climbing. But the infrastructure to enforce compliance at the transaction level is basically nonexistent. Or worse, it’s centralized and opaque, which defeats the whole point of putting this stuff onchain in the first place. Smart contracts lack context, and that’s a genuine vulnerability. Wallets call contracts directly. AI agents hallucinate transactions. Sanctions lists change faster than governance can keep up. These aren’t manufactured problems.
So why does Newton feel different? Because it isn’t trying to replace your compliance stack. It enhances it. Policy evaluation happens offchain, but the result a cryptographic attestation gets enforced onchain. Smart contracts actually require it at execution time. That’s the critical distinction between this and the typical "trust us, we checked" API approach. You get a verifiable proof that a policy was evaluated and satisfied, not just a JSON response an application could ignore. It works. Period.
The architecture reads clean. BLS attestations. Privacy commitments. Composable SDK. You submit an intent, get a decision from an operator quorum. Standard stuff, but applied to a real pain point. The policy engine runs Rego, which enterprises already use for cloud-native policy. You write standard rules sanctions screening, KYC, source-of-funds, velocity limits, investor eligibility and Newton makes it cryptographically verifiable. You don’t need to understand the zero-knowledge stuff on the backend. Honestly, that’s where the magic is. The Rego evaluator compiles down to RISC-V and runs inside a ZK virtual machine. The proof certifies that given this specific policy and input data, you got exactly this output. No side effects. No external state. Pure determinism.
And determinism? That’s what makes this trustless. Anyone can challenge an attestation. Not just operators. A compliance auditor, a competing app, or some automated bot can all submit challenges. You catch a discrepancy between what operators attested and your independent evaluation? You generate a ZK proof showing the policy produces a different output, submit it onchain within the dispute window, and if the proof verifies, the operators who signed the incorrect attestation get slashed. That’s not governance voting. That’s not multi-sig approval. It’s just math. The economics are straightforward too — the cost of attacking Newton scales with total stake. You can’t just compromise a few nodes and call it a day.
Privacy gets tricky, and I appreciate how Newton handles it. The blockchain never sees identity data. Encrypted references stored in the IdentityRegistry, decryption requiring a quorum of operators. There’s also the Newton Privacy Envelope using HPKE, which enables stuff like sealed-bid auctions where no one not even operators can see individual bids before the evaluation window closes. Encrypted bids get evaluated collectively, results attested via BLS signatures without revealing losing bids. That eliminates front-running and information leakage in a way onchain auctions have never really solved.
The friction? Predictable. Latency on policy evaluation. Operator network costs. Yet another layer for developers to learn. Enterprise adoption needs regulatory comfort that decentralized attestations might not provide. And then there’s the token. Always the token. The incentive design risks drifting toward speculation rather than genuine policy enforcement. I’ve seen this before.
But the use cases are broad. Stablecoin issuers embedding policy evaluation at the transfer level. Tokenized securities with investor eligibility checks that can’t be bypassed even if someone compromises the admin key. Institutional DeFi access without permissioned forks. AI agents with programmatic guardrails. Cross-border payments with verifiable compliance receipts that satisfy regulators without exposing identity. Even fraud mitigation with non-custodial 2FA a compromised private key alone isn't enough to move funds.
Applications submit intents through Newton’s Gateway API, get back an aggregate BLS signature, pass that to the smart contract. The contract validates against the TaskManager, confirms it’s valid and unexpired, and executes. Alice signs once. Compliance receipt stays onchain as proof that sanctions, KYC, velocity, and source-of-funds policies were evaluated and passed.
Honestly? This is infrastructure we’ve needed for a while. Not some massive blockchain rearchitecture. Not a centralized compliance vendor. Not another proprietary protocol with vendor lock-in. Just neutral, auditable infrastructure that serves diverse participants with diverse requirements. A regulated European bank and a permissionless DeFi protocol can both use Newton, each with policies appropriate to their context, without being constrained by each other’s requirements. That’s the architectural bet. It’s not about making everyone agree on the same rules. It’s about making enforcement cryptographically sound so you don’t have to trust the intermediary.
#Newt $NEWT $BIRB $TAIKO

Mavis Evan

IT'S NOT ABOUT MAKING EVERYONE AGREE. IT'S ABOUT MAKING ENFORCEMENT CRYPTOGRAPHICALLY SOUND

ESTAMOS FAZENDO ISSO DO JEITO ERRADO: POR QUE AS PONTES ESTÃO QUEBRADAS E NEWTON RESOLVE ISSO

Newton Protocol (NEWT): Onde a IA Realmente Encontra DeFi Sem o Mínimo de Bost*

Tópicos em Alta