FLOKI

Floki dates its birth to June 25, 2021, after Elon Musk said his Shiba Inu would be named Floki. The more consequential event came days later. In the project’s own retrospective, two early developers abandoned or harmed the launch and the community recovered control before a V3 relaunch at 01:00 UTC on July 8. That account is project testimony, not an independent adjudication.

BNB Chain followed on July 20. From then on FLOKI was a two-chain token, but the repeated labels V1, V2 and V3 make contract identity part of the story. Today’s verified addresses come from the later Nottingham era, not from the first viral launch.

The January 2022 Nottingham upgrade took a snapshot, distributed new tokens one-for-one and deployed fresh Ethereum and BNB contracts. The code fixes 10 trillion units per chain, tracks vote checkpoints and lets holders delegate voting power. Floki’s timeline records completion on January 23 and the first DAO vote on February 8.

That was a governance mechanism, not a legal incorporation event. DAO votes later addressed blacklisted wallets, tax reductions and burns, but proposals still need an execution path. The project’s own legal text denies corporate voting and ownership even while protocol votes remain available.

Floki’s February 2023 vote reduced the buy/sell tax to 0.3% and destroyed roughly 5.1 trillion tokens held in the original cross-chain bridge. Current documents say ordinary transfers are untaxed and centralized exchanges can facilitate 1:1 movement between Ethereum and BNB Chain. Each contract still reports a fixed 10-trillion starting supply.

Burns therefore require chain-aware reading. The token contracts do not contain a mint or an automatic burn function; supply leaves circulation when tokens are sent to a burn address. FlokiFi fee purchases and early-unstake penalties can add burns, but product revenue, treasury receipts and circulating supply are different measures.

FlokiFi Locker launched on July 31, 2022, supporting locks and vesting for fungible tokens, LP positions, NFTs and ERC-1155 assets. Its published economics send 25% of fees to FLOKI buy-and-burn and 75% to treasury. This gives FLOKI an indirect fee link rather than a claim on revenue.

Staking went live on October 27, 2023 alongside TokenFi. A FLOKI holder locks for 3, 12, 24 or 48 months and earns the separate TOKEN asset; leaving early burns 5%, 10%, 15% or 20%. TokenFi may be governed by the Floki DAO, but TOKEN and FLOKI are not the same property.

Valhalla completed the longest product arc on June 30, 2025, launching its browser MMORPG on opBNB mainnet. FLOKI powers the game economy and on-chain NFT interactions. A shipped game is stronger evidence than years of roadmap copy, though adoption and revenue still need their own measurements.

On January 26, 2024, Hong Kong’s Securities and Futures Commission placed the Floki and TokenFi staking programs on its suspicious investment-products list. The SFC said they were unauthorised for offering to the Hong Kong public and that the administrator, The People’s Movement Corp., had not demonstrated how advertised annualised targets of 30% to over 100% could be achieved.

That notice concerns the staking products and their marketing in one jurisdiction. It should not be rewritten as a court judgment about the token. It does show why TOKEN rewards, stated targets and regulatory eligibility must be separated from a holder’s base right to transfer FLOKI.

The published Solidity contract lets its owner replace tax and treasury handlers. Both live deployments returned 0x000000000000000000000000000000000000dEaD as owner when reviewed, so that onlyOwner route is no longer usable. This is a meaningful constraint: there is no proxy and no owner mint function in the reviewed token code.

Operations remain administered elsewhere. The official treasury page lists Ethereum and BNB treasury wallets and says a multisig needs at least three approvals; the FlokiFi page lists separate contract multisigs across supported chains. At the September 4 review, the Ethereum treasury handler was controlled through the project Safe, while the BNB handler owner was a single externally owned account; handler code can change operational parameters and destinations. The cited pages do not identify every signer or the person controlling that BNB account. DAO voice, immutable token supply and operational custody are therefore three different layers, not one claim of decentralization.

The LCX-hosted MiCAR paper describes 18 decimals, 10 trillion units across both chains, no token-contract tax and no present governance right. The reviewed deployments and Floki materials instead show 9 decimals, 10 trillion nominal units per chain, a 0.3% buy/sell charge through a handler and vote delegation. These sources disagree about the technical specification. Deployed code establishes what the token can do; the existence of protocol voting does not grant the corporate rights denied by the project disclaimer.