Prelaunch mechanics, clearly stated.
Supply, bonding curve, tax flow, treasury routing, mining status, and launch boundaries before token creation.
What 2 Hats Jack is trying to be.
2 Hats Jack is a meme-inspired token project built around transparent wallet visibility, a $BTCB-oriented treasury story, and a mining concept that aims to reward participation after revenue reaches the controlled receiver wallet.
The project is not affiliated with, endorsed by, or associated with Jack Mallers, Strike, or Twenty One. It is inspired by Bitcoin conviction energy, not by any official partnership or brand license.
Supply, bonding curve, and first liquidity.
- Total token supply at launch: 1,000,000,000 $2HATS
- The launch is expected to move through a bonding curve that completes at 18 $BNB.
- When that point is reached, 20% of the token supply and the raised $BNB are deposited into PancakeSwap as the opening liquidity pool.
- The exact live liquidity pair, burn destination, and contract address only become final once the token is created on four.meme.
Wallet funding starts at graduation, not before.
The bonding curve is the launch phase. Four.meme documentation describes tax-token fees as activating after the token graduates from the bonding curve, so public project wording should not claim that treasury, reward, burn, or liquidity wallets are funded before bonding completes.
- During bonding, buyers participate in the curve and help push the launch toward the graduation point.
- At bonding-curve completion, the token graduates and the opening PancakeSwap liquidity pool is seeded.
- After graduation, eligible swaps carry the configured trading tax and the tax-routing system begins funding the configured lanes.
- Any pre-graduation contract accruals should be treated as protocol-held launch mechanics unless and until outbound wallet funding is visible on-chain.
The post-graduation 90 / 5 / 5 split.
- Buy tax target after graduation: 1%
- Sell tax target after graduation: 2%
- On taxed post-graduation swaps, the intended first-layer routing is 90% revenue / 5% burn / 5% liquidity.
- The 5% burn lane and the 5% liquidity lane are outputs of the four.meme launch contract behavior, not manually redirected later by the project.
Control begins only after the 90% bucket lands.
The project-controlled logic starts only when the 90% revenue bucket reaches the published receiver wallet. From there, the current intended downstream plan is:
- 65% to treasury as $BTCB
- 30% to mining rewards as $BTCB
- 5% retained as Reserve $BNB
This downstream BTCB treasury and rewards flow begins after the receiver wallet receives routed tax proceeds. It is separate from the four.meme-controlled burn and liquidity lanes.
Current public reference addresses.
- Revenue receiver / collector: 0x54d320d19bf011df984fee3910f4c0dc9e6186a3
- Treasury / controller: 0x999A1279fD5EbA8b2a8a02F0b44EeA1b583aA185
- Treasury target asset: $BTCB on BNB Smart Chain — 0x7130d2A12B9BCbFAe4f2634d864A1Ee1Ce3Ead9c
Wallet connection and future claim flow.
The mining panel can connect a wallet, check for BNB Smart Chain, attempt chain switching when needed, and store the connected address locally.
The live mining contract address and the final claim contract behavior remain pending until deployment.
Disclosure limits.
- Not financial advice.
- No return, price, treasury growth, reward frequency, or liquidity outcome is guaranteed.
- Any buyer should verify the real contract address, launch URL, wallets, and liquidity pair before any on-chain action.
