"Not your keys, not your coins." Yes. But not enough.
You hold the private key. You self-custody. You don’t trust a centralized exchange. You do everything right according to the Web3 philosophy.
But when a protocol you interact with gets exploited, your key is still safe—but your assets aren’t.
Because Web3 solves the problem of who holds the keys—but it hasn’t solved the problem of authorization: who decides whether this transaction is allowed to happen?
@NewtonProtocol For the first time, they put the answer in before the funds move. They fill that gap by setting up authorization checks before funds transfer (pre-settlement enforcement).
Mainnet Beta checks every transaction through four main layers:
👉 Compliance (regulatory compliance, sanctions, jurisdiction).
👉 Identity (identity verification, KYC/credentials).
👉 Security (approved payees, spending caps, prompt injection defense for agents).
👉 Risk (leverage limits, concentration, oracle health, depeg, counterparty risk...).
All checks produce an onchain signed receipt (publicly verifiable proof).
They don’t change the UX much because users still sign the transaction themselves, but Newton AVS #Newt blocks it if it violates policy.
Newton doesn’t compete directly with wallets or custody solutions (like Magic Labs, which they partner with).
Instead, they add a policy & authorization layer between intent and execution. This is a smart direction because:
⭐ Self-custody is becoming mainstream.
⭐ Agentic AI & automation is booming and needs strong guardrails.
⭐ Institutional capital demands verifiable compliance.
Newton repositions itself from “a protocol compliance” to the next logical step in the Web3 philosophy of “Not your keys” into “Not your unauthorized transaction”.
It perfectly matches their real product (VaultKit + policy engine live on mainnet beta $NEWT
You hold the private key. You self-custody. You don’t trust a centralized exchange. You do everything right according to the Web3 philosophy.
But when a protocol you interact with gets exploited, your key is still safe—but your assets aren’t.
Because Web3 solves the problem of who holds the keys—but it hasn’t solved the problem of authorization: who decides whether this transaction is allowed to happen?
@NewtonProtocol For the first time, they put the answer in before the funds move. They fill that gap by setting up authorization checks before funds transfer (pre-settlement enforcement).
Mainnet Beta checks every transaction through four main layers:
👉 Compliance (regulatory compliance, sanctions, jurisdiction).
👉 Identity (identity verification, KYC/credentials).
👉 Security (approved payees, spending caps, prompt injection defense for agents).
👉 Risk (leverage limits, concentration, oracle health, depeg, counterparty risk...).
All checks produce an onchain signed receipt (publicly verifiable proof).
They don’t change the UX much because users still sign the transaction themselves, but Newton AVS #Newt blocks it if it violates policy.
Newton doesn’t compete directly with wallets or custody solutions (like Magic Labs, which they partner with).
Instead, they add a policy & authorization layer between intent and execution. This is a smart direction because:
⭐ Self-custody is becoming mainstream.
⭐ Agentic AI & automation is booming and needs strong guardrails.
⭐ Institutional capital demands verifiable compliance.
Newton repositions itself from “a protocol compliance” to the next logical step in the Web3 philosophy of “Not your keys” into “Not your unauthorized transaction”.
It perfectly matches their real product (VaultKit + policy engine live on mainnet beta $NEWT