Reward-Drop ETA: 2016-08-04 05:02:04 UTC (98 weeks, 3 days, 13 hours, 50 minutes) But probably sooner  , could easily be July, might even be June. |
|
|
|
|
Daily bump.
dooglus's 18e98-1c is the MinAddress to beat.
To answer a question I got by PM: I will probably close out this contest at the end of this month unless there is a lot of activity but I expect activity will die off pretty rapidly as we go farther back into the blockchain.
Any "older timers" want to claim your 0.1 BTC?
|
|
|
|
Popping some popcorn on this one. Yes, Penner, why did you lock your thread? Personally I am glad you did so I only have to watch one thread. mrimport is either a naïve noob or a failed scammer Penner is either a scammer or has a hacked account Both are funny, that is for sure. Why did you lock the other thread after that screenshot was posted?  wasnt me?? what does locking it do? stop people from writing? mrimport: Penner locked his thread, try to keep up. Because this topic is to warn users and not to spam,spam but fine il reopen it
NO, please don't let's keep all the entertainment in one thread please. |
|
|
|
"firstbits" is harder to use, because in order to expand a firstbits address you need to search from the genesis block onwards until you find it.
With MinAddress the block number is in the address so there's much less searching required.
This is not true. One to One Correspondence between MinAddress and Full Address implemented to prevent mistakes in MinAddress
In order to implement the one to one correspondence the decoder must verify the block in the MinAddress is the very first block to contain the Bitcoin address - just like firstbits. See: I think the one to one correspondence between MinAddress and Full Address can be used to make the MinAddress mistake proof. MinAddress can have 3 levels of checks:
>Block must exist
>Address must be uniquely present in block
>Block should be the first block where the address was used.
The three level of dependencies will ensure that if MinAddress is misspell it will lead to an error rather than some other address. Though this is not 100% full proof but it will make the chance of random change leading to a valid MinAddress very very low.
|
|
|
|
|
I would think the message protocol would be pretty simple.
Assumptions:
You have the Bitcoin address and you know the Bitcoin address is controlled by the person you wish to send the message to.
The person to receive the message publishes their public key in the block chain and/or sends you a standard signed message to give you their public key.
Now you have the public key so you:
Create a random AES bulk encryption key (BEK).
Combine this one time use BEK with a known header.
Encrypt this combination using the public key.
This becomes the message header.
Encrypt the message with the random AES BEK.
Send the message header containing the encrypted BEK.
Send the encrypted message.
The receiver simply extracts the BEK from the message header with their private key and then decrypts the message with the one time use BEK.
Any holes in this?
|
|
|
|
Min-Address: 4dd40-1nvs
1NvSZnD1yGorz7GVPQH7g8Mx66enzXHYqA
Nice try but your block number (4dd40) is much greater than the lowest block number posted so far. 18e98 is the number to beat, yours must be lower than that in order to win. |
|
|
|
Nice project! Is there any other way to make it short? Re-using the address is not good, so any other way???
~~MZ~~
Let's be clear - Re-using the address to receive multiple times is completely ok secure but reduces your privacy and by extension the privacy of the entire Bitcoin system. Partial spending from an address is slightly less secure and can hurt anonymity and privacy. This is because you'll be leaving coins at an address where the full public key is known. "When you spend, spend the whole balance and don't use that address any longer" is the message here. [I like that message](Note, some feel keeping a few coins at an address used for every day spending and spending multiple times is fine because it is still quite secure but reduces privacy.) Fixed up a bit. Please read my rant up above in this very thread for more details: https://bitcointalk.org/index.php?topic=774741.msg8758673#msg8758673 |
|
|
|
|
Verified. 18e98-1c is the MinAddress to beat.
Getting interesting now, I can no longer win my own game.
|
|
|
|
Rule clarification:Starting with the next posted entry, any address submitted must contain 0.1 BTC or more. The history of the contest so far: 4d8fd-13f 13fG1Shr3gaDqGSXpgmqjhYUCXwFSShoKd 0.10010000 BTC
4c6ed-19b 19bgmFmEhpgNi8nbqnJ2pnQHXz9mpKxDkA 0.00991042 BTC
47e7d-19jd 19jD5PfF5TqeF5xJWa5US2rM7GHVr5hdX 0.05062073 BTC
470f4-1eyzk 1EYzkw5ZzTmigPY764njrL6bwG9boTUdZx 0.23536188 BTC
42a1d-12hy 12hYBWiPqfwdveGzpbRdGxeqnoMcNvGNSq 0.39833634 BTC
30f5c-1kg 1KGBMAWskevoU7u3qP5fcw4zojbx7AbL1W 0.58539396 BTC
2f4f3-1t 1TBZjmXho6mdGhoESaMV2svtqJXYtWfEp 0.00000000 BTC
24aa0-15e 15eiAnGmwGVKSGjSKowcDw7N6CmhG7jfoo 0.74575615 BTC
21412-1ez4 1Ez4a2mxKi97eXdnTV1Y4fb8NBZ6BDutGd 0.10000000 BTC
1a355-1ci 1CiunxVSGagXxowVVkrbcHrUTXx9tohCAG 0.03039492 BTC
is the MinAddress to beat.
|
|
|
|
Yes, I have verified that even though they made some sort of cut and paste mistake in their post, RB14060's MinAddress of 1a355-1ci is now the one to beat (signature verified and the address has funds).
Huh, not quite sure how that happened! Must've been a change address or something, cause I don't see it in my client nor does it show up in an address sweep. Oh well! You must have used the private key of 1a355-1ci = 1CiunxVSGagXxowVVkrbcHrUTXx9tohCAG to sign the message in your post otherwise I would not have been able to verify the signed message with the public key for 1a355-1ci = 1CiunxVSGagXxowVVkrbcHrUTXx9tohCAG. Therefore you must own the private key for 1a355-1ci. 1a355-1ci is the number to beat. Anyone? |
|
|
|
Move over everyone 1a1d9-1dz 1CiunxVSGagXxowVVkrbcHrUTXx9tohCAG Your MinAddress must be less than 1a1d9 GznG1tqEr2/TeGkJCAm05+YKklRyAe+GEC9BQF2NBLt/ra4B6BbtWKEDdD/CtpcHR+Nrnz50907DG8oP/VHg/Fw= EDIT: I can throw some coins in it if need be. EDIT 2: Added coins to get above dust (hopefully)? Hi, The minaddress in your post is not of the address you have put. The second part of minaddress will always have starting characters of your address. The correct minaddress for your address is 1a355-1ci, plz check. Yes, I have verified that even though they made some sort of cut and paste mistake in their post, RB14060's MinAddress of 1a355-1ci is now the one to beat (signature verified and the address has funds). RB14060: everything is correct in your post except the MinAddress of 1a1d9-1dz should be 1a355-1ci. The Bitcoin address for the MinAddress 1a1d9-1dz is 1Dz9QVrUopFGcwPokuhXYYGu5XCkPtg4Er and that address is younger than the address 1CiunxVSGagXxowVVkrbcHrUTXx9tohCAG but only by two days. Perhaps you own both? At any rate you are now in the lead and you did send the BTC to an address you do control (whew!). OP
can you tell when is the dateline ?
If you go to here and look at the first transaction for this address ( which happens to be from 1a1d9-1dz to 1a355-1ci) you will find they received 0.25 BTC on 2011-02-10 23:43:23 in block number 107349. It is interesting to note that the difficulty for that block was only 25,997.88 (difficulty today is 27,428,630,902.26) Kluge is gonna win  Not unless he can find an address to beat 1a355-1ci |
|
|
|
I would like it if we were somehow able to view our watch only wallet from our iphone... Is this at all possible?
it might be possible to take a copy of the "master public key" which can generate addresses only (no risk to find out the private keys from this) and build a watch only app on top of that. i've seen that in electrum and point of sale apps that use address generation only feature. There is probably an easier way to do this: download (or write) a compliant watch only ap, enter the xpub key, done.
Great minds think alike! |
|
|
|
I would like it if we were somehow able to view our watch only wallet from our iphone... Is this at all possible?
Can you connect the Trezor to your iPhone? I don't have an iPhone but I don't think you can do that yet. Yes if you have the right cord, but i dont think it does anything If you can connect it then you would have to try to run Chrome, see it the plug in will load into the Chrome browser, connect it physically, see if they can talk to each other. If all that works then you should be able to unplug the Trezor and wala! a watch only wallet on your iPhone. There is probably an easier way to do this: download (or write) a compliant watch only ap, enter the xpub key, done. |
|
|
|
|
Verified. 21412-1ez4 is the MinAddress to beat.
|
|
|
|
I would like it if we were somehow able to view our watch only wallet from our iphone... Is this at all possible?
Can you connect the Trezor to your iPhone? I don't have an iPhone but I don't think you can do that yet. |
|
|
|
--snip--
Yes, basically the person who wins this game will be a person who still controls an old (very old?) address (still has the private key), still had BTC at that address (or puts some new BTC there), and is willing to publicly declare and prove their ownership of that address.
Wow that hard to beat since you have BTC already since 2011 Meanwhile i start know bitcoin since 2014, so there's no chance for me to win this Probably not. 30f5c-1kg is the MinAddress to beat. Anyone? |
|
|
|
I think this game is about who hold the oldest BTC address..
Who had it will win this giveway, am i right ?
Yes, basically the person who wins this game will be a person who still controls an old (very old?) address (still has the private key), still had BTC at that address (or puts some new BTC there), and is willing to publicly declare and prove their ownership of that address. |
|
|
|
30f5c-1kg
Is the current MinAddress to beat. Private key and BTC amount verified. Min-Address: 47e7d-19jd
Good try but your block number (47e7d) is greater than iamnotcool`s (30f5c) and michietn94's (470f4). 1TBZjmXho6mdGhoESaMV2svtqJXYtWfEp was my first address after Instawallet, IIRC. I still have the private key and MinAddress says it's 2f4f3-1t but I don't know if I need to waste time and treasure signing a message and refunding it to over the dust limit (whatever that is). That is up to you. The number to beat right now is 30f5c so 2f4f3 would put you in the lead. Ok so I clicked submit and got 42a1d-12hy
Now what?
Good try but your MinAddress block number (42a1d) would need to be under 30f5c to be in the running. If you can find an earlier address you can try that. |
|
|
|
|
Show Posts
