Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

New answers tagged

0

This is answered by Can't specify rpcport for testnet but it comes from an issue in the 0.17.XX change where options need to be specified by network type.


1

A pruned node will always catch up, whats the hassle? The issue stems from having Bitcoin Core opened but the wallet in question is not loaded in Bitcoin Core (because you closed it). Bitcoin Core will continue to be synced and receive new blocks and transactions. However, it will discard old blocks once it has stored the configured amount of block data. ...


1

It sounds like your wallet.dat file is still intact, but some of the environment data has gotten corrupted (possibly due to moving wallet files). Try doing db_load -r lsn wallet.dat This will reset the LSNs in the wallet.dat file which should cause the errors in the db.log to go away. Once you do that, delete the database/ folder and start Bitcoin Core.


2

If you have a wallet that isn’t opened for the period of pruning, it won’t be able to scan transactions. If you set the limit to 2GB, and 4GB of blocks pass without opening the wallet, it may miss incoming transactions as the required blocks will have been deleted.


0

You need to install a bitcoin full node, then create a program to scan from latest block to first block all the unspent outputs and keep in memory, maybe in something like Redis, the status of the balances of the addresses until you reach the 1 million you are looking for


1

Insight Block Explorer is the program. It has an API you can query. You'll need to install the block explorer. It runs in a nodejs environment.


2

bitaddress.org does not use the same private keys for paper wallet generation as for the single wallet. It uses the same initial entropy that you provide, but new private keys are generated for the paper wallet. Thus the addresses are different.


3

A transaction is confirmed when it is included in a block, so you will need to watch for a message that alerts your node (or whatever software you are using to watch the P2P gossip traffic) to a new block, that includes the transaction in question. It doesn't matter if a node run by a miner relays your transaction to other nodes on the network, it only ...


0

Bitcoin Core has locks in place that will stop multiple calls to build a transaction to be executed in parallel. Instead, they will be executed sequentially, as the lock gets relinquished by the previous call. So, the other thing that comes to mind is that there are limits to the ancestry set of transactions that may be submitted to the mempool at the same ...


0

While I did wait for the blockchain to download and to see if Bitcoin-Core could simply read its own file. The program failed to read in any of the info from my wallet.dat file, even after following the instructions in the post listed in my initial question. I ended up using walletool, which worked without a hitch. It gave me a list of every public and ...


0

Follow this example: https://github.com/OutCast3k/coinbin/ This app does everything you need


0

"Then again on average 1 in every 515 34-character addresses you generate won't have any digits in them other than the leading 1" I think it's 1 in every 261 34 char BTC addresses. It's because there are only 9 numbers available (0 not base 58 conform): (58/49)³³ = 261.007... One can create easily long vanity addresses like someone did with this one: ...


Top 50 recent answers are included