Plume set out to make tokenized assets feel like ordinary on-chain building blocks. PLUME’s history shows why the rail, the asset and the legal claim still have to be read separately.
PLUME entered the market as an Ethereum ERC-20 on 2025-01-21. The canonical proxy address is the first identity anchor; a ticker alone cannot distinguish it from copies or from its later native form.
Mainnet followed on 2025-06-05. On chain ID 98866, PLUME became gas, with a zero-address native representation and a separate WPLUME wrapper. A bridge connects the economies without making the contracts identical.
Plume describes itself as a full-stack RWA chain and some disclosure text says Layer 1. Its network, security and legal technical sections identify Arbitrum Orbit, AnyTrust data availability and settlement to Ethereum.
That is more than vocabulary. A sequencer, rollup contracts and a permissioned data committee sit between a user transaction and Ethereum finality. The public contract list also exposes proxy-admin, inbox, outbox and bridge surfaces.
The project’s own regulatory paper even contains both tendencies: business sections call Plume a Layer 1, while technical sections describe an Ethereum-settled Layer 2. The inconsistency survives because the terms answer different audiences, not because the underlying dependencies disappear.
Arc is meant to assemble asset tokens and transfer restrictions; Passport supplies smart-wallet identity; Nexus carries asset data. Together they target the operational friction around onboarding an off-chain claim.
The architecture should not be mistaken for universal legal enforcement. Arc documentation marks parts under development, and a smart contract cannot create title, custody or redemption where an issuer document does not.
For every RWA, the useful question changes from “is it on Plume?” to “who owes what, under which law, against which assets, through which contract?” PLUME answers none of those instrument-level questions.
Native PLUME can be delegated. The user guide gives a 21-day unstaking wait, but another unstake from the same validator before a pending request completes resets the timer. It documents a 0.5% Phase 1 commission, while additional revenue and allocation benefits remain explored or forthcoming.
The repository shows an EIP-2535 diamond and UUPS reward treasury. Admin roles can alter stake and cooldown settings, reward assets and validators; upgrade roles can change code. Current role holders were not established in the reviewed public pages.
The allocation begins at 10 billion: 59% for community, ecosystem and foundation, 21% for early backers and 20% for core contributors. Twenty percent was described as circulating at TGE, and Plume Ltd later disclosed retaining 4,666,554,520.
The modified MiCA paper says supply is fixed, with no continuing mint or burn mechanism. The Ethereum implementation disagrees at the capability level: privileged roles can mint without a hard cap, burn from accounts, pause and upgrade. A policy promise and an enforced invariant are different evidence.
The EU disclosure names Plume Ltd, incorporated in the BVI and owned by Plume Foundation SEZC, as issuer and offeror. It also says registration is not approval and denies deposit insurance or investor compensation.
The website terms place the interface under the Cayman foundation and disclaim fiduciary duties. Interface access, token issuance and a third-party RWA offering can therefore involve different counterparties and laws.
PLUME offers network utility, possible governance participation and staking economics. It does not confer equity in those entities or a redemption claim on tokenized assets. The biography remains a map of boundaries rather than a shortcut from “real world” to ownership.
Plume Ltd was registered in the British Virgin Islands.
The legal disclosure dates the PLUME token launch.
The MiCA chronology records the start of admission to trading.
Plume opened mainnet and described bridging Ethereum PLUME into native gas.
The website terms identify Plume Foundation SEZC as interface provider.
The modified white paper records notification to the Dutch AFM.
The issuer published its revised EU disclosure without claiming regulatory approval.
Last evidence review: 2026-09-05
PLUME is the native gas and staking asset of Plume mainnet, chain ID 98866. The same economic unit also appears as an upgradeable ERC-20 on Ethereum at 0x4C1746A800D224393fE2470C70A35717eD4eA5F1 and as WPLUME on Plume at 0xEa237441c92CAe6FC17Caaf9a7acB3f953be4bd1. These addresses prevent namesakes and bridge representations from being mixed.
Plume sells a chain and application stack for tokenized real-world assets. PLUME pays execution fees and may be delegated to validators, but it is not a claim on the buildings, private credit or funds represented by other tokens on that network.
Tokenizing an asset does not automatically join its legal ownership, data, compliance, custody and settlement. Plume tries to package those missing rails through Arc for issuance, Passport for accounts and Nexus for data, while supplying an EVM environment for applications.
The hard question is where control remains. Official materials alternate between L1 branding and an Arbitrum Orbit AnyTrust rollup that settles to Ethereum. Token disclosures say fixed supply, while deployed code retains roles that can mint, burn from an address, pause transfers and replace the implementation.
Transactions spend native PLUME as gas, and holders can delegate it to validators. The portal guide describes a 21-day unstaking period: if another unstake from the same validator is requested before an in-progress request completes, the timer resets. It also states a 0.5% commission in Phase 1. The staking repository adds a more complicated control map: diamond facets, an upgradeable reward treasury and admin, validator, upgrader and timelock roles.
Ethereum users bridge the ERC-20 into the Plume environment through supported providers. Native PLUME is represented by the zero address in EVM interfaces, while WPLUME is the transferable wrapped contract. Rollup liveness also depends on a sequencer, Ethereum contracts and a permissioned AnyTrust data-availability committee.
Arc can assemble compliant token contracts and restrictions, but its documentation still labels portions under development. Each issued RWA therefore needs its own contract, issuer, offering terms, custody and redemption review; PLUME ownership supplies none of those rights by itself.
The economic asset across native Plume gas, its WPLUME wrapper and the Ethereum ERC-20 at 0x4C1746A800D224393fE2470C70A35717eD4eA5F1. Each representation and bridge route has separate contract risk.
Current branding uses RWA chain and sometimes L1. Technical, security and legal materials describe an Arbitrum Orbit AnyTrust rollup settling to Ethereum, so this dossier records the conflict.
The legal paper says fixed supply and no ongoing minting. The live implementation nevertheless exposes role-gated minting without a code cap, plus upgrade authority. Both facts matter.
The portal guide states a 21-day unstaking period. If you unstake again from the same validator before an in-progress request is completed, the timer resets; the original request therefore does not guarantee a fixed withdrawal date. Actual validator, slashing, commission and upgrade outcomes also depend on the staking contracts and privileged roles.
No. Rights in a security, fund, vault or invoice token come from that instrument’s issuer, contract and legal documents, not from holding the chain gas token.
The MiCA paper names BVI-incorporated Plume Ltd as issuer and offeror. Website terms name Cayman-based Plume Foundation SEZC for the interface; those are different legal layers.
Choose a tracking site for Plume:
