Topic: Python BTC Local Webserver (Read 370 times)

I can make a custom WIF so you can easily find private key for it? We know the limit for desktop computers with puzzle transaction. #64 and #120 stay unbreakable even we know exactly the ranges. WIFs have a lot more to bruteforce. You can ask PawGo about it. He is an expert on WIFs. Probably knows the limit of unknown chars.
The chances to find custom WIFs  by bruteforce are the same as to bump into some randomly generated private key by some custom-devised bruteforce algorithm.

I saw your github PawGo. Perfect!!! Of course for vanity WIFs you do not need webserver. Can be done separately.

Exactly so. I do not put here functionality like recovering WIFs or kangaroo jumps.
But you can use it to make custom WIFs just use base58 alphabet(123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz):

5JDoNotSteaLBitcoinMightGetYouinPrisonSomeTimeXXXXX
5JBadAddressDoNotSendAssetsYouMightLoseitALLXXXXXXX
5HpJ2UnLimitedNoLimitTheReaLThingFacesJumpForJoyXXX
5K1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uFAddressXXXXXXXX

Warning message is pointless if the user have intention to steal someone else Bitcoin.


But any project don't need to have other practical use beside use case intended by it's creator.

The whole point for me of this script is secp256k1-curve testing ground. There is functionality to view subgroup structure and change generator point(since we are in a cyclic group of prime order where any element except identity can be a generator and generates the entire group). Balance check is just for fun. Guess no software exists there that can help you get private key of some wallet since the range is enourmous(i mean the upper range where all rich wallets reside). Could be some math solution like getting private key from public key, as i know there are ways(like point subtraction and scalar division) but all require some condition that appear to be hard to supply.

It goes off-topic but when I think about it, I think it is not worst than brain wallet. At the end, what we receive from brain wallet is not "random" too. And knowing part of brainwallet we may try to brute-force the rest. At the end in one case we talk about sha256 and in other case as a base58 decoding.
The idea behind Vanity WIF (do not blame me, I have never did that personally, I was just contacted by some people who use my program to generate that WIFs) is to be able to remember WIF partially, knowing that it is technically possible to restore the missing part. That way we may have known "human readable" part (date, sentence, etc). and have part which is calculated by program, looking for a correct (importable) WIf. Of course one may decide to do extra steps, like prepare WIF in uncompressed form, extract private key and then use it in compressed form - but it is an extra complication, which could cause other problems ("I forgot how I did that 5 years ago").

As a Post Scriptum I may add that we all are humans, years of evolution caused we have ability to find patterns. We may say one text "is random" while other is not. We may say that WIF cannot contain the same characters repeated 10 times, because we feel it is unnatural. But the chance for that is exactly like the chance for any other combination. Additionally, let's do not forget about different languages. English words has no meaning in Dutch or Spanish and vice versa. Random letters would mean nothing for me, but they could be a "Hello World" in Chinese.
Like they say, if you take many monkeys and they will press random typewriter keys for a long enough, one of them will finally write the whole "Hamlet".

That's a terrible idea. If the private key isn't random, it can be brute-forced much easier.

And now you are talking about something interesting. Kind of Vanity WIFs ;-)
I know some people may use my WifSolverCuda as a "cracker" for their manually generated WIFs. You may for example remember that you wanted to have "5JVeryConfusedxxxxxxxxPersonWithDementiaAndBackPain" and all you need is to find 8 unknown characters which would produce the correct WIF.

Let's keep is aside, as it is very difficult problem. Owner may have strong proof that he owns coins moved, but on opposite it will be difficult for him to proof that it was not him who moved the coin. On the other hand, talking about about keeping what you found - in some jurisdiction you are obliged to return it to the state - if for example you find a 500 year old coin on beach.

Project is interesting, especially idea to create a "subsets" of results modifying generator point. However I am not sure about any practical use (in terms of BTC).

This is a whole different subject (ethical vs. technical), but if you guess a private key that holds some balance, technically you 'found' the coins.
If transferring them is a crime or not will probably depend on your jurisdiction. I believe that keeping something you found isn't illegal everywhere.

As a Bitcoin user, this isn't something I worry about. Let them try! I don't think a warning matters, anyone who uses Bitcoin should understand this already.

I'll test it when I have more time

The project is awesome, and thanks for making it open source... But there is a problem with it. Is not ethical to create a tool for the users to steal coins in case they find a private key with balance.

I know it would be awesome to fin a key with more than 100 BTC, but in the moment we spend those coins we will become criminals.

I hope you can add this kind of warning to your software on the ReadMe file.

This is great tool, it reminds me of directory.io. But i'd like to mention the private key/address is overlapped on my browser (Firefox).




I add address from 1st page to bloomfilter and restart the server, only to found out the sound is quite loud. A warning would be appreciated in future .


I only try it with small txt file, but what's RAM usage of this tool use when we use list address from Loyce?

Nice work.

So if I'm reading this correctly, this webserver only supports secp256k1 points, right? I just read the part where the generator point can be changed from G of secp256k1, but didn't see any information about lists of curves.

Hello

If I have well understood, it is like a key.lol server without the balance check feature ?

Or do I miss something ? Your github doesn't give a lot of explanations.

Have a great day 

A-one.