BNBTiger Club research

Research and project history.

A chronological publication of BNBTiger news, contract changes, community accounts, and independent on-chain reviews.

Sort timeline
Club research

Dead address, not a locked vault.

An independent review of the TigerOG project’s Freedom Bridge, its BNBTiger-to-TIGEROG migration contract, and the separate Axelar cross-chain path.

The verified converter sends legacy BNBTiger from the caller directly to 0x…dEaD, then sends the same raw amount of TIGEROG from its reserve to that caller. It does not place the legacy token in a project-controlled vault.

The migration contract exposes no downgrade, redemption, release, unlock, or reverse-conversion function. Axelar can move TIGEROG between supported chains, but it does not provide a route back into the legacy BNBTiger contract.

Reviewed project
TigerOG / Freedom Bridge
Finding
One-way legacy conversion
Evidence
Verified code + receipt + RPC
Report
FB-TIGEROG-01

Editorial standard: project statements are separated from independently reproducible contract and transaction evidence.

On-chain event

A live conversion shows where legacy tokens go.

A successful conversion transaction records BNBTiger moving from the caller directly to 0x…dEaD. TIGEROG then moves from the migration contract’s reserve to that caller in the same raw amount.

This matters because the legacy tokens are not deposited into an unlockable project vault. The verified migration contract exposes an upgrade path, but no downgrade, redemption, release, or reverse-conversion function.

Public announcement

TIGEROG and Freedom Bridge are announced.

The legacy-token community later introduced a third contract: TIGEROG, 0xCF7F…dbB5. A 22 January X post presented Freedom Bridge as an optional path from BNBTiger to a tax-free, multichain TIGEROG and specifically told holders to review the information before converting.

Freedom Bridge also references Axelar’s Interchain Token Service. That cross-chain system concerns TIGEROG moving between supported networks; it is separate from reversing TIGEROG back into the legacy BNBTiger contract.

Community account

The holder community fractures.

Not every holder accepted the move to the replacement contract. A group continued organizing around the legacy 0xac689… token and described its work as a community takeover. Its own account says the migration divided participants into those supporting the original contract and those following the new contract.

Context: “abandoned,” “takeover,” and similar descriptions express that group’s perspective. The verifiable fact is that both contracts continued to exist and were promoted by different communities.

Verified exchange record

A replacement BNBTiger launches.

A new Bnb Tiger Inu contract, 0xF858…e4cB5, was introduced in September 2025. The group behind that relaunch said a compromised marketing wallet made the old structure unsafe. That explanation is a project statement; it is not independently proven by the exchange notice.

What is independently documented is the exchange action: on 9 September, BitMart said it completed a project-requested swap from the old BNBTIGER to the new contract at a 10:3 rate, with trading scheduled to resume on 10 September.

Published history

The original BNBTiger contract begins.

Contemporary community posts place BNBTiger’s launch on 3 January 2022. The lasting identifier is the BNB Smart Chain contract beginning 0xac68931b. Later project publicity described BNBTiger as a decentralized experiment rather than a conventional company-owned token.

Evidence note: the date comes from archived promotional material; the contract address is independently visible on BscScan.