New answers tagged

0

I have tested setting watch-only to true and it gets rid of the errors and the node can still sign.


0

As chytrik said, a better way of doing it would be to export an extended public key (xpub) from the node wallet and put the on your app then generate new child address from the xpub using BIP32. If you still want to execute getnewaddress on your node, you would have to expose the bitcoin RPC by adding server=1 to the bitcoin.conf file on your node in order ...


1

It is a bug, you should report it.


0

listsinceblock will only list txs your wallet is interested in i.e. transactions involving as input or as output an address A such that: either A is an address whose private key is known to your wallet and consequently can sign transactions that spend UTXOs of A or A is an address your wallet is following as watch-only i.e. does not know A's private key but ...


2

Based on Raghav Sood's answer, I found the more specific answer to the OP would be using getmempoolentry, in order to get an individual transaction info. Otherwise you'll be flooded with tons of transactions. Documented here You can also use gettransaction, it returns bip125-replaceable flag as well, however just for Bitcore prior to 0.10.0 according to ...


2

The getrawmempool RPC command, in verbose mode, produces an output that contains all known mempool transactions for your nodes. This output contains a bip125-replaceable boolean field which you can use to determine if a tx is explicitly or implicitly replaceable by fee.


Top 50 recent answers are included