Every system begins with good intentions. A hosted node here, a whitelisted relayer there. Each is harmless on its own — and together they become habit.

Gateways become platforms. Platforms become landlords. Landlords decide who may enter and what they may do.

The only defense is trustless design: systems whose correctness and fairness depend only on math and consensus, never on the goodwill of intermediaries.

Trustlessness is not a feature to add after the fact. It is the thing itself. Without it, everything else — efficiency, UX, scalability — is decoration on a fragile core.

Trustlessness is how credible neutrality is achieved. Without it, the system becomes one that depends on intermediaries.

Signed the trustless manifesto!

https://trustlessness.eth.limo/general/2025/11/11/the-trustless-manifesto.html

--@vbuterin

First day at Optasia.com. I missed these guys (was there for 6 years, in the past), and feels healthy to work on something not crypto-related, after a long time. Will probably post much less -but may have some interesting stuff to share, especially during trips.

I don't get Minecraft Youtube. (you probably relate if you have kids)

But then, I watch this. And I find it exciting. So who am I to judge?

How to write a Web Server in pure bash: https://www.youtube.com/watch?v=L967hYylZuc

BTW, the whole channel is amazing.

For some reason @wdimapp's image feed brings up casts that I've totally missed.

It could be that an image embed requires some additional effort (even if marginal) from the poster, so it's a filter by itself. Or that my brain can scan through a feed of images more efficiently than text.

But there's something there.

This is starting to look good. Nothing really fancy, it's practically a guide on how to formalize and leverage a specific FIP-2 use case.

At the same time, the spec takes into consideration practical limitations and implementation hurdles (for example, how easy it is to implement at scale, with minimal resources).

Start a thread in discussions if you have questions, or suggestions, or any other feedback. Also, interested in applications that could leverage it, other than blog feeds.

https://github.com/vrypan/snappub

So, I started working on the ideas described in https://blog.vrypan.net/2025/10/24/snapchain-and-static-blogs/ which lead me down a rabbit hole:

  • https://github.com/vrypan/snappub This repo has the initial spec for RSS feed to use Snapchain as their notification backend (what used to be a "RSS ping service"). This is a very efficient way to notify RSS readers that a feed has been updated.

  • https://github.com/vrypan/snappub-tools To help with testing, especially devs that know little about Farcaster and Snapchain, I started building a set of tools to help them send updates and check if a feed has been updated.

  • https://github.com/vrypan/fc-appkey Which had me face the old problem with posting to Farcaster from your own apps: appkeys (aka signers). So, I decided to fix this for everyone. fc-appkey is easy to install (just binary, brew, etc) and will show you the QR code in your terminal, and let you generate appkeys:

  • And btw, I realized that I can use a single repo for all my homebrew taps, so, I'll start migrating all of them under vrypan/homebrew-tap.

I've been spending more time on https://reederapp.com lately. Which comes with my blog becoming the core of my online presence again. And also, bckt-generated RSS feeds getting some love.

Being able to post on Farcaster (which is easy, compared to writing a new blog post) and then selectively converting casts to blog posts with a single command, is liberating. I could automate the process, but I like the curation step -not everything I post here is worth becoming a blog post.

I also have a couple of ideas on how to piggyback on snapchain to offer ActivityPub-like or even ActivityPub-compatible functionality for static blogs.

Hey! I’m you, three years from now. Don’t bother.

BTW, @dwr, there was a very interesting community/movement around "IndieWeb" about 8-9 years ago. I have not followed it for some time, but anyone building an open web3 should have a look at their concepts and ideas.

--@vrypan