james-prysm d35d65625f stateless block v4 (#16699) ...

**What type of PR is this?**

Feature

**What does this PR do? Why is it needed?**

Introduces a stateless mode for validator client using getBlockv4 with
payload included in response

```
participants_matrix:
  el:
    - el_type: geth
      el_image: ethpandaops/geth:glamsterdam-devnet-0
  cl:
    - cl_type: prysm
      cl_image: gcr.io/offchainlabs/prysm/beacon-chain:latest
      vc_image: gcr.io/offchainlabs/prysm/validator:latest
      vc_extra_params:
        - --enable-beacon-rest-api
        - --enable-stateless
        - --verbosity=debug
      cl_extra_params:
        - --verbosity=debug
    - cl_type: lodestar
      cl_image: ethpandaops/lodestar:glamsterdam-devnet-0
    - cl_type: lighthouse
      cl_image: ethpandaops/lighthouse:glamsterdam-devnet-0
  count: 2

network_params:
  gloas_fork_epoch: 1
  seconds_per_slot: 4
  withdrawal_type: "0x01"
  validator_balance: 40000
  num_validator_keys_per_node: 1000

additional_services:
  - dora
  - assertoor
  - spamoor
  - checkpointz
spamoor_params:
  image: ethpandaops/spamoor:master
  

assertoor_params:
  run_stability_check: false
  run_block_proposal_check: false
  tests:
    - { file: "https://raw.githubusercontent.com/ethpandaops/assertoor/refs/heads/master/playbooks/gloas-dev/builder-lifecycle.yaml" }

snooper_enabled: false
global_log_level: debug

port_publisher:
  additional_services:
    enabled: true


checkpointz_params:
  image: ethpandaops/checkpointz:gloas-latest

docker_cache_params:
  enabled: false

```

needs https://github.com/OffchainLabs/prysm/pull/16705

**Which issues(s) does this PR fix?**

related to https://github.com/ethereum/beacon-APIs/pull/580

**Other notes for review**

**Acknowledgements**

- [x] I have read
[CONTRIBUTING.md](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md).
- [x] I have included a uniquely named [changelog fragment
file](https://github.com/prysmaticlabs/prysm/blob/develop/CONTRIBUTING.md#maintaining-changelogmd).
- [x] I have added a description with sufficient context for reviewers
to understand this PR.
- [x] I have tested that my changes work as expected and I added a
testing plan to the PR description (if applicable).

---------

Co-authored-by: james-prysm <jhe@offchainlabs.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-01 13:43:35 +00:00

22 KiB

Raw Permalink Blame History

View Raw