We suspect in some cases the archive is bigger than normally.
I'm adding a listing of the file sizes to catch that.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
* attestation pool support and tests
* REST endpoints changes
* initial ncli and validator client support
* updated tests file
* fixed typos
* review improvements
* remove V1 endpoint
* revert v1 removal
* V2 endpoint version available to pre electra
---------
Co-authored-by: Pedro Miranda <pedro.miranda@nimbus.team>
- Differentiate log for invalid packet seqnr without reorder buffer and
not
- Using unsigned types for message type and requst IDs
- Reassign logging weights in RLPx handler
- Fix potential uTP clock drift overflow
- arraybuf: seq-like fixed-capacity container stored on the stack
- Add cross-platform fsync() primitive and improve Direct mode
- Add updateFilePos() primitive and tests
- bump miniupnp to `miniupnpc_2_2_8`
- Fix for API VERSION 18 UPNP_GetValidIGD after last bump miniupnp
- update `ci.yml` and use non-deprecated `results`
- bump miniupnp to version that includes Status related fixes
- bump libnatpmp to `8257134a5dcb077e40db1946554d676e444406e4`
The comment in `readExecutionTransaction` is not actually relevant when
the `rlp.decode` template is called from a non-generic function.
The function still cannot be simply inlined; `is_valid_versioned_hashes`
is itself generic and would require an `export eth_types_rlp` to work
properly (generic sandwich issue). The non-generic function wrapper
seems simpler and avoids injecting RLP into importing modules.
Normally, running LC and DAG sync at same time is fine, but on tiny
devnet where some peer may not support the LC data, we can end up in
situation where peer gets disconnected when DAG is in sync, because
DAG sync never uses any req/resp on local devnet (perfect nw conditions)
so the LC sync over minutes removes the peer as sync is stuck.
We don't need to actively sync LC from network if DAG is already synced,
preventing this specific low peer devnet issue (there are others still).
LC is still locally updated when DAG finalized checkpoint advances.
* check blob versioned hashes when no EL is connected
When no EL is conencted, we have to at the very least ensure that the
data in the beacon block is consistent with the execution payload.
We already do this for the block hash, but also have to do it for the
`blob_kzg_commitments`. To validate that they are linked with the
execution payload, we have to RLP decode all EIP-4844 blob transactions
and compare their blob versioned hashes with the hashed commitments.
* simplify loop in case where `blob_versioned_hashes` doesn't exist
* skip blob transaction parsing pre Deneb
* bump nim-blscurve to `d5d595a59ca906898c51af7f9511a01082435393`
- Regenerate `blst_abi.nim`
- Expose Pippenger multiplication for combining multiple sigs of same msg
* bump nim-kzg4844 to `7bd7f115db8983be2549ce1a55891355c404fdc0`
- Ensure compatibility with patched `blst.h` from `nim-blscurve`
tersec
Jakub Sokołowski
Agnish Ghosh
Pedro Miranda
Etan Kissling
dependabot[bot]
Joel Williamson
Pedro Miranda
Jacek Sieka
Advaita Saha