How the $2HATS Smart Contract Collects and Distributes Funds
Contract Address (BSC): 0x40fc200e43725771923e4bd8bec3115af8c6ffff
View on BscScan: https://bscscan.com/address/0x40fc200e43725771923e4bd8bec3115af8c6ffff
One of the most common questions in the $2HATS community is: "How does the tax actually work, and when does that money show up in the treasury or mining pool?" This article breaks down the mechanics step by step, using the published wallet registry from the official project site.
1. How the Tax Is Collected
Every time $2HATS is bought or sold on-chain, the smart contract automatically applies a small transaction tax:
Buy tax: 1%
Sell tax: 2%
This isn't sent anywhere at the moment of the trade. Instead, like most BEP-20 tax tokens on BNB Chain, the contract collects the taxed tokens and holds them in its own contract balance first. You can verify this at any time by checking the token balance held by the contract address itself on BscScan.
2. The 90/5/5 Revenue Split
Once collected, the tax allocation is divided as follows:
90% — Project treasury and $BTCB mining pool funding
5% — Reserved allocation (operations/marketing)
5% — Reserved allocation (liquidity support)
This split is what funds the $BTCB mining pool, the $JACK faucet, and the referral program over time — it's the economic engine behind the ecosystem, not just a static tax.
3. From Contract Balance to Wallet: The Swap-and-Send Step
Collected tax tokens sitting in the contract don't do anything useful as raw $2HATS — they need to be converted. The contract uses a swap-and-send mechanism:
The contract accumulates taxed $2HATS tokens from buys and sells.
Once the accumulated balance reaches the equivalent of 0.01 BNB, the swap threshold triggers.
At that point, the accumulated tokens are automatically swapped via PancakeSwap into BNB, then routed toward $BTCB accumulation.
The converted funds are sent to the project's published revenue and treasury wallets according to the 90/5/5 split.
Because the threshold is a fixed BNB value rather than a fixed token count, how often it triggers depends on trading activity and the current token price. Busier trading days mean the threshold fills faster and distributions happen more frequently. Quiet periods mean it takes longer to accumulate enough taxed tokens to hit 0.01 BNB, so the swap-and-send event fires less often.
4. The Published Wallet Registry
Per the project's official "Wallets in one lane" registry, here is where funds actually land after conversion:
Role
Address
Revenue receiver
0x54d320d19bf011df984fee3910f4c0dc9e6186a3
Treasury / controller
0x999A1279fD5EbA8b2a8a02F0b44EeA1b583aA185
Reward asset ($BTCB, BSC)
0x7130d2A12B9BCbFAe4f2634d864A1Ee1Ce3Ead9c
The revenue receiver is the first stop after the swap-and-send trigger fires — this is the wallet that catches the converted tax. From there, funds move toward the treasury/controller wallet, which is the lane that funds both ongoing treasury $BTCB accumulation and the mining pool. The project has not published a separate, standalone wallet exclusively for the mining pool distinct from the treasury/controller address — the treasury/controller appears to serve both roles.
5. Important: Distribution Timing
This is the part the community should understand clearly: funds collected by the contract do not move instantly, and reaching the receiver wallet is not the final step either.
Tax collection happens in real time with every buy/sell.
Conversion and movement to the revenue receiver only happen once the 0.01 BNB threshold is reached — not continuously, and not on every single trade.
From the revenue receiver, funds are then routed onward to the treasury/controller wallet for $BTCB accumulation and mining pool funding — this is a second step, and it doesn't necessarily happen on the same schedule as the initial swap-and-send.
Depending on trading volume, gas conditions, and price movement, there can be a noticeable delay between when tax is first collected and when it's fully reflected in the treasury or mining pool balance.
In short: if you check the treasury wallet right after a trade and don't see funds move yet, that's expected. Tokens may be sitting in the contract awaiting the 0.01 BNB threshold, or sitting in the revenue receiver awaiting the next transfer to treasury. Nothing has gone missing — it's a multi-step routing process by design. The project encourages the community to track balances over days, not minutes, for an accurate picture of treasury and mining pool growth.
6. Verifying It Yourself
Full transparency is available on-chain and via the official project site:
Contract page: https://bscscan.com/address/0x40fc200e43725771923e4bd8bec3115af8c6ffff
Live stats board: treasury, reserve, mining status, supply, LP, and burn metrics are tracked live on the official site
Anti-scam note: the only official contract is 0x40fc200e43725771923e4bd8bec3115af8c6ffff — always cross-check any wallet or contract shared elsewhere against the official registry above, and ignore addresses shared via DM.
2 Hats Jack is a meme-inspired project. Nothing in this article is financial advice, and no treasury growth, mining rewards, or token performance is guaranteed.

BUY 2HATS NOW ON BINANCE

🎩🎩