echo -n "1Ca15MELG5DzYpUgeXkkJ2Lt7iMa17SwAo" | sha256sum
9e027d0086bdb83372f6040765442bbedd35b96e1c861acce5e22e1c4987cd60
That hex number is the private key for 15ZwrzrRj9x4XpnocEGbLuPakzsY2S4Mit !!!
This is not the case. The private key for that hex address is 5K1sjALvVxbsTRMf3aGKnB6E39uZfqQ6XQTGh5z3DrBDq3pG9A6 and its address is 18JT3KeFV36Hkgo3Xi9bfgNYAXCVXBGyFg.
Have you considered protecting the corresponding bitcoin cash wallets ? At least one of them got raided after your publication.
private address in HEX 9e027d0086bdb83372f6040765442bbedd35b96e1c861acce5e22e1c4987cd60
private address in WIF 5K1sjALvVxbsTRMf3aGKnB6E39uZfqQ6XQTGh5z3DrBDq3pG9A6
[ but there are two wifs L2Wru6Ew8pQuhcWAvMpdtPY4YWK1CQcwPCWxFvzkoi47crJBAVaP ]
Then address is 18JT3KeFV36Hkgo3Xi9bfgNYAXCVXBGyFg
But there is only the compressed address ... 15ZwrzrRj9x4XpnocEGbLuPakzsY2S4Mit
There is no balance on this private-address
IMHO, having done this stuff for a solid six months after a double hiatus from bitcoin in 2011, and 2013, I have seen very little to nothing come of these types of 'looking for private keys', just hashes in generals that they them selves came from hashes is just shit from shit, you still get shit, a lucky monkey on a type write can also generate 'war and peace', given enough time.
There are 10k ways to HACK bitcoin, there are a zillion paths to be taken, one must test them all to find that path that works for them, certainly you don't want to follow the 'pack' in this shit, as it will lead you to NO WHERE.
Probably best advice for people serious about this game is ...
1.) Study the C++ code for bitcoin, as none of the docs are real, its all bullshit, only the code is real
2.) roll you own, write your own parsers ( block chain to text, its probably best to do CSV), most of the database programs can handle 200GB very well; probably best c/c++ & python
3.) have many databases that are selective for each mission, one for addresses, one for balances ( short life ), one for public-keys, ..
4.) Have many bloom-filters for all of the above, searching for the monkey means O(1) search time, you can have just a bloom for address, you need blooms for your rain-bow table, for your private-key warehouse, for your public-keys, for your ecdsa integer farm, ...
5.) getting back 2, none of the code on github works, I mean NONE, its not maintained, and it will all lead you to dead ends, if a guy actually wrote a 'bot' that harvested valuable addresses and swept those accounts he would NOT give that software away for free, 99% of the shit you find on GITHUB is somebody's dead-end,
6.) study all the papers on the subject, there are 1,000's of well written technical papers on ECDSA SECP256, read them all, write your own sig ecdsa software write your own hash library, vector everything, always place vector check points every few 100 steps so you know everything is working.
7.) there are 1,000's of variables, and it only takes one to generate false-positives, know at all times that all your inputs are correct,
8.) have a bell or timer set to generate music, I have a A-G guitar chord set,so depending up what my bots find, they play the different chord sets so that I know the nature of the problem, and the chord set doesn't nauseate people around the house
9.) I find that hacking BTC is harder than mining, but far more interesting,
10.) Don't be a fool, if you don't have years of experience in programming, cryptograhy, database, networking, math, physics, then your chance of making any kind of interesting discovery is nil; Lots of smart people working on this "Discrete Log Problem" for a long time, if it were an easy problem, then it would have been solved, I think some 50 years since computers have been generally available people have been trying to solve this problem by brute-force
11.) like I said there are 10k ways to hack btc, there is the address angle, the public-key angle, the random priv-key angle, ... the ecdsa pool angle, ... you need to really play around with all until you find a method that works for you, then dive deep and really understand why your succeeding, don't try to do them all, there is too much, just doing the ECDSA can be a full time job for a mathematician
...
Most of this stuff is done for intellectual curiosity IMHO its to much work for the 'get rich quick moron' which are the majority of this board, its far easier to clone your own coin, start your own mining pool, or exchange and rip people off if you goal is to 'steal', most of us when we do find coin, are more than happy to make note of the find to the owner.
It's a vast multi-disciplinary field 'hacking btc', I can see it become a major career path, there are already dozens of masters thesis written on this subject, bound to be many phd's born of this stuff
For the young kid, I can offer no better path than BUTERIN did, first study the BTC source, and master that, then write your own btc client/server in python, and completely understand all, then modify your source so it can output 'data' as you want, ... Most of the 'action' is happening now, most of the easy stuff that is talked about in papers or this forum is what happened in 2014 or earlier, ... unless you write your own client/server that is tuned to study the now, your not going to make 'great' discovery's.
Passive Analysis is still wide open, very little work has been done on the block-chain using machine learning or digital signal processing techniques, but then again like the stock-market, what bitcon did in the past in terms of private-key generation means nothing tomorrow, as the core-devs are constantly hacking the code, and fixing the 'holes', thus to find the new holes, you must stay one step ahead of the core-devs,
