Maybe he did find out the private key, but decided to not send the coins to another wallet. This is to me the only reason why there are new input to that address.
The new inputs are dust, which is either spam or meant for tracking. It doesn't prove someone has the private key. 
Topic: 25BTC damaged paper wallet - Fake? (Read 687 times)
Maybe he did find out the private key, but decided to not send the coins to another wallet. This is to me the only reason why there are new input to that address.
you thant say what hi is mad man...
I think this is children pfotoshop, maked as a joke...
Maybe he did find out the private key, but decided to not send the coins to another wallet. This is to me the only reason why there are new input to that address.
Who knows, maybe they went on a journey to learn C# or Python to be able to run the provided code!!!
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
Here we are 426 days + later and...nothing happens
Well, all thanks to you and your FinderOuter, its amazing and works perfect. But I will like to know if its dependent on GPU and/or CPU ? How can the speed be increased ?? As I noticed its faster with fewer characters to find and slower with much more characters...For CPU you may also try https://github.com/PawelGorny/WifSolver
For GPU: https://github.com/PawelGorny/WifSolverCuda but it will not work for cases where the end is totally destroyed (it is using checksum collision algorithm).
For the case from the OP, the best would be BitCrack, simple iteration over possible keys. But as I do not know the number of known/missing characters, it is difficult to evaluate the time needed.
But I will like to know if its dependent on GPU and/or CPU ?
FinderOuter is only running on CPU but I have plans to add GPU support. You can see the roadmap here:https://github.com/Coding-Enthusiast/FinderOuter/issues/47
How can the speed be increased ?? As I noticed its faster with fewer characters to find and slower with much more characters...
Obviously if your key is missing less characters it is faster to find those missing and each missing character multiplies the total number of permutations by 58. There is a new option to manually reduce this search space in v0.15.0.0. See issue #58 for more info. Who knows, maybe they went on a journey to learn C# or Python to be able to run the provided code!!!
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
Here we are 426 days + later and...nothing happens
Well, all thanks to you and your FinderOuter, its amazing and works perfect. But I will like to know if its dependent on GPU and/or CPU ? How can the speed be increased ?? As I noticed its faster with fewer characters to find and slower with much more characters... I believe that wallet recovery tools, especially the ones written in Python, should least have an introductory tutorials/documents/videos about the language.
My philosophy is that users shouldn't have to spend time learning anything in order to use a tool. For example nobody spends time learning how to use a web browser just to visit a website, while there is a lot going on in the background that user doesn't even see.This is why in FinderOuter I've focused on a user friendly UI where they have to fill boxes instead of a command line tool where they have to first learn the commands and then type in those commands.
Because we keep telling people to brute-force passwords or a few characters of secret keys, but almost nobody here really knows how to write such a script (that's intuitive and easy to use by newbies, not some hacked-together spaghetti code like the kind I cook up).
It is really a tough to create a tool that is easy to use, sometimes you think you've made it easy but in fact it was the opposite. For instance I believed that separating the derivation path and the key index makes it more clear in mnemonic recovery but it turned out it was more confusing.The other issue is lack of feedback. My repository is getting about 50 visitors per day and about a dozen clones and yet over the past year I've only received only a handful of bug reports or suggestions.
it seems that bitaddress version (1.6) dates from 11 Jan 2014..don't exist in 2012 
Bitaddress 1.6 was introduced on 29 July 2012. Nothing was introduced on 11 Jan 2014.The releases that you see on github was just the date it was published. The actual versions were actually published pretty early: https://github.com/pointbiz/bitaddress.org/commits/master?after=72aefc03e0d150c52780294927d95262b711f602+139&branch=master
Who knows, maybe they went on a journey to learn C# or Python to be able to run the provided code!!!
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
I believe that wallet recovery tools, especially the ones written in Python, should least have an introductory tutorials/documents/videos about the language. I single out Python specifically because it's easy to write and run. And only the parts that are necessary to use the script or understand how it works. Because we keep telling people to brute-force passwords or a few characters of secret keys, but almost nobody here really knows how to write such a script (that's intuitive and easy to use by newbies, not some hacked-together spaghetti code like the kind I cook up). Heck, even I'm not sure how I'd go about and write a Python brute-forcer doesn't that isn't insanely slow from bad programming.
We see this frequently with GPU-accelerated private key crackers here. Almost nobody here knows CUDA and OpenCL programming, let alone algorithmic optimizations like bloom filters. And I think that contributes to why people give up on otherwise easy-sounding tasks; they're just too daunting to do alone.
it seems that bitaddress version (1.6) dates from 11 Jan 2014..don't exist in 2012
Who knows, maybe they went on a journey to learn C# or Python to be able to run the provided code!!!
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
Most people think others are gonna scam that guy with private key. But probably that guy is gonna scam others with random address (visible) and random pvt key. After people message them, he'll sell that to them for 1 btc or something. When you bruteforce it, you'll realise that he scammed you when you didn't get the address in that range...
Who knows, maybe they went on a journey to learn C# or Python to be able to run the provided code!!!
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
At least that question led me to add a new feature to FinderOuter to make it possible for users to recover their WIFs missing up to 11 characters at the end.
You actually can generate compressed keys in v1.6, just not on the paper wallet itself. You'll have to generate it first and then convert it in the wallet details page. Don't think it matters if it's fake or not, unless the person is selling it?
I find it odd mainly because the account hasn't been touched ever since OP made that post : https://blockchair.com/bitcoin/address/1DGwqAM8mV4aJVPidoBp9Zfz8GKhAzLkma
It still holds the 25 BTC. Considering that OP has basically most of the private key, why the lack of interest in running pyhton programs in order to retrieve the missing characters?
It still holds the 25 BTC. Considering that OP has basically most of the private key, why the lack of interest in running pyhton programs in order to retrieve the missing characters?
Exactly my thoughts.
I find it odd mainly because the account hasn't been touched ever since OP made that post : https://blockchair.com/bitcoin/address/1DGwqAM8mV4aJVPidoBp9Zfz8GKhAzLkma
It still holds the 25 BTC. Considering that OP has basically most of the private key, why the lack of interest in running pyhton programs in order to retrieve the missing characters?
It seems that he hasn't logged a day after making that post, leaving only an e-mail on his profile. Perhaps this is some sort of scan to have people message him and the conversation would go from there?
It still holds the 25 BTC. Considering that OP has basically most of the private key, why the lack of interest in running pyhton programs in order to retrieve the missing characters?
It seems that he hasn't logged a day after making that post, leaving only an e-mail on his profile. Perhaps this is some sort of scan to have people message him and the conversation would go from there?
Someone posted about a damaged 25btc paper wallet, but it looks like a fake post, since the private address starts with L and not 5, as it was in this bitaddress version.
Image of the paper: https://i.stack.imgur.com/e87Ju.jpg
Discussion: https://bitcoin.stackexchange.com/questions/98944/how-can-i-recover-the-missing-end-of-my-private-key
What do you think?
Image of the paper: https://i.stack.imgur.com/e87Ju.jpg
Discussion: https://bitcoin.stackexchange.com/questions/98944/how-can-i-recover-the-missing-end-of-my-private-key
What do you think?
Jump to: