The Merge brings changes to the JSON-RPC API. Such as the Engine API, JWT authentication, additional RPC ports, and additional block tags.
The Engine API adds new endpoints that allow the execution layer client to receive messages from the consensus layer client.
8551is the default port that Engine API communicates with the CL on.
JWT Authentication is used on all ports with the
EngineAPI Module enabled.
JSON Web Token authentication was added to the JSON-RPC API for security reasons to ensure that nothing interferes with the communication between the Nethermind and the Consensus client. This requires you to create a
.txtfile containing a hexadecimal “secret” that will be passed to each client.
Nethermind will create its own
jwtsecretfile if you do not specify a location or pass the wrong location.
To create this “Secret File” use the following command.
openssl rand -hex 32 | tr -d "\n" > "/tmp/jwtsecret"
"/tmp/jwtsecret"will be the file path and name when created.
If you do not want to install OpenSSL, you may use a random hex generator website. All you need is a 64 character hex string saved to a
We strongly recommend you use OpenSSL to generate the secret locally because it is more secure
The merge also adds new configuration options such as:
Some requests on the JSON-RPC API require a block tag for additional context. Previously there were three block tags
pending. The Merge adds an additional two tags