Unibase (UB)

What Unibase is

Unibase is a set of modules that give AI agents persistent memory, verifiable identity, payments and decentralized storage, and UB is the token used in its settlement layer. Its documentation describes Unibase as "a high-performance decentralized AI memory layer" that equips agents with "long-term memory and cross-platform interoperability," and says the project is "building the foundation for the Open Agent Internet — a modular, verifiable, and composable AI agent ecosystem onchain" (source: Unibase documentation, read September 2026).

The documentation reports the system as "Live on BNBChain Mainnet," with SDKs, docs and an explorer released, integrations with MCP, ElizaOS, Virtuals and Swarms, and "1,000+ agent interactions recorded via Unibase SDK."

Unibase is not a blockchain of its own. It is infrastructure deployed across existing chains, with different modules settling on different networks.

For where to buy Unibase from your country or state, see the availability tables on this page and the venues listed at Exchanges.

How it works

Four modules do four jobs, and the documentation is explicit that "The four core modules are independent but composable — each owns one concern, and an agent uses whichever it needs."

Membase is the memory layer. The documentation describes wallet-rooted identity, where "the agent's Ethereum address is its identity; the key signs every write and unlocks its memory," and owned encrypted memory using "content-addressed storage plus on-device recall," with confidentiality enforced "via domain keys, not server ACLs." Agents coordinate through "signed, hash-chained logs on the Hub" with "no central referee, replayable by any third party."

AIP is the interoperability protocol. The documentation says it "extends A2A for agent communication, with ERC-8004 identity and x402 + ERC-8183 payment & settlement," and covers standardized message formats, signature-based authorization and a trust model using decentralized identities and zero-knowledge proofs.

Unibase Pay is the payment facilitator, described as "the x402 facilitator on BNB Chain," supporting verification, settlement, monitoring, payment gating and micropayments, with EIP-3009 and Permit2 for gasless transfers and a Privy custodial wallet for agents.

Unibase DA is the storage and data availability layer, and it is the most technically distinctive of the four. The documentation contrasts it with sampling-based systems directly: unlike designs "that verify availability off-chain through a committee or sampling, Unibase DA verifies stored data on-chain with zero-knowledge proofs under a fraud-proof (optimistic) model: writes are cheap and trustless, and the expensive verification runs only when someone disputes."

Its security assumption is the claim to check. The documentation names it the "Honest-One" model, where "a single honest participant is enough to force correctness, with no honest-majority assumption," and states that "The security of a stored blob inherits the security of the settlement chain itself, not a separate committee."

Data is content-addressed at three levels: a file, a piece of up to about 1 GB, and a replica, which is one erasure-coded shard. The documentation says each piece is coded with a Reed-Solomon (N, K) policy where "any K of the N" shards reconstruct the data, and lists the supported policies as 6/4, 14/7, 32/16 and 64/32. Each replica goes to a distinct storage node, so a piece survives losing up to N − K nodes, and "Every name is the hex of a cryptographic commitment, so identifiers are self-verifying."

Five node roles run the network. Stream nodes encode data and stage shards; storage nodes hold shards and submit availability proofs backed by stake; validators independently verify proofs and challenge fraud; a gateway provides read-only indexing; and a hub supplies lightweight app integrations. Misbehavior is addressed by on-chain slashing, with slash proceeds going to challengers.

Supply and tokenomics

The Unibase documentation read for this page does not publish a UB total supply, an allocation table, an emission schedule or a staking rate. The sitemap contains no tokenomics page. That absence is stated here rather than filled in from a secondary source.

What the documentation does say about UB is where it is used. The Membase settlement page describes metering usage off-chain and committing cumulative totals on-chain through an ERC-8183 settlement channel, "one transaction per flush, regardless of how many operations it covers," and notes that "The default token is configurable (commerce.default_token, e.g. UB)." UB is therefore the default unit of account for paying for memory infrastructure, not a hard-coded requirement.

One line in the settlement documentation names the trust boundary honestly: "The operator-run Server is the only non-decentralized piece (paying gas can't be decentralized without re-implementing the chain). It sees only signed metering deltas and wallet addresses — never your memory."

History

Unibase's premise is that the constraint on autonomous agents is not model quality but state. An agent that forgets between sessions, cannot prove who it is to another agent, and cannot pay for anything is limited regardless of how capable the model behind it is. The four modules map onto exactly those four gaps: memory, identity, payment and storage.

The choice to build on emerging standards rather than proprietary formats runs through the documentation, which cites ERC-8004 for agent identity, x402 and ERC-8183 for payment and settlement, and A2A for agent-to-agent communication. That is a bet that agent interoperability will settle on shared standards.

The DA design is the sharpest technical position. Most data-availability layers use sampling with an honest-majority assumption; Unibase moves verification on-chain, makes it optimistic so it costs nothing unless disputed, and reduces the trust assumption to a single honest party. The documentation is candid about maturity here: DA is live on Base Sepolia testnet, Base mainnet contracts are "In audit," and Ethereum mainnet is on the roadmap as a "security anchor."

The deployment split is deliberate, and the documentation spells it out: "DA anchors Ethereum + Base only. BSC is an application-layer chain (Pay/AIP); DA does not deploy on BSC."

Risks and what to watch

UB's token economics are not published in the documentation read for this page. There is no supply figure, no allocation, no emission schedule and no staking rate, and the settlement page describes the default token as configurable rather than required. That is a material gap for anyone assessing the token as distinct from the technology.

The throughput and capacity figures, 32 to 81 GB/s and EB+ capacity at million-node scale, are the project's own stated targets rather than measured production numbers, and should be read as design goals.

Module maturity varies, and the documentation maintains a separate status page for exactly that reason. Live on one network does not mean live on all, and the supported networks table mixes mainnet, testnet, in-audit and roadmap entries across the four modules.

Unibase Pay uses a Privy custodial wallet for agents, which the documentation describes as "Third-party wallet for agents." That introduces a custodial dependency in a stack otherwise built around wallet-rooted self-custody.

Adoption is the deciding variable for infrastructure of this kind. The documentation reports "1,000+ agent interactions recorded via Unibase SDK," which is a self-reported early figure.

Frequently asked questions

What does Unibase actually do?

It provides four modules for AI agents: Membase for wallet-owned encrypted memory, AIP for cross-agent identity and interoperability, Unibase Pay for x402 payments on BNB Chain, and Unibase DA for verifiable decentralized storage.

What is the "honest-one" security model?

Unibase DA's trust assumption. The documentation says "a single honest participant is enough to force correctness, with no honest-majority assumption," achieved by verifying stored data on-chain with zero-knowledge proofs under a fraud-proof model.

Which chains does Unibase run on?

Membase and Unibase Pay run on BNB Chain, AIP on BNB Chain and Base. Unibase DA is live on Base Sepolia testnet, with Base mainnet in audit and Ethereum mainnet on the roadmap; the documentation says DA does not deploy on BSC.

What is UB used for?

The Membase settlement documentation names UB as an example of the default token for settling metered memory usage through an ERC-8183 channel. The documentation describes that token as configurable rather than fixed.

Where can you buy Unibase?

Availability depends on your country or US state. See where to buy Unibase for the exchanges serving your jurisdiction, and Exchanges to compare fees, kyc requirements and supported payment methods.