From 8e90e9b52ed0a6ec7f1570cf4b5f4c03dafcd41d Mon Sep 17 00:00:00 2001 From: Manuel Montenegro Date: Tue, 19 Sep 2023 11:36:19 +0200 Subject: [PATCH] Apply PR suggestions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: David Núñez --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 19b312b2..2da3e6e9 100644 --- a/README.md +++ b/README.md @@ -71,15 +71,15 @@ $ ape networks list ## NPM publishing process -When a new smart contract is deployed it is needed to add to NPM package: +For interoperability, we keep an NPM package with information of deployed smart contracts, such as address, ABI, etc. -https://www.npmjs.com/package/@nucypher/nucypher-contracts +The NPM package can be found in https://www.npmjs.com/package/@nucypher/nucypher-contracts and the process to update it is as follows: -1. Download the last version of the package in a separated folder. Ropsten versions end in -`-ropsten`. +1. Download the last version of the package in a separate folder. Testnet versions end in +`-` (e.g., `-goerli`). ```bash - $ npm i @nucypher/nucypher-contracts@x.y.z[-ropsten] + $ npm i @nucypher/nucypher-contracts@x.y.z[-] ``` 2. Copy the `artifacts` folder and paste it into the nucypher-contracts local repository. Only the files that we want to be uploaded must be kept.