Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.5.0 - 2025-08-06

This release adds IPC transport support for local Ethereum node communication via Unix domain sockets.

This release intends to improve the reliability and fault-tolerance of the transport layer.

Websocket transport implementation.
Support for subscriptions over websockets.
Provider functions for websocket subscriptions (subscribe_blocks/0, subscribe_pending_transactions/0, subscribe_logs/0, subscribe_logs/1, unsubscribe/1).
Internally added a MessageHandler responsible for handling incoming async messages/notifications and routing them to the appropriate caller.
Internally added Exth.Rpc.Call struct that represents a chain of RPC calls that can be executed in sequence or as a batch.
Internally changed Exth.Rpc.Client to use Exth.Rpc.Call structs that allow batch requests to be made piping requests, like:
```
client
|> Rpc.request("eth_blockNumer", [])
|> Rpc.request("net_version", [])
|> Rpc.send()
```

Transport layer was responsible for serializing, deserializing and sending requests. Now, it's only responsibility is to send requests and receive responses, to keep its scope as minimal as possible.
Encoding and decoding logic was moved to Exth.Rpc subdomain.

Support for dynamic configuration through both inline options and application configuration
examples directory with practical usage examples

Moved Exth.Rpc.Encoding.encode_request/1 logic to Exth.Rpc.Request.serialize/1
Moved Exth.Rpc.Encoding.decode_response/1 logic to Exth.Rpc.Response.deserialize/1
Removed Exth.Rpc.Encoding module
Transport module does not receive an encoder/1 and decoder/1 option anymore. It's now direct to call Exth.Rpc.Request.serialize/1 and Exth.Rpc.Response.deserialize/1 functions.
These changes aim to reduce the complexity of Exth.Rpc and Exth.Transport modules and make it easier to understand its internals.

Exth.Provider was refactored to reduce its complexity
Fixed dialyzer warnings on Exth.Provider related to has no local return. Some types were fixed and the dialyzer warning does not appear anymore. No more warnings when defining providers.

Documentation for Exth.Rpc.Request and Exth.Rpc.Response structs
Allow inverting arguments order on Exth.Rpc.send/2 and Exth.Rpc.Client.send/2
- This change allows for more flexible usage patterns (pipes)
Creation of request IDs on Exth.Rpc.Client.send/2 when no pre-assigned IDs are provided
Creation of requests with no pre-assigned IDs with Exth.Rpc.request/2 and Exth.Rpc.Client.request/2

mint dependency is now :optional instead of only: :dev;
Updated README.md for documentation purposes, with more examples and better formatting;

Initial release of Exth
Core JSON-RPC functionality
- Request/Response handling
- Method generation
- Parameter encoding
Transport layer abstraction
- HTTP Transport implementation using Tesla
- Configurable middleware support
Provider interface
- Ethereum namespace support (eth_* methods)
- Net namespace support (net_* methods)
- Web3 namespace support (web3_* methods)
Client caching mechanism
Comprehensive documentation
MIT License