Skip to content
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

[FEAT] Add new config parameter to set batch-size for registration validators on relays #226

Closed
blevkivskyi-everstake opened this issue Jan 9, 2025 · 1 comment · Fixed by #244

Comments

@blevkivskyi-everstake
Copy link

To improve performance when dealing with a high number of keys, we propose adding a new configuration parameter to the mux config like lighthouse validator.

A error when sending a large number of keys to a relay will be fixed::

HTTP error response: 413 / Failed to buffer the request body: length limit exceeded
@ank-everstake
Copy link

Example flow:

5000 keys on VC(validator client)
1 beacon node (BN)
3 relays
    1000 allowed validator keys to use #x relay
    1000 allowed validator keys to use #y relay
    3000 allowed validator keys to use #z relay

batch_size for relays
    100  #x relay
    200  #y relay
    1000 #z relay


Beacon node   requests to register 5000 keys
commit-boost  receives 5000 keys
commit-boost  makes requests to relays in batches
    10 requests*100 keys to #x relay
    5   requests*200 keys to #y relay
    3 requests*1000 keys to #z relay

Possibly we will also ask to rate-limit misbehaving VC(such as Lighthouse) that sends requests for registrations for each slot rather than each epoch.
Maybe under separate flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants