@0x/mesh-rpc-client
Advanced tools
Changelog
v8.1.0
Changelog
v8.0.0-beta-0xv3
@0x/mesh-ts-client
's getOrdersAsync
endpoint to include the snapshotID
and snapshotTimestamp
at which the Mesh DB was queried along with the orders found. (#591)ETHEREUM_RPC_MAX_REQUESTS_PER_24_HR_UTC
from 100k to 200k (#596).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)ENABLE_ETHEREUM_RPC_RATE_LIMITING
and config option enableEthereumRPCRateLimiting
which 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)SnapshotTimestamp
field to GetOrdersResponse
, the return type of the mesh_getOrders
RPC method. This way, the caller can know at what point in time the snapshot had been created. (#591)web3-provider
dependency used by @0x/mesh-rpc-client
in order to fix a bug where it was requiring either process
OR window
to exist in the global scope (#601).@0x/mesh-rpc-client
to avoid the client from hanging endlessly if it misses a response due to network disruption (#603).Changelog
v7.0.1-beta-0xv3
@0x/mesh-browser
package that resulted in some config options not being passed through correctly (#502).Changelog
v7.0.0-beta-0xv3
Note: This release will require wiping your Mesh's DB before upgrading. The DB location defaults to ./0x_mesh/db
.
RPC_PORT
environment variable. The new RPC_ADDR
environment variable allows specifying both the interface and port (#487).0.0.0.0
to localhost
. Users who previously did not set RPC_PORT
may need to now manually set RPC_ADDR
to enable other applications to access the RPC API. If you are using Docker Compose, we recommend using links. If you do need to set RPC_ADDR
to bind on 0.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).EXPIRED
event such that it is emitted when an order is expired according to the latest block timestamp, not anymore based on UTC time. (#490)EXPIRATION_BUFFER_SECONDS
env config since we no longer compute order expiration using UTC time. (#490)UNEXPIRED
order 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)Transfer
and Approve
ERC721 events which differ from the ERC721 standard. (#494)