Farcaster Devs

Can a hub use Helios for its Eth/OP RPC? https://github.com/a16z/helios
@sanjay?

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

It should be feasible, as it can listen on a port and act as a verifying proxy. So it would just be a matter of running it that way, and pointing the Hub at it as the chain RPC endpoint. Haven't tried it in practice though.

Wannabe contributor for /walletbeat.

Censorship resistance requires privacy.

I couldn't find the min hw specs to run Helios. Do you know what they are?

It's pretty modest. You can run light clients in your browser against Ethereum L1 + OP Mainnet + Base all at once in a tab using the following page. My browser measures it as using ~300 MiB for all three networks combined. Probably more efficient if run headlessly.

It's pretty modest. You can run light clients in your browser against Ethereum L1 + OP Mainnet + Base all at once in a tab using the following page. My browser measures it as using ~300 MiB for all three networks combined. Probably more efficient if run headlessly.

https://helios.a16zcrypto.com/demo

Once it's synced, does it still need a third party RPC? So, it's not replacing the RPC, just provides a trusted one?

building open source public goods @a16zcrypto

Do you know what's the lightest possible version of a stand alone Eth client, that does not need to post transactions to the chain?

Correct, it still needs a persistent connection to the remote RPC provider to keep up with the chain head, or to fetch chain data when requested by the client, etc. The only thing it does is to turn an untrusted RPC endpoint into a trusted one.
cc @ncitron.eth