What is the difference between a native and a wrapped asset token?

A native token is issued directly by the issuer (or its transfer agent) on the chain, and is the asset in tokenized form. A wrapped token is issued by someone else against an asset they hold, whether a share in custody, a fund unit or another token locked in a contract, and is a claim on that holder. The native token's enforceable record is the issuer's register; the wrapper's is the wrapper issuer's books plus whatever record the underlying asset has.

Is a fund token that exists on several blockchains native or wrapped?

It can be either. If the transfer agent issues the fund's shares directly on each chain and treats every chain as part of the register, each version is native. If the fund issues on one chain and a bridge locks those tokens and mints copies elsewhere, the copies are wrapped and depend on the bridge. Franklin's FOBXX is recorded by its transfer agent on several chains (Stellar, Polygon, Arbitrum, Avalanche, Ethereum, Aptos, Base and Solana per its timeline); AltStreet's review noted that Franklin's contracts page listed no BENJI address for BNB Chain, which Franklin's timeline also names. Check the issuer's official list of contract addresses, chain by chain.

Why do wrapped tokens exist at all?

To bring an asset to a chain or a venue its issuer does not support. Custodial wrappers bring off-chain securities on-chain when the issuer has not tokenized them; bridge wrappers move a token from one chain to another for use in that chain's markets. Both add a party, and with it custody, contract and redemption risk.

Are wrapped tokens riskier?

They add risks native tokens do not have: the wrapper issuer's solvency and honesty, the custody of the wrapped asset, and, for bridged tokens, the bridge's smart contracts and validators. Bridge exploits have been among the largest losses in crypto, because the locked assets backing every wrapped copy sit in one place. A native token avoids those layers but keeps the issuer's own risks and its administrator powers.

How do I know whether the token I hold is native?

Compare its contract address with the address the issuer or transfer agent publishes for that chain, and read the token terms for who issued it. If the issuer of the token is not the issuer of the security, or the token was minted by a bridge contract, it is a wrapper. A token labeled with the fund's name on a chain the issuer does not list is, at best, someone else's wrapper.

Native vs Wrapped Tokens

Tokenized Real-World Assets

Definition

A native token is created directly on a blockchain by the asset's issuer or the issuer's agent, so the token itself is the asset's record: for a tokenized security, a transfer of the token is a transfer on the issuer's master securityholder file. A wrapped token is a token that stands for something held somewhere else: an asset in custody off-chain, a security held by an intermediary, or another token locked in a smart contract or a bridge on a different chain. Moving a wrapped token moves a claim on the holder of the wrapped thing, not the thing. The distinction matters for tokenized securities because it decides where the enforceable ownership record sits. With a native token issued by the issuer's transfer agent, the record is the issuer's own register (subject to the agent's correction powers). With a wrapper, the record of the underlying asset is somewhere else, kept by a custodian, a token issuer or a bridge contract, and the token holder depends on that party continuing to hold it and to honor redemption.

Why it matters

Most tokenized-asset failures that hurt investors were not failures of the asset; they were failures of a party between the investor and the asset. Native issuance removes those parties: when the issuer's transfer agent records shares directly on a chain, the token is the share. Wrapping adds them back: a custodian holding the asset, a contract holding a locked token, a bridge minting copies on another chain. SEC staff draw the same line for securities, between issuer-sponsored tokens, where 'a transfer of the crypto asset on the crypto network results in a transfer of the security on the master securityholder file', and third-party tokens, where holders 'may be exposed to risks with respect to the third party, such as bankruptcy, to which a holder of the underlying security would not necessarily be exposed' (January 28, 2026). As tokenized funds spread across chains, the practical version of the question is chain by chain: is the version I hold issued by the fund's transfer agent on this chain, or a copy made by someone else?

Common misconceptions

•The token's name and ticker do not tell you whether it is native. Anyone can deploy a contract with a fund's name; only the issuer's published address list is authoritative.
•Multi-chain does not mean wrapped. An issuer can issue natively on several chains if its transfer agent treats each as part of the register.
•A wrapper backed one-for-one is still a claim on the wrapper. If the custodian or bridge fails, is hacked or freezes redemptions, the backing does not help a holder who cannot reach it.
•Native is not the same as permissionless. Native tokenized securities usually carry allowlists, freeze functions and transfer-agent correction powers.
•Wrapping a security does not change whether it is a security. A wrapper of a tokenized fund share is itself likely a security, and offering it needs registration or an exemption.

Technical details

Native issuance: the chain as part of the register

Mechanism: the issuer or its transfer agent integrates the chain into the master securityholder file; on-chain balances, linked to off-chain identity records, are the holder records.

Variants: fully on-chain register, or an off-chain register that the token updates (SEC staff describe both as issuer-sponsored).

Controls: the transfer agent typically keeps freeze, burn, reissue and correction powers, and an allowlist of eligible wallets.

Examples from AltStreet's reviews: FOBXX shares recorded as BENJI tokens by Franklin's transfer agent; Superstate fund shares issued and recorded by Superstate Services LLC, an SEC-registered transfer agent; YLDS certificates recorded by Figure Equity Solutions.

Custodial wrappers: an off-chain asset held for token holders

Mechanism: a third party holds the asset (a share, a fund unit, a bar of gold) and issues tokens representing it.

Legal claim: a security entitlement or a beneficial interest if structured as custody; a debt claim if structured as the wrapper issuer's own instrument.

Added parties: the wrapper issuer, its custodian, and whoever attests that tokens outstanding equal assets held.

Redemption: back into the underlying asset (to a brokerage or custody account) or into cash, usually for onboarded holders above a minimum.

Bridge wrappers: a token copied to another chain

Lock-and-mint: the original token is locked in a contract on chain A and a wrapped copy is minted on chain B; burning the copy releases the original.

Burn-and-mint (issuer-run): the issuer burns on one chain and mints on another, keeping supply native on both; this is native issuance across chains rather than wrapping.

Risk: a lock-and-mint bridge concentrates the backing for every copy in one contract or validator set; if it is exploited or its keys compromised, the copies can become unbacked.

Diligence: for any chain, confirm whether the token is issuer-minted (native) or bridge-minted (wrapped), and whether the issuer recognizes the bridged version for redemption.

Where the enforceable record sits

Native token: the issuer's register, kept by its transfer agent; on a conflict between chain and off-chain records, the documents say which controls (often the transfer agent's records).

Custodial wrapper: the wrapper issuer's books for the token claim, and the custodian's books (or the issuer's register) for the underlying asset.

Bridge wrapper: the bridge contract for the wrapped copy, and the original chain's register for the locked token; the issuer may not recognize the wrapped copy at all.

Practical test: who will honor a redemption request from a holder of this exact token on this exact chain, and under what document?

Checklist before using a token on a new chain

Match the contract address to the issuer's or transfer agent's official list for that chain.

Read whether the issuer recognizes that chain's version for subscriptions, redemptions and distributions.

If wrapped, identify the wrapper issuer or bridge, its audits, its custody arrangement and its redemption terms.

Check allowlist rules: a native permissioned token will not move to an unapproved wallet, so a token that moves freely on a chain where the issuer requires allowlisting is not the issuer's.

Check distributions: income on a native fund token is paid by the fund on that chain; a wrapper may pass it through late, partially or not at all.

Frequently asked questions

What is the difference between a native and a wrapped asset token?: A native token is issued directly by the issuer (or its transfer agent) on the chain, and is the asset in tokenized form. A wrapped token is issued by someone else against an asset they hold, whether a share in custody, a fund unit or another token locked in a contract, and is a claim on that holder. The native token's enforceable record is the issuer's register; the wrapper's is the wrapper issuer's books plus whatever record the underlying asset has.
Is a fund token that exists on several blockchains native or wrapped?: It can be either. If the transfer agent issues the fund's shares directly on each chain and treats every chain as part of the register, each version is native. If the fund issues on one chain and a bridge locks those tokens and mints copies elsewhere, the copies are wrapped and depend on the bridge. Franklin's FOBXX is recorded by its transfer agent on several chains (Stellar, Polygon, Arbitrum, Avalanche, Ethereum, Aptos, Base and Solana per its timeline); AltStreet's review noted that Franklin's contracts page listed no BENJI address for BNB Chain, which Franklin's timeline also names. Check the issuer's official list of contract addresses, chain by chain.
Why do wrapped tokens exist at all?: To bring an asset to a chain or a venue its issuer does not support. Custodial wrappers bring off-chain securities on-chain when the issuer has not tokenized them; bridge wrappers move a token from one chain to another for use in that chain's markets. Both add a party, and with it custody, contract and redemption risk.
Are wrapped tokens riskier?: They add risks native tokens do not have: the wrapper issuer's solvency and honesty, the custody of the wrapped asset, and, for bridged tokens, the bridge's smart contracts and validators. Bridge exploits have been among the largest losses in crypto, because the locked assets backing every wrapped copy sit in one place. A native token avoids those layers but keeps the issuer's own risks and its administrator powers.
How do I know whether the token I hold is native?: Compare its contract address with the address the issuer or transfer agent publishes for that chain, and read the token terms for who issued it. If the issuer of the token is not the issuer of the security, or the token was minted by a bridge contract, it is a wrapper. A token labeled with the fund's name on a chain the issuer does not list is, at best, someone else's wrapper.