chore(release): v2.5.0-beta

[shamardy]

v2.5.0-beta - 2025-07-04

Features:

WalletConnect Integration:

• WalletConnect v2 support for EVM and Cosmos coins was implemented, enabling wallet connection and transaction signing via the WalletConnect protocol. #2223 #2485 #2508

---

Work in Progress (WIP) Features:

Cosmos Network and IBC Swaps:

• Pre-swap validation logic was implemented for maker order creation, requiring HTLC assets and healthy IBC channels on the Cosmos network, with all changes gated behind the ibc-routing-for-swaps feature. #2459
• The taker and maker order types were extended with an order_metadata field to carry protocol/IBC details, and cross-checks for IBC channels were added (also feature-gated), enabling both parties to validate IBC routing before a swap. #2476

TRON Integration:

• Initial groundwork for TRON integration was started, including the addition of basic structures and boilerplate code; no end-to-end functionality is yet available. #2425

---

Enhancements/Fixes:

Event Streaming:

• Streamer IDs in the event-streaming system were strongly typed to improve type safety and code clarity. #2441

Peer-to-Peer Network:

• Hardcoded seed node IP addresses were removed from the peer-to-peer network configuration to improve maintainability. #2439

Orders and Trading Protocol:

• The minimum trading volume logic was revised to remove BTC-specific volume behavior, standardizing the calculation across all coins. #2483

Tendermint / Cosmos:

• A helper for generating internal transaction IDs for Tendermint transactions was introduced. #2438
• The IBC channel handler was improved to enhance safety and reliability when interacting with IBC channels. #2298

Wallet:

• Unconfirmed z-coin notes are now correctly tracked. #2331
• HD multi-address support for message signing was implemented, allowing message signatures from multiple derived addresses. #2432 #2474
• A delete_wallet RPC was introduced to securely remove wallets after password confirmation, while preventing the deletion of the currently active wallet. #2497
• A race condition during the initialization of Trezor-based hardware wallets was resolved by ensuring the correct account and address are loaded before fetching the enabled address, preventing startup errors. #2504

UTXO:

• Validation of expected public keys for p2pk inputs was corrected, resolving an error in p2pk transaction processing. #2408
• Transaction fee calculation and minimum relay fee handling for UTXO coins were improved for accurate fee estimation. #2316

EVM / ERC20:

• ETH address serialization in event streaming was updated to use the AddrToString trait for consistency. #2440

Pubkey Banning:

• Expirable bans for pubkeys were introduced, allowing temporary exclusion of certain public keys. #2455

RPC Interface:

• A unified interface was implemented for legacy and current RPC methods. #2450

DNS Resolution:

• IP resolution logic was improved to fail only if no IPv4 address is found. #2487

Database and File System:

• More replacements of dbdir with address_dir were made as part of an ongoing improvement to database architecture. #2398

Build and Dependency Management:

• Duplicated mm2 build artifacts were removed from the build process to reduce clutter. #2448
• Static CRT linking was enabled for MSVC builds, improving the portability of Windows binaries. #2464
• The timed-map dependency was bumped to version 1.4.1 for improved performance and stability. #2413 #2481
• The base58 crate was removed and replaced with bs58 throughout the codebase for consistency and security. #2427
• Dependencies were reorganized using the workspace.dependencies feature for centralized management. #2449

---

Other Changes:

Documentation:

• Old URLs referencing atomicDEX or previous documentation pages were updated throughout the documentation. #2428
• A DeepWiki badge was added to the README to highlight documentation resources. #2463

Core Maintenance:

• Workspace dependencies were organized for consistent dependency management across the project. #2449
• A unit test was added to validate DEX fee handling for ZCoin. #2460
• Improved ERC20 token lookup to use platform ticker alongside contract address for proper token identification across platforms. #2445

---

NB - Backwards compatibility breaking changes:

WalletConnect/EVM Coin Activation Policy:

• The priv_key_policy field for EVM coin activation now requires the new enum variant format: "priv_key_policy": { "type": "ContextPrivKey" }. #2223

TRON/EVM Chain Specification:

• EVM coin configurations must now include chain_id inside the protocol_data field. Legacy chain_id fields are deprecated. #2425

mm2 Build Artifacts:

• The mm2 binaries have been removed from build outputs. Users must reference new artifact locations. #2448

Seednode Configuration:

• Hardcoded seed nodes were removed. KDF will no longer connect to 8762 mainnet by default without proper seednodes configuration. #2439

IBC/Cosmos Changes:

• The ibc_chains and ibc_transfer_channels RPC endpoints have been removed. #2459
• The ibc_source_channel field now requires numeric values only (e.g., 12 instead of channel-12). #2459

---

[smk762]

A quick report from this morning's trezor testing:
TREZOR ACTIVATION REPORT.md

tl;dr

• task::enable_eth::init returns errors upon trezor activation attempt regardless of priv_key_policy structure.
• z coin and tendermint task activation succeeds for trezor regardless of priv_key_policy structure or its presence/absence, and returns the same address either way. add_new_address is not supported, so this is assumed expected behavior.
• qtum and utxo task activation on trezor successful using priv_key_policy": "Trezor", but not priv_key_policy": {"type": "Trezor"}.

The breaking change in #2223 implies an object (not string) should be used for priv_key_policy, though it is currently inconsistently applied in the API, which is a little confusing.

The failing ETH activation in Trezor, unless expected and WIP, I'd consider a blocker.
The param inconsistency I can delegate to an issue for future polishing.

ETH Trezor activation atttempt gave me:

{
    "mmrpc": "2.0",
    "result": {
        "status": "Error",
        "details": {
            "error": "Coin does not support Trezor wallet",
            "error_path": "lib.platform_coin_with_tokens.v2_activation",
            "error_trace": "lib:104] platform_coin_with_tokens:457] v2_activation:792]",
            "error_type": "Internal",
            "error_data": "Coin does not support Trezor wallet"
        }
    },
    "id": null
}

This is likely due to ETH not having a trezor_coin value in the coins repo. I'll aim to fix that.

MATIC/BNB return ActivatingCoin and then

{
    "mmrpc": "2.0",
    "result": {
        "status": "Error",
        "details": {
            "error": "DataError",
            "error_path": "lib.platform_coin_with_tokens.eth_with_token_activation.coin_balance.mod.pubkey.client",
            "error_trace": "lib:104] platform_coin_with_tokens:474] eth_with_token_activation:438] coin_balance:493] mod:417] pubkey:180] client:93]",
            "error_type": "Internal",
            "error_data": "DataError"
        }
    },
    "id": null
}

Not much in console logs, just 01 05:40:00, coins::coin_balance::common_impl:486] INFO BNB HD wallet hasn't been enabled before. Create default HD account then nothing else related.

[smk762]

Though some issues remain unresolved with Trezor and WalletConnect, none are blocking for next Wallet release - and changes required for next wallet release in this PR appear to be functional (in CLI at least).
On that basis, I'll approve for the sake of not delaying the next Wallet release, and await retesting the remnants in 2.6.0

[DeckerSU]

LGTM. All third-party dependencies in this project were scanned manually, and no malicious code was found. However, this review covered only intentional inclusions; logic errors, non-functional code, or similar issues in third-party libraries were not assessed during this review.