you can send the source ?
tks
Topic: upgrade Directory.io program (Read 1882 times)
Yes, i agree with this warning, unless you don't want an address no more, you should never put it on internet. you don't know what would happened.
WARNING: DO NOT SEARCH FOR AN ACTUAL PRIVATE KEY AT THIS SITE. TELLING THE SITE YOUR PRIVATE KEY WILL ALLOW IT TO TAKE YOUR BITCOINS.
Thanks Cpt. Obvious. Why not put the font size to 72pt or something like that?
Never enter private keys to any site anywhere. Ever. So it applies also to the aforementioned site. No news there.
It was originally posted in the Beginners & Help sub-forum, so I think the warning was very appropriate.
Thanks Cpt. Obvious. Why not put the font size to 72pt or something like that?
Never enter private keys to any site anywhere. Ever. So it applies also to the aforementioned site. No news there.
@privatenode:
You may want to take the search WIF key functionality out of the page, so people do not shit their pants. I think the value-add in your site is the range warning for potentially leaked addresses. And I could think about an API you could query for the current search front of the LBC pool (with recently over 1 mio pages on directory.io per second it's moving quite fast) basically the directory.io link at https://lbc.cryptoguru.org/stats
The balance does not seem to work, http://block.okcoin.cn/address/1EoXPE6MzT4EnHvk2Ldj64M2ks2EAcZyH4 has zero contrary to the claimed 15068 (Satoshi?)
Also your page offset starts at 2
http://washen.me/1 is nirvana
Rico
Hi Rico, I'm focusing make the ASCII address bar, trying to make it more "EASY TO READ".
1. if you can give me an API from your LBC i can think a good way to uses it to display where we already went through and will process in next few weeks/months. so i could mark those addresses as potential leaked.
2. The WIF key is pretty much i just quote that API, as Directory.IO uses
Code:
http://directory.io/warning:understand-how-this-works!/5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCHK2Zzv
I just made it shorter, and post it with a search form. as
http://washen.me/querypk/5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCHK2Zzv
I just made it shorter, and post it with a search form. as
http://washen.me/querypk/5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreCHK2Zzv
Quote
func main() {
http.HandleFunc("/", PageRequest)
http.HandleFunc("/querypk/", RedirectRequest)
http.HandleFunc("/search", search)
log.Println("Listening")
log.Fatal(http.ListenAndServe("washen.me:80", nil))
591,2-9 99%
http.HandleFunc("/", PageRequest)
http.HandleFunc("/querypk/", RedirectRequest)
http.HandleFunc("/search", search)
log.Println("Listening")
log.Fatal(http.ListenAndServe("washen.me:80", nil))
591,2-9 99%
3. Once i finish my decoration ,I will put it to github. never dealt with those UI thing, so bugging me.
4. the first page got some buggy key, when i send balance query from server, some thing just don't match, blockchain.info returns an error with it, so i have to block it.
AND, Do you remember last time we searched out one of my private key with your LBC?that is why i think people should not be scared, but they should be prepared. there's not too much different from our apps, the goal is push bitcoin move forward from some different angle.
WARNING: DO NOT SEARCH FOR AN ACTUAL PRIVATE KEY AT THIS SITE. TELLING THE SITE YOUR PRIVATE KEY WILL ALLOW IT TO TAKE YOUR BITCOINS.
Thanks Cpt. Obvious. Why not put the font size to 72pt or something like that?
Never enter private keys to any site anywhere. Ever. So it applies also to the aforementioned site. No news there.
@privatenode:
You may want to take the search WIF key functionality out of the page, so people do not shit their pants. I think the value-add in your site is the range warning for potentially leaked addresses. And I could think about an API you could query for the current search front of the LBC pool (with recently over 1 mio pages on directory.io per second it's moving quite fast) basically the directory.io link at https://lbc.cryptoguru.org/stats
The balance does not seem to work, http://block.okcoin.cn/address/1EoXPE6MzT4EnHvk2Ldj64M2ks2EAcZyH4 has zero contrary to the claimed 15068 (Satoshi?)
Also your page offset starts at 2
http://washen.me/1 is nirvana
Rico
well, it doesn't. there's no space to store anything, but two go program, one is original directory. another one is doing the search fro multi API with various IP binded to server.
actually there's plenty sites providing by fork the very same directory.io, only thing i did is forked http://www.allprivatekeys.com/vulnerability.php, that address vulnerability to a more graphic level.
actually there's plenty sites providing by fork the very same directory.io, only thing i did is forked http://www.allprivatekeys.com/vulnerability.php, that address vulnerability to a more graphic level.
If you generate private keys randomly, it will be extraordinarily unlikely that you will you ever see one at the very beginning or at the very end.
Oh, and this...
Oh, and this...
WARNING: DO NOT SEARCH FOR AN ACTUAL PRIVATE KEY AT THIS SITE. TELLING THE SITE YOUR PRIVATE KEY WILL ALLOW IT TO TAKE YOUR BITCOINS.
at first ,i want to make it clear, The LBC Program is not meant to harm anyone AFAIK. I'm also running over 100+ CPU threads with LBC project started from bitcointalk. I personally consider its a very interesting project..
if you put all those bitcoin "ADDRESSES" as a Chain, you should notice the most vulnerable addresses are belongs to the Very Beginning, End, and Middle of this chain under the pressure and some other LBC Like APPS.
=DANGER===============!!====DANGER===========!!==========DANGER=
so, i made this program to help me create a safe wallet when btc address I'm using in my wallet are used for a period.
i tired to use multi-sign wallet with my colleague, but the issue still remains, to transfer Bitcoins i have to open multi wallet to sign a single transaction. and that's just bugging me. and for once i nearly lost a co-sign key and that would costs me 36 bitcoins in that wallet.
so i made this program for me, modified from Directory , which allows me to locate the address i'm using located in the chain, as i group few very good address, i can make a wallet that safer in the coming days.
the keys to do so, is need to avoid use key in certain location, to avoid the LBC and LBC like porject , and never in the very beginning or the end of the chain.
I will offer its source code on github once i finished al the functions i planned for current version. for now i finished the massive balance query function without cors support needed. also the query can be easier, check help on website for details.
http://washen.me
if you put all those bitcoin "ADDRESSES" as a Chain, you should notice the most vulnerable addresses are belongs to the Very Beginning, End, and Middle of this chain under the pressure and some other LBC Like APPS.
=DANGER===============!!====DANGER===========!!==========DANGER=
so, i made this program to help me create a safe wallet when btc address I'm using in my wallet are used for a period.
i tired to use multi-sign wallet with my colleague, but the issue still remains, to transfer Bitcoins i have to open multi wallet to sign a single transaction. and that's just bugging me. and for once i nearly lost a co-sign key and that would costs me 36 bitcoins in that wallet.
so i made this program for me, modified from Directory , which allows me to locate the address i'm using located in the chain, as i group few very good address, i can make a wallet that safer in the coming days.
the keys to do so, is need to avoid use key in certain location, to avoid the LBC and LBC like porject , and never in the very beginning or the end of the chain.
I will offer its source code on github once i finished al the functions i planned for current version. for now i finished the massive balance query function without cors support needed. also the query can be easier, check help on website for details.
http://washen.me
Jump to: