Bitcoin rescan wallet
It controls what kind of addresses are produced by getnewaddress , getaccountaddress , and createmultisigaddress. A -changetype argument has also been added, with the same options, and by default equal to -addresstype , to control which kind of change is used. Note that some RPCs do not yet support segwit addresses. Support for segwit in those RPCs will continue to be added in future versions. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.
This includes the ability to send to BIP addresses including non-v0 ones , and generating these addresses including as default new addresses, see above. A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses.
Due to a backward-incompatible change in the wallet database, wallets created with version 0. Note that this only applies to new wallets; wallets made with previous versions will not be upgraded to be HD.
There is a checkbox to mark the transaction as final. The RPC default remains unchanged: Bitcoin Core now has more flexibility in where the wallets directory can be located. Previously wallet database files were stored at the top level of the bitcoin data directory. The behavior is now:. Care should be taken when choosing the wallets directory location, as if it becomes unavailable during operation, funds may be lost.
This would allow pruned nodes to serve the most recent blocks. Please backup first the app data directory. Alternatively if that does not help you can also delete the BloomFilterNonce.
All three methods might screw up the internal state of the wallet. There is also a hidden double spend feature if all the above does not help, but that is a bit experimental. Again before doing anything of the above do a backup so in case anything get screwed up we have a change to recover.
Also save the seed words. Thank you for your reply! As stated on reddit I will consolidate posts to here, this problem is two-fold:. First, as mentioned above, some of my withdrawals never hit the blockchain. So I must wait to resolve these issues before moving on to try and recover the coins that are marked as having been withdrawn without actually ever having been confirmed…. I feel bad for my trading partner same partner for both stuck trades now. The mining fee issue can be solved but it is a bit of effort and I did not had time yet to implement that.
If people would follow the instruction in the popup to always pay at least the 0. But seems the last days 0. All tx inside Bitsquare have 0.