Read the protocol like an engineer.
$NPKN is built as an Ethereum-hub, multi-spoke security token : ERC-3643 on the canonical hub, Base for retail reach, XRPL for institutional rails, Chainlink for the NAV oracle and cross-chain transport. This room is where the protocol opens up as it ships.
What it's actually built on.
Two layers, two right answers. The $NPKN token issues canonically on Ethereum. A credibility decision, because that is where tokenized securities, custody, and compliance tooling already live. The future RSX settlement layer is designed as a permissioned Avalanche L1. A privacy decision, because per-company revenue data belongs on a ledger whose validators owe legal duties to see it.
EthereumCanonical hub · L1 settlement
SolidityContract language
OpenZeppelinAudited primitives
ChainlinkNAV oracle · proof feedsChainlink CCIPCross-chain transport
BaseRetail spoke · Coinbase L2
XRPLInstitutional spokeThe Engine, as code.
Seven contracts carry the whole covenant. Each one exists to make a promise unbreakable rather than merely stated.
| Contract | What it does |
|---|---|
| NPKN Token | ERC-3643 permissioned security token on the Ethereum hub. The on-chain form of the registered common share. Identity registry + compliance module enforce who may hold and transfer. |
| Identity & Compliance Registry | On-chain allowlist bound to off-chain KYC/eligibility. Transfers that would break securities law revert at the contract layer, not in a terms-of-service PDF. |
| NAV Oracle Consumer | Reads the Chainlink feed publishing attested NAV per token each quarter, with the signed attestation report hashed alongside it. The Engine's formulas key off this number and nothing else. |
| Engine: Buyback & Cancel | Leg A of the capital-return covenant: pre-committed formula, independent execution agent, TWAP execution, published wallet. Every burn mirrors a legally real share cancellation. |
| Engine: Tender Module | Leg B: quarterly Dutch-auction self-tenders priced against attested NAV, plus opt-in stablecoin distributions. Never paid in newly emitted NPKN. |
| Treasury Issuance Guard | Treasury shares can only issue above last-attested NAV per share. Accretion is enforced by code: dilution below NAV is not a governance vote away; it is unrepresentable. |
| CCIP Bridge Adapters | Lock-and-mint transport between the Ethereum hub and the Base / XRPL spokes. Compliance travels with the token: spoke balances obey the same identity registry. |
CONTRACT CODE IS NOT YET PUBLIC. AUDITS (OMNISCIA) AND PUBLICATION PRECEDE TGE, NOTHING GOES LIVE UNAUDITED, AND NOTHING TRADES BEFORE THE FOUR GATES PASS.
What you can inspect today.
The room grows as the protocol ships: contracts, audit reports, testnet addresses, and the oracle spec will land here as each gate passes. Here's what's already public.
Building on tokenized equity, compliance rails, or the RSX? Talk to us: m@npkn.com
The spec is the white paper.
Section 7 is written to be implemented from, not marketed with. Read it the way you'd read an RFC.