Invalid Signature Error, Yet Bitcoin Transactions Confirmed

Hi, we’ve been getting the following kind of error, but the transactions went through and got confirmed on Bitcoin mainnet.

Invalid basic signature: Ed25519 signature could not be verified: public key b84d80a54a2131eb92041967549201fb03dd55a3a32b659fffa69e9aad550517, signature fc056a8674c63ebb8cec4b155b831c2a2ee7553c99c58db3228b8049b492c80c557d3fda27e7580d97cad0504d42407f2c1adf2250613e8506cd7ddd62334403, error: A signature was invalid
Invalid signature: Invalid basic signature: Ed25519 signature could not be verified: public key 9cf0fe43f7d3c039bad8535e06a2d259edc8957053acca1d334a93c457fe1f29, signature 67cb55c79d422b82a358136e88f748a8a3c8168d5c21205e9f2c6b5c2b2d84c37f51f118703116bed3e7429918b3579ea985a265863d3aaece7603bab4adc406, error: A signature was invalid

Not sure how to avoid this error being returned. Is there anything certainly off in the signatures? It’s confusing since the Bitcoin transactions get confirmed.

@xalkan, can you please provide more context? It would be helpful to have details on what exactly you did that led to this error and where you experienced this error (e.g., in a frontend that you wrote yourself, or in the frontend of some dapp).

For example, as you mentioned that Bitcoin “transactions went through”, did you call the management canister’s bitcoin_send_transaction method, or did you maybe use a dapp that made such calls? If so, which dapp was that?