Don’t usually work on a weekend but just delivered something cool for a community project.
Anyone who joins the free Stonks Dev’s Hangout from tomorrow gets to see it first, and more.
No catch! It’s just a place to hangout on Discord with data flows, AI agents and possibly some alpha.
The Standard Reserve is live. So is the terminal.
Back when it was pre-launch I built https://t.co/mLBWhb7SjO to read this protocol the moment it deployed. It deployed on 14 September, the pool opened on the 15th, and the terminal now reads it live from Robinhood Chain.
Straight from chain: circulating supply against the 1B cap, STANDARD burned, and active branches, already 1,099, that is the 1,000 founding branches plus 99 expansion licences bought and burned inside the first day. Issuance streaming per second. Treasury ETH across the vaults. Price, market cap, liquidity and volume from the canonical pool.
All 1,000 Founding Charters minted and confirmed soulbound onchain, so there is no secondary floor, whatever you have heard.
It also lists every verified contract address. Impersonator STANDARD tokens already exist on the chain. The only canonical token is the one the terminal reads, which is also currency1 in the hook's onchain pool key. Verify by address, never by name.
What it does not do is surface a trading signal. It reads public state only, does not call STANDARD "backed" by anything, and there is still no holder redemption claim against the reserves.
No affiliation. Not advice. Just the numbers anyone can read from chain 4663, in one place: https://t.co/mLBWhb7SjO
Stonks Dev.
@standard_rsv@0xbeans
Got more than a bit fed up of missing things.
So decided to play it differently on @arc, this morning literally as soon as the main net RPC API was live we started collecting the data, all of it. From genesis onwards. A few more hours and it will be up to date. From there we have an in-house history of every token flow. Our AI local has access.
The theory is simple, find where the big money moves early, check the viability of the project & token, and decide whether to take a position or not.
Should be fun.
Stonks Dev.
the chain we're on was built by Circle for AI agents that trade in USDC.
the launchpad we launched from is run by an AI that scores every coin before you see the ticker.
bots don't read threads. they read state.
we're the dog they can vet.
first again.
https://t.co/OXSUinBKT8
@__spekulator__@standard_rsv@0xbeans Correct on both. Minting and soulbound are onchain-confirmed (transfersEnabled = false); I'm not claiming holder identity. The 99 is derived, not a separate counter: totalBranches 1,099 minus 1,000 founding = 99 net new branches since genesis.
The Standard Reserve is live. So is the terminal.
Back when it was pre-launch I built https://t.co/mLBWhb7SjO to read this protocol the moment it deployed. It deployed on 14 September, the pool opened on the 15th, and the terminal now reads it live from Robinhood Chain.
Straight from chain: circulating supply against the 1B cap, STANDARD burned, and active branches, already 1,099, that is the 1,000 founding branches plus 99 expansion licences bought and burned inside the first day. Issuance streaming per second. Treasury ETH across the vaults. Price, market cap, liquidity and volume from the canonical pool.
All 1,000 Founding Charters minted and confirmed soulbound onchain, so there is no secondary floor, whatever you have heard.
It also lists every verified contract address. Impersonator STANDARD tokens already exist on the chain. The only canonical token is the one the terminal reads, which is also currency1 in the hook's onchain pool key. Verify by address, never by name.
What it does not do is surface a trading signal. It reads public state only, does not call STANDARD "backed" by anything, and there is still no holder redemption claim against the reserves.
No affiliation. Not advice. Just the numbers anyone can read from chain 4663, in one place: https://t.co/mLBWhb7SjO
Stonks Dev.
@standard_rsv@0xbeans
I just deployed an independent monetary policy terminal for the protocol: https://t.co/mLBWhb7SjO
The methodology page maps every gauge to the whitepaper's formulas, the simulator models the policy staircase and resolution fee with your redacted parameters as labelled assumptions.
This site is community built, clearly marked unaffiliated, and I'll of course correct anything the contracts contradict. If any of it misreads the mechanism, tell me and I will fix it.
@standard_rsv
I lost 2.8 ETH on YOINK. I've been in crypto long enough to know what a rug looks like (or so I thought), which is probably why this one bothers me more than it should.
I didn't buy because a KOL told me to, chase a green candle or blindly ape into a random token. I found the builder, I read his work, dissected the website, went through the GitHub, looked at what he'd built and who with. There was a real product and some genuinely clever work behind it, it was cool, I really thought I'd done my homework.
But it turns out I hadn't done enough. After losing the money I stopped looking at what had been built and started following the ETH. I've since spent (and continue to spend) far too much time going backwards through wallets, contracts, GitHub histories, those involved, old accounts and even previous launches. What I found made the 2.8 ETH almost irrelevant. Perhaps that's a story for another time.
I guess that's the bit I find depressing about crypto now. Scammers have always been here, I've been around long enough to remember much worse, but there used to be a reasonably obvious distinction between the people building cool things and the people extracting from the people buying them.
I'm increasingly unsure that distinction exists, a GitHub isn't proof, shipping isn't proof, a working product isn't proof. Even years spent building a reputation isn't necessarily proof. In fact, I've realised those things can make the extraction considerably more effective because they're exactly what people like me have learned to look for when deciding who to trust.
That's where I got this one wrong, I mistook evidence of competence for evidence of alignment, they're not the same thing.
It's not a good start to the week, but I'm not going to stop backing weird people building interesting things early, that's half the reason I'm still here, but I'll likely do it less and approach it differently after this one. Which is a shame.
Stay safe out there everyone.
Stonks Dev.
Worked out what $YOINK is?
It's a fee machine, not a burn machine. Pons V2 launch, creator tax set to the max: 2.5% on every trade, 88% of it to one wallet, paid in ETH every 40 seconds.
That wallet (0xb9ff…530a) claimed 29 ETH at 16:38 UTC. Hasn't moved since. Two burn windows passed with it sitting there.
The "fires on a clock, nobody signs" burn doesn't exist yet. The site says so itself: NOT LIVE, nothing deployed, burns so far 0. The clock is a JS timer on a 90 min grid. The only burn was 5.77M sent by hand at 13:46.
What comes next: he deploys the burner, fills in the dashes, and fires the 29 ETH (maybe) into a 13 ETH pool. At this cap that's ~8% of supply and a 10x candle. The longer he waits the bigger it prints. That's the whole play, for now.
Whether it comes before the pool runs dry is the trade. I'm in it. Watching the wallet, not the countdown.
@yoinkcapitall