Bitcoin Forum
June 23, 2024, 09:13:59 AM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Development & Technical Discussion / Re: Private keys on: December 18, 2017, 09:12:32 AM
Thanks guys for clearing that all up for me! Great answers. Seems like I've got some reading up to do but I'm really impressed by blockchain Cheesy
2  Bitcoin / Development & Technical Discussion / Private keys on: December 16, 2017, 01:59:28 AM
I'm starting to get my head around Bitcoin, Blockchain etc. but I want to learn more about private keys, their generation, and use.

As I understand any 128-bit sequence can be a private key which can, in turn, be used to generate a 32-bit address using a one-way function.

1. Is there a set of rules that narrow down what is a good private key?
2. Is there anything in place to avoid collisions (multiple private keys to one address) other than statistics?

Also, roughly how many public addresses are currently storing bitcoin?
3  Bitcoin / Development & Technical Discussion / Re: Signature Forging on: December 05, 2017, 09:28:54 PM
When you start initializing an address in your wallet (or when you create an address by your own) what basicaly happens is that your PC will randomly(!) generate a private key (following rules, ofc.).
Out of this private key you can calclulate your public key (an address is the 'visualisation' of a public key). This is a one-way-function. This means you can generate the pub key out of the priv key easily..
I see. Seems pretty secure. The last problem that I have then is how hard would it be to imitate the public key? a public key is derived from the private one but it is considerably shorter (64-bit?). Shouldn't multiple private keys match that public key? couldn't it be possible (and easier than a brute force on the private key) to simply find something that hashes out to the private key as it is the only part that is actually verified?

Yes, “straight up brute forcing” is indeed possible.  I sincerely suggest that you try this.  It will keep you busy and out of trouble.  To make it easier, there is a public directory of all Bitcoin private keys.  Yes, that site really does list all Bitcoin private keys.  Get rich!  Happy hunting!

(P.S., why are highly intelligent people in a “Development & Technical Discussion” forum seriously answering questions about bruteforcing secp256k1!?  Doubly-hashed, undisclosed public keys are just gravy.)


I'm just learning here and as I understand this forum's main goal is to educate/demystify/discuss bitcoin. It seems that you understand but I'm just starting to.
I appreciate everyone's help by the way. I know this must seem trivial.
4  Bitcoin / Development & Technical Discussion / Re: Signature Forging on: December 05, 2017, 11:40:34 AM
Okay so I understand more now, a complete brute force would take multiple billion years because of the magnitude of possibilities (2256) Than you to https://bitcoin.stackexchange.com/questions/2847/how-long-would-it-take-a-large-computer-to-crack-a-private-key
But I'm still getting my head around the verification process for checking signatures. Even using the public key to cut down the possibilities there would still be billions of years of computing to crack the key. I was under the impression that you could get more info about the private key from every signature you see but that's incorrect, isn't it?
Also, what would happen if someone were to just send out random falsified transactions? Wouldn't that slow down the other nodes? couldn't you just write all the false transactions and have other nodes verify them?
5  Bitcoin / Development & Technical Discussion / Re: Signature Forging on: December 05, 2017, 11:14:03 AM
As you (hopefully) already read, it is impossible (in human terms) to 'crack' the private key out of a public key.
This is where I get confused. I'm still reading into this. Private keys work on the basis of proving that you own the one and only privatekkey and the messages you write with it are indeed your own. But in blockchain, there is nothing hidden so the blockchain cannot verify using a private key. So how does it do that? How does it ensure the transaction uses the right key?

There is no possible attack vector in 'forging transactions'.
Even straight up brute forcing it, it's still possible right? Just not practical because it would take ages or tonnes of computer power.
Just out of curiosity though, if you poured the 1000s of THashes of computing involved in mining to crack a private key, how long do you reckon it would take?
Also, what would happen if you flooded the system (neighboring bitcoin nodes) with 1000s of random guesses?
Sorry for the tonnes of questions....
6  Bitcoin / Development & Technical Discussion / Signature Forging on: December 05, 2017, 08:58:03 AM
I'm relatively new so please be patient with me.
So I read a lot about people trying to crack private keys and passwords for wallets but why is there no talk of forging transactions?
No signature is perfectly safe and if you can see it used enough it should be possible to replicate it.
So why aren't people pushing around false transactions and brute forcing until they steal the BTC from someone else?  Huh

7  Bitcoin / Bitcoin Technical Support / Re: Reading the Blockchain on: November 29, 2017, 12:18:13 PM
You can just use Bitcoin Core which is already able to read and parse the blocks to get them into an easier to understand format. You can use the getblock RPC command to get the details of each block.

Fair enough. But if I want to sift through the data using my own software, how would I go about that? Is it possible?
8  Bitcoin / Bitcoin Technical Support / Reading the Blockchain on: November 28, 2017, 11:02:46 AM
I downloaded the blockchain and have all the .dat files.
Now: how do I explore the inner workings of each block? Is there a way to parse them to text/XML?
I know this is probably ridiculous because of it's length and size but theoretically it should be possible to scrape the Blockchain right?

EDIT: I found a fraction of the answer in this thread: https://bitcointalk.org/index.php?topic=40822.0
9  Bitcoin / Bitcoin Discussion / Re: Do Banks fear cryptocurrency on: November 23, 2017, 08:30:46 AM
Banks should be afraid of loosing business and their precious fees. (Unless they start somehow incorporating blockchain)
Governments should be afraid because they loose control over their own currency. (Unless they start "minting"/mining bitcoins)
People should be afraid because there is no customer service to call in crypto-currency. You get scammed or hacked and no one will save you.

Changes are coming...
10  Bitcoin / Bitcoin Discussion / Re: Bitcoin bubble on: November 23, 2017, 07:54:42 AM
The tricky part is that Bitcoin has no inherent value of its own other than the cost of the power to mine it. People are excited at Blockchain technology and it's potential so they are associating a lot of value to it. The truth is the cost of the power required to mine a single bitcoin (according to my very rough calculations) is 1000USD to 2000USD. As you can tell from current prices, it is FAR beyond that. So yeah, BTC should come down eventually either by a "pop" or by an increasing cost of mining/processing transactions.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!