Content pfp
Content
@
https://warpcast.com/~/channel/walletbeat
0 reply
0 recast
0 reaction

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
4 recasts
27 reactions

Sebastian Bürgel pfp
Sebastian Bürgel
@scbuergel
What sync committee do you use as a trust anchor in that? Merge block?
1 reply
0 recast
1 reaction

polymutex pfp
polymutex
@polymutex.eth
There is a mainnet checkpoint checked into the repo itself at `deploy/helios/data/checkpoint`, and there's a CI workflow updates it every few days: https://github.com/walletbeat/walletbeat/blob/beta/.github/workflows/helios-refresh.yaml Helios is also started with the `--strict-checkpoint-age` flag, which makes it refuse to start if that checkpoint is too old: https://github.com/walletbeat/walletbeat/blob/5ca663f98b5511caf08d5ee2bf67e466f2fd85a1/deploy/helios/helios-wrap.sh#L30-L36
1 reply
0 recast
1 reaction