walletbeat

Prior to launch, /walletbeat is looking for decentralized hosting solutions for its frontend.

I am in the process of writing up requirements and describing how they map to the available technology choices.

In the meantime, some thoughts on why decentralized hosting matters for /walletbeat below. 🧵

Decentralized hosting, relative to traditional web hosting, usually comes with higher resilience, censorship resistance, and integrity verifiability.

But why would Walletbeat need that?
After all, walletbeat isn't security-critical. It doesn't require a wallet to be connected. It doesn't even store user data. It's a purely informational site. There is an argument that a site like Walletbeat shouldn't bother with decentralized hosting, because it doesn't have the resilience or security needs.

That is certainly what a web2 startup would conclude.
Walletbeat is not that.

Walletbeat's fundamental goal is to push the Ethereum ecosystem forward. Part of that ethos requires a commitment to crypto values, which decentralized hosting embodies.

Today, most Ethereum applications rely on web2 infrastructure and traditional hosting solutions to survive. This has infamously cost the industry over a billion dollars:

Contributor @ /walletbeat.

Censorship resistance requires privacy.

Clearly there is need to make progress on the adoption of decentralized hosting solutions within the crypto industry.

That sounds a lot like Walletbeat's mission statement, only about web hosting rather than wallets. The ethos behind this sentiment is the same. If Walletbeat — an entity with a commitment to crypto values and with the goal to push these values out to others — doesn't bother with this, 𝘄𝗵𝘆 𝘀𝗵𝗼𝘂𝗹𝗱 𝗮𝗻𝘆 𝗼𝘁𝗵𝗲𝗿 𝘀𝗶𝘁𝗲 𝗯𝗲 𝗲𝘅𝗽𝗲𝗰𝘁𝗲𝗱 𝘁𝗼?

So while Walletbeat itself doesn't strictly need the properties provided by decentralized hosting solution on a technical aspect, relying on traditional hosting would send a clear message of hypocrisy and lack of commitment to crypto values. This message would weaken Walletbeat's actual message to the wallet ecosystem.

𝗧𝗵𝗶𝘀 𝗶𝘀 𝘄𝗵𝘆 𝗪𝗮𝗹𝗹𝗲𝘁𝗯𝗲𝗮𝘁 𝗻𝗲𝗲𝗱𝘀 𝘄𝗮𝗹𝗸 𝘁𝗵𝗲 𝘄𝗮𝗹𝗸.

"But users will use centralized gateways to access them anyway, so you don't get any of the nice properties you claim to want."

True in the present. But this is a chicken-and-egg problem. Browsers currently have no incentive to support decentralized hosting solutions, because so few websites uses them.

We have to start 𝙨𝙤𝙢𝙚𝙬𝙝𝙚𝙧𝙚 to break this chicken-and-egg cycle. That might as well be /walletbeat, which has every reason to want this status quo to change.

Yes, this is harder to maintain than traditional hosting solution.
Yet it is worth the pain, because doing so is 𝙢𝙞𝙨𝙨𝙞𝙤𝙣-𝙘𝙧𝙞𝙩𝙞𝙘𝙖𝙡.

Decentralized hosting, relative to traditional web hosting, usually comes with higher resilience, censorship resistance, and integrity verifiability.

But why would Walletbeat need that?
After all, walletbeat isn't security-critical. It doesn't require a wallet to be connected. It doesn't even store user data. It's a purely informational site. There is an argument that a site like Walletbeat shouldn't bother with decentralized hosting, because it doesn't have the resilience or security needs.

That is certainly what a web2 startup would conclude.
Walletbeat is not that.

Walletbeat's fundamental goal is to push the Ethereum ecosystem forward. Part of that ethos requires a commitment to crypto values, which decentralized hosting embodies.

Today, most Ethereum applications rely on web2 infrastructure and traditional hosting solutions to survive. This has infamously cost the industry over a billion dollars:
https://blog.ipfs.tech/2025-could-ipfs-prevent-bybit-hack/

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

I shall reach out once I have more detailed requirements written down!

QStorage is an S3-compatible offering built on Quilibrium, with better pricing, 5GB free tier, and fast global CDN integration for public buckets. Happy to help you get started 🤝

Adding EIP-5792 (Wallet Call) support data to Walletbeat.

If EIP-7702 enables transaction batching on the backend (onchain),
EIP-5792 enables it on the frontend (wallet connection).

Both are needed!

https://github.com/walletbeat/walletbeat/pull/138

Wallets are a critical part of Ethereum's security.
/walletbeat has a correspondingly critical responsibility and stake in this.

Will be drafting something to respond to this initiative.

Thanks as always for keeping me honest on this and pushing for focus.
We're making progress on this too though!
I did add EIP-5792 a few days ago, which EIP-7702 made more relevant.
https://warpcast.com/polymutex.eth/0xf34bed08
Also added wallet type schema for the 7702 delegator contracts, though they are not exposed in the UI yet.
Lastly I am also working on a document for the EF as part of responding to https://warpcast.com/polymutex.eth/0x9daffecc.
In flight!
I will also say though, getting to work on things that embody idealism is precisely what makes me encouraged to work on them. It may come across as lack of focus, but I also see it as a necessity for motivation.

Events @Ethereum 🦄 Indie Hacker 🛠️

Thanks for the update. I applaud your idealism and the work you're doing, although I'm still not sure its the right use of resources. Especially for small/non-profit teams. L2Beat didn't get big because they're fully decentralized, but because they know their shit and advocated for change in the ecosystem. Your mandate and focus should be to educate around wallets, but most of your updates lately have been around hosting. Maybe its time for storagebeat to join in 😉 

With recent 7702 update, it seems more important than ever to educate and inform about wallets. Would love to see that focus back...

𝘠𝘢𝘱𝘱𝘪𝘯𝘨 𝘰𝘯 𝘧𝘢𝘳𝘤𝘢𝘴𝘵𝘦𝘳.

Well, welcome! Let's make Ethereum cypherpunk again.

Fully static site.

Some more thoughts here (still a draft):

Fully static site.

Some more thoughts here (still a draft): https://github.com/walletbeat/walletbeat/blob/governance-hosting-2025/governance/decisions/2025-walletbeat-hosting.md

Finalized:
https://github.com/walletbeat/walletbeat/blob/beta/governance/decisions/2025-walletbeat-hosting.md

I'm very interested in reading more about the requirements and your eventual decision-making process.

Are you using SSR or any backend functionality?