Saulius Grigaitis

81 posts

Saulius Grigaitis banner
Saulius Grigaitis

Saulius Grigaitis

@sauliuseth

I’m interested in a wide range blockchain related challenges (consensus, zero knowledge proofs, PQ cryptography etc.)

Vilnius Katılım Nisan 2010
33 Takip Edilen196 Takipçiler
Saulius Grigaitis retweetledi
Lido
Lido@LidoFinance·
The 29th Lido Node Operator Call is coming up tomorrow at 4pm UTC 📢 Tune in here: youtube.com/live/hzTpFFq4O… Agenda: • Lido ValSet Updates w/ Iryna • stVaults Testnet Progress w/ stETH Workstream • Grandline w/ @sauliuseth • CSM Evolution & Community Stakers Identification Framework w/ @d_gusakov and @sasha_gusakova
YouTube video
YouTube
English
6
10
47
15.1K
Saulius Grigaitis retweetledi
Lido
Lido@LidoFinance·
It's time for the 29th Node Operator Community Call! Mark your calendar for next Tuesday, June 17th, 4pm UTC. Agenda: • Lido ValSet Updates w/ Iryna • Grandine w/ @sauliuseth • stVaults Testnet Progress w/ stETH Workstream • CSM ICS (Identified Community Staker) Preview w/ @d_gusakov
Lido tweet media
English
3
12
49
4K
Saulius Grigaitis retweetledi
grandine.eth
grandine.eth@grandineio·
Grandine is open-sourced! 📰Announcement: @grandine/grandine-is-open-sourced-b1815cf0ae39" target="_blank" rel="nofollow noopener">medium.com/@grandine/gran… 🧑‍💻Repository: github.com/grandinetech/g…
English
1
10
43
2.7K
Saulius Grigaitis retweetledi
grandine.eth
grandine.eth@grandineio·
The latest docker image of Grandine is available with Holesky 2.0 genesis hub.docker.com/layers/sifrai/… . Fingers crossed for a successful launch tomorrow!
English
0
1
1
260
Saulius Grigaitis retweetledi
grandine.eth
grandine.eth@grandineio·
We finally released the documentation of the Grandine Ethereum Consensus Layer Client grandine.io 📙📗📕
English
0
1
3
207
Saulius Grigaitis
Saulius Grigaitis@sauliuseth·
20. However, it feels a bit weird to have such two modes. Especially when users by default would use specification non-compliant optimised mode.
English
0
0
0
95
Saulius Grigaitis
Saulius Grigaitis@sauliuseth·
19. This would allow us to quickly bring back support for updated test vectors in case the new test vectors touch some cases that the optimized version doesn't cover.
English
1
0
0
105