B3 백서

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 13쪽 중 2쪽

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:
프로젝트로 돌아가기