A coin with a proportional claim.
BASKT is a launchpad for redeemable basket coins. Each live coin is paired with a basket vault. Most launch capital is allocated to that vault; holders can burn the launched coin to redeem a proportional share of its assets.
Launch coin → fund basket vault → hold or trade coin → burn coin to redeem basket share.
Fund the basket first.
- Basket Vault
- 80%
- Initial Liquidity
- 10%
- $BASKT flow
- 5%
- Creator / platform
- 5%
Allocation of launch capital. The $BASKT bucket is separate from the launched coin’s basket vault.
The six launch steps are Coin, Thesis, Basket Assets, Launch Split, Treasury / Redeem Rules and Publish. Publishing currently saves a pending launch configuration. It does not deploy contracts or accept funds. Next, the creator reviews a quote and signs deployment and funding on the saved coin page. The public live feed includes only confirmed, funded launches.
Prepare a basket coin →Many assets. One or two per coin.
Assets come from a central registry with chain, contract address, decimals and liquidity tier. Only enabled, redeemable assets on the launch chain can be selected. One asset receives a 100% target weight; two weights must total 100%.
Weights describe the launch target. Actual vault balances determine redemption. Stock tokens and tokenized equities are outside this MVP. The registry must be approved before assets are made selectable.
Logos resolve from the registry, an operator-approved token list or stored explorer metadata, then fall back to initials. A symbol or image is not proof of token identity.
Burn for your share of the vault.
Burn coin. Receive your basket share.
Your share = tokens burned / outstanding redeemable supply
Each asset received = vault balance × your share, less the redemption fee.
- Redemption fee
- 1%
- Of that fee → $BASKT flow
- 50%
- Of that fee → platform
- 30%
- Of that fee → creator / maintenance
- 20%
Amounts round down to asset base units. Burning is irreversible. Execution requires a deployed vault contract and a wallet-confirmed transaction.
The denominator is the contract’s outstanding redeemable supply before the burn. It must include every token eligible for redemption; a marketing or exchange-reported circulating-supply figure is not sufficient.
A vault worth $80,000 and a holder burning 1% of the eligible supply imply an $800 gross basket share. The configured fee is deducted from each received asset. The actual payout is in basket assets, not a guaranteed USD amount.
Burned tokens leave supply and the vault loses the proportional gross asset amounts. Ignoring rounding and market changes, NAV for remaining tokens stays approximately constant. Fee routes and residual dust must follow the deployed contract’s rules.
The current estimator floors gross amounts and fees to each asset’s smallest unit. Fee allocation gives any split-rounding residue to the final fee bucket. Execution cannot be enabled until deployed contracts match these rules.
The platform bucket is separate.
The configured launch allocation and part of redemption fees may route to a $BASKT flow bucket. Those funds do not belong to a launched coin’s redeemable basket vault and are excluded from its NAV.
Real buybacks, burns, staking and creator verification depend on deployed contracts and legal review. No yield, dividends or revenue entitlement are promised.
Read $BASKT tokenomics →Verify before committing funds.
BASKT is a launchpad for redeemable basket coins. Redemption depends on deployed contracts and available vault assets. NAV is an estimate, not a guaranteed market price. No guaranteed yield or dividends.
Burning is irreversible. Assets can lose value or become illiquid; contracts and data sources can fail. A creator address is not a vault. A recorded event is not a substitute for inspecting the contract and transaction.
Pending launch means configuration only. Live requires deployed token and vault addresses, actual funding and verified activity ingestion. No demo coins, placeholder balances or fabricated activity are shown.
BASKT is independent and experimental, with no Robinhood or Pons endorsement.
Your wallet. Your approval.
Privy authenticates the connected EVM wallet. The server verifies that the submitting wallet belongs to the session. A server publication only stores metadata; it never signs a token transfer on your behalf.
- Network
- Robinhood Chain
- Chain ID
- 4663
- Gas currency
- ETH
- Explorer
- Robinhood Blockscout ↗