Comments (7)
cheatfate
commented on July 18, 2024
This issue should be fixed in unstable.
from nimbus-eth2.
pinebit
commented on July 18, 2024
When the fix from unstable branch is going to be released?
Also, is this affecting kurtosis only, or this is happen in real network(s)?
Thank you!
EDIT: we tested Nimbus BN with kurtosis for all combinations of VCs (various vendors) and this failed for them all.
from nimbus-eth2.
tersec
commented on July 18, 2024
In theory, it's in https://github.com/status-im/nimbus-eth2/releases/tag/v24.5.1 as #6261
Is what you're seeing specifically still this issue or another cause of failure?
from nimbus-eth2.
nflaig
commented on July 18, 2024
Is what you're seeing specifically still this issue or another cause of failure?
gave this another try using statusim/nimbus-eth2:amd64-latest and I am still seeing the same error as reported in the issue
from nimbus-eth2.
pinebit
commented on July 18, 2024
The specific errors we saw is similar (if not identical) to the origin description:
WRN 2024-05-28 13:25:19.254+00:00 Could not obtain blinded execution payload header topics="beacval" error="Unable to decode Deneb blinded header: Serialization error with HTTP status 204, Content-Type <missing> and content @[]" slot=138 validator_index=173 head=c8980f7d:137
NTC 2024-05-28 13:25:19.255+00:00 Payload builder error topics="beacval" slot=138 head=c8980f7d:137 validator=9592c95f err="Unable to decode Deneb blinded header: Serialization error with HTTP status 204, Content-Type <missing> and content @[]"
WRN 2024-05-28 13:25:19.279+00:00 Block failed validation topics="beacval" blockRoot=00000000 blck="(slot: 138, proposer_index: 173, parent_root: \"c8980f7d\", state_root: \"a36af555\", eth1data: (deposit_root: d70a234731285c6804c2a4f56711ddb8c82c99740f207854891028af34e27e5e, deposit_count: 0, block_hash: 1491705c0bc212c9be1c15f33c39cc6f6fdf58358d37040299770921e5d495ea), graffiti: \"charon/v1.1.0-dev-ddb95fd\", proposer_slashings_len: 0, attester_slashings_len: 0, attestations_len: 1, deposits_len: 0, voluntary_exits_len: 0, sync_committee_participants: 512, block_number: 78, block_hash: \"0x5d573185b1a5a78af8b4483a64ad8013e8ec746e3a89de8fd31c215e002a3aa5\", parent_hash: \"0x14ed1972d36be2d0960942e86eb2035f864c1e2706fe9d25ab5c1e2b690949f0\", fee_recipient: \"0x8943545177806ed17b9f23f0a21ee5948ecaa776\", bls_to_execution_changes_len: 0, blob_kzg_commitments_len: 0)" signature=b9c904e6 error="(Reject, \"BeaconBlock: Invalid proposer signature\")"
We (at Obol) use Nimbus in mainnet with no issues. Therefore we concluded the issue above is related to Kurtosis. We intensively use Kurtosis for testing our product (Charon DV) compatibility against various BN/VC combinations from different vendors. Other vendors (Lighthouse, Teku, Lodestar, Prysm) work just fine, but not Nimbus. Therefore we suspect a bug in Nimbus that only affects Kurtosis environment in some way.
I was trying to build the mentioned unstable branch to a local docker image, but the provided scripts failed to build for any target arch. For example, on MacOS ARM64 host:
What's Next?
View a summary of image vulnerabilities and recommendations → docker scout quickview
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
==================STARTING BUILD==================
Build Tools = 0
PLATFORM=Linux_amd64
Building: Nim compiler
make[2]: *** [vendor/nimbus-build-system/makefiles/targets.mk:81: build-nim] Error 126
make[1]: *** [vendor/nimbus-build-system/makefiles/targets.mk:124: vendor/nimbus-build-system/vendor/Nim/bin/nim] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [vendor/nimbus-build-system/makefiles/targets.mk:116: update-common] Error 2
make: *** [dist-amd64] Error 2
And docker says the builder image is running as AMD64 under Rosetta. I quickly checked the build script and did not find any obvious switches to change this behavior. I also tried to build AMD64 target platform but not successful, having the same errors.
from nimbus-eth2.
nflaig
commented on July 18, 2024
Did some more testing, if I force Lodestar to use JSON body to submit the block to publishBlockV2 the error is gone
participants:
- el_type: geth
el_image: ethereum/client-go:stable
cl_type: lodestar
cl_image: nflaig/lodestar:ssz-api-json-publish
vc_type: nimbus
vc_image: statusim/nimbus-validator-client:amd64-latest
count: 2
- el_type: geth
el_image: ethereum/client-go:stable
cl_type: nimbus
cl_image: statusim/nimbus-eth2:amd64-latest
vc_type: lodestar
vc_image: nflaig/lodestar:ssz-api-json-publish
count: 2
# ...Running this setup, passed block production assertions, the chain finalized and no missed proposals.
from nimbus-eth2.
pinebit
commented on July 18, 2024
Great, I just did the same for our Charon DV by setting https://github.com/attestantio/go-eth2-client/blob/e02b07f2405232b26018a50a25d9fcd9ed75c205/http/parameters.go#L100 (because we use go-eth2-client. And this seem helped.
Leaving this for Nimbus team to investigate why this is happening.
from nimbus-eth2.
Related Issues (20)
- Nimbus CL < > Prysm VC incompatibility HOT 3
- Nimbus CL < > Lodestar VC incompatibility HOT 4
- Handle 404 errors in getAggregatedAttestation response HOT 1
- The debug REST API is not serving recent states (less than 2 days old) HOT 6
- Checkpoint-synced nodes appear to not use ERA files HOT 2
- Error: Unhandled exception: Asynchronous task [sendMessageSlow() at pubsubpeer.nim:301] was cancelled! [FutureDefect] HOT 8
- Release tarballs missing vendor folder
- Single command for beacon node and checkpoint sync. Remove separate command for `trustedNodeSync` HOT 3
- Require flag when resuming from past-weak-subjectivity database / genesis HOT 1
- build error: incompatible pointer type HOT 5
- Check conten-type and return 415 if not supported by route HOT 7
- Beacon node's P2P degrades permanently after 40 minutes of no connectivity HOT 8
- Bug: Error build with cmd "make -jX nimbus_beacon_node" HOT 11
- Compilation error when "import libp2p/multicodec" is added to sync_manager.nim HOT 12
- Checkpoint sync fails with "Attempt to download checkpoint state timed out" on holesky on all endpoints HOT 7
- [SEC]
- Can no longer use systemd's MemoryDenyWriteExecute on nimbus-beacon-node 24.6.0 HOT 2
- 8GB need for compilation HOT 1
- nimbus spontanously crashes with "database disk image is malformed" HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nimbus-eth2.