-
Already mentioned this in chat. (apparently related to the timeout bug?). Just adding it here for visibility.
https://forums.counterparty.io/discussion/897/problems-sweeping#latest
##
---
Wan…
ghost updated
7 years ago
-
Are there any cases where we'd prefer `.unwrap()` over `.expect()`? If not, I think adding a pre-commit hook check to ensure `.unwrap()` is not used could speed up PR review for newcomers.
-
I'm not a python developer but we are using your lib to make payments with bitcoin. Currently the script we made works fine with one problem.
The payments are collected from a redis server in a pri…
-
-
According to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin the header may be one of:
```
Access-Control-Allow-Origin: *
Access-Control-Allow-Origin:
Acce…
-
I was wondering why insight.bitpay.com and trezor's insight give different values for estimate fees.
It's because your node doesn't see segwit, so it bases the fee/byte calculations based on ONLY n…
-
bitcond is spending hours "Rolling forward" upon startup, seemingly reprocessing blocks that were previously processed. There have been reports of this happening since July on stackexchange and reddit…
-
Setting up bitcoind is annoying and I bet many people wont do it. Using blockr.io is a poor alternative.
A good idea might be to use BitcoinJ's SPV verification to obtain the transaction history and …
-
These will make the server easier to deploy in certain contexts, particularly inside container orchestration systems.
gtank updated
4 years ago
-
**Is your feature request related to a problem? Please describe.**
Several problems in recent mining-client version:
- Only one user could use it each time(limit by stacks-node)
- User must deploy …