01
Compliance can't stop at issuance
Eligibility and jurisdiction checks that only run at mint don't govern the secondary transfers where exposure actually builds.
Solutions / RWAs
Regulated assets onchain. Compliance that travels with them.
Newton is the policy enforcement layer for tokenized assets: investor eligibility, jurisdiction, and transfer restrictions enforced on every movement, verified onchain, not just at issuance.
Why enforcement
Issuance is the easy part. Every transfer after is the risk.
A tokenized asset can change hands long after it's issued. The rules have to move with it, or they don't hold at all.
02
Off-chain restrictions don't travel
Rules kept in legal docs and spreadsheets can't follow an asset across wallets, protocols, and venues.
03
Auditors need proof, not assurances
Regulated issuers have to show each transfer was checked. A claim isn't evidence.
What Newton enforces
Compose the rules your asset already carries.
Enforced on every transfer before it settles, at issuance and on the secondary market. Start from templates built on named providers: Persona identity and accreditation, Chainalysis screening. Or compose your own in Rego, deterministic and reviewable.
Investor eligibility
Investor eligibility
Restrict holdings and transfers to addresses that meet identity and accreditation rules.
Jurisdiction
Jurisdiction
Enforce region-specific rules on who can hold or receive an asset.
Transfer restrictions
Transfer restrictions
Apply lock-ups, holding periods, and allowlist rules on every transfer.
Sanctions screening
Sanctions screening
Screen sender and recipient against sanctions and risk lists before a transfer settles.
How it works
From policy to proof, in four steps.
1. Write or select a policy
Start from an RWA policy template or write your own in Rego, using identity attestations, jurisdiction rules, and transfer restrictions.
RWA Compliance
What are onchain transfer restrictions?
Transfer restrictions are the rules that govern who can hold or receive a tokenized asset: eligibility, accreditation, jurisdiction, lock-ups, and allowlists. Newton enforces them on every transfer, at issuance and on the secondary market, and records each check as a verifiable onchain attestation, so the restrictions hold wherever the asset moves.
FAQ
Frequently asked questions
Yes. Policies are evaluated on every transfer, not only at mint. Eligibility and jurisdiction rules that stop at issuance don't govern the secondary transfers where exposure actually builds; Newton's checks travel with the asset.
Newton enforces policies at the transaction layer rather than inside the token, so it works with standard token contracts and can complement token-embedded compliance standards.
Newton enforces the controls: eligibility, jurisdiction, sanctions screening, and the ability to block a non-qualifying transfer, each attested onchain. Your counsel maps controls to obligations; the receipts give them per-transfer evidence.
A signed onchain receipt for every check, verifiable on the Newton Explorer, plus permanent onchain attestations of every policy version. Evidence, not assurances.
Go deeper
See enforcement in the real world.
Guide
Compliance that travels with the asset
How authorization stays attached to a tokenized asset as it moves.
Docs
RWA integration
Eligibility, jurisdiction, and transfer restrictions at the transaction layer.
Protocol
Whitepaper
How the AVS evaluates and signs each transaction before settlement.
Put your asset's rules onchain.
Book a call and our team will help you get your first RWA policy live.