-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepared Capella beacon block is blinded
when requesting a full block
#12950
Comments
It's a misconfiguration
also tangentially related :#12103 |
aware of the issue, will address as we clean up the api. closing for now |
Reopening the issue. The |
@michaelsproul, the latest prysm develop branch should have this issue fixed. |
Fantastic, thanks! This wasn't something I ran into personally, but I'll let you know if I see any more reports! |
Hey @james-prysm, this is currently reproducing in hive when I changed the prysm validator client to switch to use the rest API of prysm beacon node:
Then the builder is unable to build anything throughout the entire epoch. These are the parameters I'm currently using: prysm beacon node: --verbosity=trace
--accept-terms-of-use=true
--datadir=/data/beacon
--chain-config-file=/hive/input/config.yaml
--genesis-state=/hive/input/genesis.ssz
--p2p-tcp-port=900
--p2p-udp-port=9000
--p2p-host-ip=172.19.0.5
--p2p-local-ip=172.19.0.5
--execution-endpoint=http://172.19.0.3:8551
--jwt-secret=/jwtsecret
--min-sync-peers=1
--subscribe-all-subnets=true
--enable-debug-rpc-endpoints=true
--disable-monitoring=false
--monitoring-host=0.0.0.0
--monitoring-port=8080
--http-mev-relay=http://0x95fde78acd5f6886ddaf5d0056610167c513d09c1c0efabbc7cdcc69beea113779c4a81e2d24daafc5387dbf6ac5fe48@172.19.0.3:18550
--deposit-contract=0x4242424242424242424242424242424242424242
--contract-deployment-block=0
--rpc-host=0.0.0.0
--rpc-port=4001
--grpc-gateway-host=0.0.0.0
--grpc-gateway-port=4000
--grpc-gateway-corsdomain=*
--suggested-fee-recipient=0xa94f5374Fce5edBC8E2a8697C15331677e6EbF0B validator client:
This is on |
Hi @marioevz , the initial issue was related to the |
Thanks @rkapka, let me run with these changes to see if anything changes 👍 |
@marioevz I'm glad to hear this. Closing. |
Describe the bug
We (Lighthouse) received a report on Discord of a failed proposal due this error being returned from the
/eth/v2/beacon/blocks
endpoint:This is a Lighthouse VC connected to a Prysm BN, and the inner error
Prepared Capella beacon block is blinded
comes from the Prysm BN. I don't understand what this means, because on this code path the Lighthouse VC is definitely hitting the/eth/v2/beacon/blocks
endpoint. Is this the result of a misconfiguration where the Prysm BN wants to use a builder, and therefore can't build local blocks? Or is this likely related to the recent Geth block-building bug?Has this worked before in a previous version?
No response
🔬 Minimal Reproduction
No response
Error
No response
Platform(s)
No response
What version of Prysm are you running? (Which release)
No response
Anything else relevant (validator index / public key)?
No response
The text was updated successfully, but these errors were encountered: