Tiger King Coin Review: Contract Identity, Liquidity, and Project-Liveness Audit
Is there a currently accountable, independently verifiable project and liquid market behind the V2 token, or only a transferable legacy contract and stale promotional footprint?
Do not buy TKING because the unit price looks small, a chart exists, holders remain, or the 2021 community announced a migration. New exposure stays blocked until the exact V2 contract and migration lineage, current official team and product activity, contract provenance, charitable and utility claims, pool address and reserves, liquidity control, holder concentration, executable test sale, legal access, custody, and full-position exit all pass current checks.
- Risk
- Extreme
- Research fit
- No new exposure while project liveness, current official control, audit evidence, pool liquidity, holder concentration, and a full-size exit remain unverified
- Aggregate buy score
- Not published
Tiger King Coin at a glance
Avoid by default - decision blockedExtreme
- Established0
- Needs proof4
- Hard risk11
- Context0
V2 mapped; ticker remains ambiguous
V2 mapped; ticker remains ambiguous
Similar match, not exact match
- 01identitypartial / 4 claims
- 02livenessblocked / 4 claims
- 03contractconflicted / 3 claims
- 04liquidityblocked / 4 claims
- 05executionblocked / 4 claims
- 06lossblocked / 3 claims
Start with the exact asset, then retire what the old page got wrong
Two Ethereum contracts use the Tiger King name. The older V1 contract is an exact-match verified token with a 1% burn on transfers. Historical project announcements document a 1:1 snapshot migration and identify the later V2 address. The V2 contract is a simpler fixed-supply ERC-20 whose Etherscan page uses similar-match source code and lists no submitted contract security audit. Transferability and holder count do not prove a live product, accountable team, charitable activity, market depth, or a sellable position. Until current primary evidence closes those gaps, the research outcome is avoid by default.
The 2022 article repeated project road-map and adoption claims, named unsupported exchange routes, published annual price targets through 2030, and implied regulatory approval and team activity without decision-grade primary evidence or an executable-liquidity test.
The original URL and publication date are preserved, but the price forecasts, exchange instructions, adoption assumptions, regulatory implication, and recommendation are withdrawn. The replacement begins with contract lineage, present project liveness, current liquidity, source limitations, test-sale execution, and total-loss controls.
01Reviewed V2 token0x24e89bdf2f65326b94e36978a7edeac63623dafa
Ethereum ERC-20 with 18 decimals and 900 billion token supply shown by Etherscan. The source is a similar bytecode match; constructor differences can affect deployed parameters.
Verify source02Historical V1 token0xC626d951Eff8E421448074bd2aD7805C6D585793
Exact-match verified Ethereum contract originally minting one trillion TKING and burning approximately 1% on transfers. Historical announcements describe it as deprecated after the V2 snapshot.
Verify source03Historical migration1:1 snapshot in August 2021
The project announcement channel described a holder snapshot, halted trading, 1:1 V2 redistribution, and relaunch at the reviewed V2 address. This is historical project evidence, not proof of current control or support.
Verify source04Current project layerNot sufficiently verified
The website linked from Etherscan could not be independently retrieved during this review, and no reviewed current primary source established accountable development, treasury, charity reporting, governance, or a maintained product.
Verify sourceA transferable token is not the same as a live, investable project
TKING must pass four separate layers: canonical identity, current accountable project evidence, contract and liquidity controls, and a real exit. The 2021 migration helps resolve which Ethereum token the historical team called V2, but it does not establish current product delivery, audited security, charitable impact, liquidity, or buyer protection.
01Historical and deprecatedV1 contract
The V1 source includes an automatic burn on transfers and public burn functions. Project announcements told holders that a snapshot migration would replace it.
Do not buy or value V1 as current TKING. Preserve it only as lineage evidence and reject migration messages asking for funds or seed phrases.02Simple fixed-supply ERC-20V2 contract
The reviewed V2 ABI exposes standard transfer and allowance functions without a public mint, pause, tax, blacklist, or owner function. Etherscan identifies the source as a similar match, not an exact match.
Read deployed constructor values and bytecode directly. Simplicity reduces one code surface but does not create project value or liquidity.03Historically documentedMigration evidence
The announcement channel described an August 2021 1:1 snapshot and later published the V2 address and a Uniswap V2 pair route.
Use it to map history, not to assume every holder received tokens, the pair remains liquid, the team is active, or a new migration is legitimate.04UnresolvedCurrent value path
No reviewed current primary evidence established recurring product usage, verifiable charity flows, protocol revenue, token-holder rights, treasury reporting, or accountable operations.
Keep the decision blocked until current, independently checkable evidence exists and a full-size sale works within written limits.Claims that need careful treatment
Both contracts display Tiger King and TKING. The older exact-match contract has transfer burns; the later V2 contract is a different, simple fixed-supply ERC-20.
Identify chain and full contract before reading balances, price, holders, or pool data. Treat V1 as deprecated historical lineage unless current primary evidence proves otherwise.The historical announcement channel said a V2 audit had been completed, while Etherscan currently lists no submitted contract security audit for the V2 address and the reviewed source is only a similar match.
Require the original report, auditor identity, scope, findings, deployed bytecode match, and current relevance. Do not convert a Telegram file reference into an audit pass.The V1 contract began at one trillion and burns on transfers. The V2 Etherscan token page shows a 900 billion maximum total supply while some market aggregators publish differing circulating figures.
Read totalSupply on the exact contract and reconcile known treasury, exchange, pool, migration, burn, and holder balances before valuation.Historical materials promoted tiger support, dApps, community initiatives, and Joe Exotic-related activity, but no reviewed current primary reporting substantiated ongoing operations or economic value capture.
Require dated deliverables, repositories, accountable entities, wallets, receipts, beneficiaries, governance, and independent confirmation. Marketing copy is not evidence.Fifteen dimensions, no hidden score
Each dimension keeps the evidence, current status, limitation, and decision use visible. The model does not average away a failed contract, security, liquidity, custody, or exit condition.
01V2 mapped; ticker remains ambiguousContract identity
partial
Historical project announcements identify 0x24e8...3dafa as V2, while the older 0xC626...85793 contract remains on-chain under the same name and symbol.
Use chain ID and full address at every step. Reject ticker, logo, or wallet label as identity proof.Linked hard stops: identity
02Historical announcement evidenceMigration lineage
supported
The project channel described a 1:1 snapshot redistribution and V2 relaunch in August 2021.
Verify a holder's own transaction history. Never send V1 or approve a wallet to claim a surprise migration.Linked hard stops: identity
03Narrow ERC-20V2 contract surface
partial
The V2 ABI exposes standard balances, transfers, and allowances with fixed constructor supply and no public mint or owner controls in the matched source.
Confirm deployed bytecode and constructor values; narrow code does not prove issuer integrity, utility, or liquidity.Linked hard stops: contract
04Similar match, not exact matchSource provenance
supported
Etherscan warns that the V2 contract matches another contract's deployed bytecode and that constructor differences may alter behavior.
Treat name, symbol, decimals, initial balance, owner, and fee receiver as deployed parameters that require direct chain verification.Linked hard stops: contract
05Current pass not establishedSecurity audit
conflicted
Etherscan lists no submitted contract security audit. A historical announcement referenced a V2 audit file, but its scope and deployed-bytecode match were not independently validated here.
Require original report, auditor, scope, findings, fixes, bytecode match, and later changes before crediting audit evidence.Linked hard stops: contract
06Not sufficiently verifiedProject liveness
blocked
No reviewed current primary source established a maintained product, active repository, accountable team, current roadmap delivery, treasury reporting, or support process.
A transferable token, holder count, or social profile does not pass project liveness.Linked hard stops: liveness
07Current use unresolvedToken utility
blocked
Historical whitepaper and promotional claims do not establish a current, measurable reason users must acquire or retain TKING.
Require live users, transactions, recurring demand, product access rules, and token-holder rights from current primary evidence.Linked hard stops: liveness
08Current reporting unresolvedCharitable claims
blocked
Historical materials framed tiger support as part of the project, but reviewed current sources did not provide audited donation flows or recurring impact reporting.
Verify entities, wallets, recipients, receipts, dates, governance, conflicts, and independent beneficiary confirmation.Linked hard stops: liveness
09Contract supply visible; circulation uncertainSupply and distribution
partial
V2 total supply can be read on Ethereum, but exchange, pool, treasury, dormant, lost, and holder classifications need current reconciliation.
Use live on-chain balances and concentration analysis rather than aggregator circulating-supply labels.Linked hard stops: identity, liquidity
10Not reviewed to decision gradeHolder concentration
blocked
A holder count does not show related wallets, exchanges, pools, treasury, insiders, migration distributors, or immediately sellable supply.
Cluster top holders, label contracts and venues, and stress simultaneous selling before sizing.Linked hard stops: liquidity
11Current reserves and control unverifiedPool liquidity
blocked
Historical announcements named a Uniswap V2 pair, but current reserves, LP ownership, locks, fee tier, router path, and full-size exit were not established by current primary evidence.
Read the exact pair contract, reserves, LP token distribution, liquidity controls, route, and quote immediately before any action.Linked hard stops: liquidity, execution
12Hard stop until testedSell execution
blocked
Thin legacy-token markets can display a price while a meaningful sale produces extreme impact or fails.
Simulate and then execute only a minimal lawful test round trip; stress-quote the full position before considering entry.Linked hard stops: execution, loss
13Sparse and inconsistentMarket data quality
partial
Aggregators can disagree on supply, market cap, venues, and activity, and displayed prices may be based on tiny trades.
Use on-chain reserves and executable router quotes with timestamps. Never infer liquidity from market cap.Linked hard stops: liquidity, execution
14MaterialBrand and legal dependency
partial
The token historically relied on a celebrity and entertainment brand, charitable framing, and promotional claims that can create rights, endorsement, regulatory, and continuity risks.
Verify current entities, permissions, disclosures, jurisdiction, venue access, and promotional responsibility before relying on the brand.Linked hard stops: liveness, loss
15Standard Ethereum risks plus legacy scamsCustody and recovery
supported
Two same-ticker contracts and historical migration messaging increase phishing, fake-claim, wrong-token, approval, and support-impersonation risk.
Use full addresses, isolated test wallets, hardware confirmation, minimal approvals, and a tested venue-return route.Linked hard stops: identity, execution, loss
Scenarios define evidence, not price targets
Verifiable reactivation
PremiseA currently accountable project publishes auditable product, treasury, charity, contract, holder, and liquidity evidence and a meaningful market supports full-size exits.
WatchCurrent entities, repositories, deliverables, user activity, wallets, reports, audits, pair reserves, LP control, holders, and executed sales.
TreatmentRestart research from zero. Historical promises do not receive credit, and all six hard stops must pass before any capped exposure is considered.
Token trades, project remains stale
PremiseThe V2 ERC-20 remains transferable and occasional trades produce a displayed price, but accountable operations and durable utility remain unverified.
WatchTrade count, unique counterparties, reserve depth, holder changes, official updates, repository work, product usage, and verifiable cash flows.
TreatmentRemain out. Transferability and a chart are insufficient for an investment thesis or reliable exit.
Identity or liquidity failure
PremiseA buyer uses V1, a copycat, a fake migration, a stale pair, or a pool too thin to exit; approvals, support impersonation, or concentration amplify losses.
WatchFull contracts, domains, wallet prompts, pair tokens, reserves, LP holders, top wallets, quote impact, failed sales, and migration messages.
TreatmentStop, disconnect, revoke unnecessary approvals, move unaffected assets if safe, document transactions, and do not send more funds to recover losses.
Run the gates, arithmetic, and exact route separately
The workbench stores inputs only in the current browser session. It does not fetch prices, publish a recommendation, or convert a passed checklist into suitability. Raydium live execution evidence remains in the separate section below.
TKING: verify the evidence before price
Six hard stops
- 01
Ethereum chain, current V2 contract, V1 lineage, personal migration history, decimals, supply, wallet label, and venue contract all match full-address evidence.
Unknown or failed = stop - 02
A current official domain, accountable team or entity, maintained product or repository, support route, treasury, utility, and charitable reporting are independently verified.
Unknown or failed = stop - 03
Deployed V2 bytecode, constructor parameters, source provenance, functions, audit scope, approvals, token distribution, and privileged or related addresses are understood.
Unknown or failed = stop - 04
The exact current pool, pair tokens, reserves, router, LP ownership or locks, holder concentration, venues, and full-position price impact are verified on-chain.
Unknown or failed = stop - 05
A minimal lawful buy, transfer, approval, test sale, withdrawal, return deposit, and sale work with measured fees, spread, slippage, settlement, and taxes.
Unknown or failed = stop - 06
A total-loss budget, custody and recovery plan, thesis breakers, review date, and full-position exit are written and do not depend on new buyers, a migration, or a prior price.
Unknown or failed = stop
Unknown is not a pass. Verify every hard stop with current evidence.
Decision math, not a forecast
Multiply a user-supplied live supply by a hypothetical price. The result says nothing about probability, demand, custody, or whether the full position can exit.
Supply x target price. No probability or liquidity assumption is included.
Route verifier
Use 0x24e89...3dafa only after matching it in Etherscan, wallet, venue, router, pair, and transaction simulation. Read constructor values and totalSupply directly.
The Etherscan source is a similar match and does not prove current project activity, audit coverage, or liquidity.- Ethereum chain ID 1
- Full V2 contract
- 18 decimals and live totalSupply
- Deployed bytecode and constructor values
- Venue and wallet contract match
- Minimal transfer and return path
A research thesis is incomplete until the full position can exit
Contract labels, website ownership, social accounts, pool addresses, reserves, liquidity ownership, token balances, holder concentration, venue support, quotes, transfer behavior, approvals, taxes, spread, price impact, deposits, withdrawals, and legal access can change. Never rely on this page for a live quote. Re-verify the full chain, contract, pool, router, reserves, and a minimal round-trip immediately before any action; unknown remains a hard stop.
- 01
Read V2 totalSupply, top holders, labeled exchanges, pair contracts, and recent transfers directly from Ethereum with a timestamp.
- 02
Resolve the current official pool from at least two independent paths, then verify pair tokens, reserves, router, fee, LP supply, and LP holders on-chain.
- 03
Quote a minimal buy and sale and the full intended position. Record expected output, price impact, gas, router, allowance, route, and block number.
- 04
Run only a minimal lawful round trip after all other gates pass; confirm the received amount and revoke unnecessary approvals.
- 05
Test exchange deposit and withdrawal support for the exact V2 contract. A ticker listing can map to a different chain or contract.
- 06
Keep displayed price, market cap, holder count, momentum, and social activity outside the evidence verdict. None proves a liquid exit or live project.
Define the stop conditions before the position exists
Exit or remain out
- The exact V2 contract or migration lineage cannot be independently confirmed from full-address and transaction evidence.
- Current official project ownership, team accountability, product delivery, treasury, utility, or charity reporting remains absent or unverifiable.
- The deployed bytecode, constructor parameters, source, audit claim, or token distribution cannot be reconciled.
- The named pool is stale, reserves are immaterial, LP control is concentrated or unknown, or holder concentration creates an exit overhang.
- A minimal sale, venue round trip, approval revocation, or full-size quote fails or breaches written slippage and loss limits.
- New exposure requires a celebrity event, social campaign, migration, exchange promise, prior high, or new buyers rather than measurable current demand.
Protect the route
- Never send V1 or V2 tokens, ETH, or stablecoins to a person or website promising migration, recovery, validation, support, or airdrop eligibility.
- Never enter a seed phrase or private key into a TKING, celebrity, charity, exchange, wallet-sync, audit, claim, or recovery page.
- Verify chain 1 and the full contract in Etherscan, wallet, router, pair, and signed transaction. Same ticker and logo are not identity proof.
- Use an isolated test wallet, exact allowance, hardware-wallet confirmation, and immediate revocation after a test route.
- Check the router and spender independently. A malicious approval can drain unrelated tokens even when the TKING contract itself is simple.
- Treat unsolicited DMs, urgency, guaranteed relaunch prices, celebrity claims, exchange promises, and blacklist threats as stop signals.
Who can research further
- The default fit is no new exposure while any hard stop is unknown or failed.
- Only researchers who can decode Ethereum contracts, pair reserves, LP ownership, holder concentration, transaction simulations, and approvals should investigate further.
- Any future position must be sized as a possible total loss and remain small enough that a failed exit does not affect financial security.
- A holder of legacy V1 or V2 should separate recovery and exit verification from decisions to add more capital.
Write before entry
- 01Inventory V1 and V2 balances, acquisition routes, wallet addresses, approvals, venues, pair exposures, migration transactions, and tax lots separately.
- 02Do not add capital to improve an exit. First verify the exact V2 token, current pool, reserves, router, approvals, venue support, and a minimal sale.
- 03Set the maximum acceptable loss to the full position value and set a zero-tolerance rule for seed phrases, manual migration transfers, or recovery payments.
- 04Stress-quote the entire position and model gas, spread, price impact, slippage, tax, failed transactions, and simultaneous holder selling.
- 05Use multiple small, limit-aware exits only when they improve execution without depending on misleading liquidity or creating approval risk.
- 06Exit or remain out when any hard stop fails. Do not wait for a celebrity event, website return, new exchange, promised dApp, prior price, or community campaign.
Every source says what it can and cannot prove
01Primary chain explorer / EtherscanTiger King V2 token page
SupportsV2 contract address, decimals, total-supply display, holders, transfers, token metadata, ABI, and current audit-submission label.
LimitationToken metadata and market values can be issuer-supplied or aggregated; holders and displayed price do not prove project liveness or executable liquidity.
Open source02Primary deployed-contract record / EtherscanTiger King V2 contract code
SupportsSimilar-match source, constructor parameters, standard ERC-20 functions, deployment record, ABI, and no submitted-audit label.
LimitationEtherscan explicitly notes constructor differences can alter behavior; the source is not an exact-match verification and requires bytecode and storage checks.
Open source03Primary historical contract record / EtherscanTiger King V1 token and source
SupportsV1 address, exact-match source, one-trillion initial supply, transfer-burn logic, burn functions, holders, and audit-submission label.
LimitationThe contract remains on-chain but historical project announcements called it deprecated; current price or balance does not establish support or value.
Open source04Primary historical project communications / Historical TKING project channelTKING ecosystem announcements
SupportsAugust 2021 trading halt, 1:1 snapshot and redistribution, V2 relaunch address, historical pair route, audit claim, and project statements.
LimitationProject-authored Telegram posts are historical and promotional; they do not prove every distribution, current control, present operations, audit validity, or liquidity.
Open source05Primary pair-address record / EtherscanHistorical TKING V2 Uniswap pair
SupportsOn-chain inspection path for the pair address announced during the 2021 V2 relaunch.
LimitationA historical pair may be stale, drained, superseded, or irrelevant; pair tokens, reserves, LP holders, recent swaps, and router path must be read live.
Open source06Project social record / Historical TKING projectTiger King Coin official social profile
SupportsHistorical branding, linked website, and public communication footprint associated with the project.
LimitationA profile, follower count, or old post does not establish current accountable control, development, treasury, charity activity, or token demand.
Open source07Historical project document mirror / CryptoCompare asset resourcesTiger King Coin Whitepaper V3.0 mirror
SupportsPreserved historical roadmap, ecosystem, token, charity, and promotional claims for comparison with delivery evidence.
LimitationSecondary-hosted project material is not current proof of delivery, authorship, legal rights, finances, audited controls, utility, or adoption.
Open source08Primary technical standard / Ethereum Improvement ProposalsERC-20 token standard
SupportsStandard balance, transfer, allowance, approval, and event semantics used to interpret both contracts.
LimitationThe standard does not verify a deployment, issuer, distribution, project, audit, liquidity pool, or market value.
Open source09Primary library documentation / OpenZeppelinOpenZeppelin ERC-20 documentation
SupportsReference behavior and extension boundaries for standard ERC-20 implementations.
LimitationThe V2 matched source references an older implementation; documentation does not prove the deployed bytecode or constructor values.
Open source10Primary DEX documentation / Uniswap DocumentationHow Uniswap works
SupportsConstant-product pools, reserves, LP shares, swaps, and the distinction between pool state and displayed prices.
LimitationGeneral protocol documentation does not verify the TKING pair, reserves, LP control, router route, price impact, or sale execution.
Open source11Primary execution documentation / Uniswap DocumentationUniswap V2 integration guide
SupportsRouter, pair, amount-out, path, approval, and deadline concepts needed to inspect a DEX route.
LimitationA valid router call does not guarantee deep reserves, fair price, protected ordering, reliable tokens, legal access, or a full-position exit.
Open source12Primary network education / Ethereum.orgEthereum smart-contract security
SupportsGeneral contract, approval, interaction, and security boundaries for Ethereum users and developers.
LimitationGeneral guidance does not audit either TKING contract, project operations, pool, router, holder distribution, or social-engineering surface.
Open sourceDirect answers without invented certainty
Is Tiger King Coin a good investment in 2026?
The current decision is avoid by default. Historical migration evidence identifies a V2 Ethereum token, but current project liveness, accountable operations, audit proof, utility, charity reporting, pool liquidity, holder concentration, and a reliable full-position exit are not sufficiently verified.
What is the correct TKING contract address?
Historical project announcements identified Ethereum address 0x24e89bdf2f65326b94e36978a7edeac63623dafa as V2 after an August 2021 snapshot. The older 0xC626d951Eff8E421448074bd2aD7805C6D585793 contract is V1. Always verify chain and full address from current primary evidence before any action.
What happened to the old Tiger King Coin contract?
The project announcement channel described a 1:1 holder snapshot, halted trading, and a V2 relaunch in August 2021. V1 remains on-chain and uses different transfer mechanics, including an approximate 1% burn. Do not send V1 to a new migration service.
Does TKING have a 1% transaction tax?
The historical V1 source burns approximately 1% on transfers. The reviewed V2 matched source is a simple ERC-20 without that burn logic. Confusing the two contracts can corrupt quotes, balances, and execution assumptions.
Has the V2 TKING contract been audited?
A historical announcement referenced a V2 audit file, but Etherscan currently lists no submitted contract security audit and the displayed V2 source is a similar match. This review does not award an audit pass without the original report, scope, findings, fixes, and deployed-bytecode match.
Can Tiger King Coin reach one cent or one dollar?
A target can be converted into implied market value by multiplying it by live supply, but that arithmetic does not create probability, demand, or liquidity. With hundreds of billions of tokens, even small unit-price targets imply very large values. Current project and exit gates fail before price-target discussion becomes decision-useful.
Can I still sell TKING?
Do not assume so from a displayed price. Verify the exact V2 contract, current pair, reserves, router, allowance target, recent swaps, venue support, minimal sale, and full-position impact. A tiny test sale does not prove that a large position can exit.
Does holder count prove the project is active?
No. Holder count includes dormant, dust, exchange, pool, treasury, lost, related, and migration-distribution addresses. It does not prove current users, product delivery, accountable operations, or liquid demand.
What changed and why
Withdrew the 2022 forecasts, exchange instructions, adoption assumptions, regulatory implication, and recommendation. Added V1/V2 contract lineage, 2021 migration evidence, source-provenance and audit limits, project-liveness controls, pool and holder checks, hard stops, target and exit math, route verification, scam controls, source limitations, and an avoid-by-default verdict.
Original WordPress review published promotional project claims and point forecasts through 2030 without current contract, liveness, liquidity, concentration, or exit evidence. Those claims are not carried forward.