The way the privateKey is loaded has been updated. The new implementation:
Still supports specifying the privateKey on the config file. This is for backwards compatibility and for ease of development. A warning to the console is printed if this method is used.
If no privateKey configuration is specified, the privateKey is loaded from the environment variable RELAYER_PRIVATE_KEY using the envprivateKeyloader. (The variable name is customizable for advanced users.)
Custom privateKeyloaders may be implemented (configured via global.privateKey.loader). This boils down to implementing a class with an async function that returns a privateKey as a hex string. The returned privateKey format is validated to avoid hard to debug implementation errors.
The way the
privateKeyis loaded has been updated. The new implementation:privateKeyon the config file. This is for backwards compatibility and for ease of development. A warning to the console is printed if this method is used.privateKeyconfiguration is specified, theprivateKeyis loaded from the environment variableRELAYER_PRIVATE_KEYusing theenvprivateKeyloader. (The variable name is customizable for advanced users.)privateKeyloaders may be implemented (configured viaglobal.privateKey.loader). This boils down to implementing a class with an async function that returns aprivateKeyas a hex string. The returnedprivateKeyformat is validated to avoid hard to debug implementation errors.