Create a library language-agnostic to contain metadata shared accross staker agents

[pablomendezroyo]

Staker agents (such as staker packages, dappmanager and dappnodesdk) have the following hardcoded metadata. Would be interesting to have a single point of data and then use it where needed. Consider using a universal data format like JSON.

• Common stakers metadata used across different repositories:

  • Execution clients:
    • JWT from Consensus clients. i.e https://github.com/dappnode/DAppNodePackage-geth/blob/97b7bca31202d5393b444988cd975a768c54f299/entrypoint.sh#L3 and https://github.com/dappnode/DAppNodePackage-geth/blob/master/security/lighthouse/jwtsecret.hex
  • Consesnsus client - validator:
    • web3signer url (depends on the network): https://github.com/dappnode/DAppNodePackage-teku-prater/blob/899184c34d8cd7f36648066c5da106f87fd842e1/validator/entrypoint.sh#L5
    • mev boost url (depends on network): https://github.com/dappnode/DAppNodePackage-teku-prater/blob/899184c34d8cd7f36648066c5da106f87fd842e1/validator/entrypoint.sh#L10
  • Consensus client - beacon:
    • Execution client HTTP engine. i.e https://github.com/dappnode/DAppNodePackage-teku-prater/blob/899184c34d8cd7f36648066c5da106f87fd842e1/beacon-chain/entrypoint.sh#L9
    • mev boost url (depends on network): https://github.com/dappnode/DAppNodePackage-teku-prater/blob/899184c34d8cd7f36648066c5da106f87fd842e1/beacon-chain/entrypoint.sh#L29
  • Web3signer:
    • web3signer url (depends on the network)
    • mev boost url
    • Consensus client DNS
    • Consensus client beacon node API
    • Consensus client validator node API
    • Consensus client validator token bearer

• The JSON format of the library might have the following format

{
  "mainnet": {
    "executionClients": {
      "geth.dnp.dappnode.eth": {
        "engineApi": "http://get.dappnode:8545"
      },
      ...
    },
    "consensusClients": {
      "prysm.dnp.dappnode.eth": {
        "beacon": { 
          "api": "http://prysm.beacon-chain.dappnode:3500",
          "jwt": "7ad9cfdec75eceb662f5e48f5765701c17f51a5233a60fbcfa5f9e495fa99d19"
        },
        "validator": {
          "keystoresApi": "http://prysm.validator.dappnode:3500",
          "authToken": "b5bbbaf533b625a93741978857f13d7adeca58445a1fb00ecf3373420b92776c
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.e30.MxwOozSH-TLbW_XKepjyYDHm2IT8Ki0tD3AHuajfNMg",
        }
      },
      ...
    },
    "signer": {
      "keystoreApi": "http://web3signer.dappnode:9000"
    },
    "mevBoost": {
      "builderApi": "http://mev-boost.dappnode:18550"
    }
  }
}

• This library could be used in:

  • dappnode packages entrypoints
  • dappmanager
  • sdk
  • ?

• This library must have a release section

Another interesting approach would be to distribute a binary that with a given input returns all the specs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!