From a98333d708f4b0bec16ddec29a72e3f502206505 Mon Sep 17 00:00:00 2001 From: Al3xGROS Date: Wed, 10 Apr 2024 10:54:23 +0200 Subject: [PATCH] docs: update README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3b6cf9c7..2eb011a9 100644 --- a/README.md +++ b/README.md @@ -195,7 +195,7 @@ The relayer is configured via a JSON file, the path to which is passed in via th `"supported-destinations": []SupportedDestination` - - List of destinations that the source blockchain supports. Each `SupportedDestination` consists of a destination blockchain ID (`"blockchain-id"`), and a list of addresses (`"addresses"`) on that destination blockchain that the relayer supports delivering Warp messages to. The destination address is defined by the message protocol. For example, it could be the address called from the message protocol contract. If no supported addresses are provided, all addresses are allowed on that blockchain. If `supported-destinations` is empty, then all destination blockchains (and therefore all addresses on those destination blockchains) are supported. + - List of destinations that the source blockchain supports. Each `SupportedDestination` consists of a cb58-encoded destination blockchain ID (`"blockchain-id"`), and a list of hex-encoded addresses (`"addresses"`) on that destination blockchain that the relayer supports delivering Warp messages to. The destination address is defined by the message protocol. For example, it could be the address called from the message protocol contract. If no supported addresses are provided, all addresses are allowed on that blockchain. If `supported-destinations` is empty, then all destination blockchains (and therefore all addresses on those destination blockchains) are supported. `"process-historical-blocks-from-height": unsigned integer`