I want a standard spec for publishing multipart files to ethereum blobdata
Disclaimer
Quick Note
Main
As of 2026-07, Ethereum blobdata is the most censorship-resistant place on the internet. Period. (Maybe bitcoin blockchain beats it by a small margin, but also bitcoin blockchain is too expensive to be used as file storage.)
I recently published a copy of my website to ethereum blobdata. I had to ask gpt-5.6-sol to invent some arbitrary file format and metadata and so on.
Please consider pestering the devs at ETH ACD to standardise a spec for publishing multipart files to ethereum blobdata. By multipart files, I mean files larger than 128 KB which need to be split (such as using linux split) before being published. And then vice versa, receivers also need to know how to reconstruct the files before reading them.
I appreciate they don't want to force everyone to use the same spec. But also, it would be nice to have a default spec everyone can coordinate on, while also allowing people to deviate from the default.
Subscribe
Enter email or phone number to subscribe. You will receive atmost one update per month.
Alternatively, you can subscribe via RSS, or a third-party service like blogtrottr