Topic: 1DkyBEKt5S2GDtv7aQw6rQepAvnsRyHoYM - page 19. (Read 85797 times)
Definitely "A Christmas Story". At least he has a sense of humor.
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
update
two messages:
1. message "So long and thanks for all the fish.
2. message " QUICK IT COINS BTC PANTR. COM BE SURE TO DRINK YOUR OVALTINE."
Be sure to drink your ovaltine is probably a reference to: http://en.wikipedia.org/wiki/A_Christmas_Story
"Quick IT coins BTC panther. Come on be shure to drink your Ovaltine."
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
update
two messages:
1. message "So long and thanks for all the fish.
2. message " QUICK IT COINS BTC PANTR. COM BE SURE TO DRINK YOUR OVALTINE."
Be sure to drink your ovaltine is probably a reference to: http://en.wikipedia.org/wiki/A_Christmas_Story
Is it a bug or (privacy) 'feature'?
It's a bug. It was introduced accidentally when code was added to avoid sub-cent change from being created, since any sub-cent output automatically incurs a transaction fee. The code makes sure the change is always at least 1 bitcent if possible, but forgot about the case where no change is necessary. It works if the entire payment can be made using a single output, but not if more than one output is required.
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
update
two messages:
1. message "So long and thanks for all the fish.
2. message " QUICK IT COINS BTC PANTR. COM BE SURE TO DRINK YOUR OVALTINE."
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
update
ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIU == UICKITCOINSBTCPANTRY.COMBE SURE TO DRINK YOUR OVALTINE
swiss then or what? http://en.wikipedia.org/wiki/Ovaltine
From the wiki page:
"They had promotions in which listeners could save proofs-of-purchase from Ovaltine jars to obtain radio premiums, like "secret decoder ring" badges or pins that could be used to decode messages in the program. "
Ok, anyone has a secret decoder ring? i think we will need it to decode the messages...
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
update
ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIU == UICKITCOINSBTCPANTRY.COMBE SURE TO DRINK YOUR OVALTINE
swiss then or what? http://en.wikipedia.org/wiki/Ovaltine
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
update
ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIU == UICKITCOINSBTCPANTRY.COMBE SURE TO DRINK YOUR OVALTINE
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
update
Still. He has ten 10,000 BTC inputs. Why was it necessary to add the two small sub-0.01 BTC inputs and send the sum of that to a separate address?
It's a bug in the satoshi client.
In an attempt to avoid sending change less than 0.01 BTC, it sends change even when it isn't necessary.
I submitted a fix for the bug a long time ago, but it never got included in the master branch. See https://github.com/bitcoin/bitcoin/pull/898
Here's a good example. MtGox is trying to consolidate 10 50k outputs into a single 500k output, but an 11th 50k gets pulled in and spat out as change due to the same bug:
http://blockchain.info/tx-index/2048819/1
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So Iong "
0.001 = [space]
"So long and thanks for all the fish."
http://www.youtube.com/watch?v=jc6aufHz-i0
Still. He has ten 10,000 BTC inputs. Why was it necessary to add the two small sub-0.01 BTC inputs and send the sum of that to a separate address?
It's a bug in the satoshi client.
In an attempt to avoid sending change less than 0.01 BTC, it sends change even when it isn't necessary.
I submitted a fix for the bug a long time ago, but it never got included in the master branch. See https://github.com/bitcoin/bitcoin/pull/898
Here's a good example. MtGox is trying to consolidate 10 50k outputs into a single 500k output, but an 11th 50k gets pulled in and spat out as change due to the same bug:
http://blockchain.info/tx-index/2048819/1
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
starts with "So
0.001 = [space]
EDIT: message is "So long and thanks for all the fish..ENITLAVO RUOY KNIRD OT ERUS EBMOC.YRTNAPCTBSNIOCTIKCIUQ " unfortunately the important part is encoded!!
100K BTC were sent here if anyone noticed. Just sitting their:
https://blockchain.info/address/1E9k79dLuhfspdEtymzP7vhaYVGFcdfsYs
https://blockchain.info/address/1E9k79dLuhfspdEtymzP7vhaYVGFcdfsYs
That was 4 days ago and it was noticed by Spekulatius right after they moved. I see you didn't read the thread before posting. https://bitcointalksearch.org/topic/m.1111659
Also, they are not sitting there. They moved 18 hrs after landing on that address, so I'll take it you also didn't open the link you posted
No I didn't read tens of pages of posts and I did actually open the link. You can see where they went below. I was just doing a little research. Go drink some coffee, little short on the quips today.
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
Except the binary codes all came from the same address, and were close together. The leet transaction was a few days later from a different address. Likely not the same sender.
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
yeah, message is finished. special end sign!
last output transactions was binary encoded messages eventually? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
Those were sent to the address... someone's just screwing around. Today somebody sent 0.00001337 BTC.
last output input transactions was binary encoded messages eventually tentatively? take a look!
0.01010101 = 01010101 = "U"
0.01010101 = 01010101 = "U"
100K BTC were sent here if anyone noticed. Just sitting their:
https://blockchain.info/address/1E9k79dLuhfspdEtymzP7vhaYVGFcdfsYs
https://blockchain.info/address/1E9k79dLuhfspdEtymzP7vhaYVGFcdfsYs
That was 4 days ago and it was noticed by Spekulatius right after they moved. I see you didn't read the thread before posting. https://bitcointalksearch.org/topic/m.1111659
Also, they are not sitting there. They moved 18 hrs after landing on that address, so I'll take it you also didn't open the link you posted
100K BTC were sent here if anyone noticed. Just sitting their:
https://blockchain.info/address/1E9k79dLuhfspdEtymzP7vhaYVGFcdfsYs
https://blockchain.info/address/1E9k79dLuhfspdEtymzP7vhaYVGFcdfsYs
Jump to: