Releases: bloXroute-Labs/gateway
Releases · bloXroute-Labs/gateway
v2.128.111
Release notes
- Old blocks check added, prevent unsynced peers to spam gateway with old blocks.
- MevBundle
frontrunning
field has been removed,AvoidMixedBundles
field has been added. --mev-max-profit-builder
startup argument removed.- Allow Gateway to use DNS in
multiaddr
. - Added support of
BlobGasFeeCap
checks for Blob transactions inTxStore
. - Added a context to the SDN related errors.
- Allow Gateway to accept incoming Beacon P2P connections
--beacon-port
argument added. Default 0 (disabled). If set, Gateway will accept incoming beacon P2P connections on a given port.--beacon-trusted-peers-file
argument added. Default value""
. If set, Gateway will only accept incoming beacon P2P connections which PeerIds are mentioned in the file.- Added processing of Beacon API ping messages.
- Prevent processing multiple times the same block from Prysm gRPC.
- Websocket connection status fixed. Case when established connection was marked as
not_connected
. - txReceipts feed: added blobs related fields.
v2.128.108.2
Release notes
- Polygon: support of version 1.3.0
v2.128.108
Release notes
- ETH: Deneb block blobs propagation support over BDN
- ETH: Blobs can be retrieved/send via P2P and Beacon API.
v2.128.95
v2.128.90
v2.128.86
Release notes
- Eth Dencun hardfork support: Blob transactions, Deneb blocks
- Add protocol version to bxcli listpeers
- Remove mega bundle deprecated code
Important
Upgrade Gateway before the ETH Dencun hardfork activation on March 13.
Gateways with version before v2.128.86 will not be able to process blocks and block txs.
v2.128.59
Release notes
- Intents network support
- Beacon API client timeout increased
- Gateway tx gRPC feed panic fix
- Logging performance improvements
- Fix multiple ws connections to the blockchain node
- Blocks processing performance improvements
- Feeds performance optimization
- Add accounts authorization cache
- Fix Relay<>GW handshake protocol definition
- Don't initialise bridge if there are no nodes connections for BSC and Polygon networks
- BSC eth/67+ protocol version support
--tx-include-sender-in-feed
flag now has default valuefalse
v2.128.14.1
Release notes
- Add
BlxrSubmitBundle
gRPC endpoint - Add unit tests for
BlxrTx
andBlxrBatchTx
gRPC endpoints - Format output for
bxcli
feeds - Fix rare panic in
NewTxs
feed - Add support for Polygon-Mumbai network
- Add
--tx-include-sender-in-feed
flag
NOTE: --tx-include-sender-in-feed
flag enables from
field to be populated in WS and gRPC endpoints. On this version default value is true
meaning that the Gateway's behaviour stays the same as before when this flag is not provided. After the next release version default value will be set to false
so to keep receiving from
field users need to explicitly enable it. Motivation for this change is to improve performance, since sender extraction from transaction is CPU expensive operation.
v2.127.74
Release notes
- Extend logs context
- Increase gRPC batch transactions limit
- Use standard way to handle gRPC auth
- Fix the crash related to MEV Bundle reverting hashes
- Improve client handler performance
- Improve performance of sync map string hasher
- Fix redundant memory allocation for Walled IDs
- Add Beacon API to
bxcli status
- Add support for multiple Heimdall endpoints on Polygon
- Logging: add debug data for AlreadySeen events
- Refactoring: refactor ws handlers
- Refactoring: refactor gRPC blxrTx and BlxrBatchTx
- Other fixes, stability, security and performance improvements
v2.127.42
Changelog
- Drop broadcasting execution layer blocks in Ethereum network
- Fix high memory utilization on eth gateways
- Do not block the start of the gateway if can't request Beacon API endpoint