bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 13쪽 중 1쪽
# 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 프로젝트로 돌아가기