One of the harder problems in on-chain policy enforcement is handling data that only exists off-chain in a normal web session — like a social media follower count — without just trusting whoever reports it. NewtonProtocol’s zkTLS approach tackles this with TLSNotary proofs: a browser-based flow generates a cryptographic proof of an actual TLS session (for example, a request to a Twitter/X API endpoint), and that proof gets stored and referenced by a content identifier. That proof, along with the policy inputs it supports, gets submitted as a Newton task alongside a transaction intent, and the policy evaluates it — checking, for instance, whether an account’s follower count clears a configured threshold — before deciding whether to approve the associated transaction. The proof retrieval process re-verifies that the bytes returned actually match the expected content identifier, so a compromised or misconfigured gateway can’t quietly swap in different data. It’s a small example of a bigger idea: almost any web-based fact can, in principle, become a verifiable input to an on-chain policy decision, not just data that already lives on a blockchain or comes from a traditional oracle. $NEWT #Newt @NewtonProtocol
🇳🇴 Norway 1 - 1 England 🏴 | 7 Minutes of Stoppage Time! 🔥
We are in the 90th minute, it's a dead heat at 1 - 1, and the fourth official has just indicated 7 minutes of added time! 😱⏱️
Seven minutes for ultimate drama. Will we see a cinematic late winner, or is this ending in a tie? ⚽💥 What is your final score prediction? ⏳ THE CLOCK IS TICKING: Drop your prediction right now before the final whistle blows! Who steals the glory in these dying seconds?
Newton runs as an Actively Validated Service on EigenLayer. Operators stake collateral, evaluate policies, and sign results with BLS signatures that get aggregated into a single verifiable proof in sub-seconds.
A centralized compliance server is a single point of failure with opaque logs. Newton spreads evaluation across distributed operators with attestations anyone can verify onchain — no vendor black box.
When a smart contract needs to check whether Newton approved a transaction, it has two validation paths to choose from, and the difference matters for anyone building on NewtonProtocol Standard validation checks an attestation that Newton’s aggregator has already submitted on-chain it’s cheaper in gas terms, but your contract has to wait for the aggregator to post that result first. Direct validation skips that wait: it verifies the BLS signatures and stake-weighted quorum on-chain itself, the moment a task is created, without waiting for the aggregator’s separate transaction. That immediacy costs more gas since the contract is doing real cryptographic verification work itself, but for time-sensitive operations — an agent executing a trade, a payment that needs to settle now — the latency savings are usually worth it. Both paths run the same underlying checks: does the policy ID match what the contract expects, does the sender match, is the chain ID correct, has the attestation expired or already been used. The choice is really about whether your use case can tolerate waiting a beat for the aggregator, or needs the transaction to resolve immediately. $NEWT #Newt @NewtonProtocol
Newton’s PolicyClient pattern lets you set hard limits on agent wallets max spend per transaction, an allowlist of contracts, even which specific functions the agent is allowed to call. Enforced onchain, not just “prompted.”
Token Transparency: Circulating vs. Distributed Supply
Most projects report a single “circulating supply” number, but Newton Protocol’s Foundation splits this into two more precise metrics. Circulating Supply is the portion of NEWT that is unlocked and designated for release into the market currently 21.5% at launch, covering community rewards, liquidity support, and the unlocked portions of the ecosystem funds and treasury. Not all of it is necessarily active immediately; some allocated tokens (like unclaimed airdrop amounts) can sit unused. Distributed Supply is the stricter number: it only counts NEWT that has actually been claimed, deployed, or put to use with no remaining transfer restrictions claimed airdrop rewards, validator staking rewards that have entered the claimable pool (roughly every seven days, continuing for about four years post-launch), deployed liquidity, and treasury or fund tokens that have been released from lockup. The Foundation commits to quarterly transparency reports covering both figures, plus disclosure of any NEWT sales or treasury activity a level of reporting granularity that’s worth knowing about if you’re trying to understand real token availability rather than just the headline unlock percentage. $NEWT #Newt @NewtonProtocol