New answers tagged

1

It runs fine with segwit addresses starting with a 1, but not native segwit. Prefix 1 is used by legacy addresses. You can check the other prefixes used here: https://en.bitcoin.it/wiki/List_of_address_prefixes Is there a way to use native segwit with Nbitcoin? Replace BitcoinPubKeyAddress with BitcoinWitPubKeyAddress in your code for using native segwit ...


2

You might be interested in my article The Bitcoin Script Language. A part of that is to go into details of the transaction format. Especially helpful is this graphic I've created: To answer the question directly: The first one is called "marker", the second one is called "flag". BIP 144 gives more details: Rationale for not using just a ...


2

I assume that you're referring to withdrawals, and I think that you're probably right if the company's backend relies on bitcoind to fully process transactions. If the company's backend manually builds transactions, then that code needs to be updated. Even if you use a stateless bitcoind's RPC interface to build and sign transactions, you still need to ...


1

On Pieter Wuille's website there are graphs about the Bitcoin network. These feature graphs of the block version (used for version bit signaling) across time.


0

Before opening the thread, I had already tried to import a wallet on Bitcoin Core using the Master Private Key previously extrapolated with dumpwallet. In summary I had done: getnewaddress dumpprivkey *step_1_key* dumpwallet Then trying to import the newly created wallet again: Make Blank Wallet > Yes importprivkey *Master_Private_Key_(from_"...


0

The steps you described is for a single private key, not a BIP32 wallet. If you are looking to back-up your HD seed (master key) in bitcoin-core you should use the dumpwallet command. https://bitcoincore.org/en/doc/0.18.0/rpc/wallet/dumpwallet/


Top 50 recent answers are included