Bitcoin Forum
November 20, 2018, 07:04:39 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 ... 547 »
361  Bitcoin / Bitcoin Technical Support / Re: I've been fight the core download for months on: March 22, 2018, 04:55:19 AM
Your copy of the blockchain contains a corrupted block. You will need to delete the corrupted block and reindex the blockchain which will take several hours. To do this first stop Bitcoin Core. Then go to blocks folder in the Bitcoin data directory (for you that is C:\Users\john-asus\AppData\Roaming\Bitcoin\blocks) and delete the files blk00589.dat and rev0589.dat and any blk*.dat and rev*.dat files that have higher numbers. Then start Bitcoin Core again. It will tell you that it needs to reindex the blockchain, click Yes and let it do that. Once it finishes, it should resume syncing the rest of the blockchain. Note that the reindex will appear as if it is syncing the blockchain; it is not.
362  Bitcoin / Development & Technical Discussion / Re: What are the markers byte in wallet file on: March 22, 2018, 04:51:25 AM
So I tried to figure out the content of the wallet file, and a dump shows that each key value is prefixed with a non-printable mark, even when the data item is valid printable strings, what's the purpose of these markers bytes, like
\07, \09, \0a
Those aren't marker bytes. They are length prefixes. The specify the length of the following piece of data.
363  Bitcoin / Bitcoin Technical Support / MOVED: Crack this hash- win 2 Bitcoins! on: March 21, 2018, 05:00:44 PM
This topic has been moved to Trashcan.

364  Bitcoin / Development & Technical Discussion / Re: Trinary Payment Channels on: March 21, 2018, 05:00:00 PM
It is certainly possible to have more than two parties in a payment channel. It just becomes extremely complex to handle all of the failure cases which results in a lot of different punishment transactions. IIRC this is actually what allows for channel factories to work (basically payment channels created from within payment channels).
365  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: March 20, 2018, 07:01:31 PM
Is this wallet for pc?
Yes, it is a desktop wallet.
366  Economy / Services / Re: Wallet.dat file version Bitcoin-0.1.0 on: March 20, 2018, 06:56:33 PM
Bitcoin 0.1.0 uses BDB 4.7 for its wallet database (the wallet file is just a BDB database file). So you can use the utilities packaged with BDB 4.7 to extract the data from the file without needing to actually understand the format. Use db_dump to dump the contents of the database and find the things that you need. Presumably you want the private keys which are just DER encoded private keys. They're pretty easy to spot in the db_dump output.
367  Bitcoin / Bitcoin Discussion / Re: Bitcoin Core 0.16.0 Released on: March 19, 2018, 05:25:10 PM
that's not my point, what i mean is that it's pointless to release many releases in a short time, 15.1 was still new
0.15.1 was released just shy of 5 months before 0.16.0 was released. I wouldn't say that is "too many releases in a short time", after all we do releases every 6 months (or we try to).

Anyways, the point of releasing 0.15.1 was to get a release which had additional handling for forks in order to avoid network problems with the 2x fork that was planned to happen at that time but got cancelled. It had additional handling for invalid blocks and such to avoid troubles with forks in general. That is why that was released. We considered it an urgent release because of the 2x fork which could disrupt the network.
368  Economy / Services / Re: Wallet.dat file version Bitcoin-0.1.0 on: March 19, 2018, 05:06:10 PM
You can just make your own by downloading and using Bitcoin 0.1.0. It is available from
369  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.16 - How can I add more than 8 Network connection? on: March 18, 2018, 04:38:58 PM
I currently have 9 outgoing connections, since I added a node in my configuration file.
So you can have more, you just need to specify their IP address. It can't find more then 8 for you automatically.
There are 8 automatic outgoing connection slots and 8 addnode connection slots. By default, you will have 8 outgoing connections, but then you can also add 8 more by addnode'ing some nodes.
370  Bitcoin / Development & Technical Discussion / Re: Lightning Network releases Mainnet support for Bitcoin and Litecoin on: March 17, 2018, 03:07:42 AM
Note that the Lightning Network is not something that is owned by or controlled by Lightning Labs. Nor is it something that only Lightning Labs creates; there are multiple companies and groups that are creating implementations of the Lightning Network specification which was also created by multiple different groups of people.
371  Bitcoin / Development & Technical Discussion / Re: HD wallet question on: March 16, 2018, 08:21:30 PM
Would it be risky to have account be un-hardened considering that this wallet will never be used for payments? (except for consolidating and moving to other cold storage wallets)
Unhardened derivation is only risky if someone is able to learn the xpub and any of the child private keys. In that case, the xpriv corresponding to the xpub can be derived. So if you think your security if the private keys is good enough, then unhardened is fine.

Do you know how various exchanges/etc. deal with this issue?
I don't think exchanges generally have separate accounts like that dedicated to each user.
372  Bitcoin / Development & Technical Discussion / Re: HD wallet question on: March 16, 2018, 05:50:07 PM
Since account' is a hardened derivation path, you cannot generate it server side without having the master private key also be server side. So you can either make it unhardened (thus only storing the pubic key for m/44'/0') or just generate a lot of xpubs for each account and regularly refresh the available xpubs manually.
373  Bitcoin / Development & Technical Discussion / Re: Core's next version 0.16.xx or 0.17? on: March 16, 2018, 05:47:16 PM
Are there plans for a minor or bugfix update for Core
There will be minor updates if there are bugs in need of fixing tat can't just wait for the next major version. There are currently no plans for a minor release, but there may still be one as bugs are found and fixed.

or is the next version going to be 0.17?
The next major version will be 0.17 (or 17.0, depending on whether we change the version scheme). That does not necessarily mean that it will be the next version released.
374  Bitcoin / Development & Technical Discussion / Re: Why per-wallet db.log and database? on: March 16, 2018, 05:45:34 PM
So wallet.dat is BDB, and ./database/ is a transactional log?
database/ is used for whatever other temporary data BDB needs. This includes (but is not necessarily limited to) database transaction logs.
375  Bitcoin / Development & Technical Discussion / Re: Right way of pushing to Github? on: March 16, 2018, 05:44:14 PM
Github uses git. You use git push to push changes to github (assuming that you used git clone to download the source code). Read GitHub's documentation.
376  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.16 and bech32 on: March 16, 2018, 05:41:29 PM
I think you're right but I the getaddressinfo command does not exist and I can't find a similar command in the list of commands you get by typing help. Do you know what you meant instead?
Right, getaddressinfo was merged for 0.17, not 0.16. It's validateaddress for 0.16.
377  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.16 and bech32 on: March 16, 2018, 04:34:26 AM
Get an address from your wallet and go to the debug window. Then type
validateaddress <address>
Find the field for
and tell us what it says. I suspect it will say false.

Since you say that your wallet is old, there's a good chance that you still are using uncompressed public keys which are not allowed by segwit. This has nothing to do with a wallet being non-HD; it just means that you are using a wallet that does not support compressed public keys.

To use compressed public keys (so that you can use segwit), you can upgrade your wallet to use compressed public keys by starting Bitcoin Core with -upgradewallet. Note that this will not make your wallet HD, it will only upgrade it to support compressed public keys. Then you will need to flush and regenerate the keypool. Unfortunately I don't think there's a way to do that right now besides just generating a few hundred addresses. At some point it will start giving you p2sh wrapped addresses instead of legacy addresses as the keypool runs out of the old uncompressed public keys.

If your wallet is not encrypted, you can encrypt it and that will automatically flush and regenerate the keypool for you.

edit: validateaddress, not getaddressinfo
378  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core: Network settings tab options on: March 15, 2018, 10:18:43 PM
Main question is what's difference between 3rd and 4th options?
The 3rd option proxies all of your traffic. The 4th option only proxies TOR connections. So setting the 4th option allows you to connect to node's that are listening over TOR while connections to IPv4 and IPv6 nodes happen over your normal connection. The 3rd option will proxy ALL connections.

Can i just use 3rd option with port 9050 (it's TOR port)?

Also, i want to ask you about 1st and 2nd option. For what purpose they are?
The first option enables UPnP which will automatically tell your router (if it supports UPnP) to allow connections through to Bitcoin Core's P2P port. Typically routers will block such connections. Such routers will need port forwarding enabled for the P2P port. UPnP does that automatically.

The 2nd option disables the incoming connections entirely.

Do i need to disable incoming connections for maximum security?
No. The security risk is the same.
379  Bitcoin / Bitcoin Technical Support / Re: Broadcasting non standard transactions on: March 15, 2018, 04:35:37 AM
You can use a tool like to broadcast it. However your transaction probably won't be relayed and probably won't propagate well since it is non-standard.
380  Bitcoin / Development & Technical Discussion / Re: connect two bitcoin core nodes on different machine, using regtest on: March 15, 2018, 04:33:54 AM
The bitcoind is still trying to connect to
`2018-03-15 01:31:32 Binding RPC on address ::1 port 18332 failed.
2018-03-15 01:31:32 Binding RPC on address port 18332 failed.`

Anyone knows why ?
You have two programs that are trying to use the same port. You can't do that. One of your bitcoind instances will need to use a different rpcport (-rpcport) and normal p2p port (-port)
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 ... 547 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!