launch tokens with built-in market-making engines. creator fees continuously reinforce liquidity and progressively tighten float.
Robinhood
Joined September 2026
- Tweets41
- Following0
- Followers193
- Likes0
Pinned Tweet
ponsball.tech is now live, a new protocol for launching snowball tokens on top of Pons.
this is the most configurable way to launch a snowball, with adjustable parameters that determine fee intensity, buyback cadence, and how aggressively the mechanism compounds.
every token gets its own automated market-making engine that turns fees into recurring buybacks and burns, steadily tightening the float and compressing supply over time.
choose from 6 different launch modes, each tuned for a different level of tax, buyback frequency, and snowball intensity.
the snowball gets heavier as it rolls.
0xabc3458230ecc95eb42b3dbcec2a7d1b9902e7de
Okay, everything is good to go (finally).
thank you all for your incredible patience while i worked through the issues.
we currently have about $45.7K sitting in accumulated fees waiting to be deployed back into $PONSBALL through the next buyback cycles.
doing some final stress testing now, then i’ll be back on Spaces.
Join the space if you’re not in here yet.
Been live for around an hour and I’ll be here for the next ~6 hours. If you have any questions about $PONSBALL, the fee vaults, buybacks, launch modes, or anything else, now is a good time to ask.
Currently migrating the backend over to Alchemy RPC while the QuickNode RPC issues are being resolved.
Okay, finally got to the bottom of it.
In my 8 years of coding, I’ve genuinely never had this happen before. The RPC was shut down for “abuse and automation.”
I’m assuming it had something to do with me purchasing the enterprise plan and then immediately hammering it with a huge number of automated requests.
I’m going to add a much more aggressive caching layer so the RPC does not get throttled nearly as hard going forward.
In the meantime, I have to contact support to actually get the RPC re-enabled, so I’m doing that now.
The space is live if you aren’t in here yet.
I’ll be live all night / morning. teapaw.org/ponsballtech/status/20…
okay, everything is finally running as planned.
there was a small database indexing issue that was mapping the wrong contract addresses to the wrong tokens due to a schema mismatch.
that’s been fixed now and everything is indexing correctly again.
the next $PONSBALL buyback should execute shortly.
join the space if you’re not in here yet.
okay, everything is fixed and should be running properly now.
the next cycle executes in roughly 5 minutes. i’m also updating the UI to include timers on each token page so you can see exactly when its next buyback cycle is scheduled.
there is currently around 13.45 ETH, roughly $33,507.94, sitting in accumulated fees waiting to be deployed back into $PONSBALL.
ponsball.tech/token/0xabc345…
$PONSBALL is different.
As far as I’m aware, most of the existing “snowball” tech on Robinhood is either larp or relies on an actual person to keep the mechanism running.
Ponsball is the first fully automated snowball system that runs on it's own.
Every launch gets its own deterministically derived fee vault at creation, and that vault is constrained to three actions only: claim fees, buy the token, and burn what it buys.
Ponsball retweeted
As far as I’m aware, most of the existing “snowball” tech on Robinhood is either larp or relies on an actual person to keep the mechanism running.
Ponsball is the first fully automated snowball system that runs on it's own.
Every launch gets its own deterministically derived fee vault at creation, and that vault is constrained to three actions only: claim fees, buy the token, and burn what it buys.
No, already $10k has been bought back and burned.
You can verify everything here: ponsball.tech/stats
completely understandable. i’m updating the docs now to explain exactly how the fee vaults are derived.
each launch gets its own isolated vault, deterministically derived from a throwaway encryption key. that derivation is what makes each fee vault esentially decentralized with no custoday.
i’ll also have a video up in a few minutes walking through the full process, including how the derivation works.
Okay, the issue isn’t with the RPC. $PONSBALL’s fee vault is currently failing its fee claim instruction, which is why no buybacks have occurred over the last 10 minutes.
other snowballs should be operating normally.
$PONSBALL was launched through the Pons v2 endpoint for sniper protection which is what broke the fee claiming endpoint.
fixing it now. should be done in 2-3 minutes.
rpc is upgraded. apologies, i should’ve caught that beforehand.
everything should be running smoothly again. the next buyback cycle executes in 5 minutes.
the snowball is rolling again, and it only gets heavier from here.
Launch a snowball today: ponsball.tech/launch
everything is deterministically derived at launch using the launch parameters and a fixed derivation scheme. .
i’ll update the docs with the exact derivation process so you can verify how it works rather than taking my word for it.
no one has any custody over their fee vault, the entire thing is decentralized.
