stonkers@robinhood:~$ ./stonkers_bell --status
RING
RING.
CLOCK IN. WIN THE POOL.
[ 0.000012 ]chain : robinhood [4663] ......... OK
[ 0.000318 ]vrng : commit-reveal armed ...... OK
[ 0.001044 ]prize_pool : 6 stock tokens loaded .... OK
[ 0.002971 ]admin_keys : NOT FOUND ................ --
[ 0.003356 ]daily lottery paying real tokenized stocks. no house. no admin. just a bell anyone can ring.
stonkers@robinhood:~$ ./buy_ticket --interactive
payment_token:
# ticket_fee_routing [ticket] ─┬─ 90% → prize_pool ├─ 5% → clock_in (stonkbrokers) └─ 5% → treasury
qty: — max 5 / wallet / day
≥ 0.1% of supply — 1 free ticket
≥ 0.5% of supply — 2 free tickets
≥ 1.0% of supply — 3 free tickets
# connect wallet to check eligibility.
stonkers@robinhood:~$ cat /var/pool/today.txt
···
# triggers today’s draw. permissionless — anyone can ring it. no admin, no gatekeeper.
## WEEKEND BELL — every sunday the daily draws roll into one mega pool. a single winner takes the entire stack of tokenized stock. one bell, one winner.
stonkers@robinhood:~$ ./flywheel --loop
$STONKERSBELL⇄$STONKBROKER
one loop. two tokens.
$STONKERSBELL or $STONKBROKER
creates: direct buy pressure on both tokens
real tokenized stocks
creates: a prize worth actually chasing
stonkbrokers directed booster
creates: real revenue feeding the stonkbrokers ecosystem
+ weekend bell mega pool
creates: a daily habit, a reason to come back
real stocks, on-chain proof
creates: virality that spreads itself
free ticket, no cost
creates: more holding, less selling → loop closes
stonkers bell isn't a side project bolted onto the ecosystem for hype — it's a demand engine for it. every ticket buys pressure on both tokens. every free ticket rewards holding over dumping. every draw pipes real revenue straight into clock in v2. the lottery doesn't compete with stonkbrokers. it feeds it.
stonkers@robinhood:~$ ./stats --all-time
···
—
—
···
stonkers@robinhood:~$ man fairness
01_commit
before tickets close, the protocol commits to a specific future block hash. nobody knows it yet — not even the deployer.
02_resolve
once that block lands, its hash seeds the winner selection. the outcome is fixed by the chain, not by an operator.
03_verify
every input and output is on-chain. anyone can replay the draw and confirm the winner independently.
