Release v0.15.1

New Features

• Support Sepolia and Holesky out of box

Bugfixes

• When the network is congested, upstream nodes may produce new blocks too late which breaks Dshackle Heads subscription

Release v0.15.0

v0.15 mostly includes bugfixes and performance optimization.

New Features

• ERC-20 Token API for any ERC-20 contract (previously only for preconfigured)
• HTTP/WS/gRPC compression

Improvements

• use Java 17
• improved stability of WS connection
• do not make unnecessary requests to an upstream without a method, bad upstream, etc
• optimized event log for high-load setup

Bugfixes

• getrawtransaction on bitcoin requires verbosity
• doesn't fetch Bitcoin balance when provided by another Dshackle instance
• problem: doesn't accept JSON RPC with params=null
• no fresh block in Redis, causing unnecessary requests to an upstream

Release v0.14.0

The release v0.14 primarily involves a substantial refactoring of the codebase, a necessary step for further development and the introduction of new features. Most internal components have been modified, and these changes could potentially be breaking, which requred a comprehensive testing to ensure that nothing is broken.

New Features

• Subscription to pending transactions (newPendingTransactions for Ethereum, but this feature also works for Bitcoin)
• ZeroMQ connection to Bitcoin upstream
• Additional log with details for the requests made to an upstream
• Capability to send logs to a TCP socket (e.g., Vector, etc.)

Improvements

• Configurable for use with multiple parallel WebSocket connections to an upstream
• Additional Prometheus metrics
• Enhanced caching
• Improved tracking of a Dshackle upstream with automatic reconnects

Bugfixes

• Dshackle could break or mix responses if some custom methods are configured
• Breaks WebSocket connection on invalid/corrupted responses
• WebSocket connection stop to function with Geth 1.11.0
• Does not update Bitcoin methods provided by another Dshackle upstream

Release v0.13.1

Bugfixes

• looses upstream error details
• may try to verify an upstream even if the verification disabled
• uses binary frames for Websocket Proxy #180
• ignores errors from upstream with non-standard JSON RPC

New features

• more granular config for upstream validation #176

Release v0.13.0

NEW

• Support Ethereum's Merge

New Features

• CORS Origin
• Signed responses from upstreams (SECP256K1, P256)
• Switch to HTTP when Websocket connection breaks, without loosing the existing requests
• ZeroMQ for Bitcoin upstreams

Bug Fixes

• multiple issues with Websocket
• cannot resolve with local DNS

Release v0.12.0

Improvements

• Various improvements to the Monitoring & Access Log
• Options to enable/disable upstream

Bug Fixes

• breaks connection between Dshackle on large messages
• getting balance for ERC20 tokens
• high memory use with Websocket

Release v0.11.1

Security fix

Vulnerability in Log4J library

See:

• CVE-2021-44228
• https://www.lunasec.io/docs/blog/log4j-zero-day/

Release v0.11.0

New Features

• Websocket Proxy
• Health Check endpoint compatible with Kubernetes
• NativeSubscribe gRPC method to subscribe to Ethereum events (logs, newHeads, filter)

Improvements

• Use WebSocket to connect to upstream by default
• less resource intensive ERC20 balance subscription
• configurable "static" call responses

Contributors

@aldoborrero
@splix
@brianmcgee
@skylenet

Release v0.10.1

Bug Fixes

• fails to build JSON for some Ethereum blocks
• missing height in status log

Release v0.10.0

New Features

• Access Log
• Prometheus Metrics
• Support Matic (Polygon) Network

Improvements

• New Ethereum methods (post EIP1559)
• Configurable Quorum for custom methods
• Optimize routing [7cf8612]
• Reconnect to WebSockets endpoint if connection dropped

Bug fixes

• invalid response for hash-based calls [0f77b57]
• fails to respond when requested block doesn't exist [91ffb02]