Newton Protocol

Newton Protocol (NEWT) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Newton Protocol — an AI/Other | Infra project about a policy engine / programmable compliance for transactions (stablecoins, RWAs, DeFi) and scenarios with autonomous AI agents. Token (symbol: NEWT).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

What it is: a “policy engine” protocol that embeds compliance/risk rules directly into the execution of onchain transactions (“guardrails at execution”).
Who it’s for: issuers of stablecoins/RWA projects, institutional integrators, DeFi strategies and developers of “agentic” automation.
Why onchain/token: the NEWT token is claimed as the gas token, staking/slashing for validator security and governance.
What you can actually touch (Tier‑1): the protocol documentation (overview + token utility) and the SDK reference (how to read from/write to policy contracts).

How it works (very briefly)

The user does: defines policies/rules (compliance/risk/business rules) and uses them when executing transactions/automation.
The system does: checks onchain actions for compliance with the policies (including with dynamic offchain information) and provides a “trust‑minimized” guarantee that the rules are followed.
The user gets: transactions/automation with built‑in guardrails (for stablecoins/RWAs/DeFi and agent‑triggered operations).
Where the blockchain is: policy/verification/permissions and execution — onchain (in the protocol); the NEWT token is currently an ERC‑20 on Ethereum.
Token role: staking/collateral/slashing, gas/fees and participation in governance.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Newton Protocol
Also known as (aliases)	Magic Newton Foundation; NEWT
Logo (logo)	../assets/90_newton-protocol_logo.svg
Token symbol (ticker)	NEWT
Category	AI/Other \| Infra
Primary chain (chain)	Ethereum
Type	EVM
Network status	mainnet
Consensus (consensus)	PoS (Ethereum)
Launch date (launch_date)	2025-01-17
Project status (status)	active
Token (standard)	ERC-20
Token contract	0xd0ec028a3d21533fdd200838f39c85b03679285d
Token model (token_type)	utility (payments + staking + governance)
Max supply	1 000 000 000 (fixed total supply)
Issuance	fixed supply (no inflation/deflation intended)
Tokenomics (tokenomics, brief)	NEWT: gas token + staking/validator rewards + collateral/slashing + governance; 8.5% of supply allocated to network rewards (per the staking guide)
Governance	stake‑weighted governance (tokenholders who stake; DAO later)
Admins/keys	upgradeable token contract (proxy); admin details — not extracted
Audit	—
Bug bounty	yes
Team (team)	Magic Newton Foundation
Funding (investors/funding)	—
AI component (ai_component)	policy protocol for AI agents
Use‑case (use_case)	programmable compliance for on-chain execution
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	ai_score 1 / onchain_score 3 / token_score 3 / evidence_score 3
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://newt.foundation/
Docs	https://docs.newt.foundation/
GitHub	https://github.com/newt-foundation
Releases / Changelog	https://blog.newt.foundation/
Whitepaper	https://blog.newt.foundation/the-litepaper/
Roadmap	—
Security advisories	https://github.com/newt-foundation/newton-token/security/advisories
Explorer	https://etherscan.io/token/0xD0eC028a3D21533Fdd200838F39c85B03679285D
X	https://twitter.com/newtfoundation
Discord	https://discord.com/invite/magicnewton
Telegram	—
Medium	—
Audit report(s)	—
Bug bounty	https://hackerone.com/magic-bbp/
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/newton-protocol
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/newton-protocol/

General project overview

In its Tier‑1 documentation, Newton Protocol frames the problem as follows: public blockchains have already become financial infrastructure (stablecoins/RWAs/DeFi), but institutional participants lack “trusted compliance frameworks”, while AI agents are becoming autonomous market participants — and guardrails are lagging behind. In response, Newton describes itself as a decentralized policy engine that “embeds compliance, risk, and business rules directly into transaction execution” and provides “trust‑minimized” guarantees that onchain actions comply with a predefined policy.

Important: in the DecAI context, this is primarily onchain infrastructure that claims applicability to the “agentic economy”, but does not demonstrate its own AI model/inference as a product.

Features/modules

Expressive policies (cross‑chain): “developer‑friendly guardrails that work seamlessly across chains”.
Dynamic offchain data integration: “real-time offchain data” and signals in policies.
Permission management: onchain permissions (zkPermissions, session keys) for agent automation.
Model registry / collateral (claimed): the Newton Model Registry and collateral/slashing for agent operators.

Typical scenarios

Scenario 1 (issuer/institution): defines compliance policies for a stablecoin/RWA → gets executable guardrails “at execution”.
Scenario 2 (DeFi strategy): uses policies for constraints/risk in automated strategies.
Scenario 3 (agent automation): an agent initiates transactions, and the protocol checks intent/permissions and applies the policies.

Getting started (wallet/network)

What you need: an EVM wallet (if interacting with the token/contracts) and RPC access (for the SDK/integrations).
Network/chain: the NEWT token is currently an ERC‑20 on Ethereum; the protocol claims a Keystore rollup architecture as its development goal.
Fees: Ethereum fees (and potentially fees of the target rollup in the future); the token docs say that fees may be subsidized in the early phase.

Architecture/tech (non‑AI)

Components: policy contracts (entrypoint/factory/policyId, etc., per the SDK), offchain data inputs into the policy (oracle‑like integrations), the NEWT token (ERC‑20 for now; a migration to rollup‑native is claimed).
Participant roles: policy developers; users/integrators; validators (dPoS); delegators; agent operators/model developers (Model Registry).
Where logic runs: verification/attestations and enforcement of policies — onchain; data/signals may be offchain but are integrated into the policy.
Dependencies: RPC/SDK (newton-policy-sdk in the docs), offchain data feeds (Tier‑1: real-time offchain data integration).

Token/economics (expanded, no forecasts)

Token utility (Tier‑1): staking for security (dPoS), gas/transaction fees, permission management (zkPermissions/session keys), collateral/slashing for agent services, governance.
Protocol necessity drivers: the token is embedded in gas/permissions and in the security layer (staking/validators/slashing), so a “token replacement” is not shown.
Who pays fees: users who execute transactions/permission‑management operations; also participants who stake/delegate.
Where fees go: per the token docs: validators receive rewards in NEWT from protocol‑level fees; part of the fee mechanics is described as an EIP‑1559 analog in the future.
Issuance/burn: fixed supply 1B; “no inflationary minting or deflationary mechanics intended post-launch”.
Security/incentive mechanisms: staking/delegation, rewards, slashing (once there are multiple validators); network rewards (the staking guide specifies 8.5% of total supply).
Distribution and vesting: see the docs (Distribution & Vesting) — not detailed within this card.
Treasury: governance includes voting on treasury disbursements (token utility).

Governance

Who makes decisions: NEWT holders who stake tokens (in token utility: governance “once sufficiently decentralized”).
How protocol parameters change: via stake‑weighted voting (linear, stake‑weighted) on parameters/treasury/priorities.
Where: the governance model is described in the docs; voting tools were not recorded in this card.
Keys/multisig: —.

Security and incidents

Audits: — (Etherscan shows “No Contract Security Audit Submitted” for the token contract).
Bug bounty: HackerOne program (see links_*).
Incidents: —.
Threat model: risks of complex policy logic (errors/bypasses), oracle/offchain data input risks, governance/upgrade risks (the token contract is a proxy; upgrades via governance are possible).

Project status and timeline

Current status: the NEWT token exists on Ethereum mainnet; the protocol is described in the docs/litepaper; some mechanics (Keystore rollup) are claimed as future architecture.
Key releases/milestones: deployment of the NEWT token (creation tx on Etherscan — 2025‑01‑17); publications on staking/SDK in the docs.
Roadmap: —.

Ecosystem/integrations

Integrations: SDK (newton-policy-sdk, viem), policy contracts; announcements of integrations with data oracles are published in the docs/blog.
Partners: — (partners were not recorded within this card).
Where it’s actually used: as a layer of programmable compliance/policy guardrails for transactions; specific production integrations require separate verification.

AI component of the project

What is real AI here? Tier‑1 describes applicability to “autonomous AI agents” and the “agentic economy”, but does not record an own AI model/inference as a product (rather a policy infrastructure for agents).
What is truly onchain? enforcement of policies “at execution”, onchain permissions/attestations (via policy contracts per the SDK) and the NEWT token (ERC‑20 for now).
Why is a token needed? gas/fees, staking/validator security + slashing/collateral and governance (stake‑weighted).
Red flags (based on the information found): AI‑washing (AI — as applicability, without an AI model), governance/upgrade risk (token contract proxy), oracle risk (offchain data inputs).

DecAI Fit component summary

DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	low	1
Onchain necessity	high	3
Token necessity	high	3
Evidence	Tier‑1 present	3

Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

AI_0 (decision): 1
Claim (one line): the protocol is positioned as a “policy protocol” for the era of AI agents (guardrails for autonomous AI agents).
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/overview/project-and-protocol ; https://newt.foundation/
Why sufficient / why not (one line): this is Tier‑1 AI context/intent/applicability, but without evidence of own AI models (AI_1..AI_4 remain 0).
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): the protocol has a described AI model/inference (what exactly the AI does as a product component).
Evidence: Tier‑1 — —.
Why sufficient / why not (one line): Tier‑1 describes a policy infrastructure, not an AI model/inference.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): there is a demo/guide specifically for the AI component (model/agent) of Newton.
Evidence: Tier‑1 — —.
Why sufficient / why not (one line): there is an SDK/guide for policy contracts, but this is not a demo of an AI model; we do not count AI_2.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — —.
Why sufficient / why not (one line): AI quality metrics/benchmarks are not claimed as verifiable artifacts.
Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

AI_4 (decision): 0
Claim (one line): there is a technical description/versions of Newton’s AI models.
Evidence: Tier‑1 — —.
Why sufficient / why not (one line): there is a technical description of the policy/SDK, but not of an AI model.
Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

OC_1 (decision): 1
Chain: Ethereum
Addresses/identifiers: the NEWT token (ERC‑20, proxy) 0xd0ec028a3d21533fdd200838f39c85b03679285d
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/token/characteristics-and-utility ; https://etherscan.io/token/0xD0eC028a3D21533Fdd200838F39c85B03679285D ; https://etherscan.io/tx/0xed0b9eb4b6cb9402f0456b20bdb0a05e300fd86734bad5392ffe45bd4fa6c1ce
Why sufficient / why not (one line): the docs record the address and the standard; Etherscan confirms the contract and the deployment timestamp.
Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

OC_2 (decision): 1
What useful logic is onchain: policy contracts and onchain permissions/attestations (evaluation requests) for policy enforcement and agent automation.
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/overview/project-and-protocol ; https://docs.newt.foundation/developers/reference/sdk-reference
Why sufficient / why not (one line): Tier‑1 describes enforcement “at execution” and provides SDK methods for reads/requests/tasks in policy contracts.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 1
“Replace the blockchain” test: without onchain there is no trust‑minimized guarantee that “every onchain action is within predefined policy”, and policies cannot be verifiably applied “at execution”.
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/overview/project-and-protocol ; https://newt.foundation/
Why sufficient / why not (one line): Tier‑1 directly motivates the protocol as a base enforcement layer in the execution of onchain transactions.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the project has a token, NEWT (ERC‑20 on Ethereum).
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/token/characteristics-and-utility ; https://etherscan.io/token/0xD0eC028a3D21533Fdd200838F39c85B03679285D
Why sufficient / why not (one line): the docs and the explorer confirm the token/address/total supply.
Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

TK_1 (decision): 1
Claim (one line): NEWT is claimed as the protocol’s native gas token and is needed for transaction execution and permission management.
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/token/characteristics-and-utility
Why sufficient / why not (one line): in token utility, the “Transaction Fees and Permission Management” section directly records payment for execution in NEWT.
Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

TK_2 (decision): 1
Claim (one line): staking/delegation and NEWT collateral for agent services + slashing (for misbehavior/validators).
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/token/characteristics-and-utility ; https://docs.newt.foundation/how-to-guides/newt-token-staking
Why sufficient / why not (one line): the docs describe staking for security, collateral and slashing conditions.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 1
Claim (one line): NEWT holders who stake will be able to participate in governance (treasury, parameters, priorities); the staking guide mentions governance voting rights.
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/token/characteristics-and-utility ; https://docs.newt.foundation/how-to-guides/newt-token-staking
Why sufficient / why not (one line): Tier‑1 explicitly describes the governance role and voting rights via staking.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): the token is embedded in the gas/permissions and security/gov layers; a “replacement with USDC/a subscription” is not shown as equivalent.
Evidence: Tier‑1 — https://docs.newt.foundation/protocol/token/characteristics-and-utility
Why sufficient / why not (one line): token utility describes gas/permissions/staking/DAO as the base mechanics.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://newt.foundation/	Positioning: a policy protocol for programmable compliance and the “agentic economy”; high‑level how it works (policies, offchain data, trust‑minimized guarantees).
Tier‑1	https://docs.newt.foundation/protocol/overview/project-and-protocol	Tier‑1 description of Newton as a decentralized policy engine that embeds compliance/risk rules into execution; use‑cases including autonomous AI agents.
Tier‑1	https://blog.newt.foundation/the-litepaper/	Litepaper (Tier‑1): the base specification/context of the protocol.
Tier‑1	https://docs.newt.foundation/protocol/token/characteristics-and-utility	Token utility: fixed supply 1B; gas/permissions; dPoS staking; Model Registry + collateral/slashing; governance.
Tier‑1	https://docs.newt.foundation/how-to-guides/newt-token-staking	NEWT staking: staking contract, rewards, cooldown, slashing; governance voting rights.
Tier‑1	https://docs.newt.foundation/developers/reference/sdk-reference	SDK reference: reads/requests/tasks for policy contracts and evaluation/attestations (onchain logic beyond the token).
Tier‑1	https://etherscan.io/token/0xD0eC028a3D21533Fdd200838F39c85B03679285D	Onchain fact of the NEWT token (ERC‑20, max total supply 1B).
Tier‑1	https://etherscan.io/tx/0xed0b9eb4b6cb9402f0456b20bdb0a05e300fd86734bad5392ffe45bd4fa6c1ce	Timestamp of the NEWT token creation (2025‑01‑17) — the token launch/creation date.