Chain ID 1404.
Transparency FAQ
TURBO answers before anyone signs.
A public record for contract verification, allocation wallets, custody disclosures, burn reporting, launch utility, and use-of-funds evidence.
Current Public Record
Published contract and allocation facts.
These values are loaded from the same frontend data files used by the staking page.
The token contract mints the full 50B TURBO supply to allocation wallets during deployment.
Rewards come from the 500M TURBO staking pool and do not create new supply.
Wallet labels and the dashboard claim schedule are published. Multisig signer rules, legal foundation status, and claim-contract details need final confirmation before they are marked verified.
Dashboard Claim Schedule
Dashboard allocations are separate from staking.
Purchases completed in the official dashboard remain dashboard allocations until the claim window opens. Dashboard allocations cannot be staked pre-TGE because staking requires TURBO to be claimed into the user's wallet on-chain.
MetaMask RPC or token-import issues do not change a completed dashboard allocation record.
The exact TGE date should be added before claim instructions go live.
Claimed TURBO can be held, transferred, or staked after it reaches the user's wallet. Pre-TGE dashboard balances are not wallet-held staking balances.
Next on-chain step
Deploy, verify, fund, and lock the TurboMerkleClaim contract, then publish the contract address, Merkle root, and allocation manifest for wallet-level proof verification.
Wallet Register
Material wallets and public labels.
Every material allocation wallet should be traceable from role label to address, explorer activity, and reporting category.
Pending Owner Confirmations
Do not mark claims fully live until these are public.
These items are intentionally listed as blockers. They need source evidence, signed confirmation, or explorer links before the community can independently verify them.
Required before final 25/25/25/25 release timestamps are generated.
Publish the owner wallet and whether it remains single-signer or moves to multisig.
Publish custody provider, signers, and multisig threshold for Foundation, reserve, and treasury wallets.
Clarify whether Foundation means a legal entity or the project reserve/rewards structure.
Add addresses and explorer links for any lock or vesting contracts if those claims are made.
Link explorer source verification for token, staking, and the future claim contract.
Weekly burn reporting needs transaction hashes, source wallet, burn destination, amount, and remaining balance.
Reporting should map treasury, marketing, liquidity, infrastructure, ecosystem, and development movements to public wallet activity.
FAQ
Questions serious buyers will ask.
Clear answers, no hidden assumptions. Items marked pending should not be treated as verified until public evidence is added.
When will the TURBO contract address be published and verified on Super Explorer?
The TURBO token address is published as Loading..., and the staking contract is published as Loading.... The site now points contract links to BlockDAG Super Explorer at explorer.blockdag.works. Source-code verification should be linked from this FAQ once explorer verification is confirmed for the exact deployed addresses.
Will all material wallets be publicly labeled at launch?
The current public manifest labels the deployment, signing, Public Access, Foundation & Rewards, Ecosystem, Treasury, Partnerships, and Team wallets. If a separate burn reserve, liquidity wallet, staking/rewards wallet, or marketing wallet is used beyond these published roles, it should be added to the register before community reporting relies on it.
Who controls the Foundation, reserve, and treasury wallets?
The public files identify wallet roles and addresses, but they do not yet prove human signers, custody provider, or multisig threshold rules. Until signer rules are published, these wallets should be treated as project-administered wallets rather than independently verified multisig wallets.
Are Foundation, treasury, team, marketing, or ecosystem allocations locked or vested on-chain?
The TURBO token contract in this repository does not include lock or vesting mechanics. Any lock or vesting claim should be backed by a separate public lock contract, vesting contract, transaction hash, or signed disclosure. Without that evidence, the allocations should be described as administratively controlled.
Will weekly burns be visible on-chain with matching public reports?
Burn reporting should be fully visible. Each weekly report should include the transaction hash, source wallet, burn destination, TURBO amount, date, remaining Foundation reserve balance, and a note confirming that buyer balances were not reduced.
Is the Foundation a legal entity or a project reserve structure?
This needs explicit confirmation. Until the legal status is published, the word Foundation should be read as the project reserve and rewards structure shown in the wallet register, not as proof of a separate legal foundation or independent governance body.
Which utility layers are live at launch versus phased rollout?
The live frontend exposes TURBO staking, wallet staking actions, contract links, and a public SPARKS gaming link. VIP, NFTs, casino or broader gaming integrations, and application-layer fee flows should be listed as phased rollout items unless their production routes, contracts, or reporting pages are published.
Is the dashboard claim schedule the same as staking?
No. Dashboard purchases, TGE claims, and monthly releases are separate from staking. Pre-TGE dashboard allocations cannot be staked because they are not yet wallet-held TURBO. Staking starts only after TURBO is claimed into the user's wallet and the user signs staking transactions. The intended dashboard claim model is 25% at TGE, then 25% one month after TGE, 25% two months after TGE, and 25% three months after TGE.
Can I stake TURBO bought through the dashboard before TGE?
No. A dashboard purchase is an allocation record until the claim contract opens. The staking contract can only stake TURBO that already exists in the connected wallet on BlockDAG Mainnet. Once a user's claimable TURBO reaches their wallet after TGE, they can choose to stake it through the staking page.
Which RPC and explorer does the TURBO site use?
The production site now uses the BlockDAG production RPC at rpc.blockdag.works and contract links point to Super Explorer at explorer.blockdag.works. Earlier engineering or BDAGScan endpoints were rollout infrastructure and should no longer be the primary user-facing endpoints on this site.
What if MetaMask cannot connect to BlockDAG or import TURBO after a dashboard purchase?
A wallet display or RPC issue should not change a completed official dashboard allocation record. Users should verify that the purchase appears in their official dashboard account, keep the purchase confirmation, and resolve wallet/RPC setup before the claim window opens.
Will access-round funds and use-of-funds reporting be tied to public wallet activity?
The strongest reporting format is wallet-tied: treasury, marketing, infrastructure, liquidity, development, ecosystem, and rewards movement should be mapped to public transaction hashes and category labels so the community can independently verify movement instead of relying only on narrative updates.
Reporting Standard
What every future update should include.
Each public report should connect claims to wallet evidence: address, role, amount, transaction hash, date, purpose, and remaining balance.