What the OP doesn't want to see or realize is that some language words or combinations of them or even common syllabels already vastly limit the key space. It might be that they can't easily be guessed by an attacker but if you assume such a WIF characters scheme your attack space is already way smaller than a totally random private key. You're just bringing the proven deficiencies of brainwallets to WIF private keys for no reason.
Dear OP, if you think this is a good and safe method, no one here can prevent you from doing so yourself.
But stop telling this is safe. It isn't and multiple users have told you this.
Topic: string value to search for private keys based on WIF (Read 377 times)
In your software, you're generating WIFs with custom characters at the beginning, like "5HpHahMyFirstBitcoinAddress" or "SatoshiNakamoto." While it may seem convenient to generate personalized WIFs, it actually reduces the overall key strength and poses security risks.
Bitcoin private keys are derived from a secure random number generator, ensuring their unpredictability and resistance to brute force attacks. However, by using custom WIFs with specific strings, you are essentially reducing the randomness and predictability of the keys. Attackers who are aware of this custom format can optimize their search by focusing on keys that match the pattern you're using. They can generate WIFs with similar custom strings and systematically search for potential matches. This significantly weakens the security of the private keys generated using your software.
t's crucial to prioritize key strength and randomness to protect your assets.
Using standard WIFs generated from a secure random number generator ensures a higher level of security.
Remember, the strength of Bitcoin lies in its cryptographic algorithms and the randomness of private keys.
While it may be tempting to have personalized WIFs, it's essential to consider the potential risks and vulnerabilities associated with such customization.
It's always better to rely on proven methods and established security practices when it comes to handling private keys and protecting your Bitcoin.
All you are doing is introducing weakness to the key by doing this nothing more. It is no more practical to have a custom WIF than a vanity public key.
Bitcoin private keys are derived from a secure random number generator, ensuring their unpredictability and resistance to brute force attacks. However, by using custom WIFs with specific strings, you are essentially reducing the randomness and predictability of the keys. Attackers who are aware of this custom format can optimize their search by focusing on keys that match the pattern you're using. They can generate WIFs with similar custom strings and systematically search for potential matches. This significantly weakens the security of the private keys generated using your software.
t's crucial to prioritize key strength and randomness to protect your assets.
Using standard WIFs generated from a secure random number generator ensures a higher level of security.
Remember, the strength of Bitcoin lies in its cryptographic algorithms and the randomness of private keys.
While it may be tempting to have personalized WIFs, it's essential to consider the potential risks and vulnerabilities associated with such customization.
It's always better to rely on proven methods and established security practices when it comes to handling private keys and protecting your Bitcoin.
All you are doing is introducing weakness to the key by doing this nothing more. It is no more practical to have a custom WIF than a vanity public key.
Red Flags.
1. No repo for the code so no one can check how these are generated.
2. Not a wise idea to generate WIF in this format easy to brute force.
3. Looks like a bunch of "convincer" accounts trying to sucker people to use this.
Poor effort..
Must try harder.
1. No repo for the code so no one can check how these are generated.
2. Not a wise idea to generate WIF in this format easy to brute force.
3. Looks like a bunch of "convincer" accounts trying to sucker people to use this.
Poor effort..
Must try harder.
Answer for 3: I do not understand , I'm trying to force anyone for use this. It is only showing that we can do a lot with this.
Answer for 2 : No if you do not know what kind "sentences is used" you can't brute force -I can put 0,5 btc on addres and give you a publickey then you can start "bruteforcing", if you will not get the BTC you send me 0,5 btc to my account. can we agree?
Answer 1: It is in pure python. I do not paste it yet to github. No have time.
Red Flags.
1. No repo for the code so no one can check how these are generated.
2. Not a wise idea to generate WIF in this format easy to brute force.
3. Looks like a bunch of "convincer" accounts trying to sucker people to use this.
Poor effort..
Must try harder.
1. No repo for the code so no one can check how these are generated.
2. Not a wise idea to generate WIF in this format easy to brute force.
3. Looks like a bunch of "convincer" accounts trying to sucker people to use this.
Poor effort..
Must try harder.
exactly like this:
Code:
5KGRSasaGRSasaGRSasaGRSasaGRSasaGRSasaGRSasaGNyai9d
but a with a mixed small and big letters.
This is just what I don't understand, why do people think that randomization lacks security? Something that does not follow a deterministic pattern is more secure because it's less predictable, it's as easy as ABC. When you make something that follows predictable pattern can never be more secure, it breaks the law of randomization.
This really drives me crazy, why do you guys think that randomization is a bad practice?
This really drives me crazy, why do you guys think that randomization is a bad practice?
Go ahead and use this. You've been warned multiple times. We can't stop you. But don't expect any sympathy when a bot scanning millions of such addresses each second (as is the case with brain wallets) clears out your funds.
I second this! My approach is to learn on someone's mistakes, probably OPs approach is to only learn on his own mistakes. Then let it be that way. 
If you want to add a note about what your private key is for, then just add a note after the private key?
Why can't you use separate notes to accomplish that?
I don't disagree with this question which is why I said the idea itself is weird. On the other hand, the solution I offered is only aiming to solve the main flaw in OP's idea that was reducing the key's security while making the assumption that there is a reason for having such a scheme. That is from purely a problem solving perspective.
If you randomize some words, it will be perfectly safe. it will be like seed phrase. It is secure.
No, it isn't.Go ahead and use this. You've been warned multiple times. We can't stop you. But don't expect any sympathy when a bot scanning millions of such addresses each second (as is the case with brain wallets) clears out your funds.
Until someone brute forces millions of vanity-wifs and find one with a balance, which as described is trivial to do with modern computers.
You're so arrogant with security. Please avoid using that, you're going to harm yourself.
If you randomize some words, it will be perfectly safe. it will be like seed BTCphrase. It is secure.
When @OP reveal his source code, i'm going to make a vanity WIF with my name printed on it "GRSASA".
exactly like this:
Code:
5KGRSasaGRSasaGRSasaGRSasaGRSasaGRSasaGRSasaGNyai9d
but a with a mixed small and big letters.I gotta post the address then, and put 0.01BTC on it. I'll see then if it gets cracked or not. And if solve any of the 32BTC pzuzle, i gotta also put it in such a private key.
To prove to the community that its safe,
The thing is, nobody will ever know that this address belongs an vanity-wif, so thats why i consider it "Safe".
Until someone brute forces millions of vanity-wifs and find one with a balance, which as described is trivial to do with modern computers. You're so arrogant with security. Please avoid using that, you're going to harm yourself.
Are you honestly asking how an attacker could possibly guess public information which could probably be gathered by anyone in the world in 60 seconds by looking at your social media profiles? Lol.
So you're better win 100 times the Lottery to be that smart for performing all those steps. Or you'd better need to know the past and the future. But its impossible
You could have put your crush's name, your grand's grandfather name or you could write memories, or anything or something about WW2 in your WIF. Nobody will ever be able to find out those words, because it will be exactly like seed phrase. Guys if you don't agree that its safe, i will delete my account here. You, just need to randomizes some words, other than that it's completely safe
The thing is, nobody will ever know that this address belongs an vanity-wif, so thats why i consider it "Safe".
"No one will ever know my address comes from a brain wallet, so I consider it safe." - the owner of every brain wallet, minutes before all their coins were stolen.How on hell could attacker guess my whole family name?
Are you honestly asking how an attacker could possibly guess public information which could probably be gathered by anyone in the world in 60 seconds by looking at your social media profiles? Lol.
I'm agree with you.
hmm maybe some people here have WIFs generate in this way?
I will prepare for github soon the code
hmm maybe some people here have WIFs generate in this way?
I will prepare for github soon the code
The thing is, nobody will ever know that this address belongs an vanity-wif, so thats why i consider it "Safe".
I would love to create a WIF that is easy to remember, that has for example my family name on it. How on hell could attacker guess my whole family name? No way in a trillion years. To everyone now that disagree me again, here a kiss
I would love to create a WIF that is easy to remember, that has for example my family name on it. How on hell could attacker guess my whole family name? No way in a trillion years. To everyone now that disagree me again, here a kiss
This has so many benefits
I honestly recognize no such things as benefits. "Not reducing the key's security" isn't a benefit. It's the normal state in cryptographic key pairs. Obviously, not reducing the key's security is something good, but it is quite obvious to have that security. I neither understand the rest you said. Why can't you use separate notes to accomplish that? 
It's interesting as hobby project, although as other said people shouldn't use it to store their Bitcoin.
I doubt anyone willing to do it for free. But how about storing it on GitHub repository or GitHub pages?
At very least, the part 11 million is key could be brute forced quickly is definitely true. For example, check this VanitySearch benchmark https://bitcointalksearch.org/topic/m.50823897.
Don't forget even "big mafia guy" could make mistake.
is any one able create for me web page ? I would like put the alorithm to webpage
I doubt anyone willing to do it for free. But how about storing it on GitHub repository or GitHub pages?
I don't know why many disagree on the posts i do....
At very least, the part 11 million is key could be brute forced quickly is definitely true. For example, check this VanitySearch benchmark https://bitcointalksearch.org/topic/m.50823897.
I will agree to disagree my agreement if a big mafia guy like Satoshi confirms that he's disagreed about the agreement that i agree with
Don't forget even "big mafia guy" could make mistake.
I don't know why many disagree on the posts i do....
I will agree to disagree my agreement if a big mafia guy like Satoshi confirms that he's disagreed about the agreement that i agree with
Anyways, no body asked you to have 4 randoms characters. I say at least, but from 10 characters, including checksums, you're safe for years. 
I will agree to disagree my agreement if a big mafia guy like Satoshi confirms that he's disagreed about the agreement that i agree with
Anyways, no body asked you to have 4 randoms characters. I say at least, but from 10 characters, including checksums, you're safe for years.
11 millions!
Take it easy tiger! 11 M keys takes less than a second for my laptop to find and there is hashcat, it can search all alphabet, numbers, symbols, all languages, dead or alive and when they take your coins, don't come here whining about it, lol.Last year I talked about vanity private and public keys, it's more of a decorating nature, not that vanity public key is even possible. But vanity private key is a bad idea, memorizing your wife or gf's birthday is the ultimate memory challenge for most men, let alone memorizing a WIF key.
It is not recommended, and it has no use really, because you can never show it off to people, the last 6 chars are nothing to worry about, it would take less than a second, the first 2 characters are limited, so you are too much vulnerable as it is.
AND they DONT even know the "Words" you used for Vanity-WIF. Are they in Capital letters? How many repeated words? Are they written in small letters etc etc
This is effectively a brain wallet. Literally hundreds of thousands brain wallets have been hacked and had their coins stolen because they are fundamentally insecure.but still it would take hundreds of years to manually loop 11 millions time
This is just plain incorrect. Fairly modest hardware is capable of generating in excess of 5 billion keys per second. 11 million is literally nothing.I find it a good idea to use Vanity-WIF, especially to manually remember the WIF
Remembering seed phrases is risky enough. Remembering individual private keys is another level of stupid.BUT its still very safe to use.
You are wrong. What are you talking about? The last 5-6 characters are a checksum, meaning you are only have 4 random characters? So you've just reduced the entropy of your private key from 2256 to 584, which is around 11 million, and could be brute forced in under a second.
Vanity private keys are a seriously dumb idea. No one should ever use this.
Vanity private keys are a seriously dumb idea. No one should ever use this.
I DISAGREE!
Even with 4 characters as you said, it's still perfectly safe to have a vanity WIF. Let's say there are really 11 million combination left to find the address, still with this it's enough security for me. Because when you have an address, obviously no body will know your private key, so they won't even know that you have a vanity-WIF that is vulnerable for attacks and has only 4 Characters AND they DONT even know the "Words" you used for Vanity-WIF. Are they in Capital letters? How many repeated words? Are they written in small letters etc etc, Unless someone decides to search manually 11 Million times in Blockchain searching for random balance address, but still it would take hundreds of years to manually loop 11 millions time and would most likely not possible because they need to exactly know your Vanity-Words that you used for your WIF to be able to manually
search => There are millions of different words! AND they need to guess the correct word with the correct order. If they want to bruteforce the address, as i said they need to know that address actually has vanity WIF and its vanity-words, which is no way to know, so it's not possible and therefore it's definitely safe to have at least 4 random characters for vanity WIF.
I find it a good idea to use Vanity-WIF, especially to manually remember the WIF, if its written with words we like to remember and not random shitty characters that if we lost we don't remember anything of it.
Summary: It does indeed decrease the security of the key. BUT its still very safe to use. It;s like when you reveal your public key, you just reduced your security public key from 256 bits, to 128 bits. AND SO is with the vanity-wif!
-snip-
I still don't see what this achieves other than adding additional risk that you either do something wrong and trash your entropy, or you do something wrong and are unable to recover your coins.If you want to add a note about what your private key is for, then just add a note after the private key? I don't see how this:
Code:
MyFirstBitcoinAddress1qvpkmem0ne8c5mc2mx69733mxcq206rfhwnln8g5p7javkv26f6dsqdk50w
Is any better to this:
Code:
My first bitcoin address
5JYkir7TsJ4L8bJroCuLgjxxNdbEUgvjVKdUgnwhDMFF5yM2dYu
is any one able create for me web page ? I would like put the alorithm to webpage
Unless you're plannng to perform the entire vanity calculation in client side Javascript, you're going to need a server for balding the heavy lifting of the calculations.
Why would you want that? I can understand to an extent why vanity addresses can be useful, but this is, besides dangerously dumb, completely meaningless. If you want to memorize a password / phrase and use that as private key, simply use brainwallet (which is also not recommended). Messing with the private key, the cryptographic piece that needs to be as random as possible, is a recipe for disaster.
Slowly I'm becoming more and more of the position that it's better to use HD seeds instead of individual private keys, for privacy purposes, and since (an array of) vanity addresses cannot be generated from HD seeds, it doesn't really make much sense to use them anymore.
Maybe in a very weird way we could find a utility for something like this. For example having an indicator of what the private key was used for (eg. MyHotWallet). But as others mentioned you are reducing the security of the private key so here is a better idea: why don't you use a different encoding and change the algorithm itself?
that means instead of modifying the key itself, you could just add extra bits on top of the untouched random 256-bit key to indicate the utility.
You don't even have to reinvent the wheel, there is Bech32[1] encoding that is very suitable for this purpose. You just replace the HRP part with the string you want. It can contain between 1 to 83 US-ASCII characters then use the key bytes as the data part without modifying it at all. So your final key string would become something like this: MyFirstBitcoinAddress1{unchanged 256-bit encoded key} where 1 is the default separator.
I used a version byte (=0) and the BIP350 (Bech32m)[2] in the following:
5JYkir7... is a randomly generated key without modification and second line MyFirs.... is the different encoding of the same exact key without any difference between the key bytes whatsoever.
This has so many benefits:
- It doesn't reduce key security
- The restriction on the size of the "string" you use at the beginning is big enough (83 chars) to contain any note
- You don't have to write that much code to guess the range like you did here, everything is pretty straight forward and you can use already existing Bech32 encoding libraries
- The code and the result is neat and is easy to verify so the chance of bugs is minimal
- The encoding is fast and has a checksum and error detection built in.
- It can contain a version for future expansion of the algorithm
[1] https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki
[2] https://github.com/bitcoin/bips/blob/master/bip-0350.mediawiki
that means instead of modifying the key itself, you could just add extra bits on top of the untouched random 256-bit key to indicate the utility.
You don't even have to reinvent the wheel, there is Bech32[1] encoding that is very suitable for this purpose. You just replace the HRP part with the string you want. It can contain between 1 to 83 US-ASCII characters then use the key bytes as the data part without modifying it at all. So your final key string would become something like this: MyFirstBitcoinAddress1{unchanged 256-bit encoded key} where 1 is the default separator.
I used a version byte (=0) and the BIP350 (Bech32m)[2] in the following:
Code:
5JYkir7TsJ4L8bJroCuLgjxxNdbEUgvjVKdUgnwhDMFF5yM2dYu
MyFirstBitcoinAddress1qvpkmem0ne8c5mc2mx69733mxcq206rfhwnln8g5p7javkv26f6dsqdk50w
This has so many benefits:
- It doesn't reduce key security
- The restriction on the size of the "string" you use at the beginning is big enough (83 chars) to contain any note
- You don't have to write that much code to guess the range like you did here, everything is pretty straight forward and you can use already existing Bech32 encoding libraries
- The code and the result is neat and is easy to verify so the chance of bugs is minimal
- The encoding is fast and has a checksum and error detection built in.
- It can contain a version for future expansion of the algorithm
[1] https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki
[2] https://github.com/bitcoin/bips/blob/master/bip-0350.mediawiki
Nice, any windows binary? I don't use python.
This is good for display, not real world use to store.
Also can we count how many of a certain checksum exist in a subgroup?
This is good for display, not real world use to store.
Also can we count how many of a certain checksum exist in a subgroup?
at the moment there is no binary for windows, I will try do it later
about checksum -> I understand the question -> I will give an answer during few days
Nice, any windows binary? I don't use python.
This is good for display, not real world use to store.
Also can we count how many of a certain checksum exist in a subgroup?
This is good for display, not real world use to store.
Also can we count how many of a certain checksum exist in a subgroup?
Why would you want that? I can understand to an extent why vanity addresses can be useful, but this is, besides dangerously dumb, completely meaningless. If you want to memorize a password / phrase and use that as private key, simply use brainwallet (which is also not recommended). Messing with the private key, the cryptographic piece that needs to be as random as possible, is a recipe for disaster.
its not dangerous as long as at least 10 of the last WIF characters are random. The rest of 40 characters could be anything
What are you talking about? The last 5-6 characters are a checksum, meaning you are only have 4 random characters? So you've just reduced the entropy of your private key from 2256 to 584, which is around 11 million, and could be brute forced in under a second.Vanity private keys are a seriously dumb idea. No one should ever use this.
is any one able create for me web page ? I would like put the alorithm to webpage
its not dangerous as long as at least 10 of the last WIF characters are random. The rest of 40 characters could be anything
it is not dangerous:) if you can create your own "WIF" with info only for you. it doesn't matter.
It is the part of my study of curve.
It is the part of my study of curve.
Why would you want to have some known string sequence of characters in your WIF representation of private keys? Private keys are supposed to be a) random (as random as possible!) and b) not to be shown around. I guess b) was not on the priority list at all, but frankly you're shaving off some amount of bits of security from your private key(s) if you do something what you offer here.
I get the point for public addresses and I have created vanity addresses for myself in the past. But why for private keys? Sounds like a dangerous idea to me.
I get the point for public addresses and I have created vanity addresses for myself in the past. But why for private keys? Sounds like a dangerous idea to me.
here you are:
Compressed :
uncompressed:
or maybe in this subgroups:
this is cool for generating your own "privatekey" based on WIF which is very to remember.
It can be a sentence too:)
those are better:
or:
or:
Compressed :
Code:
Searching WIF start as GRSasa
start: 0x78be90f12cd4ead02411f350c27c3534c1dd9cef6ea59cdde38bc56026bc0510 stop: 0x78be90f13032b0a79f95c3cc526b26bf439aa3c77257487bb2b17c06d591641f
start_WIF L1GRSasa11111111111111111111111111111111111111BsxryJ stop_WIF L1GRSasazzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzWJja3dc
keys in subgroup 354512775363558264085012132446457683411694831749672966032882753295
Searching WIF start as GRSasa
start: 0x9694f090ba8a5b2069615b37d1b8ac0a5411641080a3c59b7967a39107502910 stop: 0x9694f090bde820f7e4e52bb361a79d94d5ce6ae884557139488d5a37b625881f
start_WIF L2GRSasa11111111111111111111111111111111111111AWbd1e stop_WIF L2GRSasazzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzWLm9i7D
keys in subgroup 354512775363558264085012132446457683411694831749672966032882753295
Searching WIF start as GRSasa
start: 0xb46b5030483fcb70aeb0c31ee0f522dfe6452b3192a1ee590f4381c1e7e44d10 stop: 0xb46b50304b9d91482a34939a70e4146a68023209965399f6de69386896b9ac1f
start_WIF L3GRSasa111111111111111111111111111111111111119LgvHE stop_WIF L3GRSasazzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzWFGh4Dy
keys in subgroup 354512775363558264085012132446457683411694831749672966032882753295
Searching WIF start as GRSasa
start: 0xd241afcfd5f53bc0f4002b05f03199b57878f252a4a01716a51f5ff2c8787110 stop: 0xd241afcfd95301986f83fb8180208b3ffa35f92aa851c2b474451699774dd01f
start_WIF L4GRSasa11111111111111111111111111111111111111BcyGtL stop_WIF L4GRSasazzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzWFJHaTc
keys in subgroup 354512775363558264085012132446457683411694831749672966032882753295
Searching WIF start as GRSasa
start: 0xf0180f6f63aaac11394f92ecff6e108b0aacb973b69e3fd43afb3e23a90c9510 stop: 0xf0180f6f670871e8b4d363688f5d02158c69c04bba4feb720a20f4ca57e1f41f
start_WIF L5GRSasa111111111111111111111111111111111111118P3E8a stop_WIF L5GRSasazzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzWKMQCGw
keys in subgroup 354512775363558264085012132446457683411694831749672966032882753295
uncompressed:
Code:
start: 0x3b580a2c2019179b5a6d36cf6a0118a1932833d5fa9e4bc03d8648e4d8d42800 stop: 0x3b580a2c2ef4c775c2376de7f6f39b04ea47378f6c06c5a4ea500df9843b4fff
start_WIF 5JGRSasa11111111111111111111111111111111111116wG6Qk stop_WIF 5JGRSasazzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzztdDoZ5
keys in subgroup 1564746042983981303547639757005054602644722015998556539731344566271
Searching WIF start as GRSasa
start: 0xbf0a3d799a661029ca23f8964c267496daaba2c03861348971ddfa49d28e2800 stop: 0xbf0a3d79a941c00431ee2faed918f6fa31caa679a9c9ae6e1ea7bf5e7df54fff
start_WIF 5KGRSasa11111111111111111111111111111111111111Rgoro stop_WIF 5KGRSasazzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzJQ7cr
keys in subgroup 1564746042983981303547639757005054602644722015998556539731344566271
or maybe in this subgroups:
Code:
Searching WIF start as GRSasaGRSasaGRSasaGRSasa
start: 0x3b580a2c240c70a374aa4b719ff418e58154a4793fc6a664ba7920853b8da8df stop: 0x3b580a2c240c70a374aa4b719ff418e5815a1ad697cfdd0181626e6393f79ce7
start_WIF 5JGRSasaGRSasaGRSasaGRSasa11111111111111111117tBvtA stop_WIF 5JGRSasaGRSasaGRSasaGRSasazzzzzzzzzzzzzzzzzzzzWneHe
keys in subgroup 28362204090837958306195533214643208
Searching WIF start as GRSasaGRSasaGRSasaGRSasa
start: 0xbf0a3d799e596931e4610d38821974dac8d813637d898f2deed0d1ea3547a8de stop: 0xbf0a3d799e596931e4610d38821974dac8dd89c0d592c5cab5ba1fc88db19ce6
start_WIF 5KGRSasaGRSasaGRSasaGRSasa11111111111111111113UF486 stop_WIF 5KGRSasaGRSasaGRSasaGRSasazzzzzzzzzzzzzzzzzzzuD5m5t
keys in subgroup 28362204090837958306195533214643208
Code:
Searching WIF start as GRSasaGRSasaGRSasaGRSasaGRSasa
start: 0x3b580a2c240c70a374aa4b719ff418e5815618478a5f140e267c0a8aa42d6e38 stop: 0x3b580a2c240c70a374aa4b719ff418e5815618478a5fb1d225352934b87fe6c7
start_WIF 5JGRSasaGRSasaGRSasaGRSasaGRSasa11111111111111mBGtj stop_WIF 5JGRSasaGRSasaGRSasaGRSasaGRSasazzzzzzzzzzzzzyJuk4X
keys in subgroup 745027007640379820505231
Searching WIF start as GRSasaGRSasaGRSasaGRSasaGRSasa
start: 0xbf0a3d799e596931e4610d38821974dac8d98731c821fcd75ad3bbef9de76e39 stop: 0xbf0a3d799e596931e4610d38821974dac8d98731c8229a9b598cda99b239e6c6
start_WIF 5KGRSasaGRSasaGRSasaGRSasaGRSasa11111111111118c3mhT stop_WIF 5KGRSasaGRSasaGRSasaGRSasaGRSasazzzzzzzzzzzzzto4v1B
keys in subgroup 74502700764037982050522
this is cool for generating your own "privatekey" based on WIF which is very to remember.
It can be a sentence too:)
those are better:
Code:
Searching WIF start as GRSasaBitcoinAddress
start: 0x3b580a2c22d843f3077ee563f199bd8bde719293a29e0666f7e2e8a2f38a8d8f stop: 0x3b580a2c22d843f3077ee563f199c13b167d33180e6f075f617a6f780a1bd70f
start_WIF 5JGRSasaBitcoinAddress111111111111111111111113v9uk5 stop_WIF 5JGRSasaBitcoinAddresszzzzzzzzzzzzzzzzzzzzzzzscBot6
keys in subgroup 320960769145151391820228526841377015810432
Searching WIF start as GRSasaBitcoinAddress
start: 0xbf0a3d799d253c817735a72ad3bf198125f5017de060ef302c3a9a07ed448d8f stop: 0xbf0a3d799d253c817735a72ad3bf1d305e00a2024c31f02895d220dd03d5d710
start_WIF 5KGRSasaBitcoinAddress111111111111111111111115Z4FBS stop_WIF 5KGRSasaBitcoinAddresszzzzzzzzzzzzzzzzzzzzzzzxi5hWj
keys in subgroup 320960769145151391820228526841377015810433
or:
Code:
Searching WIF start as GRSasaFirstBitcoinAddress
start: 0x3b580a2c23de8e0385e7c069b3a54f5fd35d1b090b7cd6fa1e806249bd7d1042 stop: 0x3b580a2c23de8e0385e7c069b3a54f5fd35d33252313114c453dc925d97ee3e8
start_WIF 5JGRSasaFirstBitcoinAddress11111111111111111168JBt9 stop_WIF 5JGRSasaFirstBitcoinAddresszzzzzzzzzzzzzzzzzzrz4FZV
keys in subgroup 489003518807551005279233331286950
Searching WIF start as GRSasaFirstBitcoinAddress
start: 0xbf0a3d799e2b8691f59e823095caab551ae089f3493fbfc352d813aeb7371042 stop: 0xbf0a3d799e2b8691f59e823095caab551ae0a20f60d5fa1579957a8ad338e3e9
start_WIF 5KGRSasaFirstBitcoinAddress1111111111111111115B3zkB stop_WIF 5KGRSasaFirstBitcoinAddresszzzzzzzzzzzzzzzzzzxUXq3C
keys in subgroup 489003518807551005279233331286951
or:
Code:
Searching WIF start as GRSasaSecondBitcoinAddress
start: 0x3b580a2c26ab25826ef457da2f86838b8c9c0968622dbde2e73b10b38c0ea40d stop: 0x3b580a2c26ab25826ef457da2f86838b8c9c09d2cc8431a686cb92798c8a422e
start_WIF 5JGRSasaSecondBitcoinAddress111111111111111111fMANh stop_WIF 5JGRSasaSecondBitcoinAddresszzzzzzzzzzzzzzzzzxRDGZU
keys in subgroup 8431095151854327677228160884257
Searching WIF start as GRSasaSecondBitcoinAddress
start: 0xbf0a3d79a0f81e10deab19a111abdf80d41f78529ff0a6ac1b92c21885c8a40d stop: 0xbf0a3d79a0f81e10deab19a111abdf80d41f78bd0a471a6fbb2343de8644422e
start_WIF 5KGRSasaSecondBitcoinAddress1111111111111111148dW9g stop_WIF 5KGRSasaSecondBitcoinAddresszzzzzzzzzzzzzzzzzwFcPNf
keys in subgroup 8431095151854327677228160884257
Cool! i am interested in about getting my own private key with the name "GR Sasa" on it
For example: find all WIF and privatekeys with word "SatoshiNakamoto"
Code:
Searching WIF start as SatoshiNakamoto
start: 0x7df8fd47b8adc531d23d23045835ff6fd4e1f25c7b884d44bbea04392b358a8f stop: 0x7df8fd47b8adc531d23d2325007c9d5c7b97992fe3540dd538f1eade837d036c
start_WIF L1SatoshiNakamoto1111111111111111111111111111C1e5EHz stop_WIF L1SatoshiNakamotozzzzzzzzzzzzzzzzzzzzzzzzzzzzcdrrXuE
keys in subgroup 47728737653408320482570141828681379189357908818141
Searching WIF start as SatoshiNakamoto
start: 0x9bcf5ce746633582178c8aeb677276456715b97d8d86760251c5e26a0bc9ae8f stop: 0x9bcf5ce746633582178c8b0c0fb914320dcb6050f5523692cecdc90f6411276c
start_WIF L2SatoshiNakamoto1111111111111111111111111111BzjmUx7 stop_WIF L2SatoshiNakamotozzzzzzzzzzzzzzzzzzzzzzzzzzzzcf6XpRa
keys in subgroup 47728737653408320482570141828681379189357908818141
Searching WIF start as SatoshiNakamoto
start: 0xb9a5bc86d418a5d25cdbf2d276aeed1af949809e9f849ebfe7a1c09aec5dd28f stop: 0xb9a5bc86d418a5d25cdbf2f31ef58b079fff277207505f5064a9a74044a54b6c
start_WIF L3SatoshiNakamoto1111111111111111111111111111C4CkK1V stop_WIF L3SatoshiNakamotozzzzzzzzzzzzzzzzzzzzzzzzzzzzcZ7RY2E
keys in subgroup 47728737653408320482570141828681379189357908818141
Searching WIF start as SatoshiNakamoto
start: 0xd77c1c2661ce1622a22b5ab985eb63f08b7d47bfb182c77d7d7d9ecbccf1f68f stop: 0xd77c1c2661ce1622a22b5ada2e3201dd3232ee93194e880dfa85857125396f6c
start_WIF L4SatoshiNakamoto1111111111111111111111111111C2CptqM stop_WIF L4SatoshiNakamotozzzzzzzzzzzzzzzzzzzzzzzzzzzzceSfktD
keys in subgroup 47728737653408320482570141828681379189357908818141
Searching WIF start as SatoshiNakamoto
start: 0xf5527bc5ef838672e77ac2a09527dac61db10ee0c380f03b13597cfcad861a8f stop: 0xf5527bc5ef838672e77ac2c13d6e78b2c466b5b42b4cb0cb906163a205cd936c
start_WIF L5SatoshiNakamoto1111111111111111111111111111BzSuApY stop_WIF L5SatoshiNakamotozzzzzzzzzzzzzzzzzzzzzzzzzzzzce1dCbo
keys in subgroup 47728737653408320482570141828681379189357908818141
If anyone is interested - I have created software in Python.
The software takes a string value to search for private keys based on WIF (Wallet Import Format).
It shows the beginning and end of each private key. For example, if we want to find private keys for the string "MyFirstBitcoinAddress", it also shows how many common keys there are within a given WIF subset.
The result is:
The software takes a string value to search for private keys based on WIF (Wallet Import Format).
It shows the beginning and end of each private key. For example, if we want to find private keys for the string "MyFirstBitcoinAddress", it also shows how many common keys there are within a given WIF subset.
The result is:
Code:
Searching WIF start as 5HpHahMyFirstBitcoinAddress
start: 0x000000b20494e6aa64f202a21999c6978d2aa36948866a34e10ace204b652841 stop: 0x000000b20494e6aa64f202a21999c6978d2abb85601ca48707c834fc6766fbe8
start_WIF 5HpHahMyFirstBitcoinAddress1111111111111111111m9jPu stop_WIF 5HpHahMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzvTh5GX
keys in subgroup 489003518807551005279233331286951
Searching WIF start as 5HpHaiMyFirstBitcoinAddress
start: 0x000001754367b8a6422e013e3c5327fc60b7943f89682b236c6c91bca2eec841 stop: 0x000001754367b8a6422e013e3c5327fc60b7ac5ba0fe65759329f898bef09be8
start_WIF 5HpHaiMyFirstBitcoinAddress1111111111111111112rYTS2 stop_WIF 5HpHaiMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzwQXqKE
keys in subgroup 489003518807551005279233331286951
Searching WIF start as 5HpHajMyFirstBitcoinAddress
start: 0x00000238823a8aa21f69ffda5f0c896134448515ca49ec11f7ce5558fa786842 stop: 0x00000238823a8aa21f69ffda5f0c896134449d31e1e026641e8bbc35167a3be8
start_WIF 5HpHajMyFirstBitcoinAddress1111111111111111118YwHuB stop_WIF 5HpHajMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzvmSWet
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHakMyFirstBitcoinAddress
start: 0x000002fbc10d5c9dfca5fe7681c5eac607d175ec0b2bad00833018f552020842 stop: 0x000002fbc10d5c9dfca5fe7681c5eac607d18e0822c1e752a9ed7fd16e03dbe8
start_WIF 5HpHakMyFirstBitcoinAddress1111111111111111114mBgAB stop_WIF 5HpHakMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzwd2Mkt
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHamMyFirstBitcoinAddress
start: 0x000003beffe02e99d9e1fd12a47f4c2adb5e66c24c0d6def0e91dc91a98ba842 stop: 0x000003beffe02e99d9e1fd12a47f4c2adb5e7ede63a3a841354f436dc58d7be8
start_WIF 5HpHamMyFirstBitcoinAddress1111111111111111117X99d8 stop_WIF 5HpHamMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzsaEm4k
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHanMyFirstBitcoinAddress
start: 0x000004823eb30095b71dfbaec738ad8faeeb57988cef2edd99f3a02e01154842 stop: 0x000004823eb30095b71dfbaec738ad8faeeb6fb4a485692fc0b1070a1d171be8
start_WIF 5HpHanMyFirstBitcoinAddress1111111111111111117DHqDC stop_WIF 5HpHanMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzqJRdtx
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHaoMyFirstBitcoinAddress
start: 0x000005457d85d2919459fa4ae9f20ef48278486ecdd0efcc255563ca589ee841 stop: 0x000005457d85d2919459fa4ae9f20ef48278608ae5672a1e4c12caa674a0bbe9
start_WIF 5HpHaoMyFirstBitcoinAddress1111111111111111111ftdQk stop_WIF 5HpHaoMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzybSsMG
keys in subgroup 489003518807551005279233331286952
Searching WIF start as 5HpHapMyFirstBitcoinAddress
start: 0x00000608bc58a48d7195f8e70cab7059560539450eb2b0bab0b72766b0288842 stop: 0x00000608bc58a48d7195f8e70cab7059560551612648eb0cd7748e42cc2a5be9
start_WIF 5HpHapMyFirstBitcoinAddress1111111111111111116BeMtK stop_WIF 5HpHapMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzyhRRbo
keys in subgroup 489003518807551005279233331286951
Searching WIF start as 5HpHaqMyFirstBitcoinAddress
start: 0x000006cbfb2b76894ed1f7832f64d1be29922a1b4f9471a93c18eb0307b22841 stop: 0x000006cbfb2b76894ed1f7832f64d1be29924237672aabfb62d651df23b3fbe9
start_WIF 5HpHaqMyFirstBitcoinAddress1111111111111111112SjG9y stop_WIF 5HpHaqMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzziSmzW
keys in subgroup 489003518807551005279233331286952
Searching WIF start as 5HpHarMyFirstBitcoinAddress
start: 0x0000078f39fe48852c0df61f521e3322fd1f1af190763297c77aae9f5f3bc842 stop: 0x0000078f39fe48852c0df61f521e3322fd1f330da80c6ce9ee38157b7b3d9be8
start_WIF 5HpHarMyFirstBitcoinAddress1111111111111111116MWHW3 stop_WIF 5HpHarMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzuZi92v
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHasMyFirstBitcoinAddress
start: 0x0000085278d11a810949f4bb74d79487d0ac0bc7d157f38652dc723bb6c56842 stop: 0x0000085278d11a810949f4bb74d79487d0ac23e3e8ee2dd87999d917d2c73be8
start_WIF 5HpHasMyFirstBitcoinAddress1111111111111111115UEQnq stop_WIF 5HpHasMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzrHb1rA
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHatMyFirstBitcoinAddress
start: 0x00000915b7a3ec7ce685f3579790f5eca438fc9e1239b474de3e35d80e4f0841 stop: 0x00000915b7a3ec7ce685f3579790f5eca43914ba29cfeec704fb9cb42a50dbe9
start_WIF 5HpHatMyFirstBitcoinAddress1111111111111111112DJriK stop_WIF 5HpHatMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzz5aJNk
keys in subgroup 489003518807551005279233331286952
Searching WIF start as 5HpHauMyFirstBitcoinAddress
start: 0x000009d8f676be78c3c1f1f3ba4a575177c5ed74531b7563699ff97465d8a842 stop: 0x000009d8f676be78c3c1f1f3ba4a575177c605906ab1afb5905d605081da7be8
start_WIF 5HpHauMyFirstBitcoinAddress1111111111111111117y41Ah stop_WIF 5HpHauMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzqJrfar
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHavMyFirstBitcoinAddress
start: 0x00000a9c35499074a0fdf08fdd03b8b64b52de4a93fd3651f501bd10bd624842 stop: 0x00000a9c35499074a0fdf08fdd03b8b64b52f666ab9370a41bbf23ecd9641be9
start_WIF 5HpHavMyFirstBitcoinAddress1111111111111111117R3kds stop_WIF 5HpHavMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzx2JnA4
keys in subgroup 489003518807551005279233331286951
Searching WIF start as 5HpHawMyFirstBitcoinAddress
start: 0x00000b5f741c62707e39ef2bffbd1a1b1edfcf20d4def740806380ad14ebe841 stop: 0x00000b5f741c62707e39ef2bffbd1a1b1edfe73cec753192a720e78930edbbe9
start_WIF 5HpHawMyFirstBitcoinAddress1111111111111111112Ko1xG stop_WIF 5HpHawMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzwioT4f
keys in subgroup 489003518807551005279233331286952
Searching WIF start as 5HpHaxMyFirstBitcoinAddress
start: 0x00000c22b2ef346c5b75edc822767b7ff26cbff715c0b82f0bc544496c758842 stop: 0x00000c22b2ef346c5b75edc822767b7ff26cd8132d56f2813282ab2588775be8
start_WIF 5HpHaxMyFirstBitcoinAddress1111111111111111119EjraJ stop_WIF 5HpHaxMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzztmkp42
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHayMyFirstBitcoinAddress
start: 0x00000ce5f1c2066838b1ec64452fdce4c5f9b0cd56a2791d972707e5c3ff2842 stop: 0x00000ce5f1c2066838b1ec64452fdce4c5f9c8e96e38b36fbde46ec1e000fbe8
start_WIF 5HpHayMyFirstBitcoinAddress1111111111111111118ss9te stop_WIF 5HpHayMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzztwFpGX
keys in subgroup 489003518807551005279233331286950
Searching WIF start as 5HpHazMyFirstBitcoinAddress
start: 0x00000da93094d86415edeb0067e93e499986a1a397843a0c2288cb821b88c842 stop: 0x00000da93094d86415edeb0067e93e499986b9bfaf1a745e4946325e378a9be9
start_WIF 5HpHazMyFirstBitcoinAddress1111111111111111116UdFTB stop_WIF 5HpHazMyFirstBitcoinAddresszzzzzzzzzzzzzzzzzzyYXgd3
keys in subgroup 489003518807551005279233331286951
Jump to: