v0.3.1

General release information

This is a PATCH release.

After v0.3.0 we noticed some race conditions on JD message flow (see #364) arising from the JDS refactor carried via #299

These race conditions arise due to the current bitcoin_core_sv2::job_declaration_protocol design, which relies on a MempoolMirror (which is arguably suboptimal).

This was addressed via #365 + #372 + #375. On the long term (ideally Bitcoin Core v32), we expect bitcoin/bitcoin#34020 to allow us to simplify bitcoin_core_sv2 design, reducing the need for all the workarounds on the suboptimal MempoolMirror design.

Moreover, #375 also addressed a small bug on jd_server_sv2::job_declarator::token_management::TokenManager (via 7b1d763).

What's Changed

• Remove one keyword in tProxy Cargo.toml by @GitGab19 in #348
• Add solution subdirectory to solution_block_dir by @Shourya742 in #350
• remove verbose debug log from bitcoin_core_sv2::job_declaration_protocol by @plebhash in #361
• JDC asks for token when none is available for RequestTransactionData.Success handler by @plebhash in #363
• update hotpath and increase UI limit to max by @Shourya742 in #357
• Adapt tproxy user_identity manipulation to SRI pool patterns by @GitGab19 in #370
• fix JD chain tip race by @plebhash in #365
• ci: replace stratum freshness check with event-driven stratum-core sync by @plebhash in #353
• refine how JDS handles downstream disconnections by @plebhash in #352
• refine JD race patch by @plebhash in #372
• make mining_device into submodule of integration_tests_sv2 crate by @plebhash in #355
• chore(deps): update stratum-core to 47b9f92 by @SV2-bot in #374
• further refine JD race patch + refine TokenManager by @plebhash in #375

Full Changelog: v0.3.0...v0.3.1