-
Seems like a
var unitIdentifier = 0xFF;
giving this error when I using your examples.
The device manual saying:
"INPUT DATA AREA
The following table lists the registers of the input area (pro…
-
### Describe the bug
The node stops producing new blocks or anything else. the logs become static except for variation in peer count and new head notifications from beacon.
upon further inspection…
-
[EIP-4788](https://eips.ethereum.org/EIPS/eip-4788) introduces a system contract which is deployed as a normal contract to the state. However it is required for networks which have the Cancun fork ena…
s1na updated
4 months ago
-
### Describe the bug
Reth complains about a bad block due block gas used mismatch.
I am using the [ethereum kurtosis package](https://github.com/ethpandaops/ethereum-package) configured with 2 nodes…
-
Hello team,
in our efforts to introduce a [CAIPs](https://github.com/ChainAgnostic/namespaces/pull/104) standard compliant [Sign-in With Tezos](https://github.com/StakeNow/tzip/pull/11) message for…
-
# 💎 Issue
The command: bazel run //cmd/beacon-chain --config=release --execution-endpoint=http://localhost:8551 --mainnet --jwt-secret=/tmp/jwtsecret
ERROR: --execution-endpoint=http://localhost:…
-
After POC Offchain, the miners don't send the beacons through the middlmen.
-
```
2024-03-12 08:19:00.047
{"@timestamp":"2024-03-11T22:19:00,014","level":"INFO","thread":"TimeTick-1","class":"teku-event-log","message":"Syncing *** Target slot: 7807295, Head slot: 7772295…
-
Not sure how to best explain this issue, but we are seeing layers uploaded with an invalid creation time when it is expected to be unix epoch 0 (`1970-01-01T00:00:00Z`)
Example of an image created …
-
### Description
OP and its roll-up networks cannot use Besu client to sync up their nodes. They work with Geth but not Besu.
### Steps to Reproduce (Bug)
1. Run op-geth
2. Run op-node
**Expec…