ncitron.eth pfp

ncitron.eth

@ncitron.eth

446 Following
3289 Followers


ncitron.eth pfp
ncitron.eth
@ncitron.eth
Well as long as you run Helios every so often you don't need to worry about this at all. As for the scheme you described, how would you know someone else had faithfully run Helios actually at the previous time? The invariant you need to maintain is that at least ever week subjectivity period, someone actually ran it *at that time*. In other words any system that timestamps that a checkpoint existed at or around the time its from works. This is why schemes like submitting checkpoints on bitcoin make sense, since PoW is a great timestamping system. For what it's worth, I don't think we need to worry to much about these "long range attacks" on Helios. They aren't particularly realistic especially compared to the light clients existing security model. These attacks are basically predicated on the idea that once a validator withdraws its stake, it's easy to get its key and sign a malicious fake block with it. I think it's just as easy (so pretty hard) to bribe a more recent such committee to sign a bad block.
0 reply
0 recast
2 reactions

polymutex pfp
polymutex
@polymutex.eth
Walletbeat now automatically deploys to IPFS via @orbiterhost, then updates ENS records. Yes, it uses Helios as a light client when interacting with the chain. Imagine ๐˜ฏ๐˜ฐ๐˜ต using a light client in 2025. Utterly inconceivable, especially for wallets, right?
6 replies
5 recasts
25 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
Well there's the storage unit system as well. But you're right that the existing protocol doesn't really charge for usage during bursty periods. Using some identity system for priority during these periods is actually a good idea.
2 replies
0 recast
1 reaction

ncitron.eth pfp
ncitron.eth
@ncitron.eth
I suspect a combination of things like WorldID and zkTLS could achieve a decent spam metric, but the bigger question is should these systems actually be built at the protocol level. Honestly don't know the answer. Dan seems to get the risks though of popular clients having defacto control of what gets reached in a non-protocol based spam detection. But if we did it at the protocol level, would we be buying anything of use? Clients can still put their own filtering on top of that, so arguably a protocol level spam filtering solution would only provide a base level of filtering and doesn't enforce what subset of the post-protocol-filtered content is shown. What does protocolizing that actually buy us then? It doesn't enforce any notion of censorship resistance (because clients can still filter you). I don't see the benefit of buying this "base filtering" from a company vs protocol.
1 reply
0 recast
3 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
New and improved Helios demo showing off Helios running on four separate networks all in the browser. https://helios.a16zcrypto.com/demo
1 reply
4 recasts
20 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
New Helios release! Version 0.8.6 enables pectra on Ethereum mainnet. This is a required upgrade and most be installed by the fork on May 7th. Upgrading is as simple as running heliosup in your terminal. https://github.com/a16z/helios/releases/tag/0.8.6
0 reply
9 recasts
44 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
RISC-V being the semi-canonical zkVM target makes this nice, but tbh R5 is not the best VM target out there for native execution. It was designed for physical chips so isn't actually optimized for virtualization as much as something like wasm is (although wasm has its own problems like high performance deterministic execution). I'm broadly in favor though.
0 reply
0 recast
1 reaction

ncitron.eth pfp
ncitron.eth
@ncitron.eth
My FID is 941 so it's definitely been a while
0 reply
0 recast
3 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
Not a ton right now but you can take a look at the helios-ts crate in the repo which has an example.
0 reply
0 recast
1 reaction

EulerLagrangodamus pfp
EulerLagrangodamus
@eulerlagrange.eth
https://warpcast.com/ncitron.eth/0x19ddf67c
1 reply
1 recast
3 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
Yep we have it working pretty well now!
1 reply
0 recast
1 reaction

ncitron.eth pfp
ncitron.eth
@ncitron.eth
We've added @linea support to Helios! This makes Linea our second supported L2 with more to come soon. Huge shoutout to the @mendifinance team for building the implementation! Head over to our GitHub to get started using Helios on Ethereum, Linea, or the Optimism Superchain! https://github.com/a16z/helios
4 replies
47 recasts
187 reactions

EulerLagrangodamus pfp
EulerLagrangodamus
@eulerlagrange.eth
Noah pulling up to the major L1 client implementations like
0 reply
1 recast
4 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
No chains going to deprecate their light client support on my watch ๐Ÿซก
0 reply
0 recast
3 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
Let me know if you run into any issues. Excited to see what you build!
0 reply
0 recast
1 reaction

ncitron.eth pfp
ncitron.eth
@ncitron.eth
So Helios saves the most recent valid checkpoint so once you sync for the first time you can just sync later from your own previous checkpoint. On initial sync you can use one hardcoded by Helios (which may be old and therefore use some more bandwidth, but still really not much), provide your own checkpoint from wherever you choose, or fetch it from a trusted checkpoint provider (from a list of services maintained by ethpandaops)
1 reply
0 recast
1 reaction

. pfp
.
@chaskin.eth
#lightclients
4 replies
2 recasts
17 reactions

ncitron.eth pfp
ncitron.eth
@ncitron.eth
It depends on how far back your checkpoint is but we're talking kilobytes not megabytes assuming a relatively fresh checkpoint @shazow.eth
1 reply
0 recast
1 reaction

ncitron.eth pfp
ncitron.eth
@ncitron.eth
Does your favorite wallet actually check the chain?
2 replies
30 recasts
131 reactions

a16zcrypto pfp
a16zcrypto
@a16zcrypto
Applications for CSX Spring 2025 are now open! Our Crypto Startup Accelerator (CSX) program provides expert guidance, capital, and resources for founders of early-stage crypto startups. More details about the program: โ†’ Will be held in San Francisco ๐ŸŒ โ†’ Minimum of $500,000 investment โ†’ The nine-week, in-person program will start in April and end with a Demo Day in June ๐Ÿ“ฃ โ†’ Participants receive hands-on guidance, mentorship, and inspiration from some of the best leaders and operators in crypto today ๐Ÿซก โ†’ Application will remain open until February 7th ๐Ÿ“œ Apply here: http://apply.a16zcrypto.com -- None of the above should be taken as investment advice or an advertisement for investment services; please see https://a16z.com/disclosures/ for more information.
5 replies
32 recasts
151 reactions