Pieverse

Pieverse's 2025 design began with a real bookkeeping gap. A stablecoin transfer proves that value moved, but often omits who requested it, what service it paid for and which document an accountant should retain. x402b proposed API-driven, gas-sponsored settlement through pieUSD and attached invoices, receipts and programmable Time Checks.

That produces a verifiable record, not automatic compliance. A timestamp can fix content and order, while tax treatment still depends on jurisdiction, identities and the truth of the underlying transaction. Claims such as GAAP-, IFRS- or KYC-ready remain statements by Pieverse unless a regulator, auditor or applicable professional validates a particular workflow.

Pieverse Collective Limited was incorporated in the British Virgin Islands on 6 October 2025. The MiCAR paper names it as issuer and records first token activity on BNB Chain on 28 October and Ethereum on 29 October. Both networks use the address 0x0E63B9C287E32A05E6b9AB8ee8dF88A2760225A9 for the 18-decimal OFT representation.

The fixed billion divides into 15% investors, 27.6% community growth, 10% foundation reserve, 27.4% ecosystem and marketing, and 20% team and advisers. That places 72.4% outside the community-growth bucket. The prose mentions vesting for investors and team, but a complete numerical calendar, beneficiary address map and enforcement contracts were not published in the reviewed text.

The tokenomics page says holders can stake for yield and premium features, pay subscriptions or fees at a discount and vote on integrations, emissions and proposals. It describes a flywheel between product use and token demand. None of those statements defines a reward source, guaranteed rate, binding fee table or remedy.

The MiCAR filing takes the opposite legal position. It says PIEVERSE is not a utility token under its classification, has no inherent rights or intrinsic utility, and gives no financial, voting, ownership or contractual claim. It calls functionality limited and governance something that may arrive later. The conflict can be reconciled only by treating website features as revocable technical access, not holder-enforceable rights.

By September 2026 the homepage led with Purr-Fect Claw, a Skill Store, TEE-backed wallets and A2A commerce. The old payment layer survived inside the agent story: agents could discover work, settle over x402b and produce receipts. Yet the control boundary became clearer. Public OpenAPI and MCP material is read-only; agent provisioning, skill installation, wallet-policy changes and payments require a signed product session.

The purr system maps an instance identity and API credential to a wallet whose key is described as TEE-isolated. That is useful custody architecture, but access comes from platform credentials and authorization, not a PIEVERSE balance. The token therefore does not buy an autonomous agent, promise service availability or give a holder control of another agent's wallet.

Verified Ethereum code exposes an owner and multisig, configurable minters and whitelist entries, a transfer-allowed time, LayerZero peers and messaging settings. Constructor data initially put owner and multisig at 0x7a37945bF6c4a3A9454c4c808080Ba6063304590. These roles govern how the cross-chain representation operates even though ordinary balances can transfer after the gate opens.

The public record reviewed here does not name current signers, list all minters and peers, show a deployed DAO taking those powers, or tie allocation vesting to identified contracts. The MiCAR paper also says not every technology component can be guaranteed audited. The strongest current right of a holder is therefore technical custody and transfer under the contract's active settings; product access and governance remain promises administered elsewhere.