hexstrings created that aren't padded but then used as byte32

[audiusproject]

hexstrings created that aren't padded but then used as byte32

[fxfactorial]

I'm sure that it did pass for some -

here is one error for example

rror: invalid bytes32 value (arg="", coderType="bytes32", value="0x476f7665726e616e6365", version=4.0.48)
    at Object.throwError (/home/edgar/Repos/audius-protocol/eth-contracts/node_modules/ethers/errors.js:76:17)
    at CoderFixedBytes.encode (/home/edgar/Repos/audius-protocol/eth-contracts/node_modules/ethers/utils/abi-coder.js:473:20)
    at /home/edgar/Repos/audius-protocol/eth-contracts/node_modules/ethers/utils/abi-coder.js:645:59

So i think this indeterminism is because the package.json doesn't explicitly pick a version of web3 and ethers & I used yarn which ignores the package-lock.json + diff version of node.

So probably easiest for now, lock in a version of web3 + ethers that you use in package.json so everything is reproducible

[hareeshnagaraj]

We have successfully run migrations agaainst ganache, ropsten and mainnet ethereum structured as is and things seem to be working. All registry keys are are initialized as expected. What error have you been seeing?

[hareeshnagaraj]

great point! we should absolutely be fixing versions in order to guarantee it to work

[dmanjunath]

Closing stale issue