$RUBIK, the token behind RUBIK CUBE.
$RUBIK is preparing to launch on pons, on Robinhood Chain mainnet. RUBIK CUBE brings together a holder mosaic, a contract scanner, and a growing product roadmap. The official CA and pons token link appear here once the launch is confirmed.
- pons fixed supply
- 1,000,000,000
- Launch venue
- pons
- Network
- Robinhood · 4663
- Contract status
- Coming soon
Built around pons on Robinhood Chain
Launch venue: pons
$RUBIK is planned for launch through pons on Robinhood Chain mainnet. pons provides the token-creation and trading infrastructure; RUBIK CUBE is an independent project.
One WETH pool
pons tokens begin trading in a Uniswap V3 pool paired with WETH. There is no bonding-curve stage followed by a DEX migration.
Graduation keeps the same pool
Graduation marks a paired-liquidity milestone. Trading continues in the original pool; it does not certify the token or guarantee its value.
Verify the launch details
Read the live launch configuration, locked-liquidity position, creator initial buy, and fee split on pons and the explorer. The published contract address is the identifier to check.
Launch mechanics: pons documentation ↗. Confirm current settings at launch. Fee discounts, revenue sharing, and buybacks for $RUBIK holders are not active product features.
Growth, done carefully
The roadmap starts with a transparent launch, then adds trading and agent utility. Each milestone will be confirmed as it becomes available.
- Now
Prepare $RUBIK for pons
Finalize the launch metadata, creator settings, and official channels. Review the transaction in the creator wallet.
- Launch
Publish the official contract
After the pons launch succeeds, verify the contract and pool, then enable the official token link and holder data.
- Next
Expand holder insights
Improve the holder mosaic and scanner with additional, verifiable liquidity and wallet information.
- Later
Develop the RUBIK CUBE product
The independent launchpad contracts and advanced agent tools are prototypes. Any production release needs separate implementation and review.