CHANGELOG
This changelog is a work in progress and may contain notes for versions which have not actually been released. Check the Releases page to see full release notes and more information about the latest released versions.
- Fixed
database is closedissues related to ourgo-sqlite3databases. - Fixed a bug that would cause the node to crash when receving log events for tokens that do not conform to the ERC20 specification.
- Fixed a data race condition in
OrderWatcher. - Fixed an issue with slow
OrderEventsubscribers blocking handling of messages.
- Added the ability for ordersync requestors to track the progress of individual ordersync connections in case connection is broken temporarily. #877
- Fixes a bug that would cause Mesh nodes to crash upon receiving requests from legacy Mesh nodes #888.
- Fixed a problem in the filtered pagination subprotocols of ordersync that caused the nodes to use the wrong orderfilter #882
- Mesh now ensures on startup that the chain ID of your Ethereum RPC endpoint matches config.EthereumChainID #733.
- 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.
- Fix bug where we weren't enforcing that we never store more than
miniHeaderRetentionLimitblock headers in the DB. This caused issue #667 and also caused the Mesh node's DB storage to continuously grow over time. (#716)
- 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).
- 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_ADDRESSESenv config (#640). - Added
getOrdersForPageAsyncmethod to@0x/mesh-rpc-clientWS 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-browserpackage. (#665). - Add support for calling JSON-RPC methods over HTTP (env config
HTTP_RPC_ADDRdefaults tolocalhost:60556). (#658)
- Fixed some of the browser typescript bindings to be consistent with the Go and smart contract implementations (#697).
- Reduced startup time for Mesh node by only waiting for a block to be processed if Mesh isn't already sync'ed up to the latest block. (#622)
- Changed the response from
@0x/mesh-ts-client'sgetOrdersAsyncendpoint to include thesnapshotIDandsnapshotTimestampat which the Mesh DB was queried along with the orders found. (#591)
- Instead of progressing Mesh forward by a single block on every invocation of the
BLOCK_POLLING_INTERVAL, we now attempt to sync as many blocks as necessary to reach the latest block available. This will reduce the chances of Mesh becoming out-of-sync with it's backing Ethereum node (#564) - Added a new environment variable
ENABLE_ETHEREUM_RPC_RATE_LIMITINGand config optionenableEthereumRPCRateLimitingwhich can be used to completely disable Mesh's internal Ethereum RPC rate limiting features. By default it is enabled, and disabling can have some consequences depending on your RPC provider. (#584) - Added a
SnapshotTimestampfield toGetOrdersResponse, the return type of themesh_getOrdersRPC method. This way, the caller can know at what point in time the snapshot had been created. (#591)
- Fixed an issue where order updates could have been missed if Mesh discovered blocks but didn't have time to process them before getting shut down. Now, blocks are only persisted to the DB once any order updates resulting from it have been processed. (#566).
- Fixed a race-condition when adding new orders to Mesh which could result in order-relevant events being missed if they occured very soon after the order was submitted and the order validation RPC call took a long time (#566).
- Upgraded the
web3-providerdependency used by@0x/mesh-rpc-clientin order to fix a bug where it was requiring eitherprocessORwindowto exist in the global scope (#601). - Fixed an issue where the internal Ethereum RPC rate limiter could be too aggressive in certain scenarios (#596).
- Add a default RPC request timeout of 30sec to all non-subscription requests sent by
@0x/mesh-rpc-clientto avoid the client from hanging endlessly if it misses a response due to network disruption (#603).
- Fixed a bug where
makerAssetFeeDataortakerAssetFeeDatawere sometimes being set to an empty string instead of0xin the browser (#579).
- Fixed a bug which could cause Mesh to crash with a nil pointer exception if RPC requests are sent too quickly during/immediately after start up (#560).
- Fixed a bug where the internal order event feed could be come blocked, rendering Mesh unable to receive any new orders or update existing ones (#552).
- Added support for persistence in the browser. Users of the
@0x/mesh-browserpackage 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).
- 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
UNEXPIREDOrderEventEndStateenum value to both@0x/mesh-rpc-clientand@0x/mesh-browserand missingSTOPPED_WATCHINGvalue 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_ADDRfrom a random available port to60557. Some documentation already assumed60557was the default port. Now all documentation has been updated for consistency with this change. (#542). - 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'srpcpackage. (#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
--archiveflag 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)
- Upgraded
@0xdeps in@0x/mesh-rpc-client
- Fixed an oversight which granted immunity from bandwidth banning for any peer using a relayed connection (#509).
- Fixed a typo in the
@0x/mesh-browserpackage that resulted in some config options not being passed through correctly (#502). - Fixed a bug in ETH JSON-RPC rate limiter where not all dates were being properly converted to UTC, causing Mesh to malfunction if the local time was a day earlier or later than UTC. (#505)
Note: This release will require wiping your Mesh's DB before upgrading. The DB location defaults to
./0x_mesh/db.- Removed
RPC_PORTenvironment variable. The newRPC_ADDRenvironment variable allows specifying both the interface and port (#487). - Due to security concerns and new rate limiting mechanisms, the default bind address for the RPC API has changed from
0.0.0.0tolocalhost. Users who previously did not setRPC_PORTmay need to now manually setRPC_ADDRto enable other applications to access the RPC API. If you are using Docker Compose, we recommend using links. If you do need to setRPC_ADDRto bind on0.0.0.0, please be aware of the security implications and consider protecting access to Mesh via a third-party firewall. (See #444 and #487 for more details). - Changed the
EXPIREDevent such that it is emitted when an order is expired according to the latest block timestamp, not anymore based on UTC time. (#490) - Removed the
EXPIRATION_BUFFER_SECONDSenv config since we no longer compute order expiration using UTC time. (#490)
- Added an
UNEXPIREDorder event kind which is emitted for orders that were previously considered expired but due to a block-reorg causing the latest block timestamp to be earlier than the previous latest block timestamp, are no longer expired. (#490) - Added support for decoding Axie Infinity
TransferandApproveERC721 events which differ from the ERC721 standard. (#494)
- Fixed a bug in the Go RPC client which resulted in errors when receving order events with at least one contract event (#496).
- Renamed env config from
ETHEREUM_NETWORK_IDtoETHEREUM_CHAIN_IDsincenetworkis a misnomer here and what we actually care about is thechainID. Most chains have the same id for their p2p network and chain. From the ones we support, the only outlier is Ganache, for which you will now need to supply1337instead of50(Learn more: https://medium.com/@pedrouid/chainid-vs-networkid-how-do-they-differ-on-ethereum-eec2ed41635b) (#485)
- Implemented a new strategy for limiting the amount of database storage used by Mesh and removing orders when the database is full. This strategy involves a dynamically adjusting maximum expiration time. When the database is full, Mesh will enforce a maximum expiration time for all incoming orders and remove any existing orders with an expiration time too far in the future. If conditions change and there is enough space in the database again, the max expiration time will slowly increase. This is a short term solution which solves the immediate issue of finite storage capacities and does a decent job of protecting against spam. We expect to improve and possibly replace it in the future. See #450 for more details.
- Added support for a new feature called "order pinning" (#474). Pinned orders will not be affected by any DDoS prevention or incentive mechanisms (including the new dynamic max expiration time feature) and will always stay in storage until they are no longer fillable. By default, all orders which are submitted via either the JSON-RPC API or the
addOrdersAsyncfunction in the TypeScript bindings will be pinned.
- Improved the aggressiveness at which we permanently delete orders that have been flagged for removal. Previously we would wait for the cleanup job to handle this (once an hour), but that meant many removed orders would accumulate. We now prune them every 5 minutes. (#471)
- The
getStatsRPC endpoint now includes a new field which accounts for the number of orders that have been marked as "removed" but not yet permanently deleted (#461). - Improved historical order sharing using round-robin algorithm instead of random selection (#454). This will reduce the warm-up time for receiving existing orders when first joining the network.
- Added ERC1155 assetData support (#453). This includes order watching and order events for orders involving ERC1155 tokens.
- Added Ability to specify custom contract addresses via the
CUSTOM_ADDRESSESenvironment variable or thecustomAddressesfield in the TypeScript bindings (#445).
- Temporarily disabled bandwidth-based peer banning (#448). A bug in libp2p was occasionally causing observed bandwidth usage to spike to unrealistic levels, which can result in peers being erroneously banned. We decided to temporarily stop banning peers while we're working with the libp2p team to resolve the issue.
- Updated DevUtils.sol contract address for the Kovan network to one including a bug fix for validating orders with nulled out
feeAssetDatafields. (#446])
- Removes the
txHasheskey in theOrderEvents emitted from theordersJSON-RPC subscription and replaced it withcontractEvents, an array of decoded order-relevant contract events. Parsing these events allows callers to find every discrete order fill/cancel event. (#420) - Renames the
Kindkey inOrderEventtoEndStateto better elucidate that it represents the aggregate change to the orders state since it was last re-validated. As an end state, it does not capture any possible intermediate states the order might have been in since the last re-validation. Intermediate states can be inferred from thecontractEventsincluded (#420)
- Removed the max expiration limit for orders. The only remaining expiration constraint is that the unix timestamp does not overflow int64 (i.e., is not larger than 9223372036854775807). (#400)
- Fixed bug where we weren't updating an orders
fillableTakerAssetAmountin the DB when orders were being partially filled or when their fillability increased due to a block re-org. (#439) - Fixed issue where we weren't re-validating orders potentially impacted by the balance increase of the recipient of an ERC20 or ERC721 transfer. (#416)
- Renamed the environment variable
P2P_LISTEN_PORTtoP2P_TCP_PORT(#366). This makes it possible to configure Mesh to use both the TCP and Websocket transports by listening on different ports.
- Created TypeScript bindings and an NPM package for running Mesh directly in the browser (#369). Documentation for the NPM package and a guide for running Mesh in the browser can be found at https://0x-org.gitbook.io/mesh/.
- Added ability to use custom bootstrap list via the
BOOTSTRAP_LISTenvironment variable (#374). Typically this should only be used for testing/debugging. - Refactored
BlockWatchso that it can be used without usingLevelDBfor Ethereum block storage. (#355)
- Fixed two related bugs: One where order expiration events would be emitted multiple times and another that meant subsequent fill/cancel events for orders deemed expired were not emitted. Fills/cancels for expired orders will continue to be emitted if they occur within ~4 mins (i.e. 20 blocks) of the expiration (#385).
- Fixed a data race-condition in OrderWatcher that could have caused order collection updates to be overwritten in the DB. (#386)
- Fixed a bug where
fillableTakerAssetAmountandlastUpdatedwere not always being properly updated in the DB. (#386)
- Fixed bug where block number would sometimes be converted to hex with a leading zero, an invalid hex value per the Ethereum JSON-RPC specification. (#353)
- Fixed bug which resulted in orders that were close to expiring being re-added and removed multiple times, resulting in multiple ADDED and EXPIRED events for the same order (#352).
- Modified Mesh's validation logic to reject and consider invalid any partially fillable orders. While this istechnically a breaking change, partially fillable orders are rare in the wild and we don't expect this will
- Lowercased
GetStatsAsyncmethod togetStatsAsyncin TS client
- Added
"declaration": true,to TS client'stsconfig.jsonso that downstream projects can use it's TS typings. (#325)
- Modified how
mesh_addOrderstreats orders that are already stored on the Mesh node. Previously, they would be rejected with codeOrderAlreadyStored. Now, if the order is stored and fillable, it will be accepted. If it is stored but unfillable, it will be rejected withOrderAlreadyStoredAndUnfillable. We additionally added aisNewproperty to the accepted orderInfos returned, so that callers can discern which orders Mesh already knew about. (#316)
- Added backup bootstrap nodes provided by the libp2p community
- Reduced AdvertiseBootDelay for bootstrap nodes
- Implemented a check that will alerts you when switching to a different Ethereum network ID. (#301) -- special thanks to @hrharder!
- RPC server is now started while block event backfilling is happening under the hood instead of waiting for it to complete (#318)
- Added a
mesh_getStatsendpoint which returns a host of useful information about the state of the Mesh node (e.g., number of fillable order stored, number of peers, peerID, etc...) (#322)
- Log messages are no longer incorrectly fired when receiving orders which have already been seen (#286)
This release fixes several bugs:
It also includes a reduction in the delay before which bootstrap nodes advertise themselves as relays from 15mins to 30sec.
This version introduces a temporary hack in order to help some Mesh nodes find their public IP address under certain circumstances.
This release fixes a bug in how AutoNAT and AutoRelay services were discovered.
This release fixes some networking related issues with our bootstrap nodes.
- Bootstrap nodes now advertise the correct public IP address.
- Bootstrap nodes now also operate as a relay.
These fixes will help smooth out any issues with peer discovery.
This release fixes a few minor bugs and includes additional documentation.
- 1.Set a custom protocol ID for our DHT in order to separate it from the default IPFS DHT.
- 2.Fixed a bug in the getOrders JSON-RPC endpoint where fillableTakerAssetAmount was sometimes being encoded as numbers instead of strings.
- 3.Converted addresses to all lowercase (non-checksummed) in the JSON-RPC API.
- 4.Improved logging.
- 5.Added a guide for running a Mesh node with telemetry-enabled.
This release adds AutoNAT support for our bootstrap nodes. This enables peers who are behind NATs to find each and connect to each other (in most cases).
In addition, this release includes some changes to default network timeouts and documentation improvements.
This is the initial beta release for 0x Mesh!
This release supports the following features:
- Automatic peer discovery via a DHT.
- A JSON-RPC endpoint for interacting with your Mesh node. It includes support for adding new orders and subscribing to order updates.
- Efficient order validation and order watching under the hood. You will get notified quickly when orders are expired, canceled, or filled.
- Basic limitations on the size and types of messages sent by peers. Peers that send malformed messages or messages that are too big will be dropped.
In addition to improving stability and scalability we plan to release many more important features in the near future. Check out https://github.com/0xProject/0x-mesh/issues for more information about what we are working on.
Last modified 1yr ago