The recent 3 governance votes on Solana are now over
The stats:
- Governance Process(SGP-1) passed
- Doubling Disinflation(SGP-2) passed
- Resource and Inclusion fee(SGP-3) failed
- >61% of stake participated
Solana had the highest participation in onchain governance ever
The X Safety team conducted an investigation into suspected Chinese inauthentic accounts involved in influence operations:
We identified a bot farm of approximately 200,000 accounts. Within this farm, we found 200 accounts posting in a manner that could manipulate a legitimate debate about American AI and energy policy.
These posts contained claims that AI data centers are driving up household electricity prices and straining the grid. Others included AI-generated cartoons that depicted data-center operators enriching themselves at the public's expense.
We remain committed to maintaining an open and authentic platform where people debate topics of public interest. We take seriously any attempts to undermine the integrity of the global town square and suspend accounts that violate our Authenticity policy.
Californians could soon see some relief from their sky-high electric bills.
The reason? Data centers.
Thanks to data centers, PG&E has been able to offer rate cuts for the fourth time in two years.
Let's keep building!
We built a router. Not meant to compete with existing routers. We need it for our upcoming solana-wide execution quality scoring. More on that in a future post
Supports 10+ propAMMs and many more AMMs
Still early days and a bit hungry on the CUs
You arenโt a real American unless you put some food in a Tupperware container, then put it in the fridge and forget about, and then it gets nasty and moldy, and you are too lazy to clean it so you just throw the entire thing out.
Most agent stacks still score tool calls as independent events. The failure mode that matters is a shared objective surviving across processes, channels, and retries. Thatโs a distributed systems problem with side effects, not a prompting problem
Bad news: Fable nuked my entire dev machine
Claude decided to test a sandbox it was building by running `rm -rf` on my home directory
The sandbox didn't work.
It's all gone
What's actually blocking SIMD-0306 activation? It's implemented (Agave v3.0.0, gate htsptAwi2y...), pending for ~a year.
Post-0286 a hot account is pinned at 12M CU โ 12% of a block it used to fill 20% of.
@toly Today: ~290M txs/day, avg fee 44k lamports (87% of it priority)
At ยฝ lamport/CU: avg fee 157k lamports = $0.011 at the same SOL price
$0.003 survives only for txs that set tight CU + loaded-data budgets
@toly@joeymeere@jacobvcreech About 5% of epoch-1015 transaction volume appears marginal enough to be priced out by SIMD-0553โs initial 0.1-lamport/CU burn. The modeled range is 2.9โ8.7% (5.2% at ฮต=-0.5). This is fee-sensitive attrition, not observed transaction P&L