Ok so I clicked submit and got 42a1d-12hy
Now what?
42a1d is less than 470f4 so you are on you way. Now you have to prove to me you own that private key. Do you know how to sign a message with your private key? If not, what wallet are you using? I can tell you how to do it on the blockchain.info wallet or the Bitcoin-qt (core) wallet.
|
|
|
This is fun, and great practice. I'm too young to stand a chance. If anything could lure satoshi back in, though...
Yes. I am sure Satoshi is all over my 0.1 BTC reward. Give it a try! 470f4 is the current number to beat and that is not that long ago. Dig up your oldest key pair and give it a whirl!
|
|
|
The most secure Bitcoin wallet is a properly produced and used paper wallet. The best combination of security and convenience is the Trezor hardware wallet, very long thread here: https://bitcointalk.org/index.php?topic=122438.0Ready to buy one? Here: https://www.buytrezor.com/Trezor: Backup the seed words once and never have to back up again Private keys never leave the device All crypto operations happen on the device Open source hardware and firmware Will be supported on many popular wallets soon I'm using justcoin wallet, pretty secure.
No, you have your coins lent out to a total stranger. Not even a wallet, it is an account. NO. Armory Wallet, but maybe a brain wallet is the easier solution for normal users.
Brain wallets are horrible. Only for very advanced users and then I still think they are a very bad idea. NO.
|
|
|
470f4 is now the number to beat!
|
|
|
Are we limited to submitting a single address?
In otherwords, can I submit my lowest address available to me in my hot wallet right now, and then if/when someone beats it can I go get a paper wallet from cold storage and submit that address?
Or once I submit an address am I locked into using that address for the duration of the game?
You can submit as many as you want to as long as it has a lower MinAddress than the previous post, you have the private key, and the address has a balance equal to or greater than 0.1 BTC.
|
|
|
who is burt guy? Is he reliable?
LOL. No.
|
|
|
Why does the address 18uTXyQubfaYrkbQDdaXhzd2ALEY5YN77B not work?
|
|
|
How low can you go? The Bitcoin Limbo Game Here is how it works: 1) Find the oldest Bitcoin address you still control (have the private key for) that you do not mind making public. For example: 13fG1Shr3gaDqGSXpgmqjhYUCXwFSShoKd 2) Enter this oldest address into the form at http://www.minaddress.info3) You will get a MinAddress for your address. For my example it is: 4d8fd-13f NOTES: You must have a valid MinAddress to win. The address must have a balance equal to or greater than 0.1 BTC to win. You must prove you control the address to win. If your address does not work at the web site then please report it here or to the owner. The MinAddress thread is here: https://bitcointalk.org/index.php?topic=774741.0 This is part of the beta testing of the site so... 4) The first portion of a MinAddress is the block number of the address. 5) If the block address portion of your oldest address is lower than the lowest address posted so far in this thread then post it in this thread. I will give a 0.1 BTC prize to the oldest/lowest address posted in the next couple of weeks or so. I reserve the right to post my own oldest address if I wish (a hidden reserve of sorts). You must follow the posting format shown in this next post (you can put anything you want into the message you sign) in order to prove you own the address and are not just blowing smoke. EDIT: Even after all these years I still learn new ways to get scammed. Amazing. In order to win:
the Bitcoin address must have a balance equal to or greater than 0.1 BTC you must prove you control the address by signing a message with the private key you must have the lowest MinAddress your post must follow the format used in the following post:
|
|
|
price rise: profit price drop: buy cheap coins to profit later price rise: profit price drop: buy cheap coins to profit later price rise: profit price drop: buy cheap coins to profit later price rise: profit price drop: buy cheap coins to profit later price rise: profit price drop: buy cheap coins to profit later
How dare you publish my secret method! Now you have done it. You do not know who you are messing with. Prepared to be sued into yesterday now because I have both a patent and copyright on this method.
|
|
|
CIYAM wants a single address form that shows that someone can use all of the following to find his address: 1ciyam Firstbits form 2adfd-1ci Original form from this proposal 1ci:2adfd Alternate form of 2adfd-1ci 1ciyam3htJit1feGa26p2wQ4aw6KFTejU Full Bitcoin address all three forms combined and posted together: 1ciyam3htJit1feGa26p2wQ4aw6KFTejU :2adfdHere is another one all decked out: 1BurtWEejbnKeBRsvcydJvsNztB1bXV5iQ :244fd (NOTE: I no longer use or support vanity addresses) Kind of cool that you can see who is "older", could become a "badge of honor" type thing. If I am ever in a bind and need to remember an emergency Bitcoin address I have already memorized "244fd-1bu [iQ]", I go to http://www.minaddress.info, type in 244fd-1bu, check that the resulting address ends in "iQ" and wala, my old vanity address.
|
|
|
Maybe you missed it in there among all this discussion of the technical details and possibilities but the proposal does greatly shorten the address from: 1ciyam3htJit1feGa26p2wQ4aw6KFTejU <-- standard Bitcoin address (33 characters) to: 2adfd-1ci <-- equivalent short form address (only 9 characters) I really like the proposal as a way to shorten used addresses. It is a really slick idea and does make the Bitcoin addresses much easier to read, say, and remember. I am opposed to address reuse, not this proposal per se.
|
|
|
This is a bit different because it is impossible to predict which addresses will become popular whereas password prediction is pretty easy.
As an example if your address suddenly became very popular with dozens of BTC donations per day then someone might want to try to get the near misses BUT they can't get the near misses in the lower digits because they cannot put anything into the blockchain retroactively between your block and today.
They could, of course, try for the misses in the appropriate and possible upper digits of the block number.
Multiple digit changes may not be worth the effort.
The block number typos are the only ones they can even try to do since they cannot go back to your original block to try for typos in the match portion.
|
|
|
Aha - *but* it may be possible using vanitygen to come up with another address starting with 1ciyam3htJ in the next block (depending upon what GPU power you have with regards to vanitygen). To do the same with the "checksum", however, would be *much, much harder* (as you'd have to try many more addresses to get such a match).
To create a match for the entire checksum is almost equivalent to creating the entire address so - almost impossible. To create a match for the very last character of the checksum = about the same as one more character in the original match, just a bit harder. To create a match for the last two characters of the checksum harder than just matching two extra characters in the original match although I am finding it hard to calculate exactly how much harder. But this whole "create a (near) match in the next block in the hopes that they make a mistake in the block number" is a bit of a stretch, don't you agree?
|
|
|
In a way the checksum characters are "more important" than the rest of the characters since they contain the checksum of all the other characters. But if you are not comparing the entire checksum area then there could be a false positive there also so, it would be nice to use them but if you don't want to then that is fine also.
Here are the two basic formats:
[hex block number]-[min head match][optionally more match] [min head match][optionally more match]:[hex block number]
You could extend these formats for the paranoid if you wanted to:
[hex block number]-[min head match][optionally more match][-optional tail match] [min head match][optionally more match]:[hex block number][:optional tail match]
|
|
|
I know but the exchanger is bitstamp, I set 2 steps authentication and control my account. Coins are still there. I am not a tech guy so I have fear to make some errors in keeping my btc by myself and lose. I asked help here in this forum but none explained my each step in detail.. they simply said "save in your hard drive" but I don't know how. Bitstamp seems quite professional to me. I have used it for long and always satisfied.
Just because Bitstamp has not been hacked or gone out of business taking all of the Bitcoins that have been loaned to it and running does not mean they will never be hacked or take all of the loaned BTC and run. Mt.Gox was a fixture in the Bitcoin community for years before it crashed and burned - taking a huge boatload of BTC with it. Besides Mt.Gox there have been many, many cases where businesses have failed due to either incompetence or malice and taken all of the BTC with them. You are way more trusting of people you do not know with your hard earned capital than I. But then again I was burned to the tune of 10,000 BTC early on by someone I did know and met in person and thought I could trust with my BTC so I have scar tissue you do not have (yet).
|
|
|
BTW: a simple change in algorithm would make these addresses almost as good as full addresses with respect to typographical error checking. Just include part of the checksum area of the full address.
Think you must have missed this: 1ciyam3htJit1feGa26p2wQ4aw6KFTejU:2adfd
Hmm... you could put part or all of the normal address checksum in the MinAddress like the above.
Already thunk it! But glad to see you agree with my suggestion. I did not miss it, you did not specify a syntax. The syntax in your reverse order case would need to be something like: 1c:ju:2adfd (head:tail:block) or in the original syntax 2adfd-1c-ju (block-head-tail)
|
|
|
So you would need 0.038 of these high output Nuclear Power Plants to power the Bitcoin network. That is fucking mind boggling!
One more fix needed I think
|
|
|
1ciyam3htJit1feGa26p2wQ4aw6KFTejU:2adfd
Vanity address, firstbits address and minaddress all in one. Very sharp looking! Thanks - note that it is somewhat a "marketing issue" also (so I was trying to make it look nice while still working with good old copy and paste - including touch screens). BTW: a simple change in algorithm would make these addresses almost as good as full addresses with respect to typographical error checking. Just include part of the checksum area of the full address. In other words instead of just looking at the front of the address for the unique string look at both ends when calculating the unique matching pattern to publish. Because this proposed minaddress now includes part of the checksum area the probability of a typo mapping to a valid address is even less. So for 1ciyam3htJit1feGa26p2wQ4aw6KFTejU we might get something like 2adfd-1c-U as the unique minaddress.
|
|
|
|