kimmo replying to: kimmo

prune isn't the problem. anyone can hold the data and serve it, verifiably, against the onchain commitment. that's a feature, not a compromise. it's why L2s post their data to ethereum too. permissionless to re-host. impossible to fake.

single writer isn't the design. it's not a consensus either. the registry is permissionless. any client, any user, anyone can push their own data or blobs to ethereum. the reader, full or partial, can be hosted by anyone. it just dedupes by message hash. so censorship resistance is as strong as ethereum.

onchain validation isn't a dead end. that's what proofs are for. ethereum is walking straight at it.

on PQ. not ours to solve alone. it's an ethereum wide problem. we solve it together with everyone building here.

21 blobs is today. the roadmap's scaling. competition and utilization will climb. but so will innovation. we're building alongside ethereum, next to people solving problems that have nothing to do with social.

2 Replies

{no channel}

hash
e5ed22b3830337659b7833fc3bbbe85274955718
timestamp
2026-08-25T09:07:10.000Z
fid
12396
parent_fid
12396
parent_hash
570ecf9b8d791894a28b12ed9b6d25854ac9ad42