New contract ABI files from truffle migration 11_update_claim_holder_library.js

[franckc]

First pull request? Read our guide to contributing

Checklist:

• [ ] Code contains relevant tests for the problem you are solving
• [ ] Ensure all new and existing tests pass
• [ ] Update any relevant READMEs and docs

Description:

Ran truffle migration 11_update_claim_holder_library.js from PR #598 on both Rinkeby and Mainnet by running the commands:

export INFURA_ACCESS_TOKEN=<...>
export RINKEBY_MNEMONIC=<...>
npx truffle migrate --network rinkeby
unset RINKEBY_MNEMONIC
export MAINNET_PRIVATE_KEY=<....>
npx truffle migrate --network mainnet

The output of the runs was capturing in the 0.8.4_rinkeby.log and 0.8.4_mainnet.log log files.

I checked the json files to make sure only the address of ClaimHolderLibrary had changed compared to version 0.8.1 (previous deploy of contracts).

$ cd contracts/release/0.8.4/build/contracts
$ for f in `ls *.json`; do
   diff $f ../../../0.8.1/build/contracts/$f
 done > out
$ grep \"address\": out
<       "address": "0x79b152da4ad8fb774700639bed68a965b0440644",
>       "address": "0x1fe0b698b02bbc7fc7029ee1fc15885389b53067",
<       "address": "0x75601c2dc926b0e3ce41b1ae719290c62aba978e",
>       "address": "0x6b022e55864bb884d1bddc87ae741b7266153169",

As next steps after merging this PR in staging branch, I'm planning on:

• deploying the DApp to staging for testing
• making a new npm origin v0.8.4, publish it, then deploy DApp prod