New answers tagged

0

You can "create, sign and broadcast a transaction with fee rate less than 1 sat/vbyte" but there is a minRelayTxFee set by default to be 1,000 satoshi per kB and a dustRelayFee defined here. So if you want your transaction to be relayed by nodes on the network you need to be careful not to drop the fee too low as not only will it not propagate ...


1

After some digging, I find out more about the answer. In bitcoin core, it is possible to NOT broadcast your own transactions with "walletbroadcast=0" option See more details at https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009422.html, https://en.bitcoin.it/wiki/Privacy ("Tor and tor broadcasting"), and https://github....


3

You cannot. The node side of Bitcoin Core treats wallet transactions as any other transaction. They aren't treated any differently from transactions received over the network. So once the transaction is added to the node's mempool, it will be broadcast to connected nodes in the same way that any other transaction would be relayed. All you can do is to ...


3

Yes, if it has a mempool (no -blocksonly). No matter the number of blocks stored, what matters is how many blocks it has been watching (ie received at the time of generation, with transactions that were part of its mempool).


2

The two are entirely uncorrelated. There's no requirement for a miner to run a fully validating node at all.


2

You can check three factors in the getblockchaininfo RPC call: The result contains a count of the blocks in your chain, and the headers your node has received from peers. For a fully synchronized node, the number of blocks equals the number of headers. Additionally, there is an initialblockdownload boolean in the response, which will be set to false once the ...


Top 50 recent answers are included