-
While debugging #297, @jcnelson & I discovered that Blockstack Core's current default UTXO provider, Blockcypher, has a bug where it doesn't display UTXOs for unconfirmed transactions:
> larry [11:…
-
Will be in satoshis:
actual response
``` js
[ { address: '12U6eu3sD8AWsrhqWc3Xq93MqnYAfSwiiU',
confirmations: 41,
vout: 0,
txId: '2f4dfd806ef7b04ef195619c16f140742c89707b10a49db2a6b93764…
-
I've followed [the docs](https://blockstack.org/docs) by the letter, but failed on lookup. (Running on Ubuntu.)
```
blockstack lookup timblee.id
Traceback (most recent call last):
File "/usr/l…
-
I upgraded from 0.70 to 0.76 and while I managed to fix most of my code that broke I have to work around this bug in a rather ugly manner.
The bug seems to stem from an inconsistent script type int…
-
The way to look up a past transaction appears to be something like this:
transaction = BigchainDB().transactions.retrieve(transaction_id)
It appears, though, to use whichever keys I last use…
-
Kudos to @boymanjor for finding this one.
Here's a test with two different transactions, each with a retirement at output index 1. `tx.OutputID(1)` provides the same hash for both: https://gist.git…
-
I'm trying to implement a multisig structure between two currently running systems, one is using js (BitcoinJS for now but it could be switched to bitcore if needed) and the other using python, pycoin…
-
History of coin wallets showing unordered in EasyDEX Dashboard.
Unspents first
Spends seconds
Spends.dest third (outgoing txs)
Need to sort them out as per timestamp and display them in order.
Otherw…
-
Thanks to #664, the integration tests are now **much** faster, however, they also now racing each other to use an unspent such that we are getting the error:
> Error: 258: txn-mempool-conflict ()
…
-
The `Wallet` abstraction is merely another form of BIP32 key management, and probably could be merged with `Account` and `Chain` in https://github.com/bitcoinjs/bip32-utils.
It'd be nice to extract t…