B3

• Name: B3
• URL: https://www.b3.fun/
• Category: consumer appchain ecosystem / gaming-and-payments infrastructure / multichain developer platform
• Tags: ethereum-ecosystem
• Summary: B3 is broader than a simple gaming Layer 3. Its official materials describe a Base-settled consumer ecosystem with horizontally scaling appchains, a developer stack for embedded accounts and player identity, a cross-chain payments and onramp product called AnySpend, data APIs, and a first-party portfolio of consumer applications. Keep this note on that protocol-and-product surface: B3OS workflow mechanics, appchain scaling, accounts, payments, and developer tooling. The named operator boundary above that stack now lives separately in npc-labs.
• What it does:
  • Operates a Base-connected Layer 3 / appchain ecosystem intended for games, apps, and enterprise use cases that need dedicated throughput and customized execution environments
  • Promotes horizontal scaling via purpose-built appchains while trying to preserve unified liquidity and a shared user experience across the broader B3 ecosystem
  • Provides developer-facing identity and account tooling through B3 Global Accounts, including social login, session keys, permissions, and cross-application user management
  • Provides AnySpend, a payments and onramp layer for cross-chain token conversion, checkout, deposits, and contract-call execution
  • Ships first-party SDKs, data APIs, and consumer applications, with the monorepo exposing how authentication, cross-chain operations, and gaming surfaces are packaged together
• Key claims:
  • Official docs describe B3 as Base’s layer 3 consumer ecosystem built for games, apps, and enterprises that need performance and support to scale
  • The protocol docs frame B3’s main architectural idea as horizontal scaling through specialized appchains with unified liquidity and user experience rather than simply making one chain faster
  • The Global Accounts docs show that B3 is also shipping embedded-account and identity infrastructure, not just chain throughput
  • AnySpend is positioned as B3’s crypto payments infrastructure, handling cross-chain routing, token conversion, checkout, deposit flows, and fiat onramps so users can pay with whatever assets they already hold
  • The homepage’s B3OS / Labs / Holdings framing and explicit revenue-accrual language around the token indicate a broader ecosystem-and-portfolio strategy beyond a pure protocol narrative
  • The public monorepo supports this broader reading by exposing SDK, authentication, cross-chain, and game-demo packages under one repository rather than a narrow chain-client codebase
• Whitepaper: No classic standalone B3 whitepaper or litepaper was found in this pass. The strongest current primary sources were the official site, docs corpus, and public monorepo; see ../whitepapers/b3-primary-sources-2026-04-27.md.
• Sources:
  • https://www.b3.fun/
  • https://docs.b3.fun/
  • https://docs.b3.fun/protocol/scaling
  • https://docs.b3.fun/ecosystem/introduction
  • https://docs.b3.fun/sdk/global-account/introduction
  • https://docs.b3.fun/anyspend/introduction
  • https://docs.b3.fun/protocol/b3-token
  • https://github.com/b3-fun
  • https://raw.githubusercontent.com/b3-fun/b3/main/README.md

Internal linkages

• Named operator boundary above the ecosystem stack: npc-labs.
• Useful adjacent chain-and-distribution contrast: base and coinbase.
• Useful adjacent multi-product integration shell: thirdweb.

Protocol / company boundary

• Keep this note on the reusable B3 stack itself: appchain scaling, B3OS workflow logic, Global Accounts, AnySpend, SDKs, data APIs, and the product surfaces builders or users directly integrate with.
• Use npc-labs for the company layer above that stack: the operator that packages B3OS, runs the Labs incubation arm, manages the Holdings layer, and decides which products or adjacent businesses become part of the default B3 loop.
• That split matters because how does B3's stack work? and who decides what gets incubated, promoted, and economically tied into the B3 ecosystem? are related but not identical questions.

Control surface

• At the project layer, the leverage sits in appchain architecture, workflow tooling, identity/account primitives, payment routing, SDK conventions, and the way B3 tries to unify those surfaces for builders.

• Do not flatten the company story back into this note: the Labs / Holdings packaging, portfolio choices, and broader distribution-and-capital-allocation shell now belong in npc-labs.

• Read B3 here as a consumer-onchain product and infrastructure stack, not as the full company boundary around it.

• Last reviewed: 2026-08-09 UTC