ssz
ssz copied to clipboard
karalabe
Opinionated 0-alloc SSZ codec for Go
For some chains like Gnosis, different field specs are defined ([example](https://github.com/ChainSafe/lodestar/blob/20c18ad85d6cb5e37d4980446d4f608ce9169c24/packages/params/src/presets/gnosis.ts#L21)). A notable example is ``` Withdrawals []*Withdrawal ssz-max:"16"` ``` which has `ssz-max=16` for Ethereum networks and `ssz-max=8` for Gnosis...
Currently the library ships the Ethereum hard forks in an enum, allowing it to be used across the lib, as well as having built in support in the code generator....
Trying to make things a bit more modular and eventually introduce proof generation
I think the thing that I am trying to figure out, is how to make this library more extensive / modular, and allow extending it for custom use cases (i.e...
Idea is to allow for a in memory tree representation of an SSZ object
I cloned the repo locally for working on https://github.com/karalabe/ssz/issues/12, and tried running `go test ./tests` at the root directory, but it looks like unit tests for `TestConsensusSpecBasics` are all failing...
This _might_ speed up the int-slice encoder a bit ```diff diff --git a/encoder.go b/encoder.go index 3f3a264..42725f0 100644 --- a/encoder.go +++ b/encoder.go @@ -198,11 +198,23 @@ func EncodeSliceOfUint64sOffset[T ~uint64](enc *Encoder, ns...
