LAST MOON

Ich habe die Angewohnheit, wenn ich auf technische Begriffe stoße, die ich nicht wirklich verstehe — ich mache nicht weiter, bis ich die Analogie finde, bei der es klickt. Fachjargon ist meistens einfach ein vertrautes Konzept, das nur ungewöhnlich eingekleidet ist.
zkPermissions tauchte in allem auf, was ich über Newton Protocol gelesen habe: Zero-Knowledge-„Circuits“, programmierbare Constraints, scoped Delegation. Okay. Aber was ist es eigentlich?
Ich habe nach einer Version in klarem Alltagsdeutsch gesucht und sie in der eigenen Dokumentation von Newton gefunden. Ein einziger Satz, der alles neu gerahmt hat.

i have a habit that's probably annoying to anyone watching me research i don't stop at the announcement. i go looking for what the announcement actually means technically and whether it holds up
when i saw Newton's github had a reference implementation for ERC-8004, i assumed this was Newton's own standard proposal. teams do this all the time — file an EIP, call it infrastructure, build the narrative
so i went and read the actual proposal. and it changed how i think about this 👀
this is the first thing worth knowing
ERC-8004 was proposed on August 13, 2025 by Marco De Rossi from MetaMask, Davide Crapis from the Ethereum Foundation, Jordan Ellis from Google, and Erik Reppel from Coinbase
that's not a Newton proposal. that's a cross-industry standard being developed by people from some of the most credible institutions in both crypto and traditional tech. the Ethereum Foundation's decentralized AI team has placed it in the 2026 roadmap. Base is confirmed as the next L2 deployment. by Q2 2026, reference implementations were live on Base Sepolia, Linea Sepolia, and Hedera Testnet
Newton didn't propose this standard. they built a reference implementation for it. that distinction matters a lot 🧐
what ERC-8004 actually does
the standard is trying to solve one specific problem: how do autonomous AI agents discover and interact with each other across organizational boundaries without a centralized gatekeeper deciding who's trustworthy
right now if an AI agent from one company wants to interact with an agent from another company — to trade, to delegate, to settle a task — there's no neutral standard for how that trust gets established. each platform builds its own solution. the result is a fragmented agent economy that can't scale
ERC-8004 proposes three trust models for agent verification:
reputation — onchain audit trail of how agents have performed historically
validation — crypto-economic staking or verification by third parties
TEE attestation — hardware-level proof that the agent ran correctly inside a trusted execution environment
and here's the critical line buried in the EIP itself: "while this ERC cryptographically ensures the registration file corresponds to the onchain agent, it cannot cryptographically guarantee that advertised capabilities are functional and non-malicious"
the standard can give an agent an identity. it cannot guarantee that agent behaves correctly. that gap is explicitly acknowledged by the authors 🙏
where Newton sits in this picture
Newton's reference implementation for ERC-8004 is specifically built around the third trust model — TEE attestation
that's not a coincidence. Newton's entire architecture is TEE-based. the policy checks run in hardware-isolated enclaves. the attestations are cryptographically signed. the results are verifiable onchain
the reputation and validation models in ERC-8004 tell you how an agent has behaved in the past and whether someone staked on it being legitimate. the TEE attestation model tells you the agent ran correctly right now, in real time, in hardware you can't tamper with
those are different categories of trust. the first two are probabilistic — past behavior and economic incentives. the third is cryptographic — hardware proof of correct execution
Newton is building the strongest trust model in the standard 👀
the part that reframes the whole thing
here's what i keep coming back to
ERC-8004 becoming an Ethereum standard means every protocol building AI agents will eventually implement some version of this trust layer. reputation, validation, TEE attestation — pick your level of trust depending on the stakes involved
for low stakes agents — content generators, scheduling tools, research bots — reputation and validation are probably enough
for agents moving real money, executing financial decisions, operating within compliance requirements — the TEE attestation model is the only one that actually holds up
and Newton's reference implementation is the only live TEE attestation implementation built specifically for ERC-8004 compliant agents
if the financial AI agent economy scales the way people think it will, the demand for the highest trust model in ERC-8004 is the demand for what Newton specifically built
ERC-8004 is still a draft standard. standards get adopted, modified, or abandoned. the fact that MetaMask, Ethereum Foundation, Google, and Coinbase are co-authoring it is the strongest possible signal it's serious — but serious proposals still fail sometimes
Newton building a reference implementation early is the right move regardless of outcome. if ERC-8004 gets adopted widely, Newton is already the infrastructure for its most rigorous trust model. if it gets modified, Newton's architecture adapts because the TEE attestation approach is sound independent of the specific standard
what i didn't expect when i started reading: this isn't Newton trying to own a standard. it's Newton positioning as the best possible implementation of someone else's standard, built by people from Ethereum Foundation, MetaMask, Coinbase, and Google
that's actually a stronger position than proposing it yourself 😅
$NEWT #Newt @NewtonProtocol

i have a habit when i research infrastructure protocols — i don't stop at what they claim to do. i try to find one specific cryptographic or architectural decision that tells me whether the people building it actually know what they're doing at a deep level
not the partnership list. not the roadmap. the specific technical choice that separates teams who understand the problem from teams who read about it
with Newton i found it buried in the privacy architecture documentation
Newton uses BLS signatures on the BN254 curve for operator attestations
that's a very specific choice and it's the right one. here's why it matters 👀
what BLS signatures actually are
most cryptographic signatures work like this: you get one signature per signer, and verifying multiple signatures requires verifying each one individually. that gets expensive fast when you have a network of operators all checking the same transaction
BLS signatures — Boneh-Lynn-Shacham — have a property that almost no other signature scheme has: aggregation. multiple operators can each sign the same message, and all those individual signatures can be mathematically combined into one single compact signature that proves all of them signed
one verification operation confirms the entire network agreed. not one per operator. one total
Ethereum's beacon chain uses BLS signatures for exactly this reason — hundreds of thousands of validators attest to blocks, and BLS aggregation is what makes verifying all those attestations computationally feasible onchain
Newton made the same choice for the same reason 🧐
the BN254 curve specifically
the curve matters as much as the signature scheme
BN254 is the pairing-friendly elliptic curve that EIP-197 added as a precompile to Ethereum in 2017. what that means practically: BLS signature verification on BN254 is dramatically cheaper onchain than it would be on other curves, because Ethereum has hardware-level support for the mathematical operations BN254 requires
Newton's operator attestations use BN254 specifically. which means every time Newton produces a policy attestation onchain, the verification cost is as low as it can possibly be on Ethereum
that's not an accident. teams that understand how this works choose BN254. teams that don't end up with expensive verification costs that limit how often the protocol can realistically run 🙏
how it works in Newton specifically
when a transaction hits Newton's enforcement layer, multiple operators each independently evaluate it against the policy. each operator produces their own BLS signature on the result
once enough operators agree — a supermajority of the operator network — their individual signatures get aggregated into one compact joint proof. that single aggregated signature is what gets submitted onchain as the attestation
from Newton's own docs: "once enough operators agree the policy is satisfied, their individual approvals are combined into one compact proof: a joint cryptographic signature that means 'a supermajority of the network checked this and reached the same answer'"
one proof. one verification. regardless of how many operators participated 👀
why this specific choice signals something
the practical consequence of using BLS on BN254 is that Newton's attestations are cheap to verify, compact enough to fit efficiently in transactions, and mathematically proven to aggregate correctly
but the signal i keep coming back to is what choosing BN254 specifically tells you about who built this
EIP-197 landed in 2017. the teams that deeply understood Ethereum's cryptographic precompiles and built around them are a small group. Magic Labs being in that group — deliberately choosing BN254 because of EIP-197 — is the kind of detail that only shows up when the people building it come from deep infrastructure background rather than building on top of what's already familiar
Rego for the policy layer. BLS on BN254 for the attestation layer
two choices buried in documentation that most people covering Newton have never read. both the right choices for the same reason — they're what engineers who understand the problem at a deep level would choose, not what a team trying to ship quickly would reach for
the honest observation
none of this matters if the protocol doesn't get used. a perfectly designed cryptographic attestation system that nobody plugs into is still just architecture
but when i'm trying to figure out whether a team actually understands what they're building, i look for decisions like this. technical choices that required knowing something most people don't know, made before anyone was watching
Newton has two of them. that's more than most 😅
$NEWT #Newt @NewtonProtocol

da ist eine Stelle in Newtons VaultKit-Ankündigung, die mich beim Lesen mitten drin stoppen ließ
nicht dieser Technik-Kram. nicht die Partnerliste. ein einziger konkreter Satz darüber, was Institutionen tatsächlich brauchen
„Die größten Asset Manager, die Tokenisierung prüfen, haben kein Diskretionsproblem. sie haben ein Problem mit nachweisbarer Kontrolle. sie können die Policy bereits formulieren. was ihnen gefehlt hat, ist eine Möglichkeit, sie On-Chain durchzusetzen – verifizierbar –, ohne ihre Compliance-Logik der Öffentlichkeit zu übergeben“
das ist eine ungewöhnlich präzise Behauptung. die meisten Projekte sagen: „Wir bauen für Institutionen.“ Newton hat etwas Konkreteres gesagt: Institutionen wissen bereits, wie man Compliance-Regeln schreibt. das fehlende Element ist nicht die Policy, sondern die Durchsetzungsebene, die nachweisen kann, dass die Policy ausgeführt wurde, ohne offenzulegen, was die Policy enthält