Is your feature request related to a problem? Please describe.
After the merge, connecting several beacon-chains to one execution clients can provoke a bad performance of the execution client and provoke unexpected behaviour of the beacon chain nodes.
Describe the solution you'd like
We will use a different JWT token for every consensus client, in the execution clients we will add a new en var where the user has to select what consensus client will use this execution client, then depending on what client is selected the execution client will use a specific jwt.
tropicar
commented
2 years ago
Is your feature request related to a problem? Please describe.
After the merge, connecting several beacon-chains to one execution clients can provoke a bad performance of the execution client and provoke unexpected behaviour of the beacon chain nodes.
Describe the solution you'd like
We will use a different JWT token for every consensus client, in the execution clients we will add a new en var where the user has to select what consensus client will use this execution client, then depending on what client is selected the execution client will use a specific jwt.