v9.4.0

Features ✅

• Improved the performance of validating order filters in the browser #809.

v9.3.0

Features ✅

• Mesh now ensures on startup that the chain ID of your Ethereum RPC endpoint matches config.EthereumChainID #733.

Bug fixes 🐞

• Fixed a compatibility issue in @0x/mesh-browser-lite for Safari and some other browsers #770.
• Fixes an issue that would allow expired orders to be returned in GetOrders 773
• Fixed a rare bug where ERC721 approval events could be missed #782

v9.2.1

Bug fixes 🐞

• Fixed a critical bug in the ordersync protocol which resulted in only 50% of existing orders being shared when a new peer joins the network. New orders are shared separately and were unaffected. #760.

v9.2.0

Features ✅

• Greatly reduced latency for propagating orders, especially for browser nodes #756.
• Added support for checkGasPrice StaticCall asset data #744

v9.1.0

Features ✅

• Improved speed and efficiency of peer discovery, especially when using custom order filters #729.
• Added a lightweight package to use for loading Mesh's Wasm binary in a streaming manner #707.

Bug fixes 🐞

• Fixed an issue where incoming orders could sometimes be dropped by peers #732.

v9.0.1

Bug fixes 🐞

• Fix bug where we weren't enforcing that we never store more than miniHeaderRetentionLimit block headers in the DB. This caused issue #667 and also caused the Mesh node's DB storage to continuously grow over time. (#716)

v9.0.0

Breaking changes 🛠

• As a result of implementing custom order filters, some of the code Mesh uses under the hood to share orders with peers has changed. As a result this version of Mesh cannot share orders with any older versions and vice versa (#630).
• Implemented a new protocol for sharing existing orders with peers. This will drastically reduce bandwidth and CPU usage and increase the speed at which new orders are propagated. (#692).
• Rename RPC_ADDR to WS_RPC_ADDR since we now support both WS and HTTP JSON-RPC endpoints. (#658)

Features ✅

• Implemented custom order filters, which allow users to filter out all but the orders they care about. When a custom order filter is specified, Mesh will only send and receive orders that pass the filter. (#630).
• Developers can now override the contract addresses for any testnet using the CUSTOM_CONTRACT_ADDRESSES env config (#640).
• Added getOrdersForPageAsync method to @0x/mesh-rpc-client WS client interface so that clients can paginate through the retrieved orders themselves (#642).
• Added support for passing in your own Web3 provider when using the @0x/mesh-browser package. (#665).
• Add support for orders involving Chai ERC20Bridge assetData (#663)
• Add support for calling JSON-RPC methods over HTTP (env config HTTP_RPC_ADDR defaults to localhost:60556). (#658)

Bug fixes 🐞

• Fixed some of the browser typescript bindings to be consistent with the Go and smart contract implementations (#697).

v7.1.0-beta-0xV3

• Update V3 contract addresses for mainnet/testnets. (#547)

Features ✅

• Added support for persistence in the browser. Users of the @0x/mesh-browser package will now be able to retain orders and other relevant parts of the state when refreshing the page or closing and re-opening the browser. (#533).

Bug fixes 🐞

• Fix bug where Mesh nodes were logging receipt and re-sharing with peers duplicate orders already stored in it's DB, if the duplicate order was submitted via JSON-RPC. (#529)
• Add missing UNEXPIRED OrderEventEndState enum value to both @0x/mesh-rpc-client and @0x/mesh-browser and missing STOPPED_WATCHING value from @0x/mesh-rpc-client.
• Fixed a potential memory leak by using the latest version of github.com/libp2p/go-libp2p-kad-dht (#539).
• Changed the default port for RPC_ADDR from a random available port to 60557. Some documentation already assumed 60557 was the default port. Now all documentation has been updated for consistency with this change. (#542).
• Fixed a potential nil pointer exception in log hooks (#543).
• Fixed a bug where successful closes of an rpc subscription were being reported as errors (#544).
• We now log the error and stack trace if an RPC method panics. Before, these errors were swallowed by the panic recovery logic in go-ethereum's rpc package. (#545)
• Previously, we used to fast-sync block events missed since a Mesh node was last online. If this was more than 128 blocks ago, the fast-sync would fail if Mesh was not connected to an Ethereum node with the --archive flag enabled. We now fast-sync only if less than 128 blocks have elapsed. Otherwise, we simply re-validate all orders and continue processing block events from the latest block. (#407)