[Poll added] Please save this SHA256 or timestamp it!

[MysteryMiner]

aedd6c30a81f53c301a2862901c32719f40e4b891c47a27039093b2c539e7f95

Please save this here or timestamp/sign it. GPG or Namecoin.

It is needed if I decide to make public announcement later as a proof I did not made it up after the shit hit the fan. Until then it will remain Mystery to be mined.

[1714771799]

1714771799

[1714771799]

1714771799

[1714771799]

1714771799

[phantastisch]

aedd6c30a81f53c301a2862901c32719f40e4b891c47a27039093b2c539e7f95

Please save this here or timestamp/sign it. GPG or Namecoin.

It is needed if I decide to make public announcement later as a proof I did not made it up after the shit hit the fan. Until then it will remain Mystery to be mined.

I will quote it for now.

[Joost]

aedd6c30a81f53c301a2862901c32719f40e4b891c47a27039093b2c539e7f95

Please save this here or timestamp/sign it. GPG or Namecoin.

It is needed if I decide to make public announcement later as a proof I did not made it up after the shit hit the fan. Until then it will remain Mystery to be mined.

I will quote it for now.

And I shall quote your quote. For now.

[justusranvier]

aedd6c30a81f53c301a2862901c32719f40e4b891c47a27039093b2c539e7f95

Please save this here or timestamp/sign it. GPG or Namecoin.

Is this what you're looking for?

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-04-07 I saw MysteryMiner post the following hash:

aedd6c30a81f53c301a2862901c32719f40e4b891c47a27039093b2c539e7f95
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBAgAGBQJRYfHeAAoJECoisBQbQ4v01AAH/1ugpXKuHQMJ/DLTpMSpXdXc
G0IOvofgUC5O0d1aBw6PvrJJTvnv8aEm3RmZp7vIwyfiYCttbG3/RYXAKqdZB2sl
vnTvDVg0FEcdDrAVyL+Riq+TuXpVJ3Hn/HFTPB9gpR00PWAFgmc1nVhsXJANxMXh
xKjgJ4s/dQugE51szKKm1rz3I/ibZN4EgBD7cANCt6Pt7fJ6OOTIfjpgBUXNDhRR
UtJYVnuRZRlZlMAt6F7AStJDp5dOwpblIvYvr0VMx3Ko7EWv+KlCX6zcNTdo4lfG
8No1jgAQJxleoNOwDSDRVPqoJ6XXV7EuPNOpXz2SSsFHjQrX2aSY+Bi1pIxdI2U=
=IpFk
-----END PGP SIGNATURE-----

[jackjack]

aedd6c30a81f53c301a2862901c32719f40e4b891c47a27039093b2c539e7f95

Please save this here or timestamp/sign it. GPG or Namecoin.

Is this what you're looking for?

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-04-07 I saw MysteryMiner post the following hash:

aedd6c30a81f53c301a2862901c32719f40e4b891c47a27039093b2c539e7f95
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBAgAGBQJRYfHeAAoJECoisBQbQ4v01AAH/1ugpXKuHQMJ/DLTpMSpXdXc
G0IOvofgUC5O0d1aBw6PvrJJTvnv8aEm3RmZp7vIwyfiYCttbG3/RYXAKqdZB2sl
vnTvDVg0FEcdDrAVyL+Riq+TuXpVJ3Hn/HFTPB9gpR00PWAFgmc1nVhsXJANxMXh
xKjgJ4s/dQugE51szKKm1rz3I/ibZN4EgBD7cANCt6Pt7fJ6OOTIfjpgBUXNDhRR
UtJYVnuRZRlZlMAt6F7AStJDp5dOwpblIvYvr0VMx3Ko7EWv+KlCX6zcNTdo4lfG
8No1jgAQJxleoNOwDSDRVPqoJ6XXV7EuPNOpXz2SSsFHjQrX2aSY+Bi1pIxdI2U=
=IpFk
-----END PGP SIGNATURE-----

And... Quoted!
Inb4 nothing happens

[MysteryMiner]

Thanks everyone! I'm not sure I will come out with the data corresponding to this hash before someone else figures out this and announces it publicly. Learning from history the good guys get no profit and only troubles from being white knight on donkey instead of black knight on stallion. I'm not sure how seriously it might affect Bitcoin but it is about exploitable vulnerability on Bitcoin accepting service that might go down completely as a result of this.

Adding poll to vote.

edit: no poll option found. Changing my glasses.

[Ditto]

Voted for notify. Can you tell us what the site is?

[MysteryMiner]

Voted for notify. Can you tell us what the site is?

Will not tell anyone until I finish one of first 4 options. If one is following Bitcointalk closely he easily might figure out that by himself.

Update: I'm dissapointed. I will goatse them at midnight. I don't want to do this because I and other people need them but what is going to be inevitable must happen sooner or later. Better it's me who pull the trigger and not someone else gets all the little fun.

[MysteryMiner]

Notified the owners and got response. I will explain everything tomorrow and post both the file behind the hash and full dump. Im very drunk right now.

[vog]

Regarding the timestamping of your SHA256: Why don't you let the bitcoin network prove your timestamp? (e.g. via Bitcoinproof)

[MysteryMiner]

Regarding the timestamping of your SHA256: Why don't you let the bitcoin network prove your timestamp? (e.g. via Bitcoinproof)

Thanks for the link! I did not know about it's existence. But does Namecoins serve the same purpose better? And Bitcoin network cannot be very accurate for this because it can vary block times for +/- 2 hours right? But it sill is very reasonable way to do, will take deeper look when have better state of mind.

The flaw turned out to be not so dramatic. I will post everything at once as soon as I get in mood of writing long text.

[vog]

But does Namecoins serve the same purpose better?

Bitcoin seems to be more active, and seems to attract more computing power, AFAICS.

And Bitcoin network cannot be very accurate for this because it can vary block times for +/- 2 hours right?

On average, every 10 minutes a new block is generated. So yes, that timestamp could be 10 minutes after you sent the transaction, or even some more minutes later. In addition, the block is only "really" assured after 6 transactions, so add 1 hour just to be safe.

However, I doubt that this will cause any problem, because it's usually not about minutes but days. I bet that quite some time elapsed between your discovery and the creation of the dataset whose SHA-256 hash you published. So I guess that adding 1 more hour (maybe 2) won't make any difference.

[MysteryMiner]

The data behind the hash is here: https://bitcointalk.org/index.php?topic=172527.0

First I tried to exploit alone for profit (failed), then notified owners, then did full disclosure for everyone to know and be aware.