If you think about the many thousands of actions you take on the internet every day - paying a bill, liking a post, messaging a friend. The ratio of those which actually involve financial transactions (like paying the bill) vs those which are purely for social or for fun - is probably about the same ratio of dApp interactions we’ll eventually see handled by trust-minimised smart contracts vs trust-minimised TEE systems (which will have 1000-10000x lower costs, no storage bounds, and real-time interactivity. ) That’s not a shot against SC platforms though; which really are the cornerstone enabling tech for decentralised architectures. There’s no incongruence thinking: TEE systems will handle 99.99% of dApp interactions by quantity whereas SC platforms will handle 99.99% of interactions by value. The future is in ensuring max alignment of both techs to enable new use-cases, and accelerate the space forward… Maybe then we can stop sitting around year after year wondering - “where the heck are all the apps we were promised?!” Because, it should be pretty clear at this stage: it’s not a shortage of blockspace!

top scores well deserved. it's not only interesting in terms of a SotA step forward - it's also just immaculately well-crafted. using it together with VRF sortitions for a beacon-chain design. thanks to each of you @XiangZhuolun @xosmig @SashaSpiegelman

industry: gets hacked “how did the devs let this happen?” the devs:

The “mullet” haircut version of decentralisation. Raspberry Pis in the front, unfathomably large proving clusters in the back

I’m the CEO of a hot dog company. I’ve worked on hot dogs for 10 years. And *I* wasn’t prepared for what I’ve just seen. Your life is about to change. So what can you do? Buy as many hot dogs as you can. Buy stock in hot dog companies.

SQLite has about 155,800 lines of code, and its test suite has roughly 92 million lines. That is ~590x more test code than actual code 🤯 This is the level of testing you need for a real production database. Here are some types of tests they run. Out-of-memory tests - SQLite cannot just crash when memory runs out. On embedded devices, OOM errors are common. They simulate malloc failures at every possible point and verify that the database handles them gracefully. I/O error tests - Disks fail. Networks drop. Permissions change mid-operation. SQLite inserts a custom file system layer that can simulate failures after N operations, then verifies that no corruption occurs. Crash tests - What happens if power cuts out mid-write? They simulate crashes at random points during writes, corrupt the unsynchronized data to mimic real filesystem behavior, then verify the database either completed the transaction or rolled it back cleanly. No corruption allowed. Fuzz testing - They throw malformed SQL, corrupted database files, and random garbage at SQLite. The dbsqlfuzz tool runs about 500 million test mutations every day across 16 cores. 100% branch coverage - Every single branch instruction in SQLite's core is tested in both directions. Not just 'did this line run', but 'did this condition evaluate to both true AND false'. Databases are really unforgiving :) By the way, if you want to go deeper, I recommend reading the official SQLite documentation on their testing strategy. The doc is pretty practical and deep. Have linked it below.

Yo, @SasuRobert - i'm cooking up a high perf, high composability sharded ledger and i'm going to steal your designs for sPOS - thanks!

RT @marczeller: We make little to no revenue on scroll, and they don't even pretend to be decentralized anymore. Centralized networks are r…

The hidden cost of hiring the wrong people.

It’s amazing how, for some MFs, the difference between: “it’s a landgrab!!” and “it’s aligned <3” is just posting some dumb blobs on-chain (which does nothing for ETH either way)

1/5 As an investor, I see Tesla’s proposed 2025 CEO Performance Award for Elon Musk as a model for aligning executive incentives with long-term value creation. No time based vesting. Crypto founders should study this structure. It’s all-or-nothing RSUs, vesting over 7.5-10 years, tied to $7.5 trillion in shareholder value.

Good list

Most sane LinkedIn post I’ve ever seen

Wonder if StarGate team will do what’s best for holders, or will it show the whole voting process is just decentralisation theatre

Daily revenue of “emerging” blockchains (last 24h): • Story Protocol – $23 • Metis – $221 • Blast – $288 • Starknet – $496 • Scroll – $527 • Sei – $540 • Immutable zkEVM – $45 • Celestia – $150 • zkSync Era – $1,938 • Mantle – $5,577 Do we really need more L1/L2?

Higher

Many such cases

Remember the symbol below. It’s the biggest evidence someone is writing overly self-congratulatory tweets for basic bitch solutions at 100x the engineering run-rate actually required

Many such cases

Pretty cool. I’ve long thought that a new ETL/materialisation abstraction layer seems like an obvious and necessary next step for managing the read-side of high-write chains You guys should look into this little known [non-crypto] tech for how far you can push the idea (no relation; I just think they’re doing cool things) estuary.dev/product/