ALT A radial BitDance Labs thesis map places User First at the center of six capability areas: Wallets, Payments, Assets, Liquidity, APIs, and Agents. The headline reads Make Bitcoin Native Usable, with people and agents identified as the users and the work marked Building.

ALT A dark editorial BitDance Labs poster presents Status Clarity Builds Trust beside three large status signals: Live for publicly verifiable availability, Building for work in progress without an availability claim, and Research for exploration without a roadmap promise. The closing statement says status should be as clear as ambition.

ALT An open developer research question asks which Bitcoin-native primitive would save builders the most time. Four equal discussion prompts show Wallet APIs, Lightning Payments, Taproot Assets Data, and Agent Payment Tools, while inviting other answers.

ALT A Research-status developer experience checklist highlights Stable APIs and predictable contracts as the foundation of developer confidence. Four supporting requirements—Explicit Permissions, Useful Errors, Testable Flows, and Complete Documentation—are presented with equal secondary weight.

ALT A four-product BitDance matrix shows BitPocket Wallet as Public and BitBond.ai, NAKAFi, and bitUSD as Building. Their roles are wallet access, agent payments, Bitcoin-native liquidity and BTCFi, and stable value for apps and agents. All four sit above a shared foundation of Bitcoin Mainnet, Lightning Network, and Taproot Assets, while human and AI agent users are identified as user groups rather than protocol layers.

ALT A Building-status bitUSD architecture diagram shows an issuance rail as only one input into six separate design boundaries: Collateral, Peg Logic, Liquidation, Redemption, Liquidity, and Risk Controls. The modules contain no live parameters or availability claims.

ALT A shared verified Bitcoin-native data layer connects two equal developer tools: the human-readable BitDance LN/TA Explorer for inspecting what happened, and the machine-readable BitDance Labs Open API for software integration. Both lead into a platform for inspecting, integrating, and building.

ALT A Building-status BitBond.ai agent payment diagram places Agent Payment at the center, connected to five equal financial guardrails: Budget and spend limits, Permission and allowed actions, Credential and proof of access, Receipt and payment record, and Audit and policy trace.

ALT An open research question asks what Bitcoin-native financial products should improve first, with four equal discussion prompts: simpler collateral UX, clearer liquidation risk, faster payments, and better wallet integration.

ALT A six-step Taproot Assets support loop connects Identify, Verify, Store Proof, Transfer, Back Up, and Recover around a center statement that full support goes beyond balance display.

ALT A BitPocket Wallet payment intent branches to three distinct selectable rails—Bitcoin Mainnet for settlement, Lightning for fast payments, and Taproot Assets for Bitcoin-anchored assets—then produces a clear receipt with the selected rail visible.

ALT A Bitcoin wallet transaction diagram selects two UTXOs as inputs, creates a recipient output and a change output, and shows that the user-facing wallet preserves visibility into amount, fee, and confirmation.

ALT A seven-layer BitDance Labs productization stack rises from Settlement through Channels, Assets, Data, APIs, and Wallets to an orange-highlighted User Outcome, showing how protocol capability becomes user value.

ALT A Research-status Lab Notes question asks what must be controlled before autonomous payments for a paid MCP service, offering spend limits, permission scopes, receipts, refunds, or something else.

ALT A Designing-status bitUSD card sits at the center of four connected agent workflow use cases: paid MCP tool calls, machine-readable data, metered compute, and programmable services.

ALT A Building-status flow connects an AI Agent to highlighted BitBond.ai policy and orchestration, then to L402 plus Lightning and MCP or agent-to-agent destinations, with separate Agent-to-MCP and Agent-to-Agent paths.

ALT A four-part BitDance Labs Open API diagram connects the application layer, a permission boundary, highlighted Open API primitives for data, payments, and wallet actions, and shared Bitcoin-native infrastructure.

ALT A five-step BitPocket self-custody responsibility flow lists Own, Sign, Back Up, Recover, and Understand Failure, with the first key-ownership step highlighted in orange.