Vector v0.0.40

Specifying chainAddresses in node.config.json is now optional for public networks

This release deeply incorporates hardhat-deploy into our ops & publishes this deployment data in our @connext/vector-contracts npm package. This means the server-node and browser-node will check this deployment data for chainAddresses and use these if none were explicitly provided.

This change is backwards compatible, you can still provide chainAddresses if you like. And for local networks or new chains that aren't formally supported yet, you would still need to explicitly provide addresses.

Changelog

• Overhauled contract ops to utilize hardhat-deploy

Artifacts

NPM

npm i @connext/vector-{browser-node,types,utils,contracts}@0.0.40

Docker

docker pull connextproject/vector_{router,node,iframe-app}:0.0.40