It was using net_version, but it should be using the eth_chainId method introduced in EIP-695. I'm not sure whether/how the network ID differs from the chain ID on mainnet and the testnets, but in Ganache in particular, the network ID is 50 while the chain ID is 1337, and this difference was causing problems for Python tests. Specifically, the Web3.py interface `Web3.eth.chainId` invokes the eth_chainId method, and the result feeds into the order hash, which wasn't lining up with the non-Python side of things.
Deployed Contract Packages
Contract | Package | Version | Git Tag |
---|---|---|---|
AssetProxyOwner | @0x/contracts-multisig |
v1.0.2 | @0x/contracts-multisig@1.0.2 |
ERC20Proxy | @0x/contracts-asset-proxy |
v1.0.1 | @0x/contracts-asset-proxy@1.0.1 |
ERC721Proxy | @0x/contracts-asset-proxy |
v1.0.1 | @0x/contracts-asset-proxy@1.0.1 |
Exchange | @0x/contracts-exchange |
v1.0.1 | @0x/contracts-exchange@1.0.1 |
DutchAuction | @0x/contracts-extensions |
v1.0.2 | @0x/contracts-extensions@1.0.2 |
Forwarder | @0x/contracts-exchange-forwarder |
v1.0.1 | @0x/contracts-exchange-forwarder@1.0.1 |
MultiAssetProxy | @0x/contracts-asset-proxy |
v1.0.1 | @0x/contracts-asset-proxy@1.0.1 |
ZRXToken | @0x/contracts-erc20 |
v1.0.1 | @0x/contracts-erc20@1.0.1 |
Development
Building solidity files will update the contract artifact in {package-name}/generated-artifacts/{contract}.json
, but does not automatically update the abi-gen-wrappers
package, which are generated from the artifact JSON. To ensure consistency, clean and rebuild abi-gen-wrappers
after any changes to the artifact JSON.