You haven't touched your bank account in 20 years, We are going to take your money give it to the people maintaining the banking system.
Actually, in the U.S. it is 3 - 5 years (depending on the state), but the money goes to the state. Wow Really?
|
|
|
I think I finished the "frameworks" (not sure it's the correct word)
As you can see the GUI and the WUI are simple and ugly If someone here has some graphical skills and has some ideas, please tell me what to do
Not ugly. Plain and simple. I think that is a lot better then a fancy GUI. Great project btw! Thanks I hope it's enough but I'm still very open to discussion if someone wants me to change that I need some thoughts Currently I have the old pywallet tabs (dump, import, delete, etc.) + new ones like ecdsa calculation, settings, signatures Should I put the old ones (dump etc., which are related to wallets) in a new Wallet tab?I supposed so Edit: "NPW" can be updated from CLI, GUI and WUI. The update is taken from github and is signed by a private key of mine.
|
|
|
Bad moderators are moderators with no enemies.
That said, bad moderators might have too many enemies, too. I do not believe that is the case here, however.
/thread
|
|
|
The thread is about brute forcing private keys, not about breaking secp256k1
I will try one more time. This is the algorithm for "bute forcing" a public/private key pair: a) Key public = G, Key private = 1 b) Is Key pubic the key we are looking for? c) If yes Key private is the one you are looking for so quit d) else Key public = Key pubic + G, Key private = Key private + 1 e) goto b) Note the following: The operation Key pubic + G requires many mathematical steps If you are looking for a Bitcoin address you have to do even more mathematical steps on each trial to hash the public key three times Now consider this much easier problem, just Key private = Key private + 1 Imagine a physical device which simply counts the numbers from 1 to n where n is the largest possible private key, a simple 256 bit counter. That is all it does is count. It is only the simplest part of the algorithm described above. This counter can be made using any possible future technology, it just has to obey the laws of physics and thermodynamics. This perfect device will count a fast a physically possible using the lowest physically possible amount of energy to do it. How long would it take to just count from 1 to n? How much energy would it take? BTW n = FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE BAAEDCE6 AF48A03B BFD25E8C D0364141 Hmm, yeah I know I've been saying this in many posts... I was answering Nagan who said that breaking secp256k1 would help brute-forcing private keys
|
|
|
If it does not matter if the solution is visible in public, you might do it using a bitcoin script, so there would be no external system involved except for the blockchain. For the example problem of factoring a large number, you might send the bounty in a transaction with a script that checks whether the product of two (or more) input numbers is actually the target number. If you want to be able to retract the bounty in case no solution is found within some time, you can construct the scriptPubKey such that it is a combination of the factor checking code with the normal scriptPubKey logic. When someone finds a solution, he would post a transaction claiming the bounty and signed with his solution.
Onkel Paul
That still doesn't prevent a miner to steal the coins Why do you think so? To claim the coins, you need to post a transaction with the solution. There would be no other way (except the possible retraction) to access the coins. The miner would see your transaction and replace your address with his
|
|
|
If it does not matter if the solution is visible in public, you might do it using a bitcoin script, so there would be no external system involved except for the blockchain. For the example problem of factoring a large number, you might send the bounty in a transaction with a script that checks whether the product of two (or more) input numbers is actually the target number. If you want to be able to retract the bounty in case no solution is found within some time, you can construct the scriptPubKey such that it is a combination of the factor checking code with the normal scriptPubKey logic. When someone finds a solution, he would post a transaction claiming the bounty and signed with his solution.
Onkel Paul
That still doesn't prevent a miner to steal the coins
|
|
|
North Korea is best Korea
|
|
|
This thread pops up every fortnight
|
|
|
I don't think it's possible How could you know if the output address was modified or not?
|
|
|
I was going to write the order of operations to be made on paper, then I got to RIPEMD-160. No way someone can complete the process (EC generation, EC point conversion, RIPEMD-160 hashing, SHA-256 hashing, base58 conversion and address building) and remain sane.
You would need something like 100-200 pages of paper with boxes printed of them to help you complete the operations, and many many hours...
The EC part seems possible if you are really motivated
|
|
|
You didn't make it for signatures in PMs, do you plan to add it there?
|
|
|
I totally see what you're describing and I agree. Maybe I wasn't clear enough though, it's the form that bothered me. I find it really negative towards other implementations (I don't have developped any). I am not an English native though, did I misunderstand the meaning of the text?
|
|
|
Who's BlackBear? Is he a new global mod? Congratulations bro.
I just voted yes. I am a black guy. I mean bad guy.
|
|
|
The thread is about brute forcing private keys, not about breaking secp256k1
|
|
|
One Bitcointalk "ad" states the following: Creating a Bitcoin client that fully implements the network protocol is extremely difficult. Bitcoin-Qt is the only known safe implementation of a full node. Some other projects attempt to compete, but it is not recommended to use such software for anything serious. (Lightweight clients like Electrum and MultiBit are OK.) Am I the only one seeing a conflict of interests here? Isn't bitcoin-qt the only known safe implementation of a full node because it's buggy and people can't rightly reproduce its bugs behaviour?
|
|
|
Estimating things with the lifetime of universe makes no sense besides measuring capabilities of the current technology. Advances in mathematics/computing will make these calculations feasible after decades at most. By the time Bitcoin (in one form or another) will adopt new algorithms.
Did you read the whole thread? It's physically impossible
|
|
|
Someone PM this guy about bitcoin
|
|
|
I think there is a thread about this in Off-Topic
|
|
|
I made the image uploading available for everybody, not only for voters. That is what was initially planned, I don't know why I put this condition.
I still have to fix the uploading for Chrome.
|
|
|
|