From b4d36fc2e94a39b733d0e515d2069c256b40eea5 Mon Sep 17 00:00:00 2001 From: igor Date: Thu, 14 Jul 2022 18:03:28 +0200 Subject: [PATCH] fixed missing redundant square bracket --- aqua-examples/decentralized-blockchain-gateway/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aqua-examples/decentralized-blockchain-gateway/README.md b/aqua-examples/decentralized-blockchain-gateway/README.md index 49d9aec..cc9f997 100644 --- a/aqua-examples/decentralized-blockchain-gateway/README.md +++ b/aqua-examples/decentralized-blockchain-gateway/README.md @@ -876,7 +876,7 @@ Since IPFS makes all data public and actually encrypting and eventually decrypti * [service addresses](./parameters/service_addrs.json) * [quorum service address](./parameters/quorum_addrs.json) -* [utility service address](./parameters/utility_addrs.json]) +* [utility service address](./parameters/utility_addrs.json) Matching service granularity to IPFS document content may make sense if we want to minimize updates due to service changes. However, we could have as easily put all the function addresses into one IPFS file. Regardless, let push our content to IPFS.