safe-global/safe-config-service v1.4.0

Safe Config Service 1.4.0

on GitHub

Changes to /chains endpoint (work in progress)

• RPC URIs are no longer represented by a single string/uri. Each RPC is now an object that specifies the authentication mechanism for that RPC (#172). The possible values are:
  • API_KEY_PATH – if an API key should be added to the base path of the the RPC (rpcUri.value)
  • NO_AUTHENTICATION – if not authentication is required to use this RPC URI (rpcUri.value can be used as is)

GET /api/v1/chains/<chain_id>

{
  ...
  "rpcUri": {
    "authentication": <"API_KEY_PATH" | "NO_AUTHENTICATION">,
    "value": <stringified-uri>,
  }
}

• A different RPC url can be set as an alternative to be used by safe-apps on a specific chain (#169) – it follows the same object structure as rpcUri and can be accessed via safeAppsRpcUri

• A new object for representing a block explorer was added. This new object has fields for address and txHash templates. These templates can then be used by the clients to correctly create the final block explorer url that targets either an address or txHash (#176)

GET /v1/chains/<chain_id>/

{
  ...
  blockExplorerUriTemplate: {
    "address": <string>, // eg.: https://etherscan.io/address/{{address}}
    "txHash": <string> // eg.: https://etherscan.io/tx/{{txHash}}
  }
}

Other changes

• Fix script to run commands inside container (#170)
• Bump gnosis-py from 3.1.13 to 3.1.14 (#174)
• Fix migration reverse lambda args (#175)
• Bump coveralls from 3.1.0 to 3.2.0 (#178)
• Set execution permission on docker entrypoint (#177)