Tokenised custody. Every asset owned directly. Every holding verifiable.

Traditional custody has a transparency problem. When an investor holds assets through a platform or a managed fund, they typically own a unit in a pooled structure — not the underlying asset itself. The custodian holds the assets, the platform holds the record, and the investor holds a claim against both. Settlement takes days. Verification requires asking someone. And in a dispute, the chain of title is a matter of contractual interpretation, not mathematical proof.

Tokenised custody changes this. Each asset is purchased and held in institutional custody, then represented as a regulated digital token — individually owned by the client, not pooled with anyone else's holdings. Ownership, backing, and compliance are enforced by the token contract itself, and verifiable on-chain at any time.

When a client acquires a Nexfolio token, they are acquiring a direct, individual claim on a specific underlying asset — an ETF unit, a managed fund holding, or an equity — held in institutional custody on their behalf. There are no pooled units. There is no intermediary holding a unitised interest on behalf of a group.

The 1:1 backing between token and underlying asset is not self-reported by Nexfolio. It is designed to be verified continuously by an independent on-chain oracle, with demonstrations currently conducted in testnet environments. Every token in circulation is intended to correspond to an identified, held asset in custody. This is the 1:1 backing requirement under the incoming Digital Assets Framework established by the Corporations Amendment (Digital Assets Framework) Act 2026, once commenced.

ERC-3643 is the international standard for regulated security tokens — also known as T-REX. What it does is embed compliance into the token itself. Every wallet that holds or receives a Nexfolio token must have passed KYC and AML verification. The contract checks this on every transfer. A non-verified wallet cannot receive a token, regardless of instruction — not from the adviser, not from the platform, not from anyone.

This means compliance is not a process running alongside the token. It is the token. There is no separate compliance layer to bypass, no manual override, no exception handling. The transfer either executes — because both wallets are verified — or it does not.

Proof of Reserve is the mechanism designed to keep the 1:1 backing honest. An independent oracle is designed to monitor Nexfolio's custody holdings and publish an on-chain attestation that every token in circulation is matched by a held asset in institutional custody — with demonstrations currently conducted in testnet environments, not a periodic report issued by Nexfolio.

The intended result is that the backing of any Nexfolio token can be independently verified by any party — the client, their adviser, a regulator, or an auditor — without asking Nexfolio anything, as the platform progresses toward production readiness.

Nexfolio is being designed and built to align with the standards of a Tokenised Custody Platform (TCP) under the Corporations Amendment (Digital Assets Framework) Act 2026, once commenced. The three statutory requirements that define a TCP — factual control of the digital token (s761GB), 1:1 asset backing (s761GD), and express accountability for custodian agent actions (s761GE) — are being implemented in software and demonstrated on testnet ahead of the planned TCP MVP targeted for late 2026.

Nexfolio intends to apply for an Australian Financial Services Licence (AFSL) to operate as a TCP. The application is in preparation and targeted for lodgement in Q3 2026. Nexfolio is not yet licensed.