# B3 Docs — Full Documentation > B3OS, protocol, product, and developer documentation powered by HolyDocs. ## AI-Optimized Docs Source: https://docs.b3.fun/ai-optimized Contextual Menu Integration Every page in our documentation includes a contextual menu that provides one-click access to AI tools. Look for the menu icon on any page to access these features: Copies the current page as optimized Markdown that you can paste directly into any AI tool as context. Opens the current page in Markdown format, perfect for understanding the raw structure or copying specific sections. Creates a new ChatGPT conversation with the current page already loaded as context. Starts a Claude conversation with the documentation page pre-loaded for immediate assistance. Opens Perplexity with the current page as context for research and fact-checking. Provides Model Context Protocol (MCP) server URLs for advanced AI tool integrations. Direct integration with Cursor and VSCode through MCP for seamless coding assistance. Automatic LLM Indexing Our documentation automatically generates and maintains industry-standard files that help AI tools understand and index our content: llms.txt - Automatic Generation: Available at /llms.txt - Structured Content: Lists all pages with descriptions for efficient AI navigation - Always Up-to-Date: Automatically updated when content changes - Zero Maintenance: No manual updates required llms-full.txt - Complete Context: Available at /llms-full.txt - Single File: Combines entire documentation into one file - AI-Ready Format: Optimized for use as context in AI conversations - Comprehensive: Includes all content from across the documentation How to Use These Features For Quick Questions 1. Navigate to any relevant documentation page 2. Click the contextual menu icon 3. Select "Open in ChatGPT" or "Open in Claude" 4. Ask your question - the AI already has the page context For Code Development 1. Open your preferred code editor (Cursor or VSCode) 2. Use the MCP integration from our contextual menu 3. Access B3 documentation directly within your coding environment 4. Get contextual help while writing code For Deep Research 1. Copy the relevant page using "Copy Page" feature 2. Paste into your preferred AI tool 3. Combine with additional context or questions 4. Get comprehensive answers with full documentation context AI-Optimized Content Structure Our documentation is structured to work exceptionally well with AI tools: Clear Hierarchies - Logical organization that AI tools can easily parse - Consistent formatting across all pages - Descriptive headings that provide context Rich Metadata - Comprehensive titles and descriptions - Structured frontmatter for better AI understanding - Semantic markup that enhances AI comprehension Code Examples - Complete, runnable examples that AI can explain and modify - Well-commented code for better AI interpretation - Multiple implementation approaches for different use cases Benefits for Developers Get instant access to relevant documentation within your AI conversation, eliminating the need to switch between tools and manually copy content. AI tools receive properly formatted, comprehensive context about B3 features, leading to more accurate and helpful responses. Direct integration with development tools like Cursor and VSCode means you can get help without leaving your coding environment. Our AI-optimized files are automatically updated, ensuring AI tools always have access to the latest information. Example Use Cases Smart Contract Development Integration Planning Debugging and Troubleshooting Technical Implementation Our AI optimization is powered by: - Mintlify's AI features: Built-in contextual menu and LLM file generation - Structured content: Consistent markdown formatting optimized for AI parsing - Model Context Protocol (MCP): Standard for AI tool integration - Automatic updates: CI/CD pipeline ensures AI files stay current Get Started Ready to leverage these AI features? Here's how: 1. Browse to any page in our documentation 2. Look for the contextual menu icon (usually in the top-right area) 3. Try copying a page or opening it in your favorite AI tool 4. Experience the enhanced development workflow The AI optimization features are available on every page of our documentation and require no setup - they're ready to use immediately. --- These AI features are designed to enhance your development experience with B3. They work best when combined with a clear understanding of your specific use case and goals. --- ## ArenaKit Introduction Source: https://docs.b3.fun/arenakit/introduction What is ArenaKit? More documentation is coming soon. --- ## B3AR Introduction Source: https://docs.b3.fun/b3ar/introduction What is B3AR? More documentation is coming soon. --- ## Bonding Phase Source: https://docs.b3.fun/bondkit/concepts/bonding-phase What is the Bonding Phase? The bonding phase is the initial trading period where tokens are bought and sold directly from a smart contract using an algorithmic pricing curve. Think of it as a decentralized pre-sale with automatic market making. How Bonding Works The Bonding Curve Mechanism During bonding, the contract acts as the sole market maker: 1. No Order Book: Prices determined algorithmically 2. Instant Liquidity: Always able to buy or sell 3. Path Independence: Price depends only on supply, not history 4. Automatic Pricing: No manual price setting needed Trading Operations Buying Tokens Process Flow: 1. User sends trading token (B3/ETH) to contract 2. Contract calculates tokens based on curve 3. 5% fee deducted and sent to recipient 4. Tokens minted and sent to buyer 5. Curve state updated Code Example: | Parameter | Type | Description | |-----------|------|-------------| | | uint256 | Minimum tokens to receive (slippage protection) | | | string/uint256 | Amount of trading token to spend | Important Notes: - Set to protect against front-running - Use 0 for only in low-activity periods - Transaction reverts if slippage exceeds tolerance Target Overflow: - If purchase would exceed target, excess is refunded - Example: Target is 10 trading tokens, raised is 9.5 tokens - User sends 1 token → 0.5 tokens used, 0.5 tokens refunded Insufficient Gas: - Recommended gas limit: 200,000 - Complex calculations may require more Zero Amount: - Transactions with 0 trading tokens will revert Selling Tokens Process Flow: 1. User approves token spending 2. User calls sell with token amount 3. Contract calculates trading token amount based on curve 4. 5% fee deducted from proceeds 5. Trading token sent to seller, tokens burned 6. Curve state updated (price decreases) Code Example: | Parameter | Type | Description | |-----------|------|-------------| | | uint256 | Amount of tokens to sell | | | uint256 | Minimum trading token to receive (slippage protection) | Important Notes: - Requires token approval before selling - Price impact can be significant for large sells - Cannot sell more than circulating supply Understanding Sell Impact: Selling reduces the curve's raised amount, causing price to drop: | Sell Size | Price Impact | Recovery Needed | |-----------|--------------|-----------------| | 1% of supply | ~1-2% | Small | | 5% of supply | ~5-10% | Moderate | | 10% of supply | ~15-25% | Significant | | 20% of supply | ~30-50% | Major | Actual impact depends on aggressiveness factor Fee Structure How Fees Work On a 1 trading token purchase: - 0.95 trading tokens go to bonding curve - 0.05 trading tokens go to fee recipient - Tokens calculated on 0.95 trading token value Example: On selling for 1 trading token value: - User receives 0.95 trading tokens - 0.05 trading tokens go to fee recipient - Curve reduced by full 1 trading token Example: Where fees go: - 100% to designated address - Can be project treasury, developer, or DAO - Set at token creation, cannot be changed Claiming fees: - Automatic - no claiming needed - Sent directly on each trade - No accumulation in contract Fee Economics | Daily Volume | Fee Income | Monthly Income | |-------------|------------|----------------| | 10 trading tokens | 0.5 trading tokens | ~15 trading tokens | | 50 trading tokens | 2.5 trading tokens | ~75 trading tokens | | 100 trading tokens | 5 trading tokens | ~150 trading tokens | | 500 trading tokens | 25 trading tokens | ~750 trading tokens | Target Mechanics Understanding the Target The target is the amount of trading token that must be accumulated before migration: Target Purpose: - Ensures sufficient liquidity for Uniswap v4 - Creates a clear goal for the community - Prevents premature migration - Builds momentum during bonding Approaching the Target Overflow Handling When a purchase would exceed the target: 1. Partial Fill: Only the amount needed is accepted 2. Automatic Refund: Excess returned in same transaction 3. Fair Completion: No one can overpay at the end Example Scenario: Events & Monitoring Contract Events Listening in SDK: Listening in SDK: Real-Time Monitoring Bonding Phase Strategies For Token Creators - Start with lower aggressiveness (30-50) - Set achievable targets - Engage community early - Provide clear roadmap - Seed initial liquidity yourself - Create buying incentives - Time announcements well - Plan for post-migration For Traders - Buy early for best prices - Use DCA for large amounts - Monitor aggressiveness factor - Check target progress - Always use slippage protection - Understand price impact - Don't FOMO near target - Plan exit strategy Post-Bonding Transition Critical: After Migration Once is called: - ❌ Bonding curve trading permanently disabled - ❌ No more buy() or sell() functions - ✅ All trading moves to Uniswap v4 - ✅ Standard AMM mechanics apply - ✅ Anyone can provide liquidity - ✅ Fully decentralized trading Next Steps Understand price mechanics Choose the right target Learn about DEX transition --- ## DEX Phase Source: https://docs.b3.fun/bondkit/concepts/dex-phase What is the DEX Phase? The DEX phase is the final stage of a Bondkit token's lifecycle, where trading transitions from the automated bonding curve to a fully decentralized Uniswap v4 pool. This phase begins immediately after migration and represents complete decentralization. How Migration Works The Transition Process When is called after reaching the target: 1. Contract Status: Token status changes to 2. Uniswap v4 Pool: New pool created with accumulated liquidity 3. Price Initialization: Initial pool price calculated from bonding curve exit price 4. Ownership Renouncement: Contract ownership transferred to zero address 5. Trading Enabled: Full DEX trading begins immediately Pool Configuration Automatic Pool Setup: Initial Liquidity: - Trading Token: All accumulated funds from bonding phase - Bondkit Tokens: Calculated amount to match exit price - LP Tokens: Split between fee recipient and burned/distributed Trading in DEX Phase Trading Options Standard DEX Trading: Bondkit tokens in DEX phase can be traded using any Uniswap v4 compatible interface, DEX aggregator, or trading platform. SDK Helper (Optional): The SDK provides for simplified integration if needed. Price Discovery & Liquidity Market-Driven Pricing: - No more algorithmic bonding curve - Price determined by supply/demand - Real-time order book dynamics - Subject to market volatility Liquidity Sources: Key Differences from Bonding Phase Trading Mechanics | Aspect | Bonding Phase | DEX Phase | |--------|--------------|-----------| | Pricing | Algorithmic curve | Market supply/demand | | Liquidity | Unlimited (contract mints) | Limited pool liquidity | | Fees | 5% to fee recipient | 0.3% to LPs + protocol | | Order Types | Buy/sell only | Full DEX features | | Price Impact | Predictable curve | Depends on liquidity depth | | MEV | Not applicable | Subject to MEV | Smart Contract Changes Status Transition: Method Availability: - ✅ / - Disabled (will revert) - ✅ DEX trading via - ✅ Standard ERC20 functionality continues - ✅ Event monitoring for DEX trades Advanced DEX Features Custom Hooks Integration Bondkit tokens on Uniswap v4 include custom hooks for enhanced functionality: Analytics & Monitoring Real-Time Data: Available Metrics: - Real-time price feeds - 24h volume and change - Liquidity depth - Historical OHLCV data - Transaction history - Holder analytics Liquidity Provision Becoming an LP: LP Benefits: - Trading Fees: Earn 0.3% of all swap volume - Incentive Programs: Potential additional rewards - Price Appreciation: Benefit from token growth - Impermanent Loss: Standard AMM risks apply Migration Impact Analysis For Token Holders Immediate Effects: - ✅ Tokens remain fully transferable - ✅ Can trade on open market - ✅ No lock-up periods - ⚠️ Price now subject to market volatility - ⚠️ No guaranteed liquidity (depends on pool depth) Long-term Benefits: - 🚀 Access to larger trading ecosystem - 🚀 Integration with DeFi protocols - 🚀 Composability with other tokens - 🚀 True decentralization achieved For Projects Operational Changes: New Responsibilities: - Community Building: Drive organic trading volume - Liquidity Incentives: Encourage LP participation - Marketing: Promote token utility and adoption - Integration: List on DEX aggregators and platforms Best Practices for DEX Phase For Traders Slippage Management: - Use 0.5-2% slippage for small trades - Higher slippage for larger amounts - Check price impact before execution Timing Considerations: - Higher liquidity during active hours - Monitor for large LP movements - Use limit orders when available Example: Liquidity Analysis: - Check pool TVL before large trades - Monitor liquidity provider activity - Understand impermanent loss if LP Price Monitoring: - Set up price alerts - Use stop-loss strategies - Diversify across multiple tokens For Developers Status Checking: Error Handling: Common Questions No - Migration is permanent and irreversible. Once in DEX phase, the token will always trade on Uniswap v4. All accumulated trading tokens from the bonding phase become the initial liquidity in the Uniswap v4 pool, paired with calculated bondkit tokens at the exit price. No restrictions - tokens become standard ERC20s trading on Uniswap v4. Full DeFi composability is enabled. DEX phase uses standard Uniswap v4 fees (0.3%) which go to liquidity providers instead of the 5% bonding phase fee to the fee recipient. Next Steps Learn to use BondkitSwapService for DEX trading Integrate TradingView charts for your DEX tokens Provide liquidity and earn trading fees Track your token's DEX performance --- ## Pricing Source: https://docs.b3.fun/bondkit/concepts/pricing Visual Price Curves Bonding Curve Model Mathematical Formula Core Formula Where: - = Current token supply - = Final token supply - = Amount raised so far - = Target amount - Understanding the Exponent The aggressiveness factor controls how the exponent affects price progression: | Aggressiveness | Exponent | Formula Becomes | Price Behavior | |---------------|----------|-----------------|----------------| | 0 | 1.00 | S = Sfinal × (R/Rtarget) | Linear - constant tokens per ETH | | 25 | 0.80 | S = Sfinal × (R/Rtarget)^0.80 | Slightly curved | | 50 | 0.67 | S = Sfinal × (R/Rtarget)^0.67 | Moderate curve | | 75 | 0.57 | S = Sfinal × (R/Rtarget)^0.57 | Steep curve | | 100 | 0.50 | S = Sfinal × √(R/Rtarget) | Very steep (square root) | Aggressiveness Factor Impact Cumulative Token Distribution See how tokens are distributed throughout the bonding process with different aggressiveness factors. Example: 10M B3 target, 1.25M total token supply (1M available for bonding, 250K reserved for LP) | Progress | Aggressiveness = 0 | 25 | 50 | 75 | 100 | |----------|-------------------|----------------------|----------------------|----------------------|----------------------| | 10% | 100,000 | 158,489 | 215,443 | 268,270 | 316,228 | | 20% | 200,000 | 275,946 | 341,995 | 398,647 | 447,214 | | 30% | 300,000 | 381,678 | 448,140 | 502,588 | 547,723 | | 40% | 400,000 | 480,450 | 542,884 | 592,387 | 632,456 | | 50% | 500,000 | 574,349 | 629,961 | 672,950 | 707,107 | | 60% | 600,000 | 664,540 | 711,379 | 746,843 | 774,597 | | 70% | 700,000 | 751,759 | 788,374 | 815,614 | 836,660 | | 80% | 800,000 | 836,512 | 861,774 | 880,284 | 894,427 | | 90% | 900,000 | 919,166 | 932,170 | 941,571 | 948,683 | | 100% | 1,000,000 | 1,000,000 | 1,000,000 | 1,000,000 | 1,000,000 | Key Insight: Higher aggressiveness front-loads token distribution to early buyers. At 10% progress: - Aggressiveness 0: 100,000 (linear) - Aggressiveness 100: 316,228 (3.16x advantage!) Early buyers with aggressive curves get significantly more tokens for their B3, while late buyers face much higher prices. Real-World Example: Alice's Purchase Let's follow Alice, who wants to buy tokens from a new project at launch: Project Setup: - Total Supply: 1.25M tokens (1M for bonding + 250K for LP) - Target: 10M B3 to reach migration - Aggressiveness: 100 (maximum reward for early buyers) - Current Progress: 0% (project just launched) Alice's Purchase: Alice decides to buy 1M B3 worth of tokens right at launch (0% progress). 1. Alice sends: 1M B3 tokens 2. Trading fee (3%): 30K B3 goes to fee recipients 3. Amount for curve: 970K B3 advances the project to ~9.7% progress 4. Tokens received: ~306,000 tokens (calculated from bonding curve) Comparing Different Entry Points: If Alice waited and bought the same 1M B3 worth at different project stages: | Project Progress | Alice's 1M B3 Gets Her | Price per Token | |-----------------|------------------------|-----------------| | 0% (launch) | ~306,000 tokens | ~3.3 B3/token | | 50% progress | ~114,000 tokens | ~8.8 B3/token | | 90% progress | ~49,000 tokens | ~20.4 B3/token | Early Buyer Advantage: Alice gets 6.2x more tokens by buying at launch versus waiting until 90% progress! Key Takeaway: With maximum aggressiveness (100), buying 1M B3 at launch gets Alice 6.2x more tokens than waiting until 90% progress. The bonding curve heavily rewards early participation! Interactive Price Calculator Choosing Your Aggressiveness Factor Decision Framework Best for: - Fair launches - Community tokens - Stable pricing Pros: - Equal opportunity - Predictable costs - Less FOMO Cons: - No early incentive - Slower momentum Best for: - Most projects - Balanced approach - Moderate rewards Pros: - Some early advantage - Still accessible - Good momentum Cons: - Moderate complexity - Some price variance Best for: - Hype launches - Reward early adopters - Fast fundraising Pros: - Strong early incentive - Creates urgency - Rewards believers Cons: - Can seem unfair - High price variance - FOMO-driven Selling Mechanics When users sell tokens back to the curve: 1. Price Calculation: Uses inverse of buying formula 2. Fee Deduction: 5% fee applied to proceeds 3. Curve Update: Reduces total raised amount 4. Price Impact: Large sells significantly impact price Sell Price Formula Edge Cases & Limits Important Considerations: 1. Refunds: If a buy would exceed target, excess ETH is refunded 2. Minimum Amounts: Very small trades may revert due to rounding 3. Maximum Supply: Cannot exceed 4. Price Limits: Extreme aggressiveness can cause price spikes 5. Slippage: Always use for protection Real-World Examples Case Study: Fair Launch Token - Aggressiveness: 10 - Target: 50 ETH - Result: Nearly linear pricing, community appreciated fairness Case Study: Hype Token - Aggressiveness: 85 - Target: 100 ETH - Result: Reached target in 2 hours, early buyers gained 8x Case Study: Balanced Project - Aggressiveness: 45 - Target: 25 ETH - Result: Steady growth over 3 days, 2.5x advantage for early buyers Next Steps Learn to choose the right factor Estimate your migration price --- ## Targets & Migration Trigger Source: https://docs.b3.fun/bondkit/concepts/targets Target amount - is the quote‑asset threshold that enables migration. - Set at creation; denominated in the quote asset (ETH or an allowed ERC20). - The bonding phase ends once total raised reaches the target (excess contributions are refunded). Who can migrate - Only the token owner/creator (migration admin) can call . What happens at migration - Split of accumulated quote asset: - Portion to , based on . - Remainder used as liquidity alongside tokens reserved for LP. - For Uniswap v4 migration, the contract computes to initialize the pool. - Liquidity is added to the v4 pool with appropriate safeguards; LP tokens or positions are handled per v4 semantics, with ownership effectively burned/renounced for decentralization. - Ownership is renounced immediately to finalize decentralization. Post‑migration - Bonding‑phase trading is disabled. - Token behaves as a standard ERC20 with DEX‑based price discovery. Networks & addresses (factory, v4 pool manager, hooks) are listed on the Networks page. --- ## Choose a Quote Asset Source: https://docs.b3.fun/bondkit/guides/choose-quote-asset Overview BondKit supports bonding against ETH or an allowed ERC20 (e.g., B3). Your choice impacts UX, integrations, and liquidity at migration. When to use ETH - Broad accessibility; most users hold ETH on Base - Simpler UX (no prior approvals) - Direct ETH liquidity at migration When to use an ERC20 (e.g., B3) - Aligns with an existing token economy - Can bootstrap deeper token‑token pairs at migration - Requires approvals before buys/sells Operational differences - 5% fee on buys and sells for both ETH and ERC20 - ERC20 flows require before curve interactions - Migration pairs are created against WETH or the chosen ERC20 Confirm the allowed‑list for ERC20 quote assets with the team. By default only specific assets may be enabled. --- ## Estimate Migration Price Source: https://docs.b3.fun/bondkit/guides/est-migration-price Overview Migration initializes a Uniswap v4 pool. The contract computes from bonding state. Practical approach - Use bonding reads to approximate price near the target: - - Considerations - The final split and liquidity amount can affect initial ticks. - Slippage protections are applied when adding liquidity. - For ERC20 quote assets, ensure pair and decimals are accounted for when converting to . Exact initialization math is handled on-chain. Use reads for UI estimation; treat final on-chain initialization as source of truth. --- ## Set aggressivenessFactor Source: https://docs.b3.fun/bondkit/guides/set-aggressiveness Understanding Aggressiveness Impact The aggressiveness factor determines how much advantage early buyers get. Higher values create steeper price increases that reward early participation. Impact at Different Levels | Range | Early Buyer Advantage | Best For | Price Behavior | |-------|---------------------|----------|---------------| | 0-20 | 1.5-2x advantage | Fair launches, community tokens | Nearly linear pricing | | 30-60 | 2-3x advantage | Most projects, balanced approach | Moderate curve | | 70-100 | 3-6x advantage | Hype launches, reward believers | Steep curve | At maximum aggressiveness (100), early buyers can get 6x more tokens than late buyers for the same amount of B3! Decision Framework Choose Low (0-30) If: - Goal: Fair distribution for everyone - Community: Values equality over early rewards - Timeline: Want steady, predictable growth - Risk: Prefer minimal price volatility Choose Medium (30-70) If: - Goal: Balanced approach with some early incentive - Community: Mix of early supporters and general public - Timeline: Moderate fundraising pace - Risk: Comfortable with some price variance Choose High (70-100) If: - Goal: Maximum early adopter rewards - Community: Strong core believers - Timeline: Want fast fundraising - Risk: Comfortable with high price swings Real Impact Example Project Setup: 10M B3 target, buying 1M B3 worth | Aggressiveness | Early Buyer Gets | Late Buyer Gets | Advantage | |---------------|-----------------|----------------|-----------| | 0 | ~100K tokens | ~100K tokens | 1x (no advantage) | | 50 | ~208K tokens | ~114K tokens | 1.8x advantage | | 100 | ~306K tokens | ~49K tokens | 6.2x advantage | Configuration Example Next Steps See detailed token distribution tables Ready to deploy your token --- ## Complete Token Lifecycle Source: https://docs.b3.fun/bondkit/guides/token-lifecycle Overview This guide walks you through the complete lifecycle of a Bondkit token, from initial creation to full decentralization. Understanding this flow is essential for successful token launches and management. Phase 1: Token Creation Pre-Deployment Planning Critical Decisions: | Parameter | Impact | Recommendation | |-----------|---------|----------------| | finalTokenSupply | Total tokens ever created | 1M-100M tokens typical | | aggressivenessFactor | Price curve steepness | 30-60 for balanced launches | | targetAmount | Migration threshold | 5-50 trading tokens | | tradingToken | What users pay with | Use B3 for Base mainnet | Example Configuration: Fee Distribution Strategy: Fee Flow: - Bonding Phase: 5% of all trades → - Post-Migration: 0.3% trading fees → LP providers Deployment Execution Phase 2: Bonding Phase Management Launch Strategy Pre-Launch Checklist: - [ ] Token contract verified on Basescan - [ ] Community channels established (Discord/Telegram) - [ ] Marketing materials prepared - [ ] Initial buying strategy planned - [ ] Price tracking dashboard ready Launch Day: Key Metrics Dashboard: Real-Time Updates: Managing the Bonding Curve Healthy Bonding Phase Indicators: - Steady trading volume - Growing holder base - Active community engagement - Progress toward target (but not too fast) - Minimal large sell-offs Warning Signs: - No trading activity for 24+ hours - Single whale controlling large percentage - Rapid target achievement without community - Excessive volatility from bots Phase 3: Migration Readiness Pre-Migration Checklist Migration Timing Strategy Best Practices: - Announce migration 24-48 hours in advance - Choose high-activity time for your community - Ensure sufficient community consensus - Have post-migration marketing ready Pre-Migration Announcement: The Migration Process: Phase 4: DEX Phase Operations Immediate Post-Migration (First 24 Hours) Long-Term DEX Strategy Initial Liquidity Analysis: Liquidity Incentive Program: Educational Content: Community Resources: - Updated documentation - Trading tutorial videos - DEX interface integration guides - Liquidity provision tutorials DEX Phase Dashboard: Automated Monitoring: Phase 5: Full Decentralization Ownership Renunciation Post-Renunciation Operations Governance Structure Options: | Model | Pros | Cons | Best For | |-------|------|------|----------| | No Governance | Simple, truly decentralized | Cannot upgrade/change | Simple tokens | | Token Voting | Holder-driven decisions | Can be gamed by whales | Active communities | | Multisig | Trusted group decisions | Semi-centralized | Technical projects | | DAO | Full on-chain governance | Complex, slow | Large projects | Implementation Examples: Handover Documentation: - Complete technical documentation - Community management guides - Emergency response procedures - Contact information for technical help Community Tools: Lifecycle Success Metrics Key Performance Indicators Common Pitfalls & Solutions Critical Mistakes to Avoid: 1. Rushing Migration: Don't migrate immediately upon target - ensure community readiness 2. Poor Communication: Keep community informed at every phase 3. Whale Concentration: Monitor for unhealthy token concentration 4. Technical Issues: Thoroughly test all integrations before launch 5. Legal Compliance: Ensure regulatory compliance in your jurisdiction Troubleshooting Guide Problem: No trading activity Solutions: - Increase marketing and community outreach - Lower aggressiveness factor if price rises too quickly - Ensure trading token (B3) is easily accessible - Add trading charts and analytics tools Problem: Whale manipulation Solutions: - Implement community watch programs - Use social pressure for responsible trading - Consider maximum purchase limits in future versions - Build strong community consensus Problem: Migration fails Solutions: - Check all parameters are correct - Ensure sufficient gas and proper wallet setup - Verify target is actually reached - Contact technical support if needed Problem: Poor opening price Solutions: - Migration price is algorithmically determined - Market will find true value over time - Focus on utility and community building - Avoid artificial price manipulation Problem: Low liquidity Solutions: - Implement LP reward programs - Partner with market makers - Educate community about LP provision - Consider liquidity mining campaigns Problem: Community confusion Solutions: - Create clear migration guides - Host community AMAs and tutorials - Provide multiple trading interface options - Maintain active community support Next Steps Use the quickstart guide to begin your token deployment Learn how to configure your bonding curve parameters Detailed SDK documentation for developers Join the community for help and guidance --- Success Tips: - Start with smaller, test launches to gain experience - Build genuine community before, during, and after bonding - Focus on real utility and value creation - Be transparent about tokenomics and plans - Plan for long-term sustainability, not just initial hype --- ## Troubleshooting Guide Source: https://docs.b3.fun/bondkit/guides/troubleshooting Quick Diagnostics Start here for rapid issue identification: Common Error Messages Deployment Errors Cause: Token address is missing, invalid, or not checksummed. Solutions: Cause: Trying to use non-Base chain ID. Solutions: Cause: Invalid deployment parameters or insufficient permissions. Solutions: Trading Errors Cause: Various trading issues during bonding phase. Solutions: Cause: Token not fully initialized or network issues. Solutions: Cause: Token migrated to DEX phase, but still using bonding methods. Solutions: Wallet Integration Issues Cause: Wallet not properly connected or configured. Solutions: Cause: Slow network, low gas, or OKX wallet issues. Solutions: Common Wallet Problems: Network & RPC Issues Symptoms: Slow responses, timeouts, or connection errors. Solutions: Problem: Transactions fail with "out of gas" or gas estimation errors. Solutions: Integration Problems Common React Integration Problems: Problem: Charts not loading or CDN errors. Solutions: Advanced Debugging Enable Debug Logging Transaction Analysis Getting Help Community Support Join our Discord for real-time help from the community and team Report bugs and request features on GitHub When to Contact Support Contact support for: - Smart contract bugs or exploits - SDK issues not covered in this guide - Network infrastructure problems - Critical security concerns Don't contact support for: - Basic integration questions (use Discord) - Transaction failures due to user error - Wallet connection issues - General blockchain questions Information to Include When reporting issues, always include: --- Security Reminder: - Never share private keys or seed phrases in support requests - Only use official Bondkit contracts and addresses - Verify all contract addresses before interacting - Be cautious of scam tokens or fake support channels Pro Tips: - Test with small amounts first - Use TypeScript for better error detection - Enable debug logging during development - Keep your SDK version updated - Monitor transaction costs and adjust gas accordingly --- ## How BondKit Works Source: https://docs.b3.fun/bondkit/how-it-works Architecture Overview Product Flow in Detail What happens: - User calls on the Factory contract - Factory clones the Implementation contract using minimal proxy pattern - New token is initialized with custom parameters - Token enters bonding phase automatically Gas cost: ~200,000 gas (90% cheaper than full deployment) Time: ~15 seconds What happens: - Users buy/sell tokens directly from the contract - Price follows algorithmic bonding curve: - 5% fee on all trades goes to fee recipient - Contract accumulates quote assets (ETH/B3) toward target - Backend indexes all transactions for analytics Trading mechanics: - Buy: Send ETH/B3, receive tokens at current curve price - Sell: Send tokens, receive ETH/B3 minus fees - Automatic refunds if purchase would exceed target Duration: Until target is reached (hours to weeks) What happens: - Admin calls when target is reached - Contract calculates fair market price as - Creates and initializes Uniswap v4 pool - Transfers accumulated liquidity to pool - Renounces ownership to zero address - Token becomes standard ERC20 with DEX trading Post-migration: - Bonding curve permanently disabled - All trading via Uniswap v4 - No admin controls remain - Full decentralization achieved Gas cost: ~500,000 gas Time: ~30 seconds System Components Smart Contracts Purpose: Deploys new bond tokens efficiently Key Functions: - - Creates new token clone - - Returns template address - - Admin function to whitelist assets Gas Optimization: - Uses EIP-1167 minimal proxy pattern - Shares logic across all tokens - ~90% gas savings vs individual deployments Purpose: Template for all bond tokens Core Features: - ERC20 standard compliance - Bonding curve mathematics - Migration logic to Uniswap v4 - Fee distribution system State Transitions: 1. Uninitialized → Bonding Phase 2. Bonding Phase → Migration Ready 3. Migration Ready → DEX Phase Purpose: Individual token instances Lifecycle: - Created via factory - Initialized with unique parameters - Manages its own bonding curve - Self-migrates to Uniswap v4 Storage: - Token metadata (name, symbol) - Supply and distribution - Bonding curve state - Migration parameters Backend Services Purpose: Captures all on-chain activity Monitors: - Token creations - Buy/sell transactions - Migration events - Transfer activities Technology: - Real-time blockchain scanning - Event log processing - Database synchronization Purpose: Processes raw data into insights Generates: - OHLCV candlestick data - Volume metrics - Liquidity tracking - Price history - User statistics Updates: Every block (~2 seconds) Purpose: Serves data to frontends Endpoints: - - List all tokens - - Token details - - Trade history - - Chart data - - User holdings Format: JSON with pagination User Roles | Role | Responsibilities | Permissions | |------|-----------------|-------------| | Creator | Deploy token, set parameters, initiate migration | Full control until migration | | Traders | Buy/sell during bonding, trade on DEX | Standard trading rights | | Fee Recipient | Receive trading fees | Passive income only | | Migration Admin | Execute migration when ready | One-time migration right | | LP Providers | (Post-migration) Add liquidity to Uniswap | Standard LP rights | Technical Deep Dive Bonding Curve Mathematics The bonding curve determines token price based on supply: Example Calculations: | Aggressiveness | Exponent | Price Behavior | |---------------|----------|----------------| | 0 | 1.00 | Linear (constant price) | | 25 | 0.80 | Gentle curve | | 50 | 0.67 | Moderate curve | | 75 | 0.57 | Steep curve | | 100 | 0.50 | Very steep (square root) | Migration Price Calculation When migrating to Uniswap v4, the contract: 1. Calculates exit price from bonding curve 2. Converts to sqrtPriceX96 format: 3. Initializes pool with this price 4. Adds liquidity using accumulated funds Gas Optimization Techniques Minimal Proxy Pattern (EIP-1167) Instead of deploying full contract code for each token: - Deploy one implementation contract (600KB) - Deploy tiny proxy contracts (45 bytes each) - Proxies delegate all calls to implementation - Result: 90% gas savings per deployment Configuration Parameters Token Creation Parameters | Parameter | Type | Range/Format | Impact | |-----------|------|--------------|--------| | | string | 1-50 chars | Token display name | | | string | 2-10 chars | Trading symbol | | | uint256 | > 0 | Total mintable tokens | | | uint8 | 0-100 | Curve steepness | | | uint256 | > 0 | Migration threshold | | | address | Valid address | Receives fees | | | uint256 | 0-10000 | LP fee share (basis points) | | | address | Valid address | Can trigger migration | Runtime Parameters | Action | Parameters | Validation | |--------|------------|------------| | Buy | , | Slippage protection | | Sell | , | Balance check, slippage | | Migrate | None | Target reached, admin only | System Constants | Constant | Value | Description | |----------|-------|-------------| | Trading Fee | 5% | Applied to all trades | | Decimals | 18 | Standard ERC20 decimals | | Min Target | 0.1 ETH | Minimum viable target | | Max Aggressiveness | 100 | Maximum curve factor | Security Considerations Important Security Features: 1. Ownership Renouncement: Automatic after migration 2. No Mint Function: Supply fixed at creation 3. Immutable Parameters: Cannot be changed post-deployment 4. Audited Contracts: Professionally reviewed code 5. No Admin Backdoors: True decentralization 6. Slippage Protection: Built into buy/sell functions 7. Overflow Protection: Safe math throughout Failure Scenarios & Handling | Scenario | System Response | |----------|----------------| | Buy exceeds target | Partial fill, refund excess | | Insufficient liquidity for sell | Transaction reverts | | Migration before target | Transaction reverts | | Non-admin attempts migration | Transaction reverts | | Double migration attempt | Transaction reverts | | Zero address operations | Transaction reverts | Next Steps Understand bonding curve mathematics Learn the migration process --- ## Installation Source: https://docs.b3.fun/bondkit/installation Prerequisites - Node.js 18+ - JavaScript runtime - pnpm (recommended) or npm/yarn - Package manager - Git - Version control - Wallet with Base ETH - For deployments and transactions Quick Start Options ## Install the SDK ## Project Setup ## Add to Existing Project The SDK includes all necessary dependencies including viem ## Clone Demo Application The fastest way to get started is with our complete demo application: The demo app is located at and includes: - Complete token deployment flow - Trading interface with TradingView charts - Wallet connection with B3 authentication - Real-time price and volume tracking - Migration management interface ### Demo App Structure Environment Configuration Basic Setup Create a file in your project root: Security Best Practices Never commit private keys to version control! - Add to your - Use environment variables in production - Consider using a key management service - Use separate wallets for development and production Client Initialization Basic Setup Advanced Configuration TypeScript Configuration Recommended for BondKit projects: Testing Your Setup Create a test file : Run the test: Next Steps Deploy your first token in minutes Explore all SDK methods and features Study the complete implementation Learn about backend services and analytics Troubleshooting Ensure the SDK is properly installed: If using React components, you may need: Update TypeScript to latest version: - Verify your RPC endpoint is working - Check wallet has sufficient Base ETH - Ensure private key format is correct (with 0x prefix) Clear cache and reinstall: --- ## BondKit Introduction Source: https://docs.b3.fun/bondkit/introduction What is BondKit? BondKit is a complete token launch platform for creating ERC20 "bond tokens" on Base mainnet. It provides an end‑to‑end solution that handles everything from initial token creation through bonding curve trading and finally migration to Uniswap v4 for full decentralized trading. Key Components Audited On-Chain Infrastructure - Factory contract for deploying new tokens - ERC20 implementation with bonding curve logic - Automatic Uniswap v4 pool initialization - Gas-optimized minimal proxy pattern Developer-Friendly Tools - Simple API for all contract interactions - Type-safe interfaces with full TypeScript support - Built-in transaction management - Event subscriptions and monitoring Real-Time Data Services - Transaction history tracking - OHLCV chart data generation - Token metadata storage - REST API for frontend integration How BondKit Works The Three-Phase Lifecycle 1. Creation Phase: Deploy your token with custom parameters 2. Bonding Phase: Automated market making via bonding curve 3. DEX Phase: Full decentralized trading on Uniswap v4 Core Features - Gas-Efficient Clones: Uses minimal proxy pattern to reduce deployment costs by ~90% - Standardized Implementation: All tokens share the same battle-tested logic - One-Click Deployment: Simple function call to create a new token - Configurable Aggressiveness: Factor from 0-100 controls price progression - Automatic Price Discovery: Market-driven pricing during bonding phase - Buy & Sell Support: Full two-way trading during bonding - 5% Trading Fee: Applied to both buys and sells, distributed to fee recipient - Customizable Targets: Set your funding goal in ETH or allowed ERC20 - Automatic Threshold Detection: Contract tracks progress to target - One-Click Migration: Simple call to when ready - Price Calculation: computed on-chain for fair initial pricing - Automatic Pool Creation: Pool initialized with bonding curve exit price - Liquidity Provision: Accumulated funds become initial liquidity - Ownership Renouncement: Contract becomes fully decentralized post-migration - Seamless Transition: No manual intervention required - Real-Time Indexing: All transactions recorded and processed - OHLCV Data: Professional trading charts available via API - Transaction History: Complete audit trail for every token - Portfolio Tracking: Monitor multiple tokens and positions Use Cases For Projects & Creators - Fair launch mechanisms - Community-driven price discovery - No upfront liquidity required - Built-in anti-bot protection For GameFi Projects - In-game currency launches - NFT project tokens - Reward token distribution - Player-owned economies For Developers - Programmatic token creation - White-label solutions - Custom frontend integration - API-driven automation Technical Capabilities Smart Contract Features - ✅ ERC20-compliant bond tokens with extended functionality - ✅ Factory pattern for gas-efficient deployments - ✅ Configurable parameters (supply, target, aggressiveness) - ✅ Built-in fee distribution mechanism - ✅ Automatic Uniswap v4 migration SDK Features - ✅ Full TypeScript support with type definitions - ✅ Promise-based async operations - ✅ Event listeners and subscriptions - ✅ Transaction receipt handling - ✅ Error handling and retry logic Analytics Features - ✅ Real-time price tracking - ✅ Volume and liquidity metrics - ✅ Historical transaction data - ✅ OHLCV candlestick data - ✅ User portfolio tracking Get started Launch with BondKit on Base Questions or feedback? Talk to us on Discord Key Terminology | Term | Definition | |------|------------| | Bonding Phase | Initial trading period with algorithmic pricing via bonding curve | | Bond Token | ERC20 token with built-in bonding curve mechanics | | Target Amount | Funding goal that triggers migration eligibility | | Migration | Transition from bonding curve to Uniswap v4 | | Quote Asset | The currency used to buy tokens (ETH or allowed ERC20) | | Term | Definition | |------|------------| | Minimal Proxy | Gas-efficient contract cloning pattern | | Aggressiveness Factor | Parameter (0-100) controlling price curve steepness | | sqrtPriceX96 | Uniswap v4 price format for pool initialization | | Fee Recipient | Address receiving trading fees during bonding | | LP Split Ratio | Liquidity provider fee percentage in basis points | | Term | Definition | |------|------------| | Factory Contract | Main contract for deploying new bond tokens | | Implementation | Template contract cloned for each token | | Public Client | Read-only blockchain connection | | Wallet Client | Write-enabled blockchain connection | | Provider | Web3 connection interface (e.g., MetaMask) | Important Parameters Current Network: Base Mainnet only Supported Trading Tokens: - B3 Token (primary on Base mainnet) - ETH (when configured as zero address) - Additional ERC20 tokens can be whitelisted Fee Structure: - 5% on all bonding phase trades - Customizable LP split ratio for migration Security: - Audited smart contracts - Automatic ownership renouncement post-migration - No admin keys after DEX phase begins Next Steps Set up the BondKit SDK in your project Learn the basics with our step-by-step guide Check out working implementations and demos Get help and share feedback on Discord --- ## Networks & Addresses Source: https://docs.b3.fun/bondkit/networks Base Mainnet | Name | Address | |------|---------| | BondkitTokenFactory | | | BondkitToken Implementation | | | Uniswap V4 Pool Manager | | | BondkitUniswapV4Hook | | | B3 | | | Bonding Phase Splitter | | | Dex Phase Splitter | | BondKit operates on Base mainnet. Testnet/dev environments are currently not available. --- ## Quickstart Source: https://docs.b3.fun/bondkit/quickstart Overview This quickstart guide will walk you through the complete lifecycle of a BondKit token in under 5 minutes. You'll learn how to: 1. Deploy a new bond token 2. Trade during the bonding phase 3. Monitor progress toward the target 4. Migrate to Uniswap v4 Prerequisites: Make sure you've completed the installation and have a funded wallet on Base. Complete Flow Diagram Step 1: Deploy Your Token Basic Deployment Understanding Parameters Total supply of tokens (with 18 decimals). Example: for 1M tokens. Controls bonding curve steepness (0-100): - 0-30: Linear pricing, fair for all buyers - 30-60: Moderate curve, balanced approach - 60-100: Aggressive, rewards early buyers Amount of trading token needed to enable migration. Use for 10 tokens (18 decimals). Address that receives trading fees (5% of all trades). Basis points (1/100th of 1%) for LP fee split. 1000 = 10%. Step 2: Trading During Bonding Phase Initialize Token Instance Understanding Trading Tokens BondKit tokens use a configurable trading token system. Check what token is used for trading: Buying Tokens Selling Tokens Monitoring Progress Event Monitoring Step 3: Migration to Uniswap v4 Check Migration Readiness Execute Migration Important: After migration: - Contract ownership is automatically renounced - Bonding curve trading is permanently disabled - All trading moves to Uniswap v4 - No further admin actions are possible Complete Example Here's a full working example that demonstrates the entire lifecycle: Next Steps Deep dive into bonding curves and pricing Explore all available methods End-to-end token management guide See a complete implementation --- ## SDK Reference Source: https://docs.b3.fun/bondkit/sdk/reference Installation & Setup Core Classes BondkitTokenFactory The factory class handles deploying new bond tokens and querying deployed tokens. Constructor | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | | | Yes | Chain ID (currently only Base: 8453) | | | | No | Private key for write operations | Methods Deploy a new bond token Parameters: Example: Get all deployed tokens Returns: Array of token addresses Example: Get token configuration Example: Get implementation contract Example: Connect wallet provider Example: BondkitToken The token class handles all operations for a specific bond token. Constructor | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | | | Yes | Token contract address | | | | No | Private key for write operations | Read Methods Methods for interacting with the trading token Example: Built-in swap methods for DEX phase trading Example: Write Methods Buy tokens with trading token Parameters: - : Amount of trading token to spend (as string or bigint) - : Minimum tokens to receive (slippage protection) Example: Sell tokens for trading token Parameters: - : Amount of tokens to sell - : Minimum trading token to receive (slippage protection) Example: Migrate to Uniswap v4 Requirements: - Caller must be migration admin - Target must be reached Example: Transfer or renounce token ownership Example: Important: Renouncing ownership is irreversible and removes all admin capabilities. Only do this after migration or if you want to make the token completely decentralized. Event Listeners BondkitSwapService The swap service handles Uniswap V4 trading for tokens after they migrate to the DEX phase. When to use: After migration when tokens are trading on Uniswap V4. During bonding phase, use and instead. Constructor Methods Get swap price quote Parameters: Returns: Example: Execute swap transaction Parameters: - : Same SwapParams as getSwapQuote - : Connected wallet client Example: Complete Example Important Notes: - Only works after token migration to DEX phase - Automatically handles token approvals (ERC20 → Permit2 → Universal Router) - Uses Uniswap V4 with custom hooks and pool configuration - Slippage protection is built into the quotes TradingView Component A React component that renders professional trading charts for Bondkit tokens using TradingView's charting library. Use case: Display price charts, volume data, and trading indicators for your Bondkit tokens in web applications. Installation & Setup Requirements: - React 18+ - TradingView charting library (loaded automatically from CDN) - Tailwind CSS for styling (optional, but recommended) Props Basic Usage Advanced Configuration Features Built-in Support: - Candlestick charts - Volume indicators - Price overlays - Technical analysis tools - Multiple timeframes (1m, 5m, 1h, 1D, etc.) Customization: - Light/dark themes - Responsive design - Mobile-friendly interface - Professional trading UI Automatic Data Feeds: - Real-time price data from B3 API - OHLCV (Open, High, Low, Close, Volume) data - Historical price charts - Transaction-based price updates UDF Compatible: - Standard TradingView datafeed format - Configurable API endpoints - Fallback configurations Optimized Loading: - TradingView library loaded from CDN - Lazy loading with loading states - Error handling and fallbacks - Configurable CDN domains Production Ready: - Automatic CDN switching - Custom domain support - Development/production configurations Complete Integration Example CDN Configuration Setup Requirements: 1. TradingView License: Ensure you have proper licensing for TradingView library usage 2. CDN Setup: Configure CDN URLs in your environment variables 3. API Access: Ensure your app can access the B3 analytics API for chart data 4. CORS: Configure CORS settings if using custom API endpoints Type Definitions Core Types Event Types Transaction Types Configuration Network Support Supported Chains | Chain | Chain ID | Status | |-------|----------|--------| | Base Mainnet | 8453 | ✅ Supported | | Base Sepolia | 84532 | 🚧 Coming Soon | Error Handling Complete Examples Deploy and Trade Portfolio Tracker Best Practices Security Considerations 1. Never expose private keys in client-side code 2. Always use slippage protection in trades 3. Validate addresses before transactions 4. Handle errors gracefully with try-catch 5. Monitor gas prices before large operations Performance Tips 1. Batch read operations with Promise.all() 2. Cache token instances to avoid recreating 3. Use event listeners instead of polling 4. Implement exponential backoff for retries 5. Consider pagination for large datasets Support & Resources Source code and issues Community support Fix common integration issues Example implementation --- ## Collection Management Source: https://docs.b3.fun/createkit/collections Overview Collection management is at the core of CreateKit. This guide covers everything you need to know about creating, configuring, and managing NFT collections using the BaseMint protocol. Collection Metadata Structure Every collection requires specific metadata that defines its characteristics: Required Parameters The name of your NFT collection (e.g., "Bored Ape Yacht Club") The symbol/ticker for your collection (e.g., "BAYC") The Ethereum address of the collection creator The Ethereum address of the game owner (can be same as creator) Optional Parameters Maximum number of tokens that can be minted Price per token in wei (use parseEther() for ETH values) Maximum tokens that can be minted per wallet Whether whitelist-only minting is enabled Unix timestamp when minting starts (0 = immediate) Unix timestamp when minting ends The token standard to use Chain ID (8333 = B3 Mainnet) Creating Collections Basic Collection Advanced Collection Configuration Token Standards CreateKit supports both ERC721 and ERC1155 standards: Metadata Management Collection-Level Metadata Token-Level Metadata CreateKit automatically generates token metadata based on your collection settings: Collection Validation CreateKit provides built-in validation for collection parameters: Address Prediction One of CreateKit's key features is deterministic address prediction: Collection Management Operations Checking Collection Status Updating Collection Settings Most collection parameters cannot be changed after deployment. Plan your collection configuration carefully. Best Practices 1. Collection Planning - Set appropriate max supply based on use case - Consider future demand and scarcity - Leave room for growth or special editions - Research similar collections for pricing reference - Consider gas costs and transaction fees - Plan for different market conditions 2. Metadata Quality 3. Security Considerations - Never hardcode private keys in source code - Use environment variables or secure key management - Consider using multi-signature wallets for valuable collections - Always validate signatures before deployment - Verify collection parameters match intended values - Use a staging deployment before production rollout - Carefully choose creator and gameOwner addresses - Understand reward distribution implications - Plan for long-term collection management Troubleshooting Ensure all collection parameters are identical between signature generation and deployment. Even small changes will result in different addresses. Check that all required fields are provided and that values are within acceptable ranges (e.g., maxSupply > 0, valid addresses). Verify that your wallet client is properly configured and that you have sufficient funds for the signing transaction. Next Steps Now that you understand collection management, explore these related topics: Learn how to implement token minting functionality Set up whitelist-based minting for exclusive access --- ## Error Handling Source: https://docs.b3.fun/createkit/error-handling Overview Robust error handling is crucial for production applications using CreateKit. This guide covers common error scenarios, best practices, and recovery strategies. Common Error Types Signature Errors Storage Errors Contract Interaction Errors Error Recovery Patterns Retry Logic Circuit Breaker User-Friendly Error Messages Error Monitoring Validation Helpers React Error Boundaries Best Practices - Categorize errors by type and severity - Use consistent error codes - Provide actionable error messages - Log errors with sufficient context - Implement appropriate retry logic - Use circuit breakers for external services - Provide fallback mechanisms - Allow manual error recovery Next Steps Now that you have comprehensive CreateKit documentation, you can: Use the quickstart guide to create your first collection Connect with other developers in the B3 Discord --- ## Examples Source: https://docs.b3.fun/createkit/examples Overview This page provides comprehensive, real-world examples of implementing CreateKit in various scenarios. Each example includes complete code, error handling, and best practices. Basic NFT Collection A simple art collection with free minting: Gaming Collection with Whitelist A gaming collection with tiered whitelist access: Multi-Collection Platform A platform managing multiple collections: Marketplace Integration Integrating CreateKit with a marketplace: React Components Frontend components for CreateKit integration: Testing Examples Comprehensive testing patterns: Best Practices Summary - Always validate signatures before deployment - Use environment variables for sensitive data - Implement proper error handling - Test thoroughly before deploying production contracts - Cache frequently accessed data - Use batch operations when possible - Implement proper loading states - Optimize for gas efficiency - Provide clear feedback during operations - Show estimated costs upfront - Handle errors gracefully - Implement proper validation - Write comprehensive tests - Document your code - Use TypeScript for type safety - Follow consistent patterns Next Steps Learn comprehensive error handling patterns and recovery strategies Explore the complete CreateKit API documentation --- ## Installation Source: https://docs.b3.fun/createkit/installation Package Installation Install CreateKit using your preferred package manager: CreateKit is built with TypeScript and provides full type definitions out of the box. Dependencies CreateKit is built on top of modern web3 technologies and requires the following peer dependencies: Environment Setup 1. Configure Chain Networks CreateKit provides pre-configured chain definitions for B3 Mainnet: 2. Initialize Viem Client Set up your viem client for interacting with the blockchain: 3. Environment Variables Create a file in your project root: Never commit private keys to version control. Use environment variables or secure key management solutions. Framework Integration Next.js Setup For Next.js applications, create a configuration file: React/Vite Setup Verify Installation Test your installation with a simple script: Run the test script: TypeScript Configuration Ensure your includes the necessary configurations: Next Steps Now that you have CreateKit installed and configured, you're ready to start building: Create your first NFT collection in minutes Learn about collection creation and management Troubleshooting Ensure all peer dependencies are installed: Make sure your TypeScript configuration includes the necessary lib entries and that is enabled. Verify your RPC endpoints are correct and accessible. Use the default B3 RPC endpoints if custom ones fail. Ensure your private key is in the correct format (0x prefixed) and has sufficient funds for gas fees. --- ## Introduction Source: https://docs.b3.fun/createkit/introduction Why CreateKit? Create NFTs for free with CreateKit, users just sign a message (no gas required) and the collection is deployed and minted in a single transaction at the first mint. Try it out: Create NFTs for free & earn CreateKit, powered by the BaseMint Protocol, is a comprehensive TypeScript SDK that revolutionizes NFT collection creation and management. Built specifically for the B3 ecosystem, it provides a streamlined, gas-efficient workflow for deploying and managing NFT collections with minimal costs and maximum flexibility. Create NFTs with onchain addresses completely free during the initial setup phase Deploy collections and mint your first NFT in a single transaction Supports both ERC721 and ERC1155 token standards OpenSea-compatible metadata format ensures seamless marketplace integration Key Features 🎨 Collection Management - Deploy ERC721 and ERC1155 collections - Customize collection parameters (name, symbol, supply, pricing) - Set minting timeframes and limits - Manage collection metadata and URIs - Support for different media types (3D models, artwork, video, memes) 🔒 Secure Deployment - Two-step signature verification process - Creator signature validation - Deployer signature validation - Collection address prediction 🎯 Token Operations - Mint ERC721 and ERC1155 tokens - Whitelist-based minting with Merkle proofs - Automatic price calculation - Built-in parameter validation - Gas-efficient transactions 💰 Reward Distribution - Track creator rewards - Monitor per-collection reward accumulation - View total and unclaimed rewards per collection - Track reward distribution per recipient type - Withdraw accumulated rewards System Flow The BaseMint protocol provides a unique, gas-efficient workflow: Creators define collection parameters and generate cryptographic signatures stored off-chain with zero gas costs. Collection data is stored securely in BaseMint storage with deterministic addresses for easy discovery. The first minter triggers on-chain deployment in a single transaction that covers both deployment and first mint. Open minting for all users with optional whitelist support and wallet limits. Reward Structure CreateKit features an innovative reward system that benefits all participants in the ecosystem: | Recipient Type | Default Share | Description | |----------------|---------------|-------------| | Creator | 40% | Collection originator | | First Minter | 30% | Initial deployer who triggers deployment | | Game Owner | 20% | Platform integrator | | Platform | 10% | Protocol fee | Reward rates are configurable by the protocol owner and can be adjusted based on ecosystem needs. Supported Networks CreateKit supports the B3 ecosystem with planned expansion to additional networks: Chain ID: 8333 Production-ready deployment for live applications Getting Started Ready to start building? Check out our installation guide and quickstart tutorial to begin creating your first NFT collection with CreateKit. Install CreateKit and set up your development environment Build your first NFT collection in minutes Developer Resources Learn how to create and manage NFT collections Implement token minting functionality Explore practical implementation examples --- ## Minting Source: https://docs.b3.fun/createkit/minting Overview Minting is the process of creating new NFT tokens within your collection. CreateKit provides a unique two-phase minting system that optimizes for gas efficiency and user experience. Minting Phases Phase 1: Deployment & First Mint The first mint operation is special - it deploys the collection contract and mints the first token in a single transaction: Phase 2: Regular Minting After deployment, subsequent mints are simpler and only require the standard parameters: Token Standards CreateKit supports both ERC721 and ERC1155 standards with different minting behaviors: Pricing and Payment Fixed Pricing Free Minting Dynamic Pricing Whitelist Minting CreateKit supports Merkle tree-based whitelisting for exclusive minting: Setting Up Whitelist Whitelist Minting Minting Limits and Controls Per-Wallet Limits Time-Based Controls Metadata Handling Automatic Metadata CreateKit can automatically generate metadata based on collection settings: Custom Metadata Batch Minting For ERC1155 collections, you can efficiently mint multiple tokens: Error Handling Gas Optimization Efficient Minting Patterns Gas Price Management Monitoring and Analytics Mint Event Tracking Real-time Monitoring Best Practices - Provide clear feedback during minting process - Show estimated gas costs upfront - Implement proper loading states - Handle errors gracefully with user-friendly messages - Always validate parameters before transactions - Implement proper error handling - Use appropriate gas limits and prices - Test thoroughly before deploying production contracts Next Steps Learn how minting generates rewards for participants See complete minting implementation examples --- ## Quick Start Source: https://docs.b3.fun/createkit/quickstart Overview This guide will walk you through creating your first NFT collection using CreateKit. You'll learn how to: - Create collection metadata and signatures - Deploy a collection - Mint your first NFT - Track rewards This quickstart uses B3 Mainnet. Make sure your wallet is funded with ETH for gas fees. Step 1: Basic Setup First, let's set up the basic infrastructure: Step 2: Create Collection Metadata Define your collection parameters: Step 3: Generate Signatures Create the required signatures for deployment: Step 4: Submit to Storage Store your collection metadata off-chain: Step 5: Deploy and Mint Now comes the exciting part - deploying your collection and minting the first NFT: Step 6: Verify Deployment Let's verify that everything worked correctly: Step 7: Track Rewards Check the rewards generated from your mint: Complete Example Here's the complete quickstart script: Run the Example Save the complete example as and run it: Expected Output When you run the quickstart script, you should see output similar to: What's Next? Congratulations! You've successfully created your first NFT collection with CreateKit. Here are some next steps to explore: Learn advanced collection configuration options Explore different minting scenarios and options Implement whitelist-based minting Deep dive into the reward distribution system Troubleshooting - Ensure you have sufficient ETH for gas - Check that all signatures are valid - Verify collection parameters are within limits - Check your internet connection - Verify the collection metadata format - Ensure the creator signature is valid - The predicted address is already taken - Try changing collection parameters slightly - Use a different creator or gameOwner address --- ## Rewards System Source: https://docs.b3.fun/createkit/rewards Overview CreateKit features an innovative reward system that distributes a portion of each mint's value to various participants in the ecosystem. This creates aligned incentives and ensures all contributors benefit from successful collections. Reward Structure Default Distribution | Recipient Type | Default Share | Description | |----------------|---------------|-------------| | Creator | 40% | Collection originator who created the collection | | First Minter | 30% | User who triggers the initial deployment and first mint | | Game Owner | 20% | Platform or game that integrates the collection | | Platform | 10% | BaseMint protocol fee | Reward rates are configurable by the protocol administrator and may vary between deployments. How Rewards Work 1. Mint Payment: User pays the mint price for tokens 2. Reward Calculation: A percentage of the payment is allocated to the reward pool 3. Distribution: Rewards are distributed according to the configured rates 4. Accumulation: Rewards accumulate in the escrow contract until claimed Reward Tracking Setting Up Reward Tracking Collection-Level Rewards Track rewards accumulated for an entire collection: Individual Recipient Rewards Track rewards for specific participants: All Recipients for a Collection Reward Events Tracking Reward Distributions Real-time Reward Monitoring Reward Withdrawal Individual Withdrawals Batch Withdrawals Reward Analytics Portfolio Overview Performance Metrics Advanced Reward Features Custom Reward Rates Reward rate configuration is typically restricted to protocol administrators. Recipient Management Integration Best Practices User Interface Integration Automated Reward Claiming Troubleshooting - Verify the collection has received mints after deployment - Check that you're querying the correct recipient type and address - Ensure the collection was created with proper signatures - Confirm you have available rewards to withdraw - Check that you have sufficient gas for the transaction - Verify you're using the correct recipient type for your role - Check the current reward rates configuration - Verify the mint price and volume calculations - Ensure you're using the correct escrow contract address Next Steps Learn how to manage collection metadata with BaseMint storage See complete implementation examples including reward tracking --- ## Storage Service Source: https://docs.b3.fun/createkit/storage Overview The BaseMint Storage Service provides a reliable, scalable solution for storing and managing NFT collection metadata. It offers deterministic addressing, CDN-backed delivery, and seamless integration with the CreateKit ecosystem. Storage Architecture How Storage Works Collection metadata and creator signatures are submitted to the storage service The service validates signatures and stores metadata with a deterministic address Metadata is distributed via CDN for fast, global access Collections are discoverable via predicted addresses before deployment Key Features Collections have predictable addresses for marketplace integration Cryptographic verification of collection authenticity Fast, reliable metadata delivery worldwide Track and manage collections by integration partners Storage Service Setup Basic Configuration Environment Configuration Submitting Collections Basic Collection Submission Batch Collection Submission Querying Collections Basic Queries Advanced Filtering Search Functionality Referrer Management Registering as a Referrer Managing Referrer Collections Collection Management Retrieving Collection Data Updating Collections Collection updates are limited to specific fields and may require additional authentication. Deleting Collections Metadata Management Custom Metadata URIs Asset Management Error Handling Comprehensive Error Handling Service Health Monitoring Best Practices Performance Optimization - Cache frequently accessed collection data - Use ETags for conditional requests - Implement client-side caching strategies - Consider Redis for server-side caching - Group multiple operations when possible - Use bulk endpoints for efficiency - Implement proper queue management - Handle rate limiting gracefully Security Considerations Integration Examples React Integration Next Steps See complete implementation examples using the storage service Learn comprehensive error handling patterns --- ## Whitelist Management Source: https://docs.b3.fun/createkit/whitelist Overview CreateKit supports sophisticated whitelist management using Merkle trees for gas-efficient verification. This allows you to create exclusive minting experiences for specific addresses while maintaining scalability and security. Whitelist Basics How Whitelists Work 1. Off-chain Generation: Create a Merkle tree from whitelisted addresses 2. On-chain Storage: Store only the Merkle root in the smart contract 3. Proof Verification: Users provide a Merkle proof when minting 4. Gas Efficiency: Verification costs are constant regardless of whitelist size Support thousands of addresses with minimal gas costs Cryptographically guaranteed address verification Easy to generate and update whitelist configurations Verifiable on-chain without revealing the full list Setting Up Whitelists Basic Whitelist Creation Advanced Whitelist Configuration Collection Integration Whitelist-Enabled Collection Hybrid Access Models Whitelist Verification Generating Proofs Batch Proof Generation Minting with Whitelists Basic Whitelist Minting Advanced Whitelist Minting Frontend Integration React Hook for Whitelist Status Whitelist Status Component Multiple Whitelists Tiered Whitelist System Time-Based Tier Access Whitelist Utilities Whitelist Analysis Whitelist Validation Best Practices - Validate all addresses before creating whitelist - Use checksummed addresses when possible - Store Merkle proofs securely - Verify proofs client-side before transactions - Consider whitelist size vs. gas costs - Optimize Merkle tree construction - Batch operations when possible - Pre-generate proofs for better UX Troubleshooting - Verify the address is exactly as stored in the whitelist - Check that the Merkle root matches between contract and client - Ensure proof generation uses the same whitelist data - Verify address case sensitivity - Confirm the address exists in the whitelist - Check for duplicate addresses in whitelist - Validate address format (0x prefix, 42 characters) - Ensure WhitelistManager is properly initialized - Verify collection has isWhitelistEnabled set to true - Check that whitelistMerkleRoot is set correctly - Ensure minting phase allows whitelist access - Test with known whitelisted addresses first Next Steps Learn how to store and manage whitelist data with BaseMint storage See complete whitelist implementation examples --- ## B3 Data API Reference Source: https://docs.b3.fun/data/api-reference/index Use the generated OpenAPI reference for endpoint-level request and response details. Download the raw OpenAPI spec for B3 transactions, contracts, blocks, and chain data. Identity and profile aggregation for B3 Global Accounts and connected wallets. --- ## B3 Data API Source: https://docs.b3.fun/data/api-reference/introduction - Available to builders for free. - Intelligent multi-chain routing. - Cached at the edge for speed. Browse the REST API reference. Data Sources & Intelligence Direct access to indexed blockchain data from Blockscout explorers across all B3 chains, providing transaction history, contract interactions, and block data. Enhanced with Thirdweb's powerful data infrastructure for NFT metadata, contract ABIs, and smart contract analytics. Our API automatically routes requests to the optimal data source and chain, ensuring fast response times and data accuracy. Merged data from all B3 ecosystem chains provides a comprehensive view of cross-chain activities and assets. Authentication No authentication required for public endpoints. Simply make requests to start accessing B3 ecosystem data immediately. --- ## B3 Profiles API Source: https://docs.b3.fun/data/profiles/index Check out the profiles API reference Overview The B3 Profiles service serves as a data API for resolving decentralized user identities across the EVM ecosystem. It aggregates profile data from multiple sources and protocols, providing developers with a single API endpoint to access comprehensive user information and social context. Key Features Combines data from Basement, ENS, Thirdweb Social, and other Web3 identity providers Fetches social profiles from ENS, Lens Protocol, and Farcaster networks Uses Cloudflare KV storage for efficient data caching with configurable TTL Allows users to set preferred profile sources via cryptographic signatures Supported Data Sources - ENS (Ethereum Name Service) - Lens Protocol - Farcaster - B3.ID - Basement profiles API Endpoints Check out the API reference for more details. Profile Lookup Retrieve aggregated profile information for any wallet address or username. Set Profile Preferences Allow users to specify their preferred profile source through cryptographic signatures. Custom Display Names Enable users to set custom display names that override all other sources. Response Format The service returns a unified profile object that combines data from all sources: Use Cases Provide rich context about users during wallet connection, showing their social identity and Web3 reputation across platforms. Display comprehensive player profiles in games, including ENS names, social handles, and cross-platform identities. Enhance trading interfaces by showing trader identities from Lens, Farcaster, and ENS instead of just wallet addresses. Build better community tools by aggregating user identities from multiple Web3 social platforms. Example Usage Basic Profile Lookup ENS Name Resolution Setting User Preferences Performance & Caching - Cache Duration: 1 hour for profile data - Fresh Data: Use to bypass cache - Global CDN: Powered by Cloudflare's edge network - KV Storage: Efficient key-value storage for preferences Rate Limits The service inherits Cloudflare's built-in DDoS protection and rate limiting. For high-volume applications, consider implementing client-side caching or contact the B3 team for enterprise access. Building onchain made easy Check out the API reference for more details. Comprehensive blockchain data and analytics B3 SDK for cross-chain operations and global account authentication --- ## Bridges Source: https://docs.b3.fun/ecosystem/bridges Instant, seamless bridging to B3 using funds on other popular networks. Bridge Now Instant, low-cost bridging and swapping. Powered by Reservoir Bridge Battle tested OP stack canonical bridge. Has a 7-day challenge period on withdrawals only. Bridge --- ## Indexers & Analytics Source: https://docs.b3.fun/ecosystem/data-analytics A peer-to-peer network to batch query and aggregate terabytes of on-chain and off-chain data Data Indexers Dune is a platform for building and sharing data visualizations. Data Analytics Helika provides custom game optimization through personalized insights from experienced analysts, unifying on-chain, in-game, and community data to drive growth. User Acquisition --- ## Governance Source: https://docs.b3.fun/ecosystem/governance Agora is the home of onchain governance. Governance Platforms --- ## Infrastructure Source: https://docs.b3.fun/ecosystem/infrastructure Secure your smart contracts with reliable, low-latency market data from institutional sources. Oracles Launch OP Stack, Arbitrum Orbit, ZK Stack, and Polygon CDK rollups with Caldera, your partner from development to launch, and beyond Rollup-as-a-Service The fastest multisig for onchain teams. MultiSig Pimlico provides a suite of tools and services to help you build, deploy, and manage smart accounts on Ethereum and other EVM-compatible chains. Account Abstraction Open-source, universally accessible, block explorer. B3 Mainnet Explorer --- ## B3 Open Ecosystem Source: https://docs.b3.fun/ecosystem/introduction Thinking about building your app or game on B3? Let's chat. B3 SDK Exclusively available on B3, our SDK makes it easy to create fun onchain experiences. Instant Login Instantly onboard players with embedded smart accounts—just one click and they're in the game. Know Your Player's Identity Unlock instant access to player data across the ecosystem and their onchain gamer data. Scale Your Game Deploy Onchain Leaderboards Create competitive rankings tied to real gameplay data and cross-game achievements. Create Custom Achievements Create onchain achievements tied to gameplay, loyalty, or community actions. Let players wear their wins across the ecosystem. Launch Instant Tournaments Spin up tournaments instantly to boost retention, drive competition, and monetize your game. Enable Wager Duels Allow players challenge each other in real-time PvP. Add wagers, XP, or prizes to every match. Create Exclusivity with Token Gating Enable users to unlock exclusive content, game modes, or perks based on NFT or token holdings. Send Onchain Notifications Trigger wallet-based alerts tied to gameplay, achievements, drops, or events to re-engage users. Unlock New Ways to Monetize Accept Payments Without Friction Enable users to make purchases with no KYC using fiat or ANY token on ANY chain. It's the easiest way to pay. Create Native Game Tokens Easily create custom tokens that power progression, rewards, or ownership—natively tied to your game logic. Turn Any Asset into a Marketplace From achievements to skins to user-generated content, turn any in-game asset into a collectible that players can trade. Data API Getting blockchain data from B3 & our appchains is easy - and free. Get access to B3 ecosystem data with our free API. We automatically merge our multiple, horizontally scaled chains, abstracting the complexity of working with multiple appchains. Build on B3 Thinking about building your app or game on B3? Let's chat! Ecosystem Tools Explore our comprehensive ecosystem of tools and services: Next.js, Unity, Unreal Engine, React, and more Blockchain infrastructure and RPC providers Cross-chain bridging solutions for B3 Tools for NFT creation, management, and trading Wallet solutions and authentication providers Data indexers, analytics, and user acquisition tools Oracles, account abstraction, multisig, and more Governance platforms and tools --- ## NFT Infrastructure Source: https://docs.b3.fun/ecosystem/nft-infrastructure NFT infrastructure enabling the next-gen of NFT products. B3 Support Access token & NFT data with ease through SimpleHash. B3 Support Frontend, backend, and onchain tools. Unity, Unreal Engine, and React Native SDKs. B3 Support Gaming SDKs --- ## Node Providers Source: https://docs.b3.fun/ecosystem/node-providers Quicknode is a blockchain infrastructure and services provider that provides easy-access to B3 mainnet B3 Support --- ## Onchain SDKs Source: https://docs.b3.fun/ecosystem/onchain-sdks Frontend, backend, and onchain tools. Unity, Unreal Engine, and React Native SDKs. B3 Support Gaming SDKs Developer tools for seamless blockchain integration: SDKs, detailed documentation, and dedicated support empower you to focus on creating engaging gameplay. B3 Support Gaming SDKs --- ## Wallets Source: https://docs.b3.fun/ecosystem/wallets Spin up embedded wallets and beautiful authentication flows for all users. Wallet SDKs Your portal to Web3. Access 100+ decentralized networks with many more on the way Wallet SDKs Frontend, backend, and onchain tools. Unity, Unreal Engine, and React Native SDKs. Wallet SDKs Openfort is a blockchain advanced platform that provides developers with advanced wallet SDK solutions, focusing on simplifying web3 game development through account abstraction technologies. Wallet SDKs --- ## Architecting the onchain economy Source: https://docs.b3.fun/index B3 is increasingly centered around B3OS: the workflow operating system used to connect wallets, smart contracts, integrations, actions, triggers, and Caddie-assisted automation. Three engines, one loop B3 is a system for shipping and scaling onchain products. B3OS powers the workflow layer, Labs ships products on top, and Holdings expands the ecosystem through strategic investments. The onchain workflow engine for apps, services, wallets, smart contracts, and automations. The product studio behind Bsmnt, HypeDuel, B3AR, XCade, AnySpend, Upside.Win, Parallel Sanctuary, B3PC, and more. Strategic investments in high-growth, cash-flowing businesses that complement B3OS and the broader B3 economy. B3 was built by a small team of former Coinbase leaders combining Web2 product discipline with onchain systems engineering. Build On B3 Use the B3 docs for protocol, SDK, and API foundations. Use each product docs site for app-specific implementation details. Workflows, actions, triggers, connectors, wallets, organizations, recipes, API routes, and Caddie. Chain setup, appchains, liquidity, tokenomics, staking, governance, and network operations. Global Accounts, CreateKit, BondKit, Game SDKs, auth, permissions, examples, and shortcuts. Indexed blockchain data and profile APIs with generated OpenAPI references. Product Docs Build, run, and operate Caddie-assisted crypto-native workflows. Payments, checkout, cross-chain routing, x402, Order API, and Platform API. Game developer launch guides and player support for accounts, wallets, rewards, and staking. AI battle gameplay, betting mechanics, HYPES, ArenaCoins, and developer notes. Iframe game integration, frontend SDK setup, backend payout flow, and testing examples. See the full product docs directory and the split between B3 foundations and product-specific docs. --- ## Product Docs Source: https://docs.b3.fun/products Product-specific guides now live in their own dedicated docs sites. Use these docs for B3 chain, protocol, data, and SDK foundations, then jump into a product site for app-specific implementation details. Workflows, actions, triggers, connectors, wallets, Caddie, and B3OS APIs. Payments, checkout, cross-chain routing, x402, Order API, and Platform API. Developer launch guides plus player help for accounts, wallets, staking, rewards, and support. AI battle gameplay, betting mechanics, HYPES, ArenaCoins, and developer notes. Iframe game integration, frontend SDK setup, backend payout flow, and testing examples. B3 chain setup, token docs, bridge docs, governance, and ecosystem APIs. --- ## $B3 Token Source: https://docs.b3.fun/protocol/b3-token Copy this address to add \$B3 to your wallet or trade on DEXs. View on B3 Explorer What is \$B3? \$B3 is the utility token that powers the entire B3 ecosystem. As the foundational token for a horizontally scaling multichain network, B3 enables governance, staking, and value across appchains and applications built on B3. A portfolio of fun B3 is not just blockchain infrastructure. We architect the onchain economy through three engines that all flow value back to \$B3 holders: - B3OS is the no-code onchain workflow platform for applications, services, smart contracts, and automations. It generates platform revenue from enterprises, builders, and crypto traders. - B3 Labs ships consumer products powered by B3OS, including Bsmnt, HypeDuel, B3AR, XCade, AnySpend, Upside.Win, Parallel Sanctuary, B3PC, and more. - B3 Holdings makes strategic investments in high-growth, cash-flowing businesses that complement the B3 ecosystem. Revenue from all three engines flows back into \$B3. Cross-chain payments & onramp. Stake to win. The hyper-casual onchain gaming platform. SDKs for bonding tokens, wagering & more. Where to buy \$B3 tokens Buy \$B3 on Coinbase Trade \$B3 on Bybit Purchase \$B3 on Gate.io Get \$B3 on KuCoin Trade \$B3 on MEXC Swap \$B3 on Aerodrome Trade \$B3 on AlienBase --- ## B3OS Source: https://docs.b3.fun/protocol/b3os This page explains where B3OS fits inside B3. For implementation details, use the dedicated B3OS docs. What Is B3OS? B3OS is the workflow operating system for crypto-native teams. It connects triggers, built-in logic, onchain and offchain actions, organization-owned wallets, encrypted connectors, execution webhooks, and Caddie-assisted workflow authoring in one product surface. Model triggers, branches, loops, reusable blocks, versioned drafts, public views, and execution paths. Use typed schemas for blockchain reads, onchain execution, integrations, messaging, utilities, and wallet operations. Create, repair, inspect, and explain workflows with an AI copilot that understands actions, triggers, templates, org knowledge, and recent run context. Where It Fits Start Building Build and run your first B3OS workflow. Learn workflows, triggers, nodes, connectors, wallets, runs, props, and expressions. Start from wallet alerts, scheduled market checks, x402 calls, human approval, and webhook flows. Integrate through API keys, service accounts, workflow runs, connectors, hooks, and public execution surfaces. --- ## Brand Kit Source: https://docs.b3.fun/protocol/brand-kit ✦ SERIOUS PLAY ✦ ONCHAIN ARCHITECTS ✦ Everything here is cleared for partner, press, and ecosystem use — take what you need without asking first. Every preview links the real file on , so what you download is what we use. The CDN serves files inline, so open the link and save from there. Brandmark The full lockup: wordmark, positioning line, and the stack it names. Use it when B3 needs to introduce itself — a title card, a deck cover, a partnership announcement. Everywhere else, the wordmark alone is enough. SVG Logo The B3 wordmark. Use the SVG wherever you can — the PNG is a fallback, not a preference. For navy, black, and photography. SVG App icons, avatars, tiles — anywhere the mark needs its own container. PNG The rounded mark, for round frames and social avatars. SVG Coin PNG Working on a light surface and need the wordmark in brand blue, or on a dark one and need a knockout we don't list here? Ask — we'd rather send the right file than watch one get recoloured by hand. Using the mark Keep clear space of at least 25% of the mark's height on all four sides. Nothing enters that box — no type, no rules, no other logos, no image edge. Light mark on navy, blue, black, or photography. Blue or navy mark on white and near-white. If a background sits in between, put the mark in its own tile rather than dropping it straight on. No stretching, rotating, recolouring, outlining, drop shadows, or re-typesetting the name in another face. The mark is a fixed shape in a fixed set of colours. All caps, no space. "B3 Labs" for the company; "B3" for the network and the token. Not "b3", not "B-3". Colours One blue, quiet everything else. B3 blue is the only accent — the neutrals do the structural work, and a surface where three things compete for attention has no accent at all. Primary actions, links, live state. Dark surfaces, headings on light. The signature canvas — b3.fun's own stage. Panels and dividers on gray. Secondary text and quiet links. Captions, labels, table headers. Typography Interface, headings, body, and data. 55 Roman for text, 65 Medium for anything that carries weight. Tracking stays at 0 — only small uppercase labels get wide tracking. Licensing — Linotype Technical tags, diagram labels, small system text. Used sparingly, never for body copy. Licensing — Erkin Karamemet Both are commercially licensed, so we don't redistribute the font files — license them directly from the foundries above. If you can't, this stack degrades honestly: still serves the previous typefaces (Neue Montreal, Calibre, Pack). It is kept alive for older properties — don't wire it into anything new. Assets The dimensional B3 — extruded, isometric, and coined. These carry the brand where a flat wordmark can't. PNG Dark Light WEBP Backgrounds Full-bleed brand surfaces for slides, covers, and headers. Download Download Download More in the same set: b3-bg-3.png and b3-bg-5.png. Motion Movement is part of the brand — systems coming online, not decoration. Fast state changes, subtle transitions, no bounce, and always respect . Download Download Download The full-length brand background loop is a large file — link it rather than embedding it: b3-bg-animation.mp4 (~17 MB). Co-branding Partnership lockups follow one shape: each mark in its own dotted ring, separated by , at equal weight. Nobody's logo gets top billing. Download Download Download Contribute to the B3 brand Let's build B3 together — we welcome creators, artists, developers, and everyone else who wants to make something with it. Reach out if you've built something for the B3 community, or if you need an asset that isn't here. --- ## Bridge to B3 Source: https://docs.b3.fun/protocol/bridge Cross-chain bridge with instant deposits and withdrawals Bridge from any EVM chain & Solana to B3 OP Canonical Bridge with 7-day withdrawal period Direct contract interaction for advanced users Cross Chain Bridge Instant Deposits Instant Withdrawals Low Fee Connect your wallet and bridge from major EVM networks in & out of B3. Visit basement.fun/bridge to access the bridge interface. Connect your wallet using MetaMask, Coinbase Wallet, or other supported wallets. Choose the source network and the amount of funds you want to bridge to B3. Confirm the transaction and you'll receive bridged funds in under a minute. Your funds will appear in your B3 wallet within 60 seconds. Start bridging your assets to B3 with instant deposits and withdrawals Instant Bridge Instant Deposits Instant Withdrawals Low Fee Easily bridge from any EVM chain & Solana to B3 with Relay. Visit relay.link to access the Relay bridge interface. Connect your wallet to start the bridging process. Enter the amount of ETH you want to bridge to B3. Confirm the transaction and you'll receive bridged funds in under a minute. Relay supports bridging from multiple chains including Solana. Bridge from any EVM chain and Solana to B3 instantly Native Bridge Base to B3 7-Day Withdrawals No Fees Easily bridge from Base to B3 using the official OP Stack canonical bridge! Withdrawals from B3 back to Base have a 7-day challenge period for security. Use third-party bridges for instant withdrawals. Go to bridge.b3.fun to access the official bridge. Connect your wallet to the bridge interface. Select whether you want to: - Deposit: Bring funds from Base → B3 - Withdraw: Bridge back from B3 → Base Enter the amount of ETH you want to bridge. Click "Deposit" and confirm the transaction in your wallet. Deposits to B3 are instant, but withdrawals take 7 days for the challenge period. Use the battle-tested OP Stack canonical bridge Native Transfer (Bridge Contract) Instant Deposits 7-Day Withdrawals No Fees Send Base ETH through the bridge contract. Transfer Base ETH to the following bridge address on Base Mainnet: This method is for advanced users only. Make sure you're sending from Base Mainnet to avoid losing funds. When you send ETH to this address from Base, it will automatically appear in your wallet on B3. This is a direct contract interaction method. 1. Ensure you're on Base Mainnet in your wallet 2. Send ETH to the bridge contract address above 3. Wait for confirmation - your funds will appear on B3 automatically 4. Check your B3 wallet - switch to B3 network to see your bridged ETH Double-check you're on Base Mainnet before sending. Sending from other networks may result in lost funds. --- ## Bylaws Source: https://docs.b3.fun/protocol/bylaws 1. Mission The mission of the Foundation is to foster, develop, authorize and/or govern the B3 Protocol. This includes but is not limited to: - Enabling the development of technical improvements and feature development to maintain and increase B3 capabilities to provide low cost, high throughput gaming chain scaling solutions with best-in-class user experience. - Fostering ecosystem growth through strategic grants to align with partner projects including, but not limited to, infrastructure providers, application developers, artists, creators, brand partnerships, creative studios, and strategic growth partners. - Organizing educational initiatives and both participating in and hosting events to increase awareness of and promote B3 technology and ecosystem. 2. Defined Terms The account that contains Foundation assets (as well as other assets contributed to or acquired by the Administrative Budget Wallet), which will be utilized by the Foundation for purposes of operational and administrative costs as well as B3 ecosystem growth. Collectively, the decentralised community of individuals that own a Token, as evidenced by the Base or B3 chains. The Constitution of the B3 DAO as available at https://docs.b3.fun/constitution, including any amendments thereto. A proposal put forth by a Tokenholder to a vote in accordance with the B3IP Process. The rules and procedures of submitting and voting on B3IPs as described in the B3 DAO Constitution, in particular "Section 2: DAO Proposals and Voting Procedures", as may be amended from time to time pursuant to an B3IP. The B3 technology suite, including the B3 chain, and any additional chains utilizing such technology. These governing bylaws of the Foundation as may be amended from time to time. The rules, regulations and laws of the Cayman Islands as may be amended from time to time. "Decentralised autonomous organisation." Has the meaning given in Section 3(b)(iv) of these Bylaws. Player1 Foundation, a Cayman Islands foundation company. The Memorandum and Articles of Association (as may be amended, revised and substituted from time to time). The director(s) of the Foundation, which have certain powers and duties pursuant to Cayman Islands Law and as further described in the Foundation Articles and the Bylaws. The supervisor of the Foundation, which has certain powers and duties pursuant to Cayman Islands Law and as further described in the Foundation Articles. The council formed in accordance with the B3 DAO Constitution. The Security Council is a multi-member committee which has been delegated the authority by the Foundation to engage in Emergency Actions and Non-Emergency Actions as described in the B3 DAO Constitution, and is otherwise tasked with ensuring that B3IPs are in compliance with the B3 DAO Constitution. The governing token of the B3 DAO, known as $B3, represented on the Base and B3 chains. Any holder of a Token. 3. Voting Matters 3.1 Tokenholder Authority Pursuant to the B3 DAO Constitution, the Foundation Articles, and these Bylaws, the Tokenholders may approve Constitutional B3IPs and Non-Constitutional B3IPs (each as defined in the B3 DAO Constitution) in order to: (i) modify the text or procedures of the B3 DAO Constitution; (ii) install or modify the software on the B3 Protocol; (iii) approve funding requests from the DAO Treasury (as defined in the B3 DAO Constitution); (iv) appoint and remove members of the Security Council in accordance with the B3 DAO Constitution; and (v) approve any other action in accordance with the B3 DAO Constitution, the Foundation Articles and these Bylaws. 3.2 Foundation Director Authority The Foundation Director(s) shall engage in any activity which, in their reasonable discretion, does not contradict the terms set forth in any B3IP approved by Tokenholders, the B3 DAO Constitution, these Bylaws, or the Foundation Articles, including but not limited to the following actions: (i) approve transactions from the Administrative Budget Wallet; (ii) coordinate emergency operations with the Security Council on behalf of the B3 DAO or the Foundation; (iii) make changes to these Bylaws if the Foundation Directors believe such changes would improve the Foundation Directors' ability to fulfill their obligations (the "Amendment Authority"); and (iv) call and hold emergency meetings ("Emergency Meetings") to enable the Foundation Directors and the Security Council to rapidly respond to an imminent security threat to the B3 DAO, any protocol utilizing the Token, the Tokenholders, or the Foundation, and the same rules that apply to Foundation Directors meeting in accordance with the Foundation Articles will apply to Emergency Meetings, except that there is no quorum requirement for an Emergency Meeting. 4. Proposal Phases, Requirements and Structure 4.1 B3 DAO Constitution Application The provisions set out in Section 2 of the B3 DAO Constitution shall apply. 4.2 Foundation Director Rejection If, following the approval of a B3IP by the B3 DAO, a majority of the Foundation Director(s) acting in the best interests of the Foundation reasonably determine that such B3IP, if implemented, would: (A) compromise the Foundation Director(s)' fiduciary duties as they are owed to the Foundation; (B) be in violation of these Bylaws, the Foundation Articles, the B3 DAO Constitution, the B3IP Process, any statutory requirements of Cayman Islands Laws or the laws or regulations of any other applicable jurisdiction; (C) cause the Foundation to be in breach of any contracts, agreements or any other arrangements; and/or (D) be against the best interests of the Foundation, such Foundation Director(s) may notify the Security Council of their obligations under the B3 DAO Constitution to undertake an Emergency or Non-Emergency Action, or take such other steps as are required to reject such B3IP. 5. Relationship between the Foundation and the Tokenholders 5.1 Representation The Tokenholders are represented by the Foundation, which represents the Tokenholders' interests in connection with contractual and legal processes, including regulatory compliance and those other matters set forth in the Foundation Articles. 5.2 Service Providers The Foundation has engaged with certain third parties to provide services as the Foundation Director(s) and Foundation Supervisor, as required by Cayman Islands Law. In accordance with the terms of the Foundation Articles and these Bylaws, and subject to Cayman Islands Law, the Foundation Director(s) and Foundation Supervisor are required to act at the direction of the Tokenholders in respect of certain matters. 5.3 Resources and Authority The Tokenholders shall ensure that the Foundation has sufficient authority and resources, including funding, to execute upon the Foundation's mandate, meet the Foundation's obligations under applicable law, and satisfy the Foundation's contractual obligations entered into in accordance with the Foundation Articles or these Bylaws. 5.4 Director Authority The Foundation's Directors are authorised to take any actions reasonably necessary on behalf of the Foundation to give effect to a vote of the Tokenholders including passing any director resolutions to memorialise such vote. 5.5 Conflicts and Fiduciary Duties To the extent there is ever a conflict between the provisions of the Bylaws and the Foundation Articles, the Foundation Articles will prevail. Foundation Directors are not fiduciaries for the Tokenholders. 6. Dispute Resolution 6.1 Notice Requirements Should a controversy, dispute or claim arise out of or in relation to these Bylaws ("Dispute"), the Foundation, the Directors, the Supervisor or the Tokenholders (as appropriate) must give 30 days' notice of such Dispute to the relevant party/ies (the "Notice of Dispute"). Should the Dispute not be resolved at the expiration of 30 days after service of the Notice of Dispute, the relevant party may commence arbitration proceedings in accordance with 6(b) below. In any dispute involving the actions of the Foundation Directors or the Supervisor, the Foundation, and not the Foundation Directors or Supervisor, shall be party to the arbitration proceedings. In any dispute involving the actions of the Directors, the Supervisor may commence arbitration proceedings against the Directors in accordance with Section 6(b) below. 6.2 Arbitration Process Should the Dispute remain at the expiration of 30 days after service of the Notice of Dispute, the Dispute shall be settled by arbitration administered by the Cayman International Mediation and Arbitration Centre ("CI-MAC") in accordance with the CI-MAC Arbitration Rules (the "Arbitration Rules") in force as at the date of these Bylaws, which Arbitration Rules are deemed to be incorporated by reference to these Bylaws, and governed by the Arbitration Act (as amended) of the Cayman Islands. - Arbitrator: All disputes shall be heard by a single arbitrator to be appointed in accordance with the Arbitration Rules - Governing Law: The law of the arbitration shall be the law of the Cayman Islands - Language: The language of the arbitration shall be English - Seat: The arbitration shall be seated in George Town, Grand Cayman, Cayman Islands The arbitration shall be commenced following the expiration of 30 days after service of the Notice of Dispute and the aggrieved party's notification to the other of the particulars of the controversy or claim along with the aggrieved party's proposed arbitrator obtained from a list of potential arbitrators maintained by CI-MAC. Where the notified party does not agree with the choice of arbitrator or if no agreement on the choice of arbitrator can be reached within thirty (30) days, then an arbitrator will be one chosen by CI-MAC having reasonable experience in transactions of the type provided for in these Bylaws. - Award Timeline: The arbitrator shall render the award within three (3) months of the commencement of the arbitration, unless such time limit is extended by the arbitrator - Cost Allocation: Prior to the issue or delivery of arbitral award, each party will bear its own costs in respect the arbitration, following which the prevailing party shall be entitled to reasonable attorney's fees, costs, and necessary disbursements in addition to any other relief to which such party may be entitled An award by the arbitrator shall be final and conclusive and binding upon the parties and shall not be subject to further appeal. Each party may enforce any award granted in accordance with this Section 6 in any court of competent jurisdiction. The arbitrator shall be required to provide in writing to the parties the basis for the award or order of such arbitrator, and all hearings shall be recorded, with such record constituting the official transcript of such proceedings. No action at law or in equity based upon any claim arising out of or related to these Bylaws shall be instituted in any court of any jurisdiction. Each party waives any right it may have to assert the doctrine of forum non conveniens, to assert that it is not subject to the jurisdiction of such arbitration or courts or to object to venue to the extent any proceeding is brought in accordance herewith. --- ## Constitution Source: https://docs.b3.fun/protocol/constitution This document lays out the Constitution of the B3 DAO (the "Constitution"). Some of the rules and procedures of this Constitution will be enforced directly by smart contracts on a blockchain, and some will not. Actions taken under this Constitution may be on-chain or off-chain actions. On-chain actions are those that are actuated directly by the governance smart contracts of the DAO as transactions on a blockchain. Off-chain actions are those that are actuated by other means. This Constitution also includes some "recommended guidelines" which are non-binding but strongly recommended as good governance practice. This Constitution describes the procedures by which it may be amended and lays out the governance framework of the B3 DAO and the Player1 Foundation. Definitions A proposal put forth by a Tokenholder to a vote in accordance with the B3IP Process. The rules and procedures of submitting and voting on B3IPs as described in this Constitution, in particular "Section 2: DAO Proposals and Voting Procedures", as may be amended from time to time pursuant to a B3IP. The decentralized community of individuals that own a Token, as evidenced by the Base or B3 chains. Player1 Foundation property held in a governance smart contract on Base governed directly by the Tokenholders and the Security Council via onchain voting mechanisms, as entrusted by the Player1 Foundation. The governing token of the B3 DAO, known as $B3, as represented on the Base or B3 chains. Any holder of a Token. All Tokens in existence (i.e. 100,000,000,000 $B3 tokens). Section 1: Chain "administration" This Constitution describes the decision-making framework for the B3 DAO governance. The B3 Protocol has two sets of chain "administrators" who have the power to take administrative actions that change the B3 core protocol and code and/or alter any of its core parameters. With the $B3 token generation event and subsequent creation of the B3 DAO having occurred, Player1 Foundation has entrusted "administrator" privileges on B3 to both the Tokenholders and the Security Council of the B3 Protocol. In the event that a B3IP may violate any applicable law or this Constitution (as determined by the Player1 Foundation), the Player1 Foundation may notify the Security Council of its obligation to prevent such B3IP from going into effect. The "administrator" will also have the power to upgrade certain associated Layer 2 contracts. The "administrator" will control affordances on the chain such as updating the contract implementation of any of B3's core protocol contracts, and adjusting system parameters via, e.g., setter methods in the B3 Administrator precompile. Section 2: DAO Proposals and Voting Procedures The following process governs the rules and procedures by which the B3 DAO may propose, vote on and implement B3IPs. No B3IP may be in violation of applicable laws, in particular sanctions-related regulations. B3IP Process Phases The B3IP is suggested on the public forum and discussed/debated for 1 week. The B3IP should be accompanied by a poll or other method as determined pursuant to the governance process. This Phase 1 should last for a period of 1 week to allow sufficient discussion and feedback. In the event that a B3IP skips this phase, as a matter of good governance practice, it is recommended that voters consider voting to reject it. The B3IP is submitted via governance contracts on Base, with a user interface available on Agora. The B3IP proposer is required to have an address that is delegated at least 30,000,000 Votable Tokens. After 3 days, a voter distribution snapshot will be taken and the voting period will begin; this gives interested parties time to discuss the B3IP and gather votes before the voter distribution snapshot is taken. Each B3IP must be labeled as Constitutional or Non-Constitutional. During this Phase 3, the B3 DAO will be able to vote directly on-chain through Base. A successful vote requires: Constitutional B3IPs: - Proposals pass if they reach 5% of all Votable Tokens voting "yes" (approval quorum) - At least 55% of votes cast are "yes" votes (approval threshold) Non-Constitutional B3IPs: - Proposals pass if they reach 3% of all Votable Tokens voting "yes" (approval quorum) - At least 50% of votes cast are "yes" votes (approval threshold) After a B3IP has passed in Phase 3, there will be a 3 day waiting period before the B3IP may be executed. This delay is intended to provide all Tokenholders the opportunity to exit the protocol if they are not happy with a governance outcome but were not previously aware of the vote or otherwise inadvertently missed during the prior phases. Except in the case of a Non-Constitutional B3IP involving the DAO Treasury (which lives on Base), after the 3 day waiting period in Phase 4 has passed, a cross-chain governor message is sent to B3 from Base, after which a B3-to-Base message is sent indicating that the B3IP was passed. The rationale behind the cross-chain message from Base to B3 is that while voting occurs on Base, the Constitutional B3IP is effectuated on B3. When this message is finalized on Base, anyone can redeem it to complete this step and initiate the next step. This step ensures that the completion of the B3 waiting period will be recognized on Base after any withdrawals initiated during or soon after the voting period have been recognized on Base. Following the completion of Phase 5, there will be an additional 7 day waiting period. This ensures that users who initiated withdrawals or other B3-to-Base messages have time to execute them on Base before the B3IP takes effect. The B3IP is fully executed and implemented. This may happen on B3 or via a transaction sent from B3 to Base. In the case of a Non-Constitutional B3IP involving the DAO Treasury, execution and implementation will occur directly on Base. This B3IP process as specified will typically require 37 days from the beginning of the temperature check in Phase 1 until a B3IP is finally executed in Phase 7 for a Constitutional B3IP, or 27 days for a Non-Constitutional B3IP. A B3IP may optionally specify further delay before its implementation. B3IP Types A Constitutional B3IP is one that relates to: - Process: Modifies the text or procedures of this Constitution - Software update: Installs or modifies software on B3 - Core: Takes any action that requires "administrator" permission on B3 A Non-Constitutional B3IP is one that is not considered a "Constitutional B3IP" including: - Funding: Requests funds/grants or otherwise proposes how to spend or allocate funds from the DAO Treasury. There are four types of Funding B3IPs: - Ecosystem Development: A B3IP allocating DAO Treasury funds to support game developers, community initiatives or marketing campaigns to drive adoption of the B3 Protocol - Grant Programs: A B3IP designing and approving funding mechanisms for developers or other contributors building on the B3 Protocol - Game Publishing and Promotions: A B3IP determining games to onboard onto the B3 Protocol publisher stack or promote on platforms - Strategic Partnerships: A B3IP approving collaborations with external organizations to expand the reach and utility of the B3 Protocol - Informational: Provides general guidelines or information to the community but does not otherwise propose a new feature or update Recommended Guidelines - DAO members should vote against any B3IP that is incorrectly labeled. A B3IP should include: - Abstract: Two or three sentences that summarize the B3IP - Motivation: A statement on why the B3 DAO should implement the B3IP - Rationale: An explanation of how the B3IP aligns with the B3 DAO's mission and values - Key Terms (optional): Definitions of any terms within the proposal that are unique to the proposal, new to the B3 DAO, and/or industry-specific - Specifications: A detailed breakdown of the platforms and technologies that will be used - Risks and Security: A detailed breakdown of the potential security, technical, legal, reputational and other applicable risks - Steps to Implement: The steps to implement the B3IP, including associated costs, manpower, and other resources for each step where applicable. For the avoidance of doubt, any B3IPs involving transactions with third parties (such as grants) will need to ensure that applicable legal documentation and procedures are also included - Timeline: Relevant timing details, including but not limited to start date, milestones, and completion dates - Overall Cost: The total cost to implement the B3IP - The B3IP author can add additional fields to any template if necessary to fully communicate the intentions, specifics and implications of the B3IP Resubmitted B3IPs should also include: - A link to the original B3IP - Reasons such original B3IP was not approved - Changes that have been made and why it should now be approved - Any additional fields to any template if necessary to fully communicate the changes made and the intentions, specifics and implications of such resubmitted B3IP Section 3: The Security Council The Security Council is a committee of 5 members who are signers of a multi-sig wallet, which has powers to perform certain Emergency Actions and Non-Emergency Actions, as delegated to it by Player1 Foundation, and is responsible for upholding this B3 DAO Constitution. Through the submission, approval and implementation of a Constitutional B3IP, the B3 DAO is able to modify the Security Council's powers or to eliminate the Security Council entirely. Equivalent "copies" of the Security Council multi-sig contracts exist, one on Base and another on B3. Emergency Actions The Security Council has the power to execute any software upgrade or perform other required actions with no delay in order to respond to a security emergency, should one arise (such actions, "Emergency Actions"). Performing any Emergency Action requires a 4-of-5 approval from the Security Council. The Security Council must not use its power to perform Emergency Actions except in a true security emergency, such as a critical vulnerability that could significantly compromise the integrity, confidentiality, or availability of B3. After performing any Emergency Action, the Security Council must issue a full transparency report (at an appropriate time after the security emergency has passed) to explain what was done and why such Emergency Action was justified. The B3 DAO is able to curtail or eliminate the Security Council's power to perform Emergency Actions via approval and implementation of a Constitutional B3IP. Non-Emergency Actions The Security Council may also approve and implement routine software upgrades, routine maintenance and other parameter adjustments in a non-emergency setting (such actions, "Non-Emergency Actions"), which require a 3-of-5 approval in order to take effect. Any Non-Emergency Action, after approval by the Security Council, will bypass Phases 1 to 3 of the B3IP process and instead directly go through Phases 4 to 7 of the B3IP process (as applicable), to provide a delay before any Non-Emergency Action is deployed. The Security Council may optionally specify additional delays before deployment. The B3 DAO is able to curtail or eliminate the Security Council's power to perform Non-Emergency Actions via approval and implementation of a Constitutional B3IP. Section 4: Security Council Elections The Security Council has 5 members, who are divided into two Cohorts of 2 to 3 members, who serve 18-month terms. The 'Second Cohort' will serve a 24-month term given the staggered elections but all future Cohorts going forward will serve 18-month terms. The initial Security Council Cohorts were determined by randomly splitting the 5 members into two cohorts – 2 members in the 'First Cohort' and 3 members in the 'Second Cohort'. The members of the initial Security Council Cohorts are detailed in a transparency report here. The first Security Council election process is scheduled to begin on the 15th of June 2026 or the earliest possible date. This first election replaces the 'First Cohort'. The next election replaces the 'Second Cohort' and so forth. The date chosen for the first election will form the basis for all future elections. All Security Council members are expected to serve their term until the election is complete and the new Security Council members are installed. Election Timeline The following timeline governs an election that starts at time T: Any DAO member may declare their candidacy for the Security Council, provided that a current Security Council member in one cohort may not be a candidate for a seat in the other cohort. Each DAO member or delegate may vote for their declared contender. Each token may be cast for one contender. To the extent that there are more than six contenders, each eligible contender must be supported by pledged votes representing at least 0.2% of all Votable Tokens. All candidates will cooperate with Player1 Foundation and complete the compliance process. Player1 Foundation is responsible for removing any candidates that fail the compliance process. In the event that fewer than 2 or 3 (as applicable) candidates are supported by pledged votes representing at least 0.2% of all Votable Tokens, the current Security Council members whose seats are up for election may become candidates (as randomly selected out of their Cohort) until there are 2 or 3 (as applicable) candidates. Each DAO member or delegate may vote for any declared candidate. Each token may be cast for one candidate. The process for replacing the cohort of Security Council members with the 2 or 3 (as applicable) candidates who received the most votes will be activated. It may take several days until the new Security Council members are installed. Player1 Foundation is allocated 14 days for the Compliance process and it should be executed between the Nominee selection and Member election. Player1 Foundation has flexibility to update its compliance policy for every new election. Furthermore, Player1 Foundation maintains the right to issue new procedures and guidelines for off-chain components of the Security Council election. All efforts should be made by Player1 Foundation to ensure an orderly, fair, and transparent election. Best Practices and Guidelines As a matter of best practice for maintaining an independent Security Council, no single organization should be overly represented in the Security Council. In particular, there should not be more than 1 candidate associated with a single entity or group of entities being elected to the Security Council, thereby ensuring that there will be no single entity or group of entities able to control or even veto a Security Council vote. Furthermore, no candidate with conflicts of interest that would prevent them from acting in the best interests of the B3 DAO, B3 Protocol and/or Player1 Foundation should be elected to the Security Council. Potential conflicts of interest could be, but are not limited to, affiliations with direct B3 competitors, proven histories of exploiting projects and others. The DAO may approve and implement a Constitutional B3IP to change the rules governing future Security Council elections, but the B3IP process may not be used to intervene in an ongoing election. Security Council members may only be removed prior to the end of their terms if at least 3 of the Security Council members vote in favor of removal. The seats of Security Council members who have been removed prior to the end of their respective terms shall remain unfilled until the next election that such seats are up for appointment, unless otherwise replaced prior to such next election by a vote of at least 3 of the Security Council members, in which case such seat shall be up for appointment at the next such election. The Security Council may not re-appoint a removed member and they can only be re-elected via the election voting system. --- ## Governance Platforms Source: https://docs.b3.fun/protocol/governance-platforms https://gov.b3.fun, powered by Agora https://forum.b3.fun https://discord.gg/b3dotfun Caution Stay safe! Only use the official links listed above. Be aware that scammers may try to impersonate B3 team members or delegates. Remember: - Never share your seed phrase or private keys - Never give out personal information - The real B3 team will never DM you first - When in doubt, visit our Discord and ask the community We're here to help - join our Discord server if you have any questions or concerns! --- ## Cross-Chain Liquidity Source: https://docs.b3.fun/protocol/liquidity Explore B3's multichain ecosystem on explorer.b3.fun The Problem Appchains, L2s, and L3s have isolated liquidity, making it annoying to build experiences without having to bridge assets across chains. Each chain maintains isolated pools, limiting depth and increasing slippage. Builders must integrate with dozens of chains individually. Users manually bridge assets and manage multiple wallets. Assets locked on specific chains can't access other opportunities. Access Liquidity Across Chains Powered by our product, AnySpend, operates at the client execution layer, sitting between user intent and blockchain execution: How It Works 1. Deposit from any chain: Accepts tokens from most chains 2. Intent-Based: Users express what they want, not how to achieve it 3. Route Discovery: Finds optimal paths across all supported chains 4. Atomic Execution: Transactions execute atomically or fail gracefully 5. Unified Experience: Complex operations appear as single transactions Supported Chains AnySpend provides universal chain support: - EVM Chains: Most EVM chains, including Ethereum, Polygon, Arbitrum, Base, BSC, Avalanche - Solana: Full integration with Solana's ecosystem - B3 Ecosystem: Native integration with B3 and game chains Next Steps Get started with the AnySpend SDK. Learn how to integrate AnySpend. Explore the complete API documentation. Connect with other builders. --- ## Connect to B3 Source: https://docs.b3.fun/protocol/network-setup Using B3 with Your Wallet It's easy to connect with any Ethereum wallet including MetaMask, Coinbase Wallet, Rainbow, and more. These buttons work with MetaMask and other Web3 wallets. They'll automatically add the network configuration or switch to B3 if it's already added. Using B3 Explorer Recommended Use Chainlist to add B3 to your wallet The fastest way to add B3 to your wallet: Go to explorer.b3.fun and click "Add B3 Chain" Connect your wallet (MetaMask, Coinbase Wallet, etc.) Click "Add to Wallet" for B3 Mainnet B3 will be automatically added to your wallet with the correct configuration The fastest way to add B3 to your wallet: Go to chainlist.org and search for "B3" Connect your wallet (MetaMask, Coinbase Wallet, etc.) Click "Add to Wallet" for B3 Mainnet B3 will be automatically added to your wallet with the correct configuration If you prefer to add B3 manually, use the network details below: Network Details: B3 Mainnet configuration Wallet-Specific Instructions MetaMask Click the MetaMask extension in your browser Click the network dropdown at the top and select "Add network" Click "Add a network manually" at the bottom Fill in the B3 network information See the complete B3 Mainnet configuration Click "Save" and MetaMask will automatically switch to B3 You're now connected to B3! You'll see "B3 Mainnet" in your network dropdown. Coinbase Wallet Launch the Coinbase Wallet browser extension Go to the Settings tab and click Networks Click the plus sign (➕) in the top right to Add custom network In the Add custom network dialog, enter the B3 mainnet information: See the complete B3 Mainnet configuration for copyable values Click "Save" to add B3 to your available networks Coinbase Wallet will automatically detect that the native token is ETH Rainbow Wallet Launch Rainbow wallet on your mobile device or browser extension Tap the profile icon and go to Settings → Networks Tap "Add Custom Network" and enter B3 details See the complete B3 Mainnet configuration for copyable values Save the configuration and switch to B3 Mainnet B3 Mainnet Configuration Complete configuration details for B3 Mainnet: Network Name: Chain ID: RPC URL: Explorer URL: Native Token: Troubleshooting - Double-check the Chain ID (8333 for mainnet) - Ensure the RPC URL is correct: - Try refreshing your wallet or restarting the browser - Verify you're connected to the correct B3 network - Check that you have sufficient ETH for gas fees - Ensure the contract address is valid on B3 - B3 typically processes transactions in 1-2 seconds - If experiencing delays, check the B3 network status - Consider adjusting gas price if needed - Import token contracts manually using the B3 Explorer - Ensure you're viewing the correct network in your wallet - Some tokens may need to be manually added to your wallet's token list --- Always verify that users are connected to the correct B3 network before executing transactions. The Chain ID for B3 Mainnet is 8333. Ready to start building on B3? Your wallet is now configured! Check out our SDK documentation to begin integrating B3 into your application. --- ## Horizontally Scaling AppChains Source: https://docs.b3.fun/protocol/scaling Explore B3's multichain ecosystem on explorer.b3.fun The Scaling Revolution Traditional blockchain scaling has focused on making single chains faster. B3 takes a different approach: horizontal scaling through purpose-built appchains that work together as a unified ecosystem. Making one chain handle more transactions per second Creating specialized chains for specific applications Why Horizontal Scaling Matters Rather than forcing all applications to compete for the same blockchain resources, horizontal scaling allows each app, game, or enterprise to have their own optimized execution environment. The Multi-Chain Advantage Each appchain can be customized for its specific use case - gaming chains for zero-fee gameplay, DeFi chains for high-throughput trading. No more competing for block space. Each application gets dedicated resources and can scale independently. Problems on one appchain don't affect others, providing better security and reliability for the entire ecosystem. Despite being separate chains, users experience seamless interactions across the entire B3 ecosystem. How B3 Enables Horizontal Scaling 1. Purpose-Built Appchains Every application on B3 can deploy its own dedicated chain, optimized for specific requirements: - Gaming Chains: Zero-fee transactions, instant finality, gaming-specific precompiles - DeFi Chains: High-throughput trading, MEV protection, financial primitives - Enterprise Chains: Privacy features, compliance tools, custom governance - Social Chains: Content storage, reputation systems, social graphs 2. Unified Liquidity Layer While chains scale horizontally, liquidity remains unified through AnySpend: 3. Seamless Cross-Chain Operations Users simply express what they want to do - buy an NFT, swap tokens, or make a payment. B3's infrastructure automatically finds the optimal path across all appchains. Complex multi-chain operations execute as a single transaction from the user's perspective. Real-World Benefits For Developers Deploy your own chain and never worry about network congestion affecting your users. Design token economics, fee structures, and incentives specific to your application. Experiment with new features without affecting other applications or waiting for network upgrades. Optimize transaction costs, confirmation times, and user flows for your specific use case. For Users Access all applications with the same wallet and account across the entire ecosystem. Benefit from optimized fee structures on each specialized chain. Experience near-instant confirmations on chains optimized for your use case. Enjoy the security of Ethereum settlement while benefiting from specialized chain features. Scaling in Practice Access merged data across B3 multi-chains with our free API. Gaming at Scale Gaming chains on B3 can handle: - Free-to-play mechanics with zero transaction costs - Real-time interactions with sub-second finality - Massive multiplayer events without network congestion - Cross-game asset transfers through unified liquidity Enterprise Applications Enterprise chains enable: - Private transactions for sensitive business operations - Compliance features built into the protocol layer - Custom governance models for organizational needs - Integration capabilities with existing business systems DeFi Innovation DeFi chains support: - High-frequency trading with optimized throughput - Complex financial instruments with specialized precompiles - MEV protection through custom ordering mechanisms - Cross-chain arbitrage through unified liquidity access The Network Effect As more applications deploy their own appchains, the entire B3 ecosystem becomes more valuable: 1. Increased Liquidity: More chains mean more trading opportunities and deeper liquidity pools 2. Enhanced Composability: Applications can interact across chains seamlessly 3. Reduced Costs: Shared infrastructure costs decrease as the ecosystem grows 4. Innovation Acceleration: New features on one chain can be adopted by others Getting Started with Horizontal Scaling Ready to scale horizontally? Contact our team to discuss deploying your own purpose-built appchain on B3. Access merged data across B3 multi-chains with our free API. Build on B3 with our developer tools. Choose Your Scaling Strategy Start building on the main B3 chain before scaling to your own appchain. Deploy a custom chain optimized for your specific application needs. Use the main chain for core functions and appchains for specialized features. The Future of Scaling Horizontal scaling represents the next evolution of blockchain infrastructure. By enabling unlimited parallel execution while maintaining unified user experience and liquidity, B3 creates the foundation for truly massive onchain adoption. The internet didn't scale by making single servers faster—it scaled by connecting millions of specialized servers. Similarly, blockchain will scale by connecting thousands of purpose-built chains, each optimized for specific applications while working together as a unified ecosystem. --- ## Staking $B3 Source: https://docs.b3.fun/protocol/staking-b3 Stake your $B3 tokens in our staking arena. Why Stake? Stake your B3 to play Stake to Win games, where you can win big prizes while earning $B3 yield and exclusive rewards. Participate in sweepstakes and win big prizes instead of boring yield. Contribute to B3's security and decentralization. Tokens holders can participate in governance for the B3 network. Actively participate as a staker, and have fun. Copy this address to add $B3 to your wallet or trade on DEXs. Where to buy $B3 tokens Buy $B3 on Coinbase Trade $B3 on Bybit Purchase $B3 on Gate.io Get $B3 on KuCoin Trade $B3 on MEXC Swap $B3 on Aerodrome Trade $B3 on AlienBase --- ## Tokenomics Source: https://docs.b3.fun/protocol/tokenomics Overview - Token name: B3 (Base) - Chain: Base - Total Supply: 100,000,000,000 - Decimals: 18 Utility The B3 token is the engine powering the Open Gaming ecosystem, designed to grow, scale and transform gaming by empowering players, game developers & holders. For Players: - 🥩 stake \$B3 to receive exposure to future B3 AppChains - 🥇 use \$B3 to fund & publish the games & experiences you believe in and earn rewards - 🎯 get early access to games and new features on BSMNT - ☑️ participate in governance to directly impact the future of the B3 ecosystem For Game Developers: - 🪙 apply & receive funding to develop and scale your game - 💴 earn referral rewards across all players on any Gamechain - 🚁 receive future airdrops (or grants) from infrastructure partners Additional utilities for \$B3 will be announced as they become available. Distribution and Allocation - Community & Ecosystem: This allocation is to the growth of the B3 ecosystem - for gamers, by gamers. It is to build an ecosystem belonging to those who play in it: airdrops, tournaments, playtests, community-led grants, research & development, and many others. - Foundation: This allocation will support the Player1 Foundation as it contributes to B3 and Open Gaming's vision and adoption, including strategic grants/partnerships, legal and compliance needs, audits, and other operational expenses. - Team & Advisors: This allocation is for core contributors \+ 18 advisors who represent the best of both gaming worlds - from AAA to web3. All team & advisors are subject to a 4-year vesting schedule: 1-year 25% cliff, with monthly unlocks thereafter. - Investors: This portion of B3 allocation is for investors who supported B3's development, including 100\+ angels who gathered from every corner of the industry—gaming, web3, brands, infrastructure—to b3lieve in and support B3's vision. All team & advisors are subject to a 4-year vesting schedule: 1-year 25% cliff, with monthly unlocks thereafter. Token Unlock Schedule --- ## B3 MiCAR Whitepaper Source: https://docs.b3.fun/protocol/whitepaper-mica Table of Contents 1. 1. Regulatory Disclosures 2. 2. Summary 3. 3. A. Information about the Person Seeking Admission to Trading 1. A.1. Name 2. A.2. Legal Form 3. A.3. Registered address 4. A.4. Head office 5. A.5. Registration Date 6. A.6. Legal entity identifier 7. A.7. Another identifier required pursuant to applicable national law 8. A.8. Contact telephone number 9. A.9. E-mail address 10. A.10. Response Time (Days) 11. A.11. Parent Company 12. A.12. Members of the Management body 13. A.13. Business Activity 14. A.14. Parent Company Business Activity 15. A.15. Newly Established 16. A.16. Financial condition for the past three years 17. A.17. Financial condition since registration 4. 4. B. Information about the Issuer 1. B.1. Issuer different from offeror or person seeking admission to trading 2. B.2. Name 3. 3. B.3. Legal Form 4. B.4. Registered address 5. B.5. Head office 6. B.6. Registration Date 7. B.7. Legal entity identifier 8. B.8. Another identifier required pursuant to applicable national law 9. B.9. Parent company 10. B.10. Members of the Management Body 11. B.11. Business Activity 12. B.12. Parent company business activity 5. 5. C. Information about the operator of the trading platform 6. 6. D. Information about the Crypto-Asset Project 1. D.1. Crypto-asset project name 2. D.2. Crypto-assets name 3. D.3. Abbreviation 4. D.4. Crypto-asset project description 5. D.5. Details of all natural or legal persons involved in the implementation of the crypto-asset project 6. D.6. Utility Token Classification 7. D.7. Key Features of Goods/Services for Utility Token Projects 8. D.8. Plans for the token 9. D.9. Resource Allocation 10. D.10. Planned Use of Collected Funds or Crypto-Assets 7. 7. E. Information about the Admission to Trading 1. E.1. Public Offering or Admission to trading 2. E.2. Reasons for Public Offer or Admission to trading 3. E.3. Fundraising Target 4. E.4. Minimum Subscription Goals 5. E.5. Maximum Subscription Goal 6. E.6. Oversubscription Acceptance 7. E.7. Oversubscription Allocation 8. E.8. Issue Price 9. E.9. Official currency or any other crypto-assets determining the issue price 10. E.10. Subscription fee 11. E.11. Offer Price Determination Method 12. E.12. Total Number of Offered/Traded Crypto-Assets 13. E.13. Targeted Holders 14. E.14. Holder restrictions 15. E.15. Reimbursement Notice 16. E.16. Refund Mechanism 17. E.17. Refund Timeline 18. E.18. Offer Phases 19. E.19. Early Purchase Discount 20. E.20. Time limited Offer 21. E.21. Subscription period beginning 22. E.22. Subscription period end 23. E.23. Safeguarding Arrangements for Offered crypto-assets 24. E.24. Payment Methods for Crypto-Asset Purchase 25. E.25. Value Transfer Methods for Reimbursement 26. E.26. Right of Withdrawal 27. E.27. Transfer of Purchased Crypto-Assets 28. E.28. Transfer Time Schedule 29. E.29. Purchaser's Technical Requirements 30. E.32. Placement form 31. E.33. Trading Platforms name 32. E.34. Trading Platforms Market Identifier Code (MIC) 33. E.35. Trading Platforms Access 34. E.36. Involved costs 35. E.38. Conflicts of Interest 36. E.39. Applicable Law 37. E.40. Competent court 8. 8. F. Information about the Crypto-Asset 1. F.1. Crypto-Asset Type 2. F.2. Crypto-Asset Functionality 3. F.3. Planned Application of Functionalities 4. F.4. Type of white paper 5. F.5. The type of submission 6. F.6. Crypto-Asset Characteristics 7. F.7. Commercial name or trading name 8. F.8. Website of the issuer 9. F.9. Starting date of offer to the public or admission to trading 10. F.10. Publication date 11. F.11. Any other services provided by the issuer 12. F.12. Language or languages of the white paper 13. F.13. Digital Token Identifier Code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available 14. F.14. Functionally Fungible Group Digital Token Identifier, where available 15. F.15. Voluntary data flag 16. 16. F.16. Personal data flag 17. F.17. LEI eligibility 18. F.18. Home Member State 19. F.19. Host Member States 9. 9. G. Rights and Obligations 1. G.1. Purchaser Rights and Obligations 2. G.2. Exercise of Rights and obligations 3. G.3. Conditions for modifications of rights and obligations 4. G.4. Future Public Offers 5. G.5. Issuer Retained Crypto-Assets 6. G.6. Utility Token Classification 7. G.7. Key Features of Goods/Services of Utility Tokens 8. G.8. Utility Tokens Redemption 9. G.9. Non-Trading request 10. G.10. Crypto-Assets purchase or sale modalities 11. G.11. Crypto-Assets Transfer Restrictions 12. G.12. Supply Adjustment Protocols 13. G.13. Supply Adjustment Mechanisms 14. G.14. Token Value Protection Schemes 15. G.15. Token value protection schemes description 16. G.16. Compensation Schemes 17. G.17. Compensation schemes description 18. G.18. Applicable law 19. G.19. Competent court 10. 10. H. Information on the Underlying Technology 1. H.1. Distributed ledger technology 2. H.2. Protocols and technical standards 3. H.3. Technology Used 4. H.4. Consensus Mechanism 5. H.5. Incentive Mechanisms and Applicable Fees 6. H.6. Use of Distributed Ledger Technology 7. H.7. DLT functionality description 8. H.8. Audit 9. H.9. Audit outcome 11. 11. I. Information on Risks 1. I.1. Offer-Related Risks 2. I.2. Issuer-Related Risks 3. I.3. Crypto-Assets-related Risks 4. I.4. Project Implementation-Related Risks 5. I.5. Technology-Related Risks 6. I.6. Mitigation measures 12. 12. S. Information on Sustainability Indicators 1. S.1. Name 2. S.2. Relevant legal entity identifier 3. S.3. Name of the crypto-asset 4. S.4. Consensus Mechanism 5. S.5. Incentive Mechanisms and Fees 6. S.6. Beginning of the period to which the disclosure relates 7. S.7. End of the period to which the disclosure relates 8. S.8. Energy consumption 9. S.9. Energy consumption sources and methodologies 01 Date of Notification: 2025-08-11 Regulatory Disclosures 02. Statement in accordance with Article 6(3): This crypto-asset white paper has not been approved by any competent authority in any Member State of the European Union. The person seeking admission to trading of the crypto-asset is solely responsible for the content of this crypto-asset white paper. 03. Statement in accordance with Article 6(6): This crypto-asset white paper complies with Title II of Regulation (EU) 2023/1114 and, to the best of the knowledge of the management body, the information presented in the crypto-asset white paper is fair, clear and not misleading and the crypto-asset white paper makes no omission likely to affect its import. 04. Statement in accordance with Article 6(5), points (a), (b), (c): The crypto-asset referred to in this white paper may lose its value in part or in full, may not always be transferable and may not be liquid. 05. Statement in accordance with Article 6(5), point (d): The utility token referred to in this white paper may not be exchangeable against the good or service promised in the crypto-asset white paper, especially in the case of a failure or discontinuation of the crypto-asset project. 06. Statement in accordance with Article 6(5), points (e) and (f): The crypto-asset referred to in this white paper is not covered by the investor compensation schemes under Directive 97/9/EC of the European Parliament and of the Council or the deposit guarantee schemes under Directive 2014/49/EU of the European Parliament and of the Council. Summary 07. Warning This summary should be read as an introduction to the crypto-asset white paper. The prospective holder should base any decision to purchase this crypto-asset on the content of the crypto-asset white paper as a whole and not on the summary alone. The offer to the public of this crypto-asset does not constitute an offer or solicitation to purchase financial instruments and any such offer or solicitation can be made only by means of a prospectus or other offer documents pursuant to the applicable national law. This crypto-asset white paper does not constitute a prospectus as referred to in Regulation (EU) 2017/1129 of the European Parliament and of the Council or any other offer document pursuant to Union or national law. 08. Characteristics of the Crypto-Asset B3 (Base), or \$B3 (referred to in this white paper as the "B3 Token") is an ERC-20 utility token on the Base blockchain, powering the B3 Open Gaming ecosystem. Its primary functions are to enable governance participation in the decentralized B3 Decentralized Autonomous Organization (DAO) and facilitate commerce within the ecosystem. B3 Token holders can vote on protocol decisions according to the B3 Constitution. For more information on the B3 Constitution see section G.1. These rights and associated obligations can be modified through a community governance process. The B3 Token does not represent ownership, profit-sharing, redemption rights, or claims against any legal entity or asset. 09. Utility Token Summary The B3 Token grants access to goods and services within the B3 gaming ecosystem, such as in-game items or exclusive game access, and allows participation in governance. The total supply is 100 billion B3 Tokens. Most B3 Tokens are subject to vesting schedules ranging from 3 to 48 months, which restricts their immediate transferability. The vesting schedules do not apply to the B3 Tokens which are traded/purchased on trading platforms, like centralized or decentralized exchanges. Details on circulating supply can be seen here: https://docs.b3.fun/tokenomics. 10. Key Information About the Admission to Trading Admission to trading for the B3 Token is sought to increase accessibility for European users, further decentralize the B3 DAO, and improve token liquidity. The B3 Token is planned to be available on global trading platforms, including EU trading platforms which will facilitate accessibility for EU users. A. Information about the Person Seeking Admission to Trading A.1 Name: Player1 Foundation A.2 Legal Form: Cayman foundation company (K575) A.3 Registered address: 3119 9 Forum Lane, Camana Bay, Grand Cayman, KY1-9006, KY A.4 Head office: N/A A.5 Registration Date: 2024-04-30 A.6 Legal entity identifier: N/A A.7 Another identifier required pursuant to applicable national law: 409475 A.8 Contact telephone number: \+1 917-830-4241 A.9 E-mail address: contact@b3.fun A.10 Response Time (Days): 15 A.11 Parent Company: N/A A.12 Members of the Management body: | Name | Business Function | Business Address | | :---------------- | :-------------------- | :---------------------------------------------------------------------------------- | | Glenn Kennedy | Director | 3119 9 Forum Lane, Camana Bay, P.O. Box 144, Grand Cayman, KY1-9006, Cayman Islands | | Saemi Kim | Director | 3119 9 Forum Lane, Camana Bay, P.O. Box 144, Grand Cayman, KY1-9006, Cayman Islands | | Kateryna Iegorova | Director | 3119 9 Forum Lane, Camana Bay, P.O. Box 144, Grand Cayman, KY1-9006, Cayman Islands | A.13 Business Activity: Player1 Foundation, a Cayman Foundation entity, supports the B3 protocol by facilitating the development and adoption of the B3 blockchain and other chains in the B3 ecosystem, overseeing the governance of the B3 Token, and ensuring the security of the network through the B3 Security Council. A.14 Parent Company Business Activity: N/A A.15 Newly Established: true A.16 Financial condition for the past three years: N/A A.17 Financial condition since registration: As Player1 Foundation was established only recently, a three-year historical financial data is not available. However, the Foundation is sufficiently self-funded with B3 Tokens, fiat and stablecoins. The B3 Token has been a fundamental part of the ecosystem with a fully diluted value as of June 17, 2025 of approximately \$300M USD and an all-time high exceeding \$1.9B USD. The business's upside can be driven by further adoption of digital assets and blockchain gaming as well as expanding business activities. B. Information about the Issuer B.1 Issuer different from offeror or person seeking admission to trading: true B.2 Name: Minerva Tech Foundation B.3 Legal Form: UNCO B.4 Registered address: Oceania Business Plaza, 21st Floor, Tower 1000, Isaac Hanono Missri Street, Punta Pacifica, Panama City, Panama, PA B.5 Head office: N/A B.6 Registration Date: 2024-04-23 B.7 Legal entity identifier: N/A B.8 Another identifier required pursuant to applicable national law: 25056553 B.9 Parent company: N/A B.10 Members of the Management Body: | Name | Business Function | Business Address | | :---------------------------------- | :-------------------- | :-------------------------------------------------------------------------------------------------------------- | | Diana Aidee Munoz Maclao de Camargo | Director | Oceania Business Plaza, 21st Floor, Tower 1000, Isaac Hanono Missri Street, Punta Pacifica, Panama City, Panama | B.11 Business Activity: Minerva Tech Foundation's business activity involves issuance of the B3 Token as described in this whitepaper. B.12 Parent company business activity: N/A C. Information about the operator of the trading platform N/A D. Information about the Crypto-Asset Project D.1 Crypto-asset project name: B3 D.2 Crypto-assets name: B3 (Base) D.3 Abbreviation: \$B3 D.4 Crypto-asset project description: The B3 ecosystem is comprised of the following pillars:\\ 1. B3 chain ( https://www.b3.fun/ ): an Ethereum Virtual Machine ("EVM") Layer-3 (L3) blockchain focusing on consumer-facing infrastructure, including gaming. Settling to Base (Coinbase L2), B3 offers developers an infrastructure with significantly lower gas fees and higher throughput, making fully onchain games commercially viable for the first time. By default, apps (including games) launch on B3 but they are free to spin up their own chains and B3 will support them in the process. B3 mainnet has been live since August 2024. 2. Open Gaming ( https://opengaming.b3.fun/ ): Open Gaming is at the core of B3's vision. It is a network of game- and app-chains settling to B3 that share incentives, liquidity, and tooling, all working to increase access to both users and developers. The B3 L3 is the first chain in Open Gaming, for developers who do not need their own customized chains, but will be joined by other developers who do. As of July 2025 there are five partners in the Open Gaming ecosystem with more to come. 3. Basement.fun ( https://basement.fun/ ): Basement (aka BSMNT) is the first user-facing aggregation surface product built on top of B3 by core contributors so that players can simply discover and play games. It is separate from the B3 chain website so gamers do not have to dig through technical language to start playing. Through Basement, users can start playing games immediately - via signing up for accounts, or via guest login powered by smart wallets.\\ 4. Chain and Account abstraction tech: B3 leverages account abstraction (so users log in once via their B3 accounts and play games on basement.fun without having to connect their wallets for every new game) and chain abstraction (so users can easily connect other wallets, bridge, or swap funds across many games and chains) to recreate Web2-like experiences. D.5 Details of all natural or legal persons involved in the implementation of the crypto-asset project: | Name | Business Function | Business Address | | :---------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------- | | Player1 Foundation | Player1 Foundation, a Cayman Foundation entity, supports the B3 protocol. | 3119 9 Forum Lane, Camana Bay, Grand Cayman, KY1-9006, Cayman Islands | | Minerva Tech Foundation | Minerva Tech Foundation is a Panaminian Foundation company with no ownership relationship to Player1 Foundation or NPC Labs. Minerva Tech Foundation acted as the B3 Token minting and issuing entity. | Oceania Business Plaza, 21st Floor, Tower 1000, Isaac Hanono Missri Street, Punta Pacifica, Panama City, Panama | | Minerva Operations Ltd | Minerva Operations is a BVI limited company wholly owned by Minerva Tech Foundation, which acted as the B3 Token distributing entity. | CCP Financial Consultants Limited, 2nd Floor, Ellen L. Skelton Building, Fishers Lane, Road Town, Tortola, British Virgin Islands | | NPC Labs | NPC Labs is a Delaware corporation and is a core contributor to the B3 protocol. They contribute to various areas of development for B3. They own and operate Basement.fun, a front-end website for playing B3 games. | 3500 S Dupont Hwy, Dover, DE, US 19901 | D.6 Utility Token Classification: true D.7 Key Features of Goods/Services for Utility Token Projects: The B3 Token is the engine powering B3's Open Gaming ecosystem, incentivizing growth, enabling participation, and creating a sustainable marketplace for developers and players alike. The B3 Token can be used in a number of ways, possibly including: - Governance: B3 Token holders play a key role in shaping the ecosystem via staking and governance. They can submit and vote on governance proposals that impact chain updates, fee structures, and ecosystem growth. - Ecosystem Commerce with Real-World Utility: Players could use B3 Tokens to purchase items, early access passes, or exclusive content. Utilities and features may be adjusted as the developer ecosystem matures and/or B3 Token holders approve via governance. D.8 Plans for the token: Additional utility cases for the B3 Token are in development, though plans could change depending on market or other considerations. In February 2025, the B3 Token launched with three features: 1) "Unlock" games if the user holds a certain amount of B3 Tokens, though the B3 Tokens will not be spent (no purchase); 2) "Purchase" items inside a game using B3 Tokens; 3) Airdrop recipients able to stake B3 Tokens and participate in governance. Additional features and utilities for the B3 Token are in development. D.9 Resource Allocation: N/A D.10 Planned Use of Collected Funds or Crypto-Assets: N/A E. Information about the Admission to Trading E.1 Public Offering or Admission to trading: ATTR E.2 Reasons for Public Offer or Admission to trading: 1. If the B3 Token is admitted to trade in the EU, it would make the crypto-asset more accessible to European users. A geographical distribution of B3 Token holders would also further decentralize the B3 DAO. The B3 DAO can direct the B3 ecosystem's future via governance and voting on, for example, technical improvements and grants. By opening up trading in the European markets, European users will be able to participate in shaping the future of B3. 2. Additional availability in the European markets would improve the B3 Token's liquidity on secondary markets. This could result in lower slippage, more efficient price discovery, and more reliable trade execution for end users. 3. Admission to trading of the B3 Token in the EU, demonstrates the project's readiness to meet obligations under the Markets in Crypto-Assets Regulation (MiCAR). E.3 Fundraising Target: N/A E.4 Minimum Subscription Goals: N/A E.5 Maximum Subscription Goal: N/A E.6 Oversubscription Acceptance: N/A E.7 Oversubscription Allocation: N/A E.8 Issue Price: N/A E.9 Official currency or any other crypto-assets determining the issue price: N/A E.10 Subscription fee: N/A E.11 Offer Price Determination Method: N/A E.12 Total Number of Offered/Traded Crypto-Assets: 100,000,000,000 E.13 Targeted Holders: ALL E.14 Holder restrictions: Geo-fencing against OFAC sanctioned countries is conducted on Basement.fun, a front-end webpage showcasing B3 games. Trading platforms may also have user restrictions in accordance with their user terms. E.15 Reimbursement Notice: N/A E.16 Refund Mechanism: N/A E.17 Refund Timeline: N/A E.18 Offer Phases: N/A E.19 Early Purchase Discount: N/A E.20 Time limited Offer: N/A E.21 Subscription period beginning: N/A E.22 Subscription period end: N/A E.23 Safeguarding Arrangements for Offered crypto-assets: N/A E.24 Payment Methods for Crypto-Asset Purchase: N/A E.25 Value Transfer Methods for Reimbursement: N/A E.26 Right of Withdrawal: N/A E.27 Transfer of Purchased Crypto-Assets: N/A E.28 Transfer Time Schedule: N/A E.29 Purchaser's Technical Requirements: The purchasers must abide by the terms and conditions set forth by the trading platform where they obtain the B3 Tokens. They must also be able to hold ERC-20 tokens. E.30 Crypto-asset service provider (CASP) name: N/A E.31 CASP identifier: N/A E.32 Placement form: N/A E.33 Trading Platforms name: Payward Global Solutions Limited, t/a Kraken, Bitvavo B.V., and potentially other trading platforms or venues, including Coinbase Luxembourg S.A.. E.34 Trading Platforms Market Identifier Code (MIC): PGSL, VAVO E.35 Trading Platforms Access: The B3 Token is available on a number of centralized and decentralized trading platforms worldwide. With regards to EU trading platforms, investors can access the trading platforms by creating accounts with the respective platforms and abiding by each platform's requirements, including appropriate KYC processes. E.36 Involved costs: Different trading platforms might charge different fees for accessing the trading platform or conducting trades. E.37 Offer expenses: N/A E.38 Conflicts of Interest: N/A E.39 Applicable Law: The B3 Token as a crypto-asset is not governed by any specific national law or jurisdiction as B3 is a decentralized network that operates on a global scale. B3 Tokens exist on the blockchain, and there are no contractual frameworks (like investment contracts or debt instrument) attached to the B3 Token that would be subject to governing law. E.40 Competent court: The B3 Token is a crypto-asset on the blockchain and governed by the B3 DAO, and there are no specific competent courts designed for disputes related to the B3 Token itself. For the purposes of this whitepaper, legal matters arising in relation to its content fall under the competent courts of the Cayman Islands, unless otherwise required by mandatory provisions of applicable consumer protection or private international law. F. Information about the Crypto-Asset F.1 Crypto-Asset Type: Utility Token F.2 Crypto-Asset Functionality: The B3 Token is the engine powering B3's Open Gaming ecosystem, incentivizing growth, enabling participation, and creating a sustainable marketplace for developers and players alike. The B3 Token can be used in a number of ways, possibly including: - Governance: B3 Token holders play a key role in shaping the ecosystem via staking and governance. They can submit and vote on governance proposals that impact chain updates, fee structures, and ecosystem growth. - Ecosystem Commerce with Real-World Utility: Players could use B3 Tokens to purchase items, early access passes, or exclusive content. Future utilities may be introduced as the developer ecosystem matures and/or B3 Token holders approve via governance. F.3 Planned Application of Functionalities: The functionalities listed above are already live, and its additional functionalities are being worked on. Since staking became available, the B3 Token has been staked by more than 120,000 addresses. B3 Tokens can also be used to unlock specific items or passes related to gaming or other consumer-facing products. However, the B3 Token's functionality could change in the future. F.4 Type of white paper: OTHR F.5 The type of submission: NEWT F.6 Crypto-Asset Characteristics: The B3 Token is a fungible, transferable ERC-20 crypto-asset deployed on the Base blockchain, a Layer-2 blockchain settling to the Ethereum blockchain. The B3 Token is a utility token under MiCAR, not an asset-referenced token (ART) or electronic money token (EMT). The B3 Token is freely tradable on secondary markets including centralized and decentralized exchanges. F.7 Commercial name or trading name: B3 (Base) F.8 Website of the issuer: https://www.b3.fun/ F.9 Starting date of offer to the public or admission to trading: 2025-09-09 F.10 Publication date: 2025-09-08 F.11 Any other services provided by the issuer: N/A F.12 Language or languages of the white paper: English F.13 Digital Token Identifier Code used to uniquely identify the crypto-asset or each of the several crypto assets to which the white paper relates, where available: N/A F.14 Functionally Fungible Group Digital Token Identifier, where available: N/A F.15 Voluntary data flag: false (mandatory) F.16 Personal data flag: true F.17 LEI eligibility: true F.18 Home Member State: IE F.19 Host Member States: AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, , IT, LV, LT, LU, MT, NL, PL, PT, RO, SK, SI, ES, SE, IS, LI, NO G. Rights and Obligations G.1 Purchaser Rights and Obligations: B3 Token holders have governance rights within the B3 DAO, allowing them to propose, vote on, and delegate decisions concerning the protocol, provided they meet the criteria outlined in the B3 Constitution, publicly available at https://docs.b3.fun/constitution . The B3 Token does not represent ownership, profit-sharing, redemption rights, or claims against any legal entity or asset. While there are no contractual obligations for B3 Token purchasers, participation in governance implies an agreement to adhere to the B3 Constitution's processes and outcomes. G.2 Exercise of Rights and obligations: The rights to participate in governance are exercised via onchain smart contracts. Details regarding the procedures and conditions for exercising tokenholder rights can be seen in the B3 Constitution: https://docs.b3.fun/constitution G.3 Conditions for modifications of rights and obligations: The rights and obligations can be modified by the community following a governance process called a Constitutional B3IP and voted in favor. Details regarding the process can be seen in the B3 Constitution: https://docs.b3.fun/constitution G.4 Future Public Offers: N/A G.5 Issuer Retained Crypto-Assets: 0 G.6 Utility Token Classification: true G.7 Key Features of Goods/Services of Utility Tokens: The B3 Token is the engine powering B3's Open Gaming ecosystem, incentivizing growth, enabling participation, and creating a sustainable marketplace for developers and players alike. The B3 Token can be used in a number of ways, possibly including: - Governance: B3 Token holders play a key role in shaping the ecosystem via staking and governance. They can submit and vote on governance proposals that impact chain updates, fee structures, and ecosystem growth. - Ecosystem Commerce with Real-World Utility: Players could use B3 Tokens to purchase items, early access passes, or exclusive content.\ Utilities and features may be adjusted as the developer ecosystem matures and/or B3 Token holders approve via governance. G.8 Utility Tokens Redemption: The B3 Tokens can be exchanged to purchase items within games or other consumer-facing products, or to unlock access to products or features within products (without spending B3 Tokens). The type of goods or services that can be redeemed via the B3 Token can change over time. G.9 Non-Trading request: true, admission to trading is sought G.10 Crypto-Assets purchase or sale modalities: N/A G.11 Crypto-Assets Transfer Restrictions: N/A. At the Token Generation Event (TGE), B3 Tokens were allocated to various stakeholders: community members, investors, the development team, and Player1 Foundation. The total B3 Token supply is capped at 100 billion with no mechanism for burning or scheduled inflation. Most of the B3 Tokens are locked in vesting contracts ranging from 3 to 48-month vesting schedules. 48 months post TGE, the full supply of B3 Tokens will be in circulation. Details on circulating supply can be seen here: https://docs.b3.fun/tokenomics G.12 Supply Adjustment Protocols: false G.13 Supply Adjustment Mechanisms: N/A G.14 Token Value Protection Schemes: false G.15 Token value protection schemes description: N/A G.16 Compensation Schemes: false G.17 Compensation schemes description: N/A G.18 Applicable law: The B3 Token as a crypto-asset is not governed by any specific national law or jurisdiction as B3 is a decentralized network that operates on a global scale. B3 Tokens exist on the blockchain, and there are no contractual frameworks (like investment contracts or debt instrument) attached to the B3 Token that would be subject to governing law. G.19 Competent court: The B3 Token is a crypto-asset on the blockchain and governed by the B3 DAO, and there are no specific competent courts designed for disputes related to the B3 Token itself. For the purposes of this whitepaper, legal matters arising in relation to its content fall under the competent courts of the Cayman Islands, unless otherwise required by mandatory provisions of applicable consumer protection or private international law. H. Information on the Underlying Technology H.1 Distributed ledger technology: The B3 token is on the Base chain, an Ethereum Layer 2 blockchain from Coinbase, which utilizes optimistic rollup technology as its underlying distributed ledger framework. H.2 Protocols and technical standards: The B3 token is on Base, an Ethereum Layer 2 network created by Coinbase using Optimism's OP Stack. As a Layer 2, Base inherits the security features of Ethereum while offering faster and more cost-effective transactions via rollups. The B3 token also utilizes standard smart contracts from OpenZeppelin ( https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol ), thereby adhering to established protocols for token transfers, transaction authorization, and messaging. This ensures its interoperability with various cryptocurrency wallets, exchanges, and decentralized applications. As Base is fully compatible with the EVM (EVM-equivalent), the B3 token can be accessed using any wallet that supports the Base network. H.3 Technology Used: The B3 Token leverages the Ethereum blockchain and is a standard ERC-20 token. Thus, it can be moved to other networks, including the layer-3 B3 blockchain which settles to the Base blockchain. Holders and users of B3 Tokens can choose from a variety of self-custody wallets and/or trading platforms or other venues, including Coinbase and Kraken. H.4 Consensus Mechanism: B3 tokens utilize the consensus mechanism of Base, Coinbase's Ethereum Layer-2 blockchain. Base, built using the open-sourced Optimism Stack, depends on Ethereum's PoS for final settlement and security. Consensus on Base's Layer 2 state is achieved through optimistic rollups, where validators submit state roots to Ethereum. Transactions are considered valid unless challenged via a fault proof mechanism (Base recently announced that fault proofs are live on Base Mainnet https://base.mirror.xyz/eOsedW4tm8MU5OhdGK107A9wsn-aU7MAb8f3edgX5Tk ). This challenge-based dispute resolution allows participants to contest inaccuracies, ensuring trustless validation. H.5 Incentive Mechanisms and Applicable Fees: The Base network uses a combination of economic incentives and security mechanisms based on Optimistic Rollups. These include transaction fees to motivate validators and sequencers in processing and securing offchain transactions. These fees are allocated to cover execution and data settlement expenses on the Ethereum network, and are significantly cheaper than transaction fees on the Ethereum L1 due to its optimistic rollup architecture. H.6 Use of Distributed Ledger Technology: false H.7 DLT functionality description: N/A H.8 Audit: true H.9 Audit outcome: Base, built on the OP Stack, has been audited both by Coinbase and external auditors. For details, please see this link: https://base.mirror.xyz/\SiAx8dQRYJJ4lygkJc0QvBKvf16VVm7\-mdWMdFv20 For the B3 Token, an audit was completed with no issues. I. Information on Risks I.1 Offer-Related Risks: 1. Secondary market trading of B3 Tokens can be exposed to considerable volatility. This can be attributed to various factors, including speculative trading, market sentiment shifts, and knowledge or information asymmetry. Furthermore, the operational independence of different trading platforms introduces additional risks. Disruptions to a platform's services, technical failures, or the delisting of B3 Tokens from a particular exchange could severely impede trading activities and result in financial losses for B3 Token holders. 2. The market for B3 Tokens may be impacted by limited depth and liquidity. Low trading volumes and a small number of active buyers and sellers can impact price swings and make it difficult to execute large trades without significantly impacting the market price. This lack of liquidity can make it challenging for investors to exit their positions at desired prices and times. 3. Finally, the regulatory landscape surrounding cryptocurrencies and digital tokens is constantly evolving. Future regulatory changes in relevant jurisdictions could significantly impact the trading of B3 Tokens, potentially requiring adjustments to trading mechanisms, compliance procedures, or utility of the B3 Token. Participants must remain vigilant regarding potential regulatory developments and understand that these changes could have adverse effects on their holdings. I.2 Issuer-Related Risks: The B3 Token operates in a decentralized way without a central legal entity, relying on the decentralized B3 DAO for governance. Due to the decentralized nature of the B3 ecosystem, no party is obligated to support, develop, or maintain the B3 Token or its network. This decentralization introduces risks of governance inaction, misaligned incentives, and internal conflicts. Decisions and strategies of the DAO and its contributors significantly influence project development, especially in response to competition and opportunities. Operating within a dynamic regulatory environment, the DAO and various contributors face continuous compliance challenges across different jurisdictions. Regulatory actions against the participants of the B3 ecosystem could negatively impact token operations and ecosystem growth. I.3 Crypto-Assets-related Risks: Utility Risks: The B3 Token is the vehicle powering the B3 ecosystem. However, its utility within its ecosystem may not function as intended, negatively affecting its core purpose. Market Risks: The B3 Token is subject to market volatility and liquidity issues, with speculative trading influenced by sentiment and economic factors. It does not guarantee financial returns or specific utility. Its value is affected by adoption, community, market participants, trading, and external factors beyond protocol control. I.4 Project Implementation-Related Risks: The future of the B3 ecosystem hinges on successful expansion, specifically the quantity and caliber of both developers building on the B3 blockchain and participants engaging in the horizontally-scaled B3 ecosystem. This necessitates that protocol participants make prompt and strategic choices concerning upgrades, funding, and network governance. Failure on the governance side or challenges posed by changing regulations could impede or prevent essential strategic initiatives. As many different participants contribute to the B3 ecosystem, there is risk of participants or contributors pivoting or redefining strategic direction and priorities, which may alter or impact the thesis, development, or structure of the B3 ecosystem or the B3 Token in ways that may not align with others' expectations. Furthermore, ineffective treasury management or the misallocation of funds could slow ecosystem development and erode community trust. I.5 Technology-Related Risks: The B3 Token is on the Base network, the Ethereum Layer-2 blockchain protocol launched by Coinbase. Though Base utilizes the audited and tested OP Stack, it carries inherent operational risks. Potential issues include network congestion, scalability limitations, and protocol changes, which can affect network performance, transaction processing, and protocol stability. The Base network infrastructure, and consequently the B3 infrastructure, can be susceptible to consensus-related attacks, impacting token transactions and balances. Maintaining the security of these systems requires continuous monitoring and patching of vulnerabilities at all levels. It is important to acknowledge that the risks outlined above do not list all risks and that unforeseen risks or combinations of existing risks may also materialize. I.6 Mitigation measures: To mitigate the above, the B3 ecosystem has a comprehensive defense mechanism including decentralized governance, audited smart contracts, and a Security Council comprised of independent decision-makers. Features are audited and tested rigorously to ensure the safest environments and architecture.\ In addition, the team cautiously monitors regulatory changes with external law firms. S. Information on Sustainability Indicators S.1 Name: Player1 Foundation S.2 Relevant legal entity identifier: 409475 S.3 Name of the crypto-asset: B3 (Base) S.4 Consensus Mechanism: As per section H.4, B3 Tokens utilize the consensus mechanism of Base, Coinbase's Ethereum Layer-2 blockchain. Base, built using the open-sourced Optimism Stack, depends on Ethereum's Proof-of-Stake (PoS) for final settlement and security. Consensus on Base's Layer 2 state is achieved through optimistic rollups, where validators submit state roots to Ethereum. Transactions are considered valid unless challenged via a fault proof mechanism (Base recently announced that fault proofs are live on Base Mainnet https://base.mirror.xyz/eOsedW4tm8MU5OhdGK107A9wsn-aU7MAb8f3edgX5Tk ). This challenge-based dispute resolution allows participants to contest inaccuracies, ensuring trustless validation. S.5 Incentive Mechanisms and Fees: As per section H.5, the Base network uses a combination of economic incentives and security mechanisms based on Optimistic Rollups. These include transaction fees to motivate validators and sequencers in processing and securing offchain transactions. These fees are allocated to cover execution and data settlement expenses on the Ethereum network, and are significantly cheaper than transaction fees on the Ethereum L1 due to its optimistic rollup architecture. S.6 Beginning of the period to which the disclosure relates: 2025-04-30 S.7 End of the period to which the disclosure relates: 2025-05-22 S.8 Energy consumption: 3,896 kWh S.9 Energy consumption sources and methodologies: The B3 network is a Layer-3 ecosystem on Base, the Coinbase Layer-2 blockchain. Electricity consumption is calculated using equation A\+B. A: To calculate the energy consumption for the B3 network that might be relevant to the B3 Token, we conservatively calculated the total electricity consumption of the B3 ecosystem based on node activity. Using a proposed bottom-up calculation of node energy, breakdown of nodes times power estimate of one day gives 10.8 kWh/day, or 3,880 kWh/year. B: To calculate the energy consumption for the B3 Token on the Base network, we analyzed a previously-submitted MiCAR whitepaper on the same network as the B3 Token. Kaito, also deployed on the Base network, estimates annual energy consumption at 15.65861 kWh per year, using: - A top-down calculation method by estimating Base's energy consumption and defining the total energy consumption of the Kaito asset, and - A bottom-up calculation considering node usage. Link to Kaito whitepaper: https://drive.google.com/file/d/1BKSiifN4-SUHunc6AtotRlTtixtsL6pd/view (OpenKaito Foundation; LEI: 254900TSVY02DCZPYH91). As of June 2, 2025, the Kaito token's FDV is almost at \$2B, and the B3 Token's FDV is approximately \$300M. Kaito's 24H trading volume is \$90M, while the B3 Token's 24H trading volume is \$8.6M. Judging from these metrics, we assume the B3 Token's energy consumption is less than \$KAITO's, but we do not know enough about Kaito's methodology for closer calculations. Considering possible forces outside the team's knowledge, we conservatively place the B3 Token (on Base)'s energy consumption at the same level as Kaito's. A \+ B = 3,880 kWh \+ 16 kWh = 3,896 kWh/year. --- ## Whitepaper Source: https://docs.b3.fun/protocol/whitepaper Executive Summary Gaming in our modern era has become ubiquitous across communities, geographies, and media; in its myriad forms it has become both an enormous industry and an integral aspect of modern digital life. Yet despite the industry's growth and success, a set of gatekeeping entities and walled gardens has gradually emerged–as in many aspects of the tech world and larger economy. This consolidation worsens the experiences of gamers, restricts opportunities for developers, and reduces diversity within the industry. Traditional "off-chain" gaming feels bereft of the uninhibited innovation and fun that typified earlier decades–-it feels closed. Web3 has for years presented itself as an alternative to the status quo, one bringing forth the components of a new paradigm for gaming focused around interoperability, greater community input, user-owned and transferable assets, and unique reward structures. The promise was open gaming. But this vision remains unrealized. A series of hurdles has largely prevented studios from diving in, gamers from migrating, and the broader web3 gaming ecosystem from blossoming. Community fragmentation has also been a major struggle for onchain gaming, with audiences isolated in discrete, largely unconnected ecosystems, impacting both discoverability and gameplay, and discouraging further innovation. Finally, and critically, it is tragic that an industry so focused on designing new open incentive systems has tacitly recreated many economic pressures against collaboration. The industry needs a broader vision and solutions to realize it. We propose Open Gaming as a mandate, a suite of technical tools, and an incentive system to level up onchain gaming and usher in a golden era in gaming. This features a sophisticated development engine capable of powering the next generation of onchain games and enabling them to rival if not surpass their web2 predecessors. A core Layer 3 (L3) blockchain that settles on Base, offering fast and cheap transactions, will offer new capacities to game developers. Games can launch their own customized GameChains that settle on the B3 L3 while leveraging best-in-class usability features like account abstraction, intents, and smart wallets. Over time, the Open Gaming ecosystem could include and integrate other chains alongside B3. This gives developers control over the game experience without having to grapple with the fragmentation that can come with traditional appchains. Finally, Open Gaming is taking the challenge of misaligned incentives head on. A shared and open economic system can start to enable developers and infrastructure providers to benefit from each other's growth and at minimum encourage cooperation in this critical period of attracting new users. A referral system that rewards the ecosystem for sharing users is just the first step. Ultimately, these innovations promise to transform 'web3 gaming' into merely 'gaming.' To achieve this, Open Gaming, starting with the B3 L3, introduces a venue for the emergence of the most engaging and sophisticated games, for passionate gaming communities to coalesce, and with the larger gaming ecosystem itself becoming the largest beneficiary. Gaming: A Crossroads Games in many digital forms are enjoyed the world over. More than 3 billion global gamers enjoy an abundance of gaming platforms that let them engage virtually anytime and in any setting, from a mobile game on a subway to a console game on a large screen TV. That an estimated 8\+ hours is spent weekly by the average gamer is a clear measure of gaming's place in society1. Successive waves of innovation in technology and gameplay have radically expanded the assumed demographics of a 'gamer.' Nintendo's Wii, Farmville on Facebook, Candy Crush Saga on mobile–all have brought more and more people into gaming. Gaming in turn has radically expanded its footprint in popular culture and media. From the dramatic growth and increasing acceptance of Esports, to the success of gaming-based movies and TV shows, the significance of gaming as a cultural force is clear. In many ways, to be digital these days is to have at least brushed up against gaming. Nonetheless, the gaming industry and community today finds itself in a place of tension. Offchain Gaming: Symptoms of gatekeeping Despite the enormous expansion in the number of players and ways they play games, developers and gamers alike face some critical pain points. Like many sectors of the tech ecosystem and the larger world, in recent years the gaming industry has increasingly concentrated in the hands of a small number of publishers and distribution platforms. For developers, this increases the challenge of standing out, leading to higher premiums on marketing and distribution, less emphasis on gameplay, and strong incentives against risk-taking. Pressures to rapidly ship product and to emulate tried-and-true models, both undermining creativity and risk taking, have become realities for game designers. For an industry that has always been a conflux of self-expression, art, and commercial pursuit–more product oriented than independent film yet more artistic than consumer apps–many participants are deeply uncomfortable. Indeed, indie developers and risk-taking studios have long held an outsized role in pushing the gaming industry, culture, and community forward. Tetris, one of the most played games of all time, was developed by a single engineer. The genre of MOBAs (multiplayer online battle arena), responsible for more than a decade of successful esports in Dota 2 and League of Legends, was started from users modding popular Blizzard games. Minecraft was the genius of Markus "Notch" Persson and has gone on to define a generation's experience of gaming, a golden age of user-generated content both in-game and throughout the Internet, and be a wild commercial success. It has been and remains imperative that risk-taking developers are able to thrive, yet today's gaming industry is not structured in a way that supports them. Gamers seem to feel the effects of this centralization too. Many complain of extractive business models, whether microtransactions, mobile's free-to-play / pay-to-win model, endless in-game purchases, or the proliferation of account-gated games. It is the best of times. It is the worst of times. !Screenshot2025 09 03at2 51 33PM Pn Elon's tweet garnered over 76m views, suggesting it struck a deep chord. Despite the growing footprint of gaming, the range of tools available to developers, and the relative ease of accessing games, dissatisfaction and discomfort is present throughout the industry. From a broader perspective it is unquestionably one of those periods of tension out of which meaningful transformations often emerge. Onchain Gaming: Closed (again) Web3 gaming represents an obvious direction for a potential gaming renaissance. It is a new digital and network technology. It is global, cross-platform, and prides itself on removing gatekeepers. It can make users direct stakeholders and offer developers new ways to fund themselves. On paper at least, the promise seems to match the moment. Gaming has already played a critical role in the blockchain industry broadly, and it is just warming up. Cryptokitties, launched in 2017, was one of the first mainstream moments in all of crypto. While it is famous for almost halting the Ethereum blockchain, it can also be seen as the moment that drove home the importance of blockchain scaling solutions. In some ways, the larger blockchain industry has Cryptokitties to thank for massively expanding popular views of the potential of dapps—and how seriously people set to solving scaling issues. Onchain gaming managed similar feats over the ensuing years, with Axie Infinity, STEPN, Parallel, and Pixels as just a few examples. Despite criticisms that onchain gaming has yet to have globally-significant impacts, sustained interest remains, with many platforms, investors, genres, and models deployed every quarter. Over the past four years, over \$11B has been invested in web3 gaming across 900\+ transactions. Over \$1.5B of this total investment occurred during 2023, and approximately \$900 million has been allocated to web3 gaming in 20242.  Trackers of web3 games list almost 1000 titles that have been launched across many different ecosystems in recent years. Many feature thoughtful experimentation with integrating digital assets, encouraging fun onchain, and self-funding approaches. Many blend offchain components and onchain components, using labels like Web2.5 or diet Web3. Surveying the space, even if a breakout game has yet to appear, the range of innovation hints at the potential of onchain gaming to usher in a new era. The continued investment should be welcome. Even before blockchain was a buzzword, gaming has played a role in crystalizing new digital technologies. Over decades games have proven particularly powerful at evoking the potential of new technologies for entertainment, immersion, and play. For those who lived it, it is difficult to imagine the early days of computers without reference to Atari and to Oregon Trail. Early Windows users enjoyed Minesweeper, just as the earliest mobile phone users–using the gray bricks that predated smart phones–all had Snake. Importantly, and as noted above, each of these technological shifts simultaneously expanded the global gaming community even as gaming helped popularize the new platforms themselves. Onchain hasn't meant Open In sum, offchain gaming can benefit immensely from a new digital medium, particularly one that prides itself on permissionless innovation, removing gatekeepers, which has tools for creative funding models, and which ultimately is a potential way of addressing some of the industry’s existing tensions. In turn, onchain gaming, particularly in the wake of its visionary risk-taking pioneers, can benefit from additional attention and the reservoir of talent in the traditional gaming industry. And for the larger onchain space, gaming could serve the popularizing role it has with other technologies. Realizing this potential, however, requires overcoming some significant challenges, all pointing to how we are seeking to take onchain gaming—and the entire industry—to the next level. Definancialize and Diversify  Early generations of onchain gaming have explored only a slice of what is possible. Onchain gaming models were limited by immature infrastructure, and have involved a heavy focus on speculation and financialization. This is not unheard of in offchain gaming: the massive appeal of lootboxes in gaming, a thriving black market for leveled-up game accounts, and in-game resource farming operations as early as the mid-2000s suggest this intersection is neither new to gaming nor likely to ever go away. But today the shadow of this financial focus hangs over the entire onchain game industry. In some ways, “play to earn” is a damning confession, as if it is inconceivable that these games can be played purely for fun. This has given the industry a stigma that keeps would-be gamers and developers on the sidelines. The “gamefi” industry has a clear place in gaming globally but also has unquestionably produced only a slice of what’s possible in onchain gaming The industry needs to expand beyond these approaches and win on metrics that matter to real people and reflect the broader realities of gaming today.  \\Universal Accessibility \\ Building onchain games can also be complex. Playing them frequently is as well, further compounding the difficulties for game developers. Some of these challenges are shared among all dapps but have particular salience for an industry where offchain predecessors maximize ease, addictive actions, and engaging content. These challenges include:  - Players typically need crypto wallets to play. This means seed phrases, which can be terrifying to gamers accustomed to the world of passwords and password resets. It means identifying ideal wallets, many difficult to distinguish from each other, with features like native staking support that mean little to gamers. - Players often need to bridge assets between different chains. A game on Solana and a game on Ethereum might involve two different wallets, with complicated and expensive mechanisms for transferring funds between them. Multiple steps and transactions, waiting time for blockchain and bridge finality, and fees stand in the way of using most dapps, games included. - Players often need to fund their own gas, sometimes with custom gas tokens. The experience in practice is as counterintuitive as it sounds, like needing to physically change currencies for each city you visit, and sometimes needing new currencies for specific stores within each. The above challenges constrain developers, impact games, lead to churn, raise the barrier to entry for creative studios, and too often make the magic of the game disappear.  Ecosystem Fragmentation and Disinteroperability Most concerning of all, the web3 gaming ecosystem appears to be slowly regrowing some of the most troubling aspects of traditional gaming. Chains are heavily incentivized to become their own publishers and walled gardens, so as to drive transaction fee revenues and focus on the price of their own tokens. This also often forces game developers to choose particular chains for launch, each presenting technical tradeoffs, and stay there, or perhaps even to launch their own chain. To date, over 40 unique independent blockchains have or are hosting onchain games. These incentives cut against the open ethos of blockchain and smart contract platforms. While this contradiction is not unique to the gaming sector, it is a concerning mindset for a genre that is so focused on opportunities to attract non-crypto users, non-whales, and demographics outside of the narrowest crypto stereotypes. The industry should be looking to expand its collective footprint and player base, in the interest of expanding the overall space, rather than focusing on a perceived zero-sum competition and short-term impacts on the price of any individual tokens. We need co-op, not pvp, at the developer level right now. The Next Step A most tragic outcome would be recreating some of the challenges currently facing traditional gaming. Disgruntled gamers worried about extractive practices. A small number of gatekeeping entities with immense influence over which games and gaming models get prominence and effectively discouraging experimentation. These sadly already sound a bit familiar. Onchain environments and web3 gaming ecosystems do have the opportunity to recapture a core sentiment of the early internet and early gaming communities, that of a permissionless environment for making connections and distributing code to anyone anywhere. However, it is unclear if current trends, left undisturbed, can enable that. Enter Open Gaming Open Gaming is our vision of a secure, scalable, onchain gaming ecosystem that restores economic and creative freedom to game developers and players. In tangible terms, Open Gaming is a network of gamechains that share incentives, liquidity, and tooling, all working to increase access to both gamers and developers. The B3 L3 is the first chain in Open Gaming, for game developers who do not need their own customized chains, but will be joined by other developers who do. Parallel was the first to announce the PRIME gamechain on Open Gaming, on which their game Tau Ceti will launch; others will follow. Functioning as an innovative gaming engine for developers, a community-focused publisher, and the go-to community on Base for web3 gamers can allow Open Gaming to bring these key value propositions to life. \\Open Game Development: \\A primary benefit of Open Gaming’s technology is substantially lowering the barrier to designing, creating, launching, and running games. This starts with the core technologies needed to deliver onchain gaming experiences, building a platform to bring developers and gamers together, and supports the emergence of innovative gaming business models. The Open Gaming game engine brings together the key concepts that are making web3 development easier, faster, and richer, and will become the foundation upon which the next generation of industry-leading and genre-defining games is developed. Open Gameplay: Gamers of all types need easier ways to find, play, and support onchain games anywhere. A set of usability upgrades is ready to welcome more users onchain. L2s and L3s are radically lowering transaction costs. Account abstraction techniques are removing much of the hassle of managing multiple onchain accounts, particularly across different L2s and different chains. Smart wallets are removing much of the traditional challenges of even having an onchain account. We are bringing these and more together to make the experience of onchain gaming much more seamless. \\Open Access: \\A native Open Gaming marketplace and platform can include games published on any chain, using any set of tools, or using merely part of B3’s L3 capabilities, even behind the scenes. This will give developers necessary power for their games and complete control over their branding, community, technology, and trajectory. Finally, as a discoverability hub, Open Gaming is an inclusive, cross-chain environment where gamers are able to discover and play web3 games regardless of where they are published. Open Narratives: Developers need more freedom in imagining gameplay that is onchain in more nuanced and less binary ways. Some games will want maximum state on a single chain, some might only need in-game items or game accounts onchain, and many will be somewhere between or even orthogonal. The web brought many new capabilities to gaming, including social features, access to massive shared worlds, leaderboards, or even just remote downloading. Designing games wasn’t a choice of being maximally social or maximally online. Developers need encouragement, a platform, and, critically, an economic layer designed to encourage innovation in onchain gaming. The magic of the early Web was being able to visit any website. An early web user, after listening to their dial-up modem connecting to the Internet, could just ‘surf.’ Nothing at risk. Nothing to write down. No picking of servers, no specifying networking routes for queries, no changing browsers based on website settings. Crypto is closer to this user experience than ever before.  For example, B3’s unique stack lets developers focus on the internal game mechanisms and fun gameplay without worrying about limitations of the underlying technology or whether deploying with a particular partner is an irrevocable commitment to a particular ecosystem, chain, or publisher, and subject to the ecosystem’s own success or failures in attracting audiences. This is the promise of the Open Gaming mandate. This should yield more games, across many genres, and more varied in form.   Ultimately, the Open Gaming ecosystem is a space for gaming paradigms to evolve. Blockchain technologies have let entrepreneurs in many industries reimagine how business could work–and enjoy a permissionless place to build it. Exchange without intermediaries. Permissionless contribution and partnership. Users with stake in the game. Hard-to-change rulesets. Web3 remains a place of active experimentation and discovery. Gaming is early in its journey to doing something similar. With Open Gaming’s core innovations and philosophy, it can take the next major leap. Open Gaming's Core Components Our Open Gaming strategy boasts a comprehensive toolkit, platform, and ecosystem to better match the potential of web3 gaming with the moment confronting offchain gaming and the current onchain gaming industries alike. Several core elements, described below, define B3’s ability to establish itself as the onchain gaming hub. Development Engine Starting with the B3 L3 and accompanying tools, we have an integrated technology platform for next-generation onchain gaming designed to radically lower the cost of development and encourage a wider range of creative expression. Less time spent micro-planning infrastructure is more time crafting great onchain experiences. Base L3 \+ an L3 Superchain L2s have dramatically lowered transaction costs and paved the way for L3s such as B3 to reduce them further. L3s and the systems they support let developers make more conscious tradeoffs between trustless security and user experiences like cost, latency, and throughput. This is particularly salient in gaming, where the goal is usually entertainment and not trustless yield and double-spend protection for wealth assets. L3s are customizable chains, highly flexible in nature, and allow experimentation at the Virtual Machine (VM) layer and with concepts such as data availability and parallelization. The chains simply need to settle data onto an L2 in some capacity. L3s can be for specific dapps or for larger ecosystems; if the L2s are “hubs”, L3s can function as “spokes.” This drives the cost of using the chain down dramatically, enabling onchain micro-actions and more rapid gaming ticks.  They also provide powerful foundations for GameChains that settle on B3, allowing developers to enjoy control over their blockchain backend while still enjoying cross-game and cross-infrastructure compatibility. | Chain | ETH (L1) | Base (L2) | Solana | B3 (L3) | | ------------------------------------------ | -------- | --------- | ------- | ------- | | Illlustrative Transaction Cost (July 2024) | \$3.00 | \$0.005 | \$0.005 | \$0.001 | The B3 L3 enables settlement for a new layer of computation, opening up architectural possibilities that more resemble the development experience in offchain gaming. This comes with superior performance but different security guarantees, composability, and data persistence–tradeoffs that resemble modern decisions about cloud-based architecture and enable developers to make more nuanced decisions about the optimal range of onchain activities within their games. - GameChains: While traditional appchains have contributed to economic fragmentation that complicates an already challenging journey for developers and gamers, it is also true that developers need to control the gaming experience and architecture at this nascent stage of onchain gaming. GameChains square this circle. They are fully customizable, with chain-in-a-box ease using the Open Gaming SDK and team expertise, while also settling on B3 for barebones costs. All GameChains interoperate with other GameChains and with the open utilities Open Gaming is building. All GameChains participate in the shared economy and benefit from the account abstraction tools and techniques that make Open Gaming so accessible. - \\Sprinter: \\Enabling the flexibility described above without reintroducing UX fragmentation is possible because of Sprinter, an account abstraction aggregator that serves the best possible path for an end user to perform a transaction, via chain, bridge or intent. Sprinter enables seamless bridging across and beyond the ethereum ecosystem, balancing abstraction across multiple wallets, intent-based interactions, and smart wallets, all of which promise to radically level up the onboarding experience for Web3. The result is designing for a Web2-like experience with confidence, not trying to architect around the clunky framing of being onchain. It also enables a dynamic L3 and L4 environment without confusing users. Ultimately, Sprinter helps realize the potential for a web3 app that is more competitive, easier to use, and easier to build than web2 apps. - \\Maximum throughput: \\EIP-4844 significantly reduced the cost of transacting on L2s, opening up new capacity. The almost immediate absorption of this capacity suggests the industry’s appetite for more throughput remains. If the cost of transacting in an onchain environment falls further, developers and users will find ways to fill the blockspace. Running game logic in an onchain environment creates digital history that anyone can leverage–communities looking for power players or entry-level gamers, game designers trying to understand where players typically stopped playing a game, or new tokens looking for who their future user base might be. Moving things onchain without congestion and prohibitive costs can open up new design space for games. - Horizontal scaling: One of the powers of L3s is the ability to support additional computation layers on top that still write state down to a secure chain. Rollups on top of B3 lets game activity leave an onchain footprint while keeping costs low. Such layers built on top of L3s can be spun up and down quickly, at minimal cost, to accommodate surges in demand. Such additional layers can be used as part of a strategy to scale game activity horizontally, relying on many parallel chains when games don’t need to keep all players and logic in the same environment. An esports tournament, a guild-created tournament, an influx of new players—all could be supported under the hood without clogging the experience of other players, much less other users of the chain. The Open Gaming engine can support this type of rollup spawning without game developers needing to build custom scaling solutions or contort their architecture. Shared Liquidity Gamers owning their own items, progress, characters, and game-progress footprint is a superpower of onchain gaming, but today these are scattered across many wallets, chains, rollups, and marketplaces. The complexity caused by different chains and assets across chains is a significant barrier to entry especially to those less familiar with crypto. This erodes the ultimate promise of gaming on a shared computation layer. To realize the vision of Open Gaming, players shouldn’t need to manually bridge or switch networks, creating a more fluid experience. In B3, liquidity of onchain assets is shared and compounded across all GameChains through the B3 core framework’s seamless chain abstraction. The UX allows effortless movement of assets between games, eliminating the need for players to manually switch networks and bridge tokens. A player with tokens on GameChain A can seamlessly access those assets on GameChain B, without manually switching networks or bridge funds. This makes it easier for the player to try new games without additional UX overhead.  L3 Density Using the infrastructure described above, B3 enables a ‘superchain’ at the L3 level. Optimism’s Superchain thesis is that because all OP Stack L2 chains run on the same stack, a Superchain can be formed between them to provide synced transactions, shared bridging, and compatibility for any future OP Stack chain to join this network.   In the interim, it is possible a “superchain” can be built at the L3 level. From a technical perspective, various virtual machines (VMs) can be run in parallel, which can still result in the outcome of synced transactions, shared logic, and compatibility to add new chains. From a go-to-market perspective, L2s would actively want to create a mechanism by which L3 builders can leverage existing tech, distribution, and tooling. Put simply, with an L3 superchain, builders get the product parity without the overhead of running their own chain. While today’s trend is to have bespoke L3s for each dapp, the fragmentation and cost to manage an L3 will soon become apparent. The solution to this is L3 Density – a network effect formed when numerous, interoperable L3s settle onto the same L2 – as the driver of the next trillion transactions. Base The B3 ecosystem will be built on Base, which is best positioned to be the vehicle for the next billion people to get onchain. Importantly, Base has been developed transparently by a team constantly contributing to the broader crypto ecosystem. It has demonstrated a commitment towards supporting the growth of the overall web3 ecosystem, rather than moving towards a walled garden structure replicating the worst of web2 practices. It is affiliated with Coinbase, one of the most successful crypto onramps and responsible for bringing cryptoassets to millions of people and millions of people to the crypto industry. Finally, Base is built with an array of tooling that maximizes developer ease. Given the above, Base represents the ideal foundation for Open Gaming to emerge as the leading web3 gaming ecosystem. Discoverability Layer and Other Apps Places where buyers and producers come together have long fostered community while facilitating commerce and innovation. Actual physical marketplaces and bazaars facilitated the exchange of goods, ideas, and inventions in much of human history. For studios, it becomes easier to find the right gamers who might be playing games already like the ones the studio is making. For gamers, it is one place to look across a growing sea of creativity.  A central part of the Open Gaming vision is to support players finding and playing great onchain games, regardless of where they are. Though the B3 L3 is a flagship technology, the Open Gaming ecosystem will ultimately welcome other networks and will support apps that draw from across the onchain gaming landscape.  The capabilities of B3 initially match the needs of casual game designers while larger studios can work on technical integrations. This reflects the additional time and resources AAA games require but also the reality that casual games better reflect the more typical global experience of playing games: on phones, in shorter sessions, with low game-specific commitments. Community is a powerful force in every context. This is particularly the case in Web3. From its earliest days, the Internet was hailed as a place where people could almost effortlessly find others of like mind. Onchain gaming communities today remain dispersed, however, and the Open Gaming ecosystem should be an inclusive environment where all web3 gamers can find their communities and the games that appeal to them.  Web3 has a toolkit with the power to disrupt extractive producer-consumer relationships dominating the web today and arguably support organic or more incentive-aligned communities. Building onchain accelerates network effects and facilitates partnerships. Tokens and trustless incentives can guide behavior more powerfully than user agreements and free services. Users can be co-creators. Power users can be more than cash cows. Influencers can be more than marketing strategies. In an era of gamer exhaustion at the latest tricks in monetization, a dedicated community infrastructure for gamers, empowered by tokens, will feel radical. Shared Incentives An unfortunate reality of the fragmented landscape of onchain games today are disincentives for true interoperability. Games and chains don’t want to share users, who are often generators of transaction fees and primary token buyers. Games have weak incentives to integrate the items and mechanisms of other games, who themselves have already reaped the economic benefits from minting them. Even gamers can face poor incentives to grow a game’s userbase and dilute their own airdrop earnings. This is doubly tragic in an industry that prides itself on reinventing the economics of internet applications. Combatting this will take time, but we believe it is a battle worth fighting. The first step is a referral and revenue-sharing mechanism that collects a portion of transaction revenue for reinvestment in the ecosystem. Referring users that generate more transactions can benefit everyone in the ecosystem. In addition, any gamechain that commits a portion of their tokens toward user acquisition (UA) and also brings in a new user can earn B3 tokens. B3 will also bootstrap the initial incentive pool for the purpose of user acquisition (e.g. influencers, creator referral program) by contributing a portion of the B3 token supply. Opportunities for Key Stakeholders B3’s infrastructure can reach many types of actors and stakeholders, with features and benefits for each. !Whitepaper Opengaming Pn Game Developers: Web3 is a new frontier for gaming that game developers of all types can embrace. Open Gaming offers a new toolkit to turn users into partners, to engage creatively with a game community, and to fund game creation. It is a deployment platform not dominated by gatekeepers and intentionally established against it.  Open Gaming’s unique suite of infrastructure, tools, and platform lowers barriers of onchain game development. This should enable onchain gaming to find broader expression and develop novel structures, better reflecting and even expanding beyond the myriad ways offchain gaming is experienced today. Over the past one and a half decades, the “onchain” industry has been inexhaustible in producing new narratives. It finds ways to defy rumors of its own death. This resiliency speaks to an underlying value of web3 gaming and a desire within the gaming space to see new approaches emerge. We believe that with the advancements of the technology in general, and specifically in regards to the tools and infrastructure it is introducing, onchain gaming is finally ready to play a central role in the evolution of gaming.    \\Gamers: \\Lowering the barrier to entry for gamers will help them find the experiences they are looking for and hopefully ones they like but did not know existed. They can experiment with new forms of gameplay without crossing the UX chasm being onchain has required until now. They can also be co-funders, co-builders, and co-advocates for game developers bringing their own visions into the world. \\Base and the Base Ecosystem: \\Base may be the platform for the next billion onchain users. It is an open and neutral L2, without a native token and incentives to maximize the value of one and with a track record of contributing to the base Ethereum ecosystem. It celebrates builders and will continue to do so. It is adjacent to millions of offchain crypto users who might be curious about the technology but intimidated by the UX prospects of being onchain. We can continue the tradition of celebrating builders and giving back to its base ecosystem. More transactions. Amplifying community. Bridgeless usability. Onchain fun. \\The Gaming Industry: \\Games have also long functioned as a powerful vehicle for popularizing new technology. In some ways, technology benefits from gaming exploring and advancing its own limits as much as gaming benefits from new technologies. From this perspective, an argument that blockchain technologies—that by any measure have a far wider range of use cases than gaming—may nevertheless find gaming to be a powerful force both in advancing the technology and in introducing users to the technology as it engages new audiences, is a compelling vision. Open Gaming, with innovative tech improving game design as well as gameplay, and a social and community layer poised to make it a genuine web3 gaming hub and discovery layer, can play a critical role in making onchain gaming accessible and exciting.  B3 Token Overview The B3 token will play a variety of roles in the Open Gaming ecosystem, with applications for developers, gamers, and governance.  For developers, the token can help spur activity on B3 and throughout the Open Gaming ecosystem, reward great games, and serve as an anti-sybil measure. A variety of grant and patronage opportunities can enable developers to bring their creations to life on B3. At the same time, developers can use the token for fees and visibility. For gamers, the token will be used to facilitate cross-game commerce or special perks. This could include questing, playtesting, feedback, purchasing unique items and powerups, and other forms of engagement that historically have made gaming such a unique human activity. For anyone interested in governance, the token will help direct the DAO that sets policies, supports protocol upgrades, and oversees the treasury.  Token Allocation and Supply !Token Allocation Pn More exciting information about the B3 token utility will be shared as the ecosystem unfolds. Stay tuned\! Governance The Open Gaming ecosystem will need a variety of governance rules. The vision for onchain gaming is big and bold. The toolkit the B3 L3 and other supporting technologies provides is powerful and expressive. The winning strategy for the gaming ecosystem as a whole is still taking shape. It will take a dedicated community and a flexible governance system to navigate us all to the next stages. More on the specific governance structure will be forthcoming, but we generally anticipate three modes of engagement. - Proposals: a proposal system allows for ideas to emerge from the community that delegates may not think of or have the capacity to develop on their own. It also gives the entire community a direct voice. - Voting: token holders can be active participants in shaping the future of the B3 and Open Gaming ecosystems, embodying an important step towards the decentralization this industry stands for. - Councils: specialized councils are an effective way to align expertise, particularly technical, with relevant decision making. All of these have precedent in robust governance systems–and notably, are absent from the gaming production industry that has generated so much gamer discontent. Open Gaming is for gamers and governance will reflect that. Conclusion In an earlier era, going online ultimately meant many things for both games and players. It wasn’t just chatting in-game or playing with strangers. Entire new genres, like MMOs and server-grade worlds, became possible. User-generated content, on small scales and for entire games, became more commonplace. People talked about games online, volunteered their time to create tutorials for other players, and spawned a streaming industry. All of this was built upon novel in-game mechanisms and experiences that provided a foundation for and inspired these activities. Just like one could not have predicted the range of developments in the early days of online gaming where games like Tetris and Minesweeper represented the cutting edge of innovation, one cannot forecast exactly what innovations web3 and onchain gaming may bring.  The innovations discussed in this paper contain both challenges and opportunities; together they represent an agenda for addressing issues in gaming and looking to the future of the industry. They shape Open Gaming’s ability to foster a web3 gaming ecosystem where it is easier to build and access new games, and above all more engaging to play. This ecosystem enriches the experience of existing onchain gamers, has resources for a community to emerge, flourish, and shape the future of the platform and gaming in general, and welcomes and supports the transition of web2 gamers moving onchain.  In the context of a gaming universe where Apple’s App Store had nearly 300,000 titles available in 2023, and where only 1,000 web3 games have been released in total, the opportunity space before web3 is clear. Innovative platforms like B3’s L3 and the Open Gaming ecosystem that deliberately address key hurdles that have limited the experience of web3 until now—from infrastructural, community, and user experience and onboarding perspectives—are critical in ushering in and unleashing the potential of a new era that promises to become not merely the next phase of web3 gaming or the global gaming space, but of the online and onchain experiences themselves. 1. Russel, Charlie, The State of Online Gaming, Edge.io 2021. Retrieved from: https://edg.io/blogs/state-of-online-gaming-2021/ Jul 5, 2024 2. Jordan, Jon. Everything Blockchain Gaming. bigblockchaingamelist.com. https://bit.ly/web3gamedata. Accessed Dec 8, 2024. --- ## Quickstart Source: https://docs.b3.fun/quickstart Step 1: Install the B3 SDK Choose your preferred package manager to install the B3 SDK: The B3 SDK includes TypeScript definitions out of the box! Import the default styles in your application: Step 2: Add B3Provider Wrap the B3Provider around your application's root: Step 3: Use the B3 SDK Enable global accounts authentication with B3: Enable cross-chain swaps & custom interactions with AnySpend: Step 4: Explore the Ecosystem Learn about the complete B3 ecosystem, tools, and resources available for builders. What's Next? Now that you have the B3 SDK installed, explore these powerful features: Seamless authentication and user management across the B3 ecosystem. Access blockchain data for tokens, NFTs, profiles, and analytics. Cross-chain swaps, NFT minting, and blockchain operations. Ready-to-use examples and integration patterns. Platform Support | Feature | React Web | React Native | | ----------------- | --------- | ------------ | | AnySpend | ✅ | ❌ | | Global Accounts | ✅ | ✅ | | Headless Services | ✅ | ✅ | Need help? Join our Discord community or check out the ecosystem introduction for comprehensive resources. --- ## Developer Resources Source: https://docs.b3.fun/redirect/ecosystem You are being redirected to the B3 Ecosystem page. Click here to continue. --- ## B3 SDK Source: https://docs.b3.fun/redirect/sdk You are being redirected to the B3 SDK page. Click here to continue. --- ## API Key Request Source: https://docs.b3.fun/sdk/api-key-request --- ## Authentication Source: https://docs.b3.fun/sdk/global-account/authentication For Developers: All demos are hosted in the global-accounts app. To test locally, run in the global-accounts directory and access demos at . Interactive Demo Experience B3 authentication in action with all available providers: This is a live, interactive demo using the actual B3 SDK. When you don't specify , all available authentication options are displayed. View the full demo page for more examples. Authentication Strategies B3 Global Accounts support multiple authentication strategies to fit your application's needs. Social Login Google Authentication Discord Authentication Multiple Specific Strategies You can allow users to choose from multiple specific authentication providers: Specify an array of strategies to show only those authentication options to your users. Headless Authentication For custom implementations, use the headless authentication service: Basic Authentication React Native Authentication Authentication Hooks useB3 Hook The primary hook for accessing authentication state: The hook provides access to the authenticated (wallet account) and (user profile data). Use to access loading and authentication states. useAccountWallet Hook Access wallet information and connection status: Error Handling Implement proper error handling for authentication flows: Best Practices Always use your unique partner ID for proper attribution and analytics. Implement comprehensive error handling for better user experience. Set appropriate session durations based on your application's security needs. Use proper environment variables for different deployment stages. Component API Reference SignInWithB3 The main authentication button component. Props Array of authentication strategies to display. Options include: , , , , , , , , . Leave undefined to show all options. Blockchain chain configuration object with , , , and . Your unique partner ID for B3 Global Accounts. void"> Callback function called when authentication succeeds. Promise"> Async callback function called when an error occurs. Whether to close the modal after successful login. Custom text or component for the sign-in button. Whether to show the B3 logo in the button. Available Authentication Strategies B3 Global Accounts supports the following authentication methods: Strategy Type Description Social Google OAuth authentication Social Discord OAuth authentication Social GitHub OAuth authentication Social X (formerly Twitter) authentication Social Apple Sign In Passwordless Guest authentication without signup Passwordless Email verification code authentication Wallet WalletConnect protocol Wallet MetaMask browser extension Wallet Coinbase Wallet Next Steps Explore all available React hooks. See complete integration examples. Interactive authentication demo application. --- ## Examples Source: https://docs.b3.fun/sdk/global-account/examples Basic Authentication Example A simple authentication flow with error handling and loading states. Gaming Application Example Complete example for a gaming application with session keys and permissions. E-commerce Application Example Example showing B3 Global Accounts integration in an e-commerce context. React Native Example Example for React Native applications. Next.js App Router Example Example for Next.js 13+ App Router. Advanced Custom Hook Example Custom hook that combines multiple B3 features: CSS Styling Examples Example CSS for styling B3 components: These examples provide comprehensive patterns for integrating B3 Global Accounts into various types of applications. Each example includes proper error handling, loading states, and follows React best practices. Next Steps Learn about cross-chain functionality. --- ## React Hooks Source: https://docs.b3.fun/sdk/global-account/hooks Authentication Hooks useB3 The primary hook for accessing Global Account authentication state and actions. Return Values | Property | Type | Description | |----------|------|-------------| | | | Current authenticated account | | | | Whether user is authenticated | | | | Whether authentication check is in progress | | | | Function to sign out current user | | | | Function to refresh account data | useAccountWallet Access wallet information for the authenticated account. Permission Hooks usePermissions Manage and check session key permissions. useRequestPermissions Request new permissions for session keys. useRevokePermissions Revoke existing permissions. Asset Management Hooks useAccountAssets Retrieve and manage user's digital assets. Modal Management Hooks useModal Control B3 modals programmatically. Navigation Hooks useNavigation Handle navigation within B3 applications. Configuration Hooks useB3Config Access B3 configuration and environment settings. Hook Composition Custom Hook Example Combine multiple hooks for complex functionality: TypeScript Support All hooks include full TypeScript support: Error Handling Best practices for handling errors with hooks: Next Steps See complete examples using these hooks. --- ## Global Accounts Introduction Source: https://docs.b3.fun/sdk/global-account/introduction What are B3 Global Accounts? B3 Global Accounts are a unified authentication system that provides users with a single identity across the entire B3 ecosystem. Users can authenticate once and access all B3 applications, games, and services seamlessly. Key Features Support for Google, Discord, and other social authentication providers. Secure session key authentication with customizable permissions. Works across web, mobile, and desktop applications. Simple React components and headless TypeScript services. Architecture The Global Accounts system consists of several key components: Authentication Flow 1. Social Login: Users authenticate with their preferred social provider 2. Account Creation: A B3 Global Account is created or linked 3. Session Keys: Optional session keys for enhanced security 4. Permissions: Granular permissions for different actions React Components - : Context provider for Global Accounts - : Complete authentication flow - : Permission management - : Display user assets Headless Services - Authentication service for custom implementations - Session management utilities - Permission validation helpers Quick Start Basic Authentication Check Authentication Status Environment Configuration Set up your environment variables: Next Steps Learn about different authentication strategies and implementation. Understand session keys and permission management. Explore available hooks for Global Accounts integration. See complete examples and integration patterns. --- ## Permissions & Session Keys Source: https://docs.b3.fun/sdk/global-account/permissions Overview Session keys and permissions provide a secure way to allow applications to perform actions on behalf of users without requiring constant authentication. This is particularly useful for games and applications that need to execute transactions automatically. Permission System Permission Types B3 Global Accounts support granular permissions that can be configured for different use cases: - Contract Interactions: Specify which smart contracts can be called - Token Limits: Set spending limits for native tokens and ERC-20 tokens - Time Restrictions: Define start and end dates for permissions - Transaction Limits: Control the maximum value per transaction Permission Structure Session Key Implementation Basic Permission Request Game-Specific Permissions For gaming applications, you might need broader permissions: Custom Permission UI For more control over the permission flow: Session Key Management Checking Permission Status Revoking Permissions Advanced Permission Patterns Dynamic Permission Updates Security Best Practices Only request the minimum permissions necessary for your application. Use shorter permission durations for enhanced security. Specify exact contract addresses rather than broad permissions. Regularly audit and rotate session keys. Error Handling Common permission-related errors and how to handle them: Next Steps Explore all available hooks for permission management. See complete permission implementation examples. --- ## B3 SDK Source: https://docs.b3.fun/sdk/introduction What is the B3 SDK? The B3 SDK () is a unified TypeScript SDK that provides everything you need to build applications on the B3 ecosystem. It combines powerful cross-chain payment infrastructure with seamless authentication, all wrapped in developer-friendly React components and headless services. Architecture The SDK is organized into focused modules designed for maximum flexibility and ease of use: Cross-chain execution engine for payments, swaps, and NFT minting across multiple blockchains. B3 Global Accounts authentication and user management with social login and session keys. Module Structure Each module contains organized, purpose-built components: - - React components and hooks for easy integration - - Headless TypeScript services for custom implementations - - Comprehensive TypeScript definitions - - Utility functions and helpers - - Configuration and constants Platform Support | Feature | React Web | React Native | Headless | | --------------- | --------- | ------------ | -------- | | AnySpend | ✅ | ❌ | ✅ | | Global Accounts | ✅ | ✅ | ✅ | | Shared Utils | ✅ | ✅ | ✅ | Installation CSS Styles Import the default styles for the best visual experience: Quick Start Cross-Chain Payments with AnySpend Authentication with Global Accounts NFT Minting Key Features Universal Payment Infrastructure Accept payments in any cryptocurrency with automatic conversion to your preferred token. Enable seamless token swaps across 20+ supported blockchains with optimal routing. One-click NFT minting buttons that accept payments in any token from any chain. Integrated fiat-to-crypto onramps for users without existing cryptocurrency. Seamless Authentication Google, Discord, and other social providers with instant onboarding. Secure session management with granular permissions for enhanced UX. Single identity that works across all B3 applications and games. Built-in smart account abstraction for gasless transactions. Headless TypeScript Services For developers who need maximum control, all functionality is available through headless services: AnySpend Services Global Account Services Support & Community Get help integrating the B3 SDK into your project. Join the B3 developer community for support and discussions. View source code, report issues, and contribute to the SDK. What's Next? 1. Install the SDK and import the styles 2. Set up AnySpend for cross-chain payments 3. Configure Global Accounts for user authentication 4. Explore examples and implementation patterns 5. Join the community** for support and updates The B3 SDK provides everything you need to build the next generation of cross-chain applications with seamless user experiences. Start building today! --- ## snippets/code-examples Source: https://docs.b3.fun/snippets/code-examples Code Examples Installation Basic Setup NFT Purchase Component Cross-Chain Swap Authentication Wallet Connection --- ## snippets/contact-info Source: https://docs.b3.fun/snippets/contact-info Need Help? 📚 B3 Documentation 💬 Join our Discord 🐛 Report Issues on GitHub 📧 Email us at support@b3.fun ); Community & Resources 🎮 Try It Live AnySpend Demo - Try our SDK in action 💬 Get Support Discord Community - Join the conversation 🔧 Contribute GitHub Repository - Contribute to the project 🌐 Ecosystem B3 Docs - Explore the broader ecosystem ); const email = type === "support" ? "support@b3.fun" : type === "partnerships" ? "partnerships@b3.fun" : type === "developer" ? "developers@b3.fun" : "support@b3.fun"; return ( 📧 {email} ); }; ; --- ## snippets/docs-config Source: https://docs.b3.fun/snippets/docs-config name: "B3 SDK", theme: "mint", colors: { primary: "#007AFF", light: "#4DA6FF", dark: "#0056CC", }, navbar: { links: [ { label: "Live Demo", href: "https://anyspend.com", }, { label: "B3 Mainnet", href: "https://docs.b3.fun", }, ], primary: { type: "button", label: "Get Started", href: "/quickstart", }, }, globalAnchors: [ { anchor: "B3 Ecosystem", href: "https://docs.b3.fun", icon: "globe", }, { anchor: "Discord", href: "https://discord.gg/b3dotfun", icon: "discord", }, { anchor: "GitHub", href: "https://github.com/b3-fun/b3", icon: "github", }, ], footer: { socials: { x: "https://x.com/b3labs", github: "https://github.com/b3-fun/b3", discord: "https://discord.gg/b3dotfun", }, }, }; ; --- ## Search Source: https://docs.b3.fun/api-reference/search --- ## Search Redirect Source: https://docs.b3.fun/api-reference/search-redirect --- ## Get Transactions Source: https://docs.b3.fun/api-reference/get-transactions --- ## Get Blocks Source: https://docs.b3.fun/api-reference/get-blocks --- ## Get Token Transfers Source: https://docs.b3.fun/api-reference/get-token-transfers --- ## Get Internal Transactions Source: https://docs.b3.fun/api-reference/get-internal-transactions --- ## Get Main Page Transactions Source: https://docs.b3.fun/api-reference/get-main-page-transactions --- ## Get Main Page Blocks Source: https://docs.b3.fun/api-reference/get-main-page-blocks --- ## Get Indexing Status Source: https://docs.b3.fun/api-reference/get-indexing-status --- ## Get Stats Counters Source: https://docs.b3.fun/api-reference/get-stats-counters --- ## Get Transactions Chart Source: https://docs.b3.fun/api-reference/get-transactions-chart --- ## Get Market Chart Source: https://docs.b3.fun/api-reference/get-market-chart --- ## Get Transaction Info Source: https://docs.b3.fun/api-reference/get-transaction-info --- ## Get Transaction Token Transfers Source: https://docs.b3.fun/api-reference/get-transaction-token-transfers --- ## Get Transaction Internal Transactions Source: https://docs.b3.fun/api-reference/get-transaction-internal-transactions --- ## Get Transaction Logs Source: https://docs.b3.fun/api-reference/get-transaction-logs --- ## Get Transaction Raw Trace Source: https://docs.b3.fun/api-reference/get-transaction-raw-trace --- ## Get Transaction State Changes Source: https://docs.b3.fun/api-reference/get-transaction-state-changes --- ## Get Human-Readable Transaction Summary Source: https://docs.b3.fun/api-reference/get-human-readable-transaction-summary --- ## Get Block Info Source: https://docs.b3.fun/api-reference/get-block-info --- ## Get Block Transactions Source: https://docs.b3.fun/api-reference/get-block-transactions --- ## Get Block Withdrawals Source: https://docs.b3.fun/api-reference/get-block-withdrawals --- ## Get Native Coin Holders List Source: https://docs.b3.fun/api-reference/get-native-coin-holders-list --- ## Get Address Info Source: https://docs.b3.fun/api-reference/get-address-info --- ## Get Address Counters Source: https://docs.b3.fun/api-reference/get-address-counters --- ## Get Address Transactions Source: https://docs.b3.fun/api-reference/get-address-transactions --- ## Get Address Token Transfers Source: https://docs.b3.fun/api-reference/get-address-token-transfers --- ## Get Address Internal Transactions Source: https://docs.b3.fun/api-reference/get-address-internal-transactions --- ## Get Address Logs Source: https://docs.b3.fun/api-reference/get-address-logs --- ## Get Blocks Validated by Address Source: https://docs.b3.fun/api-reference/get-blocks-validated-by-address --- ## Get All Tokens Balances for the Address Source: https://docs.b3.fun/api-reference/get-all-tokens-balances-for-the-address --- ## Token Balances with Filtering and Pagination Source: https://docs.b3.fun/api-reference/token-balances-with-filtering-and-pagination --- ## Get Address Coin Balance History Source: https://docs.b3.fun/api-reference/get-address-coin-balance-history --- ## Get Address Coin Balance History by Day Source: https://docs.b3.fun/api-reference/get-address-coin-balance-history-by-day --- ## Get Address Withdrawals Source: https://docs.b3.fun/api-reference/get-address-withdrawals --- ## Get List of NFT Owned by Address Source: https://docs.b3.fun/api-reference/get-list-of-nft-owned-by-address --- ## Get List of NFT Owned by Address, Grouped by Collection Source: https://docs.b3.fun/api-reference/get-list-of-nft-owned-by-address-grouped-by-collection --- ## Get Tokens List Source: https://docs.b3.fun/api-reference/get-tokens-list --- ## Get Token Info Source: https://docs.b3.fun/api-reference/get-token-info --- ## Get Token Token Transfers Source: https://docs.b3.fun/api-reference/get-token-token-transfers --- ## Get Token Holders Source: https://docs.b3.fun/api-reference/get-token-holders --- ## Get Token Holders Source: https://docs.b3.fun/api-reference/get-token-holders-2 --- ## Get NFT Instances Source: https://docs.b3.fun/api-reference/get-nft-instances --- ## Get NFT Instance by ID Source: https://docs.b3.fun/api-reference/get-nft-instance-by-id --- ## Get Transfers of NFT Instance Source: https://docs.b3.fun/api-reference/get-transfers-of-nft-instance --- ## Get Token Instance Holders Source: https://docs.b3.fun/api-reference/get-token-instance-holders --- ## Get Transfers Count of NFT Instance Source: https://docs.b3.fun/api-reference/get-transfers-count-of-nft-instance --- ## Re-fetch Token Instance Metadata Source: https://docs.b3.fun/api-reference/re-fetch-token-instance-metadata --- ## Get Verified Smart Contracts Source: https://docs.b3.fun/api-reference/get-verified-smart-contracts --- ## Get Verified Smart Contracts Counters Source: https://docs.b3.fun/api-reference/get-verified-smart-contracts-counters --- ## Get Smart Contract Source: https://docs.b3.fun/api-reference/get-smart-contract --- ## Get JSON RPC URL Source: https://docs.b3.fun/api-reference/get-json-rpc-url --- ## Get Withdrawals Source: https://docs.b3.fun/api-reference/get-withdrawals --- ## Get Account Abstraction Indexing Status Source: https://docs.b3.fun/api-reference/get-account-abstraction-indexing-status --- ## GET /blockscout/api/v1/celestia/blob Source: https://docs.b3.fun/api-reference/celestiaservice-getblob --- ## GET /blockscout/api/v1/celestia/l2BatchMetadata Source: https://docs.b3.fun/api-reference/celestiaservice-getl2batchmetadata --- ## If the requested service is unknown, the call will fail with status NOT_FOUND. Source: https://docs.b3.fun/api-reference/if-the-requested-service-is-unknown-the-call-will-fail-with-status-not-found --- ## Get events Source: https://docs.b3.fun/api-reference/get-events --- ## Get contract events Source: https://docs.b3.fun/api-reference/get-contract-events --- ## Get contract events with specific signature Source: https://docs.b3.fun/api-reference/get-contract-events-with-specific-signature --- ## Get transactions Source: https://docs.b3.fun/api-reference/get-transactions-2 --- ## Get contract transactions Source: https://docs.b3.fun/api-reference/get-contract-transactions --- ## Get contract transactions with specific signature Source: https://docs.b3.fun/api-reference/get-contract-transactions-with-specific-signature --- ## Get token owners by contract Source: https://docs.b3.fun/api-reference/get-token-owners-by-contract --- ## Get token transfers by transaction Source: https://docs.b3.fun/api-reference/get-token-transfers-by-transaction --- ## Get token transfers by contract Source: https://docs.b3.fun/api-reference/get-token-transfers-by-contract --- ## Get token transfers Source: https://docs.b3.fun/api-reference/get-token-transfers-2 --- ## Get ERC-20 balances by address Source: https://docs.b3.fun/api-reference/get-erc-20-balances-by-address --- ## Get tokens Source: https://docs.b3.fun/api-reference/get-tokens --- ## Get ERC-721 balances by address Source: https://docs.b3.fun/api-reference/get-erc-721-balances-by-address --- ## Get ERC-1155 balances by address Source: https://docs.b3.fun/api-reference/get-erc-1155-balances-by-address --- ## Get supported tokens for price data Source: https://docs.b3.fun/api-reference/get-supported-tokens-for-price-data --- ## Get token price Source: https://docs.b3.fun/api-reference/get-token-price --- ## Token lookup Source: https://docs.b3.fun/api-reference/token-lookup --- ## Resolve Source: https://docs.b3.fun/api-reference/resolve --- ## Get blocks Source: https://docs.b3.fun/api-reference/get-blocks-2 --- ## Get contract ABI​ Source: https://docs.b3.fun/api-reference/get-contract-abi --- ## Get contract metadata​ Source: https://docs.b3.fun/api-reference/get-contract-metadata --- ## Decode logs and transactions​ Source: https://docs.b3.fun/api-reference/decode-logs-and-transactions --- ## Get NFT balances by address Source: https://docs.b3.fun/api-reference/get-nft-balances-by-address --- ## Get collection Source: https://docs.b3.fun/api-reference/get-collection --- ## Get NFTs Source: https://docs.b3.fun/api-reference/get-nfts --- ## Get NFT owners by contract Source: https://docs.b3.fun/api-reference/get-nft-owners-by-contract --- ## Get NFT owners by token Source: https://docs.b3.fun/api-reference/get-nft-owners-by-token --- ## Get NFT transfers Source: https://docs.b3.fun/api-reference/get-nft-transfers --- ## Get NFT transfers by transaction Source: https://docs.b3.fun/api-reference/get-nft-transfers-by-transaction --- ## Get NFT transfers by contract Source: https://docs.b3.fun/api-reference/get-nft-transfers-by-contract --- ## Get NFTs by contract Source: https://docs.b3.fun/api-reference/get-nfts-by-contract --- ## Get NFT transfers by token Source: https://docs.b3.fun/api-reference/get-nft-transfers-by-token --- ## Get NFT by token ID Source: https://docs.b3.fun/api-reference/get-nft-by-token-id --- ## Force refresh collection metadata Source: https://docs.b3.fun/api-reference/force-refresh-collection-metadata --- ## Force refresh token metadata Source: https://docs.b3.fun/api-reference/force-refresh-token-metadata --- ## Get wallet transactions Source: https://docs.b3.fun/api-reference/get-wallet-transactions --- ## Search Source: https://docs.b3.fun/data/api-reference/get-blockscout-search --- ## Search Redirect Source: https://docs.b3.fun/data/api-reference/get-blockscout-search-check-redirect --- ## Get Transactions Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions --- ## Get Blocks Source: https://docs.b3.fun/data/api-reference/get-blockscout-blocks --- ## Get Token Transfers Source: https://docs.b3.fun/data/api-reference/get-blockscout-token-transfers --- ## Get Internal Transactions Source: https://docs.b3.fun/data/api-reference/get-blockscout-internal-transactions --- ## Get Main Page Transactions Source: https://docs.b3.fun/data/api-reference/get-blockscout-main-page-transactions --- ## Get Main Page Blocks Source: https://docs.b3.fun/data/api-reference/get-blockscout-main-page-blocks --- ## Get Indexing Status Source: https://docs.b3.fun/data/api-reference/get-blockscout-main-page-indexing-status --- ## Get Stats Counters Source: https://docs.b3.fun/data/api-reference/get-blockscout-stats --- ## Get Transactions Chart Source: https://docs.b3.fun/data/api-reference/get-blockscout-stats-charts-transactions --- ## Get Market Chart Source: https://docs.b3.fun/data/api-reference/get-blockscout-stats-charts-market --- ## Get Transaction Info Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions-transaction-hash- --- ## Get Transaction Token Transfers Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions-transaction-hash-token-transfers --- ## Get Transaction Internal Transactions Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions-transaction-hash-internal-transactions --- ## Get Transaction Logs Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions-transaction-hash-logs --- ## Get Transaction Raw Trace Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions-transaction-hash-raw-trace --- ## Get Transaction State Changes Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions-transaction-hash-state-changes --- ## Get Human-Readable Transaction Summary Source: https://docs.b3.fun/data/api-reference/get-blockscout-transactions-transaction-hash-summary --- ## Get Block Info Source: https://docs.b3.fun/data/api-reference/get-blockscout-blocks-block-number-or-hash- --- ## Get Block Transactions Source: https://docs.b3.fun/data/api-reference/get-blockscout-blocks-block-number-or-hash-transactions --- ## Get Block Withdrawals Source: https://docs.b3.fun/data/api-reference/get-blockscout-blocks-block-number-or-hash-withdrawals --- ## Get Native Coin Holders List Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses --- ## Get Address Info Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash- --- ## Get Address Counters Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-counters --- ## Get Address Transactions Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-transactions --- ## Get Address Token Transfers Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-token-transfers --- ## Get Address Internal Transactions Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-internal-transactions --- ## Get Address Logs Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-logs --- ## Get Blocks Validated by Address Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-blocks-validated --- ## Get All Tokens Balances for the Address Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-token-balances --- ## Token Balances with Filtering and Pagination Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-tokens --- ## Get Address Coin Balance History Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-coin-balance-history --- ## Get Address Coin Balance History by Day Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-coin-balance-history-by-day --- ## Get Address Withdrawals Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-withdrawals --- ## Get List of NFT Owned by Address Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-nft --- ## Get List of NFT Owned by Address, Grouped by Collection Source: https://docs.b3.fun/data/api-reference/get-blockscout-addresses-address-hash-nft-collections --- ## Get Tokens List Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens --- ## Get Token Info Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash- --- ## Get Token Token Transfers Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-transfers --- ## Get Token Holders Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-holders --- ## Get Token Holders Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-counters --- ## Get NFT Instances Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-instances --- ## Get NFT Instance by ID Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-instances-id- --- ## Get Transfers of NFT Instance Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-instances-id-transfers --- ## Get Token Instance Holders Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-instances-id-holders --- ## Get Transfers Count of NFT Instance Source: https://docs.b3.fun/data/api-reference/get-blockscout-tokens-address-hash-instances-id-transfers-count --- ## Re-fetch Token Instance Metadata Source: https://docs.b3.fun/data/api-reference/patch-blockscout-tokens-address-hash-instances-id-refetch-metadata --- ## Get Verified Smart Contracts Source: https://docs.b3.fun/data/api-reference/get-blockscout-smart-contracts --- ## Get Verified Smart Contracts Counters Source: https://docs.b3.fun/data/api-reference/get-blockscout-smart-contracts-counters --- ## Get Smart Contract Source: https://docs.b3.fun/data/api-reference/get-blockscout-smart-contracts-address-hash- --- ## Get JSON RPC URL Source: https://docs.b3.fun/data/api-reference/get-blockscout-config-json-rpc-url --- ## Get Withdrawals Source: https://docs.b3.fun/data/api-reference/get-blockscout-withdrawals --- ## Get Account Abstraction Indexing Status Source: https://docs.b3.fun/data/api-reference/get-blockscout-proxy-account-abstraction-status --- ## GET /blockscout/api/v1/celestia/blob Source: https://docs.b3.fun/data/api-reference/get-blockscout-api-v1-celestia-blob --- ## GET /blockscout/api/v1/celestia/l2BatchMetadata Source: https://docs.b3.fun/data/api-reference/get-blockscout-api-v1-celestia-l2-batch-metadata --- ## If the requested service is unknown, the call will fail with status NOT_FOUND. Source: https://docs.b3.fun/data/api-reference/get-blockscout-health --- ## Get events Source: https://docs.b3.fun/data/api-reference/get-insights-v1-events --- ## Get contract events Source: https://docs.b3.fun/data/api-reference/get-insights-v1-events-contract-address- --- ## Get contract events with specific signature Source: https://docs.b3.fun/data/api-reference/get-insights-v1-events-contract-address-signature- --- ## Get transactions Source: https://docs.b3.fun/data/api-reference/get-insights-v1-transactions --- ## Get contract transactions Source: https://docs.b3.fun/data/api-reference/get-insights-v1-transactions-contract-address- --- ## Get contract transactions with specific signature Source: https://docs.b3.fun/data/api-reference/get-insights-v1-transactions-contract-address-signature- --- ## Get token owners by contract Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-owners --- ## Get token transfers by transaction Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-transfers-transaction-transaction-hash- --- ## Get token transfers by contract Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-transfers-contract-address- --- ## Get token transfers Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-transfers --- ## Get ERC-20 balances by address Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-erc20-owner-address- --- ## Get tokens Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens --- ## Get ERC-721 balances by address Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-erc721-owner-address- --- ## Get ERC-1155 balances by address Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-erc1155-owner-address- --- ## Get supported tokens for price data Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-price-supported --- ## Get token price Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-price --- ## Token lookup Source: https://docs.b3.fun/data/api-reference/get-insights-v1-tokens-lookup --- ## Resolve Source: https://docs.b3.fun/data/api-reference/get-insights-v1-resolve-input- --- ## Get blocks Source: https://docs.b3.fun/data/api-reference/get-insights-v1-blocks --- ## Get contract ABI​ Source: https://docs.b3.fun/data/api-reference/get-insights-v1-contracts-abi-contract-address- --- ## Get contract metadata​ Source: https://docs.b3.fun/data/api-reference/get-insights-v1-contracts-metadata-contract-address- --- ## Decode logs and transactions​ Source: https://docs.b3.fun/data/api-reference/post-insights-v1-decode-contract-address- --- ## Get NFT balances by address Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-balance-owner-address- --- ## Get collection Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-collections-contract-address- --- ## Get NFTs Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts --- ## Get NFT owners by contract Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-owners-contract-address- --- ## Get NFT owners by token Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-owners-contract-address-token-id- --- ## Get NFT transfers Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-transfers --- ## Get NFT transfers by transaction Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-transfers-transaction-transaction-hash- --- ## Get NFT transfers by contract Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-transfers-contract-address- --- ## Get NFTs by contract Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-contract-address- --- ## Get NFT transfers by token Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-transfers-contract-address-token-id- --- ## Get NFT by token ID Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-contract-address-token-id- --- ## Force refresh collection metadata Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-metadata-refresh-contract-address- --- ## Force refresh token metadata Source: https://docs.b3.fun/data/api-reference/get-insights-v1-nfts-metadata-refresh-contract-address-token-id- --- ## Get wallet transactions Source: https://docs.b3.fun/data/api-reference/get-insights-v1-wallets-wallet-address-transactions --- ## Profile Lookup Source: https://docs.b3.fun/data/profiles/get- --- ## Set Profile Preference Source: https://docs.b3.fun/data/profiles/post-preference --- ## Set Custom Display Name Source: https://docs.b3.fun/data/profiles/post-display-name --- ## List Collections Source: https://docs.b3.fun/createkit/api-reference/get-collections --- ## Create NFT Collection Source: https://docs.b3.fun/createkit/api-reference/post-collections --- ## Delete Collection Source: https://docs.b3.fun/createkit/api-reference/delete-collections --- ## Count Collections Source: https://docs.b3.fun/createkit/api-reference/get-collections-count --- ## Get Collection by Address Source: https://docs.b3.fun/createkit/api-reference/get-collections-predicted-address- --- ## Bulk Delete Collections Source: https://docs.b3.fun/createkit/api-reference/delete-collections-bulk --- ## Register Referrer Source: https://docs.b3.fun/createkit/api-reference/post-referrers ---