-
**What is the bug?**
Darkside txids are incorrect
**Additional context**
In a production server, the txid issue is bypassed according to this comment: https://github.com/zcash/lightwalletd/blob/8…
-
## Problem
At the moment of the call we know that transaction exists, but instead of returning pending state it is treated as not found.
## Current flow
1. Creating TX:
```
{"jsonrpc":"2.0","id…
-
When calling "sendMessage" I get the following error. Any idea why?
{"response":null,"error":"unrecognized unsigned message sub_message","error_description":"","txid":"ce33beccb5171fd80b172a0aa2437…
-
I've been researching how to use txids for one of our use cases. I ran into a few articles that talk about how the current transaction id wraps around after 4 billion transactions. It has caused a few…
-
```
$ curl -v https://blockstream.info/api/tx/0000000000000000000000000000000000000000000000000000000000000000/outspend/0
< HTTP/2 200
< server: nginx
< date: Tue, 01 Jun 2021 00:47:42 GMT
< con…
-
I stumbled upon the following bug when using `sendBitcoin()` API call - sometimes, the call would return a txid (which my app treats as success) but this tx would never make it to the mempool. Why wou…
-
Since the purpose of the `bdk_wallet` crate is to provide useful/opinionated ways to perform standard wallet tasks, it feels to me like a simple-to-use "get me all important—nicely bundled if you don'…
-
Could scan_tx be used for importing a specific deposit TXID for a 2-of-3 multisig transaction in order to avoid syncing weeks of blocks between the multisig creation and multisig payout (cases where t…
-
I have a question about transaction `ret`.
In the normal case, the size of ret was 1. However, cases where this was not the case were found, and the results were also strange.
Here are two transac…
-
Hi, I'm afraid the best way to handle these exceptions is to hardcode them to searching code (or to wontfix it).
In Bitcoin and BCH and BSV these transactions appear in two blocks:
`e3bf3d07d4b0…