PROJECT STATUS · UPDATED 5 OCTOBER 2026
Check for yourself.
No mystery box. Here’s where the project stands, what we depend on, and what you can check yourself.
The first Short draw started on 5 October. Its entries and prize pool were locked at the start. Check draw progress and your tickets and rewards for the latest confirmed data. This is a dated update, not a live service monitor.
One official token.
QIANQI on Robinhood Chain:
Full token address
0x6EA39A23AA46E51CA6CD2d1cbc0B5bfb29ECB216
Check the network and full address. A matching name or picture alone doesn’t identify our token.
The route matters.
Getting QIANQI in your wallet isn’t enough on its own. We check who paid, who received the tokens and the eligible purchase amount. Gifts, transfers and holding alone don’t earn tickets.
Some purchases need additional checks before they count. A pending purchase isn’t a rejection, and an exchange through another token isn’t automatically eligible.
Under the announced late-confirmation rules, verified earlier purchases can earn tickets for future draws. They cannot change a draw that has already locked its entries. Publication of a purchase record alone does not award tickets.
Additional ETH routes: confirmation from 6 October, 15:10 UTC
Received means received.
Our 3% creator fee breaks down into 2.7% for prizes, 0.15% for gas and operations, and 0.15% for the team. We distribute only the fees actually collected. Only USDG that actually reaches the prize vault counts as funded prize money.
Fees waiting to be collected, tokens waiting to be sold, and hoped-for donations don’t count. If money is delayed, new prize funding waits too. Already reserved prizes stay reserved.
After a token moves into its trading pool, some Pons fees need conversion into USDG by an external operator. That dependency can delay collection. Available USDG and money still awaiting conversion are different things.
What you’re trusting.
The project checks purchases and prepares entry lists using blockchain data from its RPC provider. That means trusting both the project’s checks and the data provider. Published records help you inspect those decisions; they do not remove that trust.
Our purchase-to-payout flow has been tested in a test environment. Those results do not establish public uptime or cover every possible swap route. Internal tests and published source code are not an independent security audit.
Verification of the complete external Pons contract set remains incomplete. Conversion availability also depends on Pons. These limits remain relevant after launch.
The receipts.
- Prepared purchase records — evidence for review, not proof of awarded tickets.
- Project source code and documentation
- Contract verification findings and remaining questions
- Test results and their limits