SAFU / USDCINDEPENDENT COMMUNITY TOKENCHAIN LIVESAFU Fund is an independent BNB Chain movement created in response to the reported incident. Its 3% trading tax produces a live public ledger of USDC routed by the token’s processor—every contract and calculation open for anyone to verify.
SAFU is a volatile community token—not insurance, a savings product, or a promise of reimbursement.
Independent community project. Not affiliated with, endorsed by, sponsored by, or operated by Binance, BNB Chain, Changpeng Zhao, Nest Clearing and Custody, Circle, Flap, or PancakeSwap. Participation provides no insurance, reimbursement rights, or entitlement to Binance’s Secure Asset Fund for Users.
After Binance reported a major hot-wallet compromise, the community created SAFU as an independent BNB Chain response. The timeline below separates Binance’s published incident facts from the token’s later community origin.
Used as movement context, not as evidence of endorsement. SAFU Fund is independent from Changpeng Zhao and Binance.
Binance reported that its hot wallets were compromised around this time. The investigation remains subject to a final post-mortem.
Binance reported the estimate and said it would cover all losses using the SAFU fund and company funds.
The initial update reported cooperation with blockchain partners to freeze affected assets.
An independent expression of solidarity and transparent community action—not an official Binance initiative.
Read Binance’s incident update ↗ Facts remain labelled evolving until a final technical post-mortem.
The 3% applies to eligible buys and sells. Ordinary wallet-to-wallet transfers are not taxed. The processor retains a protocol fee before the remainder is routed.
A buy or sell through the configured market enters the tax mechanism.
The token contract applies 300 basis points to eligible trades.
Flap retains 10% of the collected tax—not 10% of the whole trade.
The post-protocol remainder is routed to the configured BNB Chain address.
Execution, token liquidation, price impact, and rounding can affect realized USDC amounts.
Green marks only facts independently readable from contracts. Amber marks the unresolved organizational-control claim. Full addresses remain visible, copyable, and linked.
0x7c907D1CE734B73e9236DCd06cefcB6346857777The canonical SAFU token contract used by this dashboard.
0x024f18294970B5c76c0691b87f138A0317156422Implementation behind the token’s minimal-proxy bytecode.
0x7FDB004751a588Fbc6Cf67B89022384c573BC9B6The contract whose cumulative getter is the primary impact total.
0x20dA3Ebe08379117fDB7f15Ff55456813b546554The configured SAFU/USDC market used for the main liquidity proof.
0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580dThe quote asset used for processor totals and attributable transfers.
0x420ef1f25563593aF5FE3f9b9d3bC56a8bd8c104Address matches Binance’s published Ethereum SAFU address, but BNB Chain control is unconfirmed.
0x8a08d98cbb218fceb318ecf3abc1ba43d8a7ab0eConfigured receiver of the 10% share of collected trading tax.
Live check: verifying…The token owner reads as the zero address.
Live check: verifying…The main pool’s LP balance at the dead address is compared with total LP supply.
2126-10-06 · 13:58:56 Europe/PragueContract timestamp resolves to 6 October 2126 at approximately 13:58:56 Europe/Prague time.
Rows require all three conditions: BNB Chain USDC, source equals this token’s processor, and destination equals the configured recipient.
| Amount | Time | Block | Transaction | Route |
|---|---|---|---|---|
| Scanning verified USDC transfers… | ||||
“Crypto is strongest when accountability is visible. This movement turns community energy into an auditable public trail.”
Every contract and attributable transfer is public.
The movement supports the principle of protecting users.
Unresolved facts stay labelled unresolved.
Market data is visually and technically separate from the impact proof. Failure here never replaces or blocks direct contract reads.
No audit badge or interface can eliminate token, liquidity, smart-contract, market, or organizational-control risk. Independently verify every address.
No. SAFU Fund is an independent community token and is not affiliated with, endorsed by, sponsored by, or operated by Binance.
No. Buying or holding SAFU creates no insurance coverage, reimbursement right, claim against Binance, guaranteed return, or entitlement to Binance’s SAFU fund.
Eligible buys and sells incur 3%. Flap retains 10% of the collected tax; 90% of the collected tax is routed to the configured BNB Chain recipient after execution effects.
Because 90% of a 3% trading tax equals approximately 2.7% of taxed trade value. The remaining approximately 0.3% represents Flap’s 10% share of the tax.
No. The hexadecimal address matches Binance’s published Ethereum SAFU address, but Binance control of the BNB Chain counterpart has not been confirmed.
The Ethereum address contains deployed smart-contract code. The same hexadecimal address on BNB Chain currently has no code. Matching characters across chains do not by themselves prove common control.
The dashboard checks the main V2 LP token supply against the balance held at the dead address. This is an on-chain condition, not a guarantee of market depth or price stability.
The current owner reads as the zero address and total supply is fixed at one billion in the audited configuration. Review the verified implementation and current contract state independently.
No. The audited configuration applies the tax to eligible buys and sells; ordinary wallet-to-wallet transfers are not taxed.
Net sent comes directly from the processor’s cumulative getter. Gross tax and protocol fee are reconciled with integer math using the live 10% fee configuration.
The page marks the data degraded after 45 seconds and stale after 90 seconds. It never substitutes zero. If unavailable, it explicitly removes the live claim.
Use the BscScan links in the proof grid, the live block number, the Flap tax page, Binance’s SAFU FAQ, and the methodology sources below.
The edge gateway reads two public BNB Chain RPC providers at the same block, caches normalized snapshots briefly, and exposes freshness and agreement instead of hiding failures.
Verifying RPC agreement…