Bitcoin Forum
December 11, 2018, 07:10:57 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: bitcoin-qt shows "n/a" instead of address after "payment to yourself"? on: March 27, 2018, 04:28:54 AM
And by the way, why does GitHub call it also commited on 3/19/2018, besides the original date of 10/10/2017?
Commits were last pushed on 3/19/2018 while the commit date is 10/10/2017. This happens because people will amend their commits and force push, but amending does not modify the commit date.
362  Bitcoin / Bitcoin Technical Support / Re: How safe is it to reuse existing blockchain files? on: March 27, 2018, 04:26:02 AM
I have seem conflicting arguments on this. The purists argue that you should never reuse files, and the rest say that it's safe because these files cannot be manipulated in any way in which would put your new node in trouble... thoughts?
Without the chainstate, it doesn't matter because your node will validate the blocks anyways and fetch whatever it doesn't have.

The argument only matters if you are copying over the chainstate too since then you have to trust that the chainstate you are copying has not been modified. Usually you can trust yourself and your computer so it really isn't an issue. It's only an issue if you have malware or someone has maliciously accessed your computer.
363  Bitcoin / Development & Technical Discussion / Re: What is key pool used for? on: March 25, 2018, 01:35:06 AM
I'm not sure as to why the keypool is still being used
To make it easier to implement HD into Core with minimal review. There are plans to generate HD keys on the fly instead of storing them in a keypool.
364  Bitcoin / Development & Technical Discussion / Re: bech32 generation in the GUI question on: March 24, 2018, 01:47:44 AM
This is a known issue. Just use the receive page.
365  Bitcoin / Development & Technical Discussion / Re: Bitcoin branch - multiple blocks on: March 22, 2018, 10:40:06 PM
I must have gotten something mixed up... isn't a coinbase a fee that the miner gets payed just for mining the block? He could really mine a block with only his coinbase transactions... basically he can decide not to include any additional transactions?
Yes. There is only one coinbase transaction per block. The coinbase transaction includes the payout for the block subsidy and the sum of the transaction fees in the block.

If so, then any other transaction he includes in his new generated block can make him money OUTPUT_1_amount - OUTPUT_2_change = transaction fee.
The transaction fee is the input amount - output amount.

So by mining a block he gets a coinbase amount (reward) + all of the transaction fees. So he broadcasts the message that he mined it... block is on the blockchain...transactions are considered valid...
The miner broadcasts the block itself. He doesn't just say that a block was mined. Miners also do not dictate what transactions are valid; a miner could include an invalid transaction in a block and the block would be rejected by all other full nodes on the network.
366  Bitcoin / Development & Technical Discussion / Re: Bitcoin branch - multiple blocks on: March 22, 2018, 10:06:54 PM
Now, if this scenario happens, does this mean that two transaction fees will be payed for the same transaction? First time it entered the block (that ended up in the "shorter" chain) and second time when that transaction was once again pulled from unconfirmed transaction pool and put in the new block (that hopefully ends up on the  "correct" chain)

From miners point of view, the second transaction fee should be necessary because it is not the second miners problem that the block from the "first" miner ended up in the "short" chain. But then again, who is paying for the second fee?

Transaction fees are collected by the miner, not really actively paid to the miner. They are the difference between the value of the inputs and the value of the outputs. Transaction fees are collected by the miner when they mine a block including the transaction. The fee is paid to the miner via the coinbase output which the miner generates. It is the same output that also pays the block subsidy (the 12.5 BTC reward a miner gets for mining a block).

In a situation for an orphan block, the miner whose block is orphaned receives no payment at all; he does not receive any transaction fees nor does he receive the block reward. This is because the transaction that contains that payment is the coinbase transaction of the orphaned block and so it does not become part of the main blockchain.

Because of this, your second question is invalid.
367  Bitcoin / Development & Technical Discussion / Re: It is NOT secure to use hardware wallets (and it never was) on: March 22, 2018, 07:02:31 PM
Just because there are vulnerabilities found does not mean that they are inherently insecure. Do you say the same things about software wallets too (many of which have had vulnerabilities found and patched, just like with these hardware wallets)? Do you say the same thing about the general purpose computer you use which you don't even know how it works? Every piece of software and many pieces of hardware will have some vulnerability found in them; given enough time, it's almost inevitable.

Worth mentioning, that the guy who found this exploit is 15 ys young.
That's slightly misleading. This 15 year old has dedicated a lot of time into working on hardware wallets, particularly in their firmware. He's been involved in numerous other vulnerability discoveries in the past with Trezors (and possibly Ledgers). The kid is very smart, probably smarter than you when it comes to hardware wallets. He's not just some random 15 year old who found this; he actually dedicated a lot of time into learning about how hardware wallets work and has been working with them for years.

Not 100% true, from what he said it was vulnerable to the "Evil Maid attack"
I don't think you understand what an evil maid attack is. It is, by definition, a physical access attack. You need to have physical access to the device in order to perform any of the known vulnerabilities (which have since been patched). An evil maid attack means literally that someone (like a maid) enters your room physically and does something malicious to a device (hence an evil maid).

Which took them close to 4 months to put out and still is not properly alerting & forcing users to update.
Vulnerabilities take time to fix and release. They can't just publish that there is a vulnerability or details about the vulnerability before a fix is available. It probably took them 4 months to figure out a solution. Also, Ledger can't force users to update, and there has been plenty of alerting (which, by the way, also cannot be forced).

Assuming you can trust everyone who handled the package from when it left their shipping dock till when it wound up in your mailbox.
There's a hardware and software attestation process that you can go through to ensure that your Ledger has not been tampered with.

What is the source for the 4 months? As far as i know this has been fixed pretty fast..
Scroll down to "Disclosure timeline"
368  Bitcoin / Development & Technical Discussion / Re: What are the markers byte in wallet file on: March 22, 2018, 06:43:56 PM
Hi, is this necessary? my understanding is Berkeley DB already keeps track of data item's length internally, for every db get operation, the Dbt return its data as well as the length.
The lengths are there because of Bitcoin Core's serialization framework. It tends to prepend everything with the length and it's kind of annoying to make it not do that. It's easier for it to just do that for everything because some things need to be length prepended and others don't, and it also depends on the use case (e.g. in transactions, length prepending is necessary, but not necessarily for the databse, but the same data ends up in transactions as well as in the database).

Also, Bitcoin Core tends to have multiple things concatenated in each key or value so the length prefix helps to differentiate between the two (e.g. each key in the wallet is some string followed by the actual key like a public key, so the length prefix lets us know where the string ends and the pubkey begins).
369  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.
370  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.
371  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.

372  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).
373  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.
374  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.
375  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.
376  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
377  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.
378  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.
379  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.
380  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.
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!