tersec

Results 96 issues of tersec

https://nim-lang.org/docs/manual.html#types-cstring-type states: > For the C backend the cstring type represents a pointer to a zero-terminated char array compatible with the type char* in Ansi C. https://ansi.org/ is very clear...

bug

https://github.com/status-im/nim-eth/blob/be5e088b21e06a85cac4826454412db8459ed4f1/eth/common/eth_types.nim#L192-L193 With Nim 1.2.10 and newer, this would raise a `RangeError/RangeDefect` due to https://github.com/nim-lang/Nim/issues/15210, when the block number's too high.

Or otherwise ameliorate these: ``` nim-beacon-chain/vendor/nim-eth/eth/p2p/p2p_backends_helpers.nim(33, 6) Hint: 'initProtocolStates' is declared but not used [XDeclaredButNotUsed] nim-beacon-chain/vendor/nim-eth/eth/p2p/p2p_backends_helpers.nim(41, 6) Hint: 'resolveFuture' is declared but not used [XDeclaredButNotUsed] nim-beacon-chain/vendor/nim-eth/eth/p2p/p2p_backends_helpers.nim(46, 6) Hint: 'requestResolver' is...

https://github.com/ethereum/consensus-specs/blob/v1.2.0-rc.3/specs/phase0/validator.md#attesting states >A validator should create and broadcast the `attestation` to the associated attestation subnet when either (a) the validator has received a valid block from the expected block proposer...

VC

Followup to https://github.com/status-im/nimbus-eth2/issues/4051 / https://github.com/status-im/nimbus-eth2/pull/4115

VC

https://github.com/status-im/nimbus-eth2/pull/4086 didn't help enough. This PR should help figure out what's going wrong. Don't merge.

DO NOT MERGE

This addresses: - it should, per spec, be retrying calls such as `newPayload` when they're crucial to forward progress. `newPayload` occurs in two timing contexts, the block processing queue which...

There haven't been any phase0 blocks in mainnet or any of the still-supported testnets in [`MIN_EPOCHS_FOR_BLOCK_REQUESTS`](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#configuration) regardless, so the spec already technically supports not serving said blocks. https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/p2p-interface.md#beaconblocksbyrange-v2 and https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/p2p-interface.md#beaconblocksbyroot-v2...

At this point, if anyone's still trying to use Ropsten, that's very likely deliberate.

Or for which this doesn't apply. So this is just a complete list of `vendors` directories. - [x] eth2-networks (n/a) - [x] gnosis-chain-configs (n/a) - [x] holesky (n/a) - [x]...