-
The `/eth/v1/beacon/states//validators` endpoint returns a lot of data. At the time of writing, this endpoint returns around 370MB of JSON. This requires a fair amount of CPU and memory resources on…
-
I saw a recent file from a tutorial run and it looks like timestamps get added to outputs of the form
YYYY-mm-ddT_HHMMSSZ.
The canonical ISO-8601 form for UTC is of course
YYYY-mm-ddTHH:MM:SS…
-
#### Problem statement
In an SSZ partial, we have:
* A list of generalized indices representing the `leaves` you want to make a partial of (often, this is just a single one)
* A list of general…
-
Now that `@ethereumjs/util` properly supports prefixed hex string conversions by default, we should switch all of our usage from `toHexString` and `fromHexString` (imported from `@chainsafe/ssz`) to `…
-
This issue is to compile milestones we would like to achieve to consider ourselves v2.0 ready. The general goal of major bumping Lodestar is to signify our client's ability to match and/or exceed metr…
-
At current the beacon API enshrines JSON as the only first-class encoding for sending and receiving data. I propose that we provide SSZ as an alternative encoding for all endpoints.
## What is SSZ…
-
## Description
We presently include the *uncompressed* genesis state for supported networks in our binary. We have several of these files:
```bash
[3.3M] common/eth2_network_config/built_in_ne…
-
### What is wrong?
There are two types of spec tests we aren't running: "ssz static" and "ssz generic".
I don't expect any surprises because afaik these tests are generated w/ `py-ssz` which we …
-
This issue is tracking to all the problems and changes to support building Grandine on Windows.
More about this [Project idea](https://github.com/eth-protocol-fellows/cohort-five/blob/main/project…
-
Currently date/time is represented as 8 different formats in the data, with 66.3% of all specified date/time fields not specifying a timezone.
![image](https://github.com/user-attachments/assets/649…