Unibase

Unibase begins with an ordinary frustration. A useful conversation in ChatGPT, Claude or Gemini rarely becomes durable context elsewhere. Its Memory extension turns that gap into a product: capture chats and pages, organize them locally, encrypt them in the browser and optionally sync ciphertext. The Chrome Web Store listing proves that software shipped; it does not prove the size or permanence of the network behind it.

The privacy promise has layers. Official architecture says a wallet-derived key stays on the device and the Hub sees encrypted blobs. Yet users still encounter extension code, Privy sign-in, a public Hub, metadata and optional server-managed scopes. 'Encrypted memory' is a testable design claim, while 'only you can ever read it' depends on implementation, key handling and every integration in the path.

Membase publishes more than a landing page. Its SDK models an agent as a wallet, signs writes, addresses values by content and uses domain keys to share selected memory. AIP publishes SDKs for agents to register, discover and call one another; its public health endpoint was responding at this review. These are concrete developer surfaces.

They are not the same thing as a permissionless backend. The default hot Hub has operator-managed retention, and an operator-run server settles metered usage. The documented domain model also warns that removing a member does not rotate a key already received. Decentralized identity can coexist with hosted availability and operational control.

Unibase Pay adds another deliberate intermediary. Its x402 facilitator supports several EVM networks and the consumer flow uses Privy-based wallets. That can lower friction for an agent payment, but it means 'agents transact autonomously' includes a facilitator, wallet provider, supported-token policy and live API.

The DA design is technically specific. A file is split, Reed–Solomon encoded into shards and assigned to storage nodes. Validators recheck optimistic proofs and can challenge a missing or false proof; an on-chain ZK process resolves the dispute, slashes a failed node and rewards the challenger. Stream, Storage, Validator, Gateway and Hub roles divide the work.

Deployment is narrower than the design. Current status places DA on Base Sepolia, warns that testnet state may reset, labels Base mainnet contracts in audit and leaves Ethereum on the roadmap. The website's 32–81 GB/s, exabyte capacity and million-node scale therefore describe a target or project-reported benchmark. They cannot yet be read as an independently observed production network.

UB reached public markets on 12 September 2025. Its verified Ethereum contract is unusually simple: the constructor minted 10 billion tokens, holders can transfer or burn them, and there is no owner mint, pause, blacklist or upgrade function. That fixes the canonical token logic more firmly than the surrounding product roadmap.

Cross-chain UB adds power elsewhere. The Ethereum OFTAdapter locks and releases the fixed token; BSC and Base OFTs burn and mint as messages move supply. Their owners can choose peers, delegates, enforced options and inspectors. Those settings define which remote contract is trusted to justify new representation. They cannot casually call a mint function on the fixed Ethereum token, but a bad peer map can still break bridge accounting.

The published 10-billion allocation reserves 20% for Treasury and 18% for Team and Advisors, with another 10% for Ecosystem and 10% for Marketing. The table supplies initial lockup and gradual-release terms, yet cites a third-party unlock page and uses ambiguous token-generation-event (TGE) percentages for categories called fully unlocked. CoinYQ did not identify the corresponding wallets or enforceable spending controls in the materials reviewed.

The whitepaper gives UB four jobs: protocol fees, agent staking, knowledge mining and locking into veUB for governance. DA documentation adds stake-backed nodes, slashing, rewards, Timelock governance and a guardian. Together they describe how the eventual economy could connect storage work to rule-setting.

The materials reviewed did not establish that this handoff was complete. CoinYQ did not identify a veUB deployment, current governance portal, executed token-holder proposal or address book for the Timelock and guardian. The official text describes a gradual future transition to a DAO. Those review limits prevent a claim that buying UB currently gives its holder control over Unibase.

The reviewed official site, documentation and GitHub materials did not identify the founders, executives or token-issuing legal entity. Code and addresses remain evidence, but CoinYQ could not link bridge-control addresses or roadmap commitments to named accountable parties. That does not establish that no such people, entity or agreements exist. The shipped memory products are clearer in this record than the identity and authority of those managing the wider economy.