From 8c1863624b064ae1b16cc52c8f53b0c649fe3743 Mon Sep 17 00:00:00 2001 From: frstrtr Date: Thu, 16 Jul 2026 09:01:31 +0000 Subject: [PATCH] btc: fix MSVC C2668 HexStr ambiguity in node submit_block_hex submit_block_hex passed a std::vector straight to HexStr. MSVC deems the vector->Span conversion ambiguous across the three overloads (Span) where GCC/Clang pick uint8_t, breaking the btc Windows release lane (release run 29467003679, node.hpp:131 C2668). Wrap in an explicit Span, the idiom already used by every other coin lane. --- src/impl/btc/coin/node.hpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/impl/btc/coin/node.hpp b/src/impl/btc/coin/node.hpp index e7b78abdd..7ea11ec82 100644 --- a/src/impl/btc/coin/node.hpp +++ b/src/impl/btc/coin/node.hpp @@ -128,7 +128,7 @@ class Node : public btc::interfaces::Node { if (!m_rpc) return false; - return m_rpc->submit_block_hex(HexStr(block_bytes), /*ignore_failure=*/true); + return m_rpc->submit_block_hex(HexStr(Span(block_bytes.data(), block_bytes.size())), /*ignore_failure=*/true); } /// Broadcast a WON block with FALLBACK semantics: P2P relay is primary,