Frequently Asked QuestionsV2 · 29 questions

TLDR: read the whitepaper for full detail. This page covers V1 → V2 migration, how the V2 airdrop works, why funds are provably safe, and how the protocol distributes supply and governance.

About THODL (V2)3 questions
What is $THODL?

$THODL is an ERC20 token on Ethereum mainnet with a 10% fee on every DEX trade. 9% of each trade feeds an immutable on-chain treasury that automatically buys the 6529 Meme NFT with the best Price-Per-TDH ratio and locks it forever. The remaining 1% goes to the dev wallet — the only source of dev income; there is no pre-minted developer allocation tied to a vesting cliff.

Owning $THODL is a single-token, liquid exposure to a continuously growing, algorithmically-curated basket of 6529 Memes — plus a proportional claim on the governance weight (TDH) those NFTs generate inside the 6529 ecosystem.

How is it different from a normal memecoin?
  • The contract is the vault. Purchased NFTs live inside BuyerContractV2 and there is literally no function in the code that can move them out — not even for the admin Safe.
  • Liquidity is permanently locked. The dev seeds initial LP from Meme card mint revenue and sends the LP tokens to 0x000…dEaD. Nobody can ever pull the rug.
  • Fees fund a productive activity (NFT accumulation), not a marketing budget or a team treasury.
  • No public ETH sale. V2 distribution is airdrop-only (V1 migrants +100% + 6529 TDHODL Meme card minters), capped at 420 entries of 111,968 $THODL each. An optional secondary 4× sale (0.25 ETH/slot) may run for unclaimed slots — 100% of that ETH goes to the treasury.
  • Emergency powers self-destruct at launch. Once disableEmergency() is called, even the admin loses the ability to touch ETH/ERC20 in the treasury.
What does PPTDH stand for and why does it matter?

PPTDH = Price ÷ TDH. It tells you how much ETH you pay per unit of TDH yield generated by an NFT. Lower PPTDH = better deal.

TDH ("Total Days Held") is the 6529 community's on-chain reputation and governance primitive. Every day a wallet holds a 6529 Meme card, it accrues TDH at a rate inversely proportional to the card's edition size:

per-copy-per-day TDH = 3941 / edition_size

The protocol's oracle ranks every active OpenSea listing by PPTDH and signals the cheapest one for purchase. This is the single metric that drives every buy.

Distribution (V2 airdrop)4 questions
When can I claim?

Visit the /claim page and connect your wallet. If the airdrop state is AirdropOpen and your wallet is in the merkle snapshot, a Claim button appears.

There is no claim deadline. The airdrop is open indefinitely — the owner closes it manually at some future date via either burnRemainingAirdrop (burn the residue) or start4xSale(deadline ≤ +62d) (sell unclaimed slots at 0.25 ETH).

Currently the airdrop is in Configured state — the merkle root will be committed after the 6529 TDHODL Meme card mint window closes and the snapshot script merges V1 migrants with Meme card holders.

How do I know if I am eligible?

Two paths to eligibility:

  • V1 migrant — if you bought $THODL on the V1 Genesis Sale, you are pre-allocated a +100% bonus entry. Two V1 wallets qualify.
  • 6529 TDHODL Meme card holder at snapshot — once the Meme card mint window closes, every wallet that holds the TDHODL Meme card gets one airdrop entry per card (subject to the 420-entry hard cap on the bucket).

The /claim page checks an off-chain proof endpoint (/api/proof?address=…) against the committed snapshot; if your wallet is not found it shows "not eligible".

How do I get $THODL if I am not in the snapshot?

Two options:

  1. Buy on Uniswap V2. Once the dev seeds initial LP (after the Meme card mint completes) and the Safe calls launch(pair), the THODLV2/ETH pool is tradable. Use the on-site /swap page, which uses the FOT-aware Uniswap router functions (mandatory because of the 10% FOT).
  2. Wait for the optional 4× sale. If the owner opens start4xSale(deadline), anyone can call buy4x() at exactly 0.25 ETH per slot to receive 111,968 $THODL. The 4× sale is capped at the remaining bucket entries and runs for at most 62 days.

The 4× sale is not guaranteed to open — the owner may instead choose burnRemainingAirdrop() as the terminal action.

When does trading open?

When the dev seeds initial LP and the Safe calls THODLV2.launch(pair). The end-to-end sequence is:

  1. factory.createPair(THODLV2, WETH) (anyone)
  2. Safe.launch(pair) (registers + flips launched)
  3. Safe.setFeeExempt(seeder, true)
  4. router.addLiquidityETH(..., to=DEAD, deadline) (seeder)

No fixed minimum ETH is enforced; the dev pairs whatever ETH the Meme card mint produces (target ~0.45 ETH) with proportional $THODL from the deployer surplus. LP tokens are sent to 0x000…dEaD — permanent lock.

How it works4 questions
How does the protocol decide which NFT to buy?
  1. An off-chain oracle scans OpenSea listings for the 6529 Memes collection (0x33FD…AaD17aF1) every 30 seconds.
  2. For every active ETH-denominated listing, it computes PPTDH = price_wei / tdh_rate (mint-window cards with supply < 299 are excluded by the on-chain minCardSupply check).
  3. The lowest-PPTDH listing is signed by the oracle into an EIP-712 BestListing message containing (tokenId, priceWei, validForBlocks, nonce, deadline).
  4. Anyone can submit the signed payload to GaslessOracleV2.submitBestListing(...), which forwards it to BuyerContractV2. Submitter gas is reimbursed from treasury ETH (capped at 100 gwei effective, 0.01 ETH per call).
  5. After a 15-block cooldown (~3 min), anyone can call triggerBuy(tokenId, seaportOrderData) to actually execute the purchase.
Who runs the oracle?

The oracle is an off-chain service whose signing key is held by the protocol. The authorised signer EOA is 0x6d9191a12fd6f1aa247db30cb14072c6cba1a6d9 and it is registered on-chain by the Safe via the V2 oracle hub.

Crucially, the oracle cannot extract funds: a compromised key could only sign listings that pass on-chain checks (right collection, all-ETH consideration, price ≤ maxNftPrice, supply ≥ minCardSupply). Worst case is "buying bad NFTs" at up to 5 ETH each, capped at one buy per ~15 blocks (~96/day max). The Safe can revoke the signer in one transaction.

What happens to the NFTs after purchase?

The NFT is transferred directly into BuyerContractV2 by Seaport (recipient = address(this)). It then sits in the contract forever.

There is no sendNFT, withdrawNFT,listOnSeaport, or any other function that can move ERC1155 tokens out of the contract. emergencyWithdrawToken explicitly operates on IERC20 only, never IERC1155.

The TDH that the NFT generates is attributed to the contract address, then routed to a governance wallet via the 6529 NFTDelegation registry consolidation mechanism — see the Governance section below.

How often does it buy?

At most one purchase every 15 blocks (~3 minutes, ~96 buys/day max). Frequency in practice depends on:

  • how much $THODL trading volume is happening (more trades → more fees → more ETH);
  • whether treasury ETH balance ≥ max(minEthForTrigger, next-buy cost);
  • whether a fresh oracle signal is sitting in the contract within its validForBlocks window.
Tokenomics5 questions
What's the total supply?

69,420,000 $THODL with 18 decimals. The number encodes the memetic constant 69420. The full supply is minted at deploy — no mint()function is exposed on the token, so supply can only ever decrease (via burns), never increase.

How is supply distributed?
Bucket%AmountHolder
Airdrop bucket67.74%47,026,560AirdropManagerV2
Deployer surplus32.26%22,393,440Safe (disposes: LP / treasury / burn)

The airdrop bucket = 420 entries × 111,968 $THODL each. Within it:

  • 2 V1 migration entries with +100% bonus (322,520 $THODL total)
  • up to 418 Meme card minter entries (filled at snapshot)

The deployer surplus disposition (LP seed, treasury injection, burn) is decided by the Safe post-deploy and published transparently on Etherscan.

Why 4× is the premium price

The protocol explicitly rewards the original minters of the 6529 TDHODL Meme card. Compare the $THODL per ETH spent for each acquisition path:

PathETH spent$THODL$THODL / ETH
Mint the TDHODL Meme card
(then claim airdrop)
~0.0625 ETH111,968 / card~1,791,488
buy4x() (if 4× sale opens)0.25 ETH111,968~447,872

Ratio: 1,791,488 / 447,872 = 4.00×. A 6529 TDHODL minter ends up with exactly 4× the $THODL per ETH compared to a 4× sale buyer — and they also keep the underlying NFT.

The 4× number is exact at the contract level: price4x = basePrice × 4 with basePrice = 0.0625 ETH (typical Meme card mint price).

What are the swap fees?

Every transfer where either the sender or recipient is a registered AMM pair triggers a flat 10% fee, split:

  • 9% (900 bps) → BuyerContractV2 (treasury)
  • 1% (100 bps) → dev wallet
  • 0% for fee-exempt addresses (deployer during setup, BuyerContractV2's own sells, LpHelperV2 when enabled)

The bps values are hardcoded constants — they cannot be changed by anyone, ever. Wallet-to-wallet (P2P) transfers pay no fee as long as neither side is a registered AMM pair.

Is there a buyback / burn mechanism?

Yes. BuyerContractV2.buybackAndBurn(ethAmount, minThodlOut) lets the Safe spend treasury ETH to buy $THODL from the LP and burn it. Net effect: the pool's ETH side grows, the $THODL side shrinks → spot price rises and float reduces.

Additionally, if the airdrop closes via burnRemainingAirdrop() all unclaimed $THODL is burned; if it closes via the 4× sale path, 100% of unsold $THODL is burned at finalize4xSale(). Both are deflationary.

The total supply can only ever go down.

Safety & immutability5 questions

The trust model rests on what the smart contract code cannot do, by construction. Every class of risk is eliminated at the code level rather than by policy.

Can the dev / Safe rug-pull the NFTs?

No. BuyerContractV2 has zero functions that transfer NFTs out:

  • No sendNFT, withdrawNFT, listOnSeaport, transferToSafe or any equivalent.
  • The only Seaport call is fulfillAdvancedOrder (a buy, not a sell).
  • emergencyWithdrawToken only handles IERC20, never IERC1155.
  • callDelegationRegistry only accepts the 6 hardcoded 4-byte selectors of known 6529 NFTDelegation methods, and the registry address itself is immutable.

BuyerContractV2 is byte-identical to V1's audited BuyerContract (only the name differs). Even with full admin powers, the Safe cannot sell or transfer a single NFT out of the treasury. It is a one-way sink.

Can the dev / Safe drain the ETH treasury?

Before launch: yes, via emergencyWithdrawETH / emergencyWithdrawToken. These exist so that setup mistakes (wrong env var, misrouted tokens) can be recovered.

After launch: no. The Safe calls disableEmergency() exactly once, which sets emergencyEnabled = false permanently. There is no enableEmergency() — the flag is non-reversible. From that moment on, even the owner cannot extract ETH or ERC20 from the treasury by any means.

Is the liquidity pool locked?

Yes, permanently. The dev seeds initial LP off-protocol from 6529 TDHODL Meme card mint revenue (target ~0.45 ETH paired with proportional $THODL from the deployer surplus). The LP tokens returned by addLiquidityETH are sent directly to 0x000000000000000000000000000000000000dEaD — a canonical address with no known private key.

Consequences:

  • The liquidity can never be withdrawn.
  • No rug-pull is possible: any removeLiquidity call from 0x…dEaD would fail.
  • Initial depth is intentionally small; subsequent depth can be added by Safe injections or by anyone via the permissionless LpHelperV2.
What is the 4× sale and is it safe?

The 4× sale is an optional terminal path the Safe can pick after the airdrop has been open for a while. It opens a window (≤ 62 days) where anyone can buy one airdrop slot at 0.25 ETH for 111,968 $THODL.

At finalize4xSale() (callable by anyone after the deadline):

  • 100% of accumulated ETH → BuyerContractV2 treasury (forwarded by the contract, no route to dev wallet).
  • 100% of unsold $THODL → burned via token.burn.
  • No auto-LP at finalize (intentional — eliminates the spot-reserve sandwich attack surface).

Direct ETH transfers to the airdrop manager (outside buy4x()) are rejected by the receive() function with UnsolicitedEth(). The only ETH that enters is intentional sale revenue.

What happens if a smart contract bug is found?

The contracts are immutable — no proxy, no upgrade path, no admin reset. If a bug is found, the only remedies are:

  • Tune the operational knobs (maxNftPrice, minCardSupply, minEthForTrigger) to limit blast radius.
  • Revoke the oracle signer if the bug involves signal injection.
  • For severe bugs: redeploy a successor contract and migrate via community vote (the original NFTs stay locked in the old contract — this is by design).

V2 itself is precisely such a successor: V1 had a fixed-ETH precondition that was wrong for the actual sale volume, and was redeployed clean to remove the failure mode. See whitepaper §0 for the full story.

Governance / TDH3 questions
How do THODL holders influence 6529 governance?

Through an off-chain (Snapshot.org-style) vote where 1 $THODL = 1 vote:

  1. A proposal opens in the $THODL snapshot space (e.g., "How should we vote on 6529 Proposal #N?").
  2. $THODL holders vote with their balances at the snapshot block.
  3. The outcome is published.
  4. The Safe signers cast the corresponding vote from the consolidation wallet on 6529.io or the relevant 6529 governance endpoint.

Over time the Safe can be replaced by an on-chain voting module that automates step 4. The contract architecture already accommodates this: callDelegationRegistry accepts arbitrary calldata (filtered by selector allowlist) and there is no requirement that the owner be a human-controlled multisig.

When does the 100k TDH activation kick in?

When the BuyerContractV2 treasury accumulates 100,000 TDH (verifiable from the 6529 NFTDelegation registry + the contract's NFT inventory). At that threshold:

  • $THODL holders can collectively direct the consolidation wallet's TDH on 6529 governance votes.
  • TDH-gated 6529 ecosystem features become available pro-rata to $THODL balance.
  • The protocol publishes a public TDH dashboard.

Pre-100k state: the consolidation wallet is registered and accruing TDH passively in the background. No governance theatre while the protocol is still warming up. See whitepaper §6.4 for the full mechanics.

What is "consolidation" on 6529?

Normally, if you own 6529 Meme NFTs across multiple wallets, each wallet has its own independent TDH score for governance. The 6529 NFTDelegation contract (0x2202CB9c00487e7e8EF21e6d8E914B32e709f43d) exposes a "consolidation" use case: wallet A consolidates to wallet B, and B inherits A's TDH for governance purposes.

For $THODL: wallet A is BuyerContractV2 (the NFT vault) and wallet B is the consolidation target — a Safe whose signers execute $THODL holders' governance decisions. Every meme-card purchase by the contract mechanically increases B's voting weight on 6529.io.

Contracts & addresses2 questions
Where are the V2 contract addresses?

All contracts are deployed and Etherscan-verified on Ethereum mainnet (V2, 2026-05-13):

V1 addresses (deprecated, bricked) are listed in whitepaper §8.2 for record only — do not interact.

How do I swap THODL?

Once the LP is live (dev-seeded after the 6529 TDHODL Meme card mint), use any Uniswap V2-compatible interface — including the /swap page on this site, which uses swapExactETHForTokensSupportingFeeOnTransferTokens / swapExactTokensForETHSupportingFeeOnTransferTokens (mandatory because of the 10% FOT).

Always set slippage ≥ 10% if you use a generic interface that does not handle FOT correctly — the standard swapExactTokens… calls will revert otherwise.

The on-site swap UI is currently disabled (paused) until the THODLV2/ETH Uniswap pool is seeded.

V1 → V23 questions
What happened to V1?

The V1 Genesis Sale required a fixed 8.097 ETH to seed initial Uniswap V2 liquidity at finalize(). The sale raised 0.376 ETH across 2 buyers — well below the threshold — and finalize() permanently reverts with LpEthShortfall.

That means the V1 buyers' ETH and their V1 $THODL allocation are stuck in the V1 sale contract with no extraction path, and the V1 LP cannot be seeded. The token's launched flag stays false on V1, so V1 $THODL trading never opens.

V2 fixes this by removing the public ETH-collecting sale entirely. The dev seeds initial LP off-protocol (from 6529 TDHODL Meme card mint revenue), and distribution happens via a merkle airdrop with no fixed-amount preconditions. V1 buyers are honored on V2 with a +100% bonus migration airdrop.

I bought in V1 — what do I do?

Nothing yet. Your V1 position migrates automatically as a V2 airdrop entry once the merkle root is set (which happens after the 6529 TDHODL Meme card mint window closes). You will see your wallet listed on the /claim page once the snapshot is committed.

The migration is at 2× your V1 amount (a +100% bonus, paid in V2 $THODL, not ETH). Concretely:

  • 0x0186…a76c · paid 0.26116 ETH on V1 → V2 airdrop: 223,918.584 $THODL
  • 0xE1a4…E5A4 · paid 0.115 ETH on V1 → V2 airdrop: 98,601.000 $THODL

The V1 ETH itself is unrecoverable (no extraction path on the bricked sale). The +100% V2 token bonus is the compensation mechanism.

Are V1 contracts shut down?

V1 contracts remain on-chain (immutable) but are no longer part of the protocol — the V1 sale is bricked, the V1 LP never seeded, and the V1 token has no listed AMM pair. Treat V1 addresses as historical record only:

  • THODL (V1) — 0x6105…979e · do not interact
  • GenesisSale (V1, bricked) — 0x7095…5a25
  • MerkleAirdrop (V1) — 0xE260…91E2 · superseded by AirdropManagerV2

See whitepaper §8 for the full address table.

Still have questions?

Read the full whitepaper (12 sections, including a complete V1 → V2 migration writeup), browse the source code on GitHub, or inspect any contract directly on Etherscan.