You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've recently switched from the c-kzg library to the Rust peerdas-kzg library on the das branch (#5941). The purpose for the switch was to:
Try out a new alternative to c-kzg;
Allow us to merge das branch to unstable without having to update c-kzg to a development version
However we've now lost the option to run the das branch with ckzg, which has been quite stable for a while. We've recently run into a few issues with peerdas-kzg, including slow startup time and stack overflow during block production (#6105). Therefore I think it would be great to have the option to use ckzg library, especially for public denvets, where a small number of reliable supernodes is required.
Ideally we want to be able to:
maintain the ckzg library version for the mainnet code path
optionally include the ckzg peerdas library when it's enabled via a feature flag, so both ckzg library will co-exist when this ckzg-peerdas feature is enabled, however this library will only be referenced by the PeerDAS portion of the code.
allow selecting the ckzg-peerdas library via a hidden runtime flag
The text was updated successfully, but these errors were encountered:
rust-eth-kzg seems to perform better in PeerDAS - I'm not sure if this has changed.
Alternatively, an option is to maintain the status quo for now, and gradually phase out c-kzg over time? We can't completely switch over to rust KZG yet, AFAIK it hasn't been audited, but I'd assume there are plans to do this.
@pawanjay176 also expressed his preference to maintain the status quo now and eventually get rid of c-kzg. It's unclear whether both libraries will be maintained in the longer term.
Description
We've recently switched from the
c-kzg
library to the Rustpeerdas-kzg
library on thedas
branch (#5941). The purpose for the switch was to:das
branch tounstable
without having to updatec-kzg
to a development versionHowever we've now lost the option to run the
das
branch withckzg
, which has been quite stable for a while. We've recently run into a few issues withpeerdas-kzg
, including slow startup time and stack overflow during block production (#6105). Therefore I think it would be great to have the option to useckzg
library, especially for public denvets, where a small number of reliable supernodes is required.Ideally we want to be able to:
ckzg-peerdas
feature is enabled, however this library will only be referenced by the PeerDAS portion of the code.The text was updated successfully, but these errors were encountered: