Topic: Help verify LBAAT.net, win coins for next 4 years (Read 2128 times)
Thanks for notifying, but i am just havingdoubts on what to put and where to put the source data and hit the magical button and get the coins
Bumping this to get some more eyes on it with the price increase. Next round of free bitcoins is April 07 at 03:00.
Thank you to bitaddress.org. It is now possible to use EC Multiplication on the vanity tab to get (and redeem) future addresses. Select the "Multiplication" radio button for LBAAT.
043AAA252230B609A68F35E2ECE44D6CAB9C123B208D2066A5B1BAC48D165238533C45AEE5B0033 1824A47EA3BB4FDA5E6491C9D0A962D9DBA532E2A528128DBA0
??
??
0.0476 coins were sent to 16aQ7YzkhEfjK3bLfF7qK7iivT3zo33g2g, but not redeemed yet.
043AAA252230B609A68F35E2ECE44D6CAB9C123B208D2066A5B1BAC48D165238533C45AEE5B0033 1824A47EA3BB4FDA5E6491C9D0A962D9DBA532E2A528128DBA0
??
??
Sent a few cents to your public key timepoint:December 28 2012 12:00 UTC
043AAA252230B609A68F35E2ECE44D6CAB9C123B208D2066A5B1BAC48D165238533C45AEE5B0033 1824A47EA3BB4FDA5E6491C9D0A962D9DBA532E2A528128DBA0
??
??
Maybe I am just being thick today but have tried to comprehend this and I just don't. Could you please explain this system to me in very simple terms?
As far as I understand it: With this system I can send coins to an address which I (or anyone else) will not be able to access until a certain point in the future.
Questions:
1) if this is the case then why do I need to supply a public key?
2) Why do I need to supply a private key? (if I have the private key I can access the funds right now)
3) Why do I need to supply a private key which starts with "04"? As I understand it the private key is merely an alternative representation of the Bitcoin address, so this just adds administrative hassle (I need to open casascius utility and enter the Bitcoin address)
4) Given the fact you only supply me with the Bitcoin address where the Bitcoins reside, how do I calculate the private key to claim the Bitcoins? Right now I have no idea how to this even with the addresses which are already claimed. On your site it asks me to enter a private key which I obviously do not have.
This could be really interesting. I remember reading this originally and really not comprehending what you meant. Now I saw that a few addresses were claimed so I thought I could just try the system out on those addresses to find out how it works but I cannot even figure that out.
So how about a how to for the mentally challenged?
As far as I understand it: With this system I can send coins to an address which I (or anyone else) will not be able to access until a certain point in the future.
Questions:
1) if this is the case then why do I need to supply a public key?
2) Why do I need to supply a private key? (if I have the private key I can access the funds right now)
3) Why do I need to supply a private key which starts with "04"? As I understand it the private key is merely an alternative representation of the Bitcoin address, so this just adds administrative hassle (I need to open casascius utility and enter the Bitcoin address)
4) Given the fact you only supply me with the Bitcoin address where the Bitcoins reside, how do I calculate the private key to claim the Bitcoins? Right now I have no idea how to this even with the addresses which are already claimed. On your site it asks me to enter a private key which I obviously do not have.
This could be really interesting. I remember reading this originally and really not comprehending what you meant. Now I saw that a few addresses were claimed so I thought I could just try the system out on those addresses to find out how it works but I cannot even figure that out.
So how about a how to for the mentally challenged?
I wrote up a few replies, but best to show by example because it's easier than it sounds.
1) Go to bitaddress.org.
2) Get a private key (5....) Save this private key and don't disclose it!
3) Put private key in the "Wallet Details"
4) POST here the public key ("Public Key (130 characters [0-9A-F]")
5) I'll send a few cents to a new address that only you can get to.
Maybe I am just being thick today but have tried to comprehend this and I just don't. Could you please explain this system to me in very simple terms?
So you want to learn about Elliptic curve cryptography is very simple terms? I'm afraid my understanding of the subject lacks a bit to achieve that.
What I can try to explain is the high level process here;
We created a list of secrets that will be disclosed for the next two hundred something years, one per hour. With these secrets and a little EC magic we can create a new public key from your public key and from there calculate a bitcoin address. With a little more EC magic we can calculate the private key to that bitcoin address by using the same secrets and the private key for the public key you provided.
This means that without disclosing a future secret (we call these timepoint secrets) we can calculate a bitcoin address from a public key you provide, but you can't calculate the private key needed to redeem the funds. We are also not able to calculate the private key, so the funds there are 'locked'. No one can access them.
When the timepoint secret is revealed you can, using the lbaat static calculator or some 3rd party tool (Armory allows for this, for example), calculate the future address private key using said secret and the private key for the public key you provided initially.
It's late and I'm not sure I made much sense, but you can read all the details at https://bitcointalksearch.org/topic/send-bitcoins-into-the-future-lbaatnet-128581 including a pretty graph. If you have more questions don't hesitate to ask, we'll do our best to explain.
This particular thread gives away a bunch of addresses that were created using the above process, and also discloses the private key to be used calculating the addresses' keys. You should not, obviously, disclose yours to anyone unless you intend them to redeem the coins when the time comes.
Maybe I am just being thick today but have tried to comprehend this and I just don't. Could you please explain this system to me in very simple terms?
As far as I understand it: With this system I can send coins to an address which I (or anyone else) will not be able to access until a certain point in the future.
Questions:
1) if this is the case then why do I need to supply a public key?
2) Why do I need to supply a private key? (if I have the private key I can access the funds right now)
3) Why do I need to supply a private key which starts with "04"? As I understand it the private key is merely an alternative representation of the Bitcoin address, so this just adds administrative hassle (I need to open casascius utility and enter the Bitcoin address)
4) Given the fact you only supply me with the Bitcoin address where the Bitcoins reside, how do I calculate the private key to claim the Bitcoins? Right now I have no idea how to this even with the addresses which are already claimed. On your site it asks me to enter a private key which I obviously do not have.
This could be really interesting. I remember reading this originally and really not comprehending what you meant. Now I saw that a few addresses were claimed so I thought I could just try the system out on those addresses to find out how it works but I cannot even figure that out.
So how about a how to for the mentally challenged?
As far as I understand it: With this system I can send coins to an address which I (or anyone else) will not be able to access until a certain point in the future.
Questions:
1) if this is the case then why do I need to supply a public key?
2) Why do I need to supply a private key? (if I have the private key I can access the funds right now)
3) Why do I need to supply a private key which starts with "04"? As I understand it the private key is merely an alternative representation of the Bitcoin address, so this just adds administrative hassle (I need to open casascius utility and enter the Bitcoin address)
4) Given the fact you only supply me with the Bitcoin address where the Bitcoins reside, how do I calculate the private key to claim the Bitcoins? Right now I have no idea how to this even with the addresses which are already claimed. On your site it asks me to enter a private key which I obviously do not have.
This could be really interesting. I remember reading this originally and really not comprehending what you meant. Now I saw that a few addresses were claimed so I thought I could just try the system out on those addresses to find out how it works but I cannot even figure that out.
So how about a how to for the mentally challenged?
First two have been claimed without much delay.
To help launch LBAAT.net (https://bitcointalksearch.org/topic/send-bitcoins-into-the-future-lbaatnet-128581), we have put BTC 15.01633744 into the future over the next 4 years. They are split up over 100 addresses. To claim, you need the timepoint secret for each interval and apply it using the following information:
Private Key:
WIF: 5KMFa22QksQjRYnkErs6Agzd2tedj2ipYTaD9erCF5vxHSHjheS
RAW: ca01b35d68b393d419ac20bdc8c2136b802c71194fa7665190e35743e8ef2927
Public Key:
0462a36a3b67f4b5bf90dc6c48ac9030f7aaa2d31210e2d7c8274bc2c350d9857bd20ee5a15a261 791b1d8329a0a82ff3e374dffb07915630127aad5c6d135a2c9
This will help test LBAAT to see if the coins sent are secure in the future. Note the BTC 1.000 prize in December 2016. Fastest finger gets the coins. If coins are redeemed early, it is a sign that the information has been compromised. This will help test the service, no warranties. Good luck!
timepoint amount @ address
2012.12.05 14:00 ( BTC 0.22213465 @ 188Ygj43Js…) Claimed 2012 12 05 14:02:49
2012.12.16 12:00 ( BTC 0.10497890 @ 15jazmcwW8…) Claimed 2012 12 16 12:46:49
2013.01.02 13:00 ( BTC 0.12081314 @ 1G9HLxdb1o…) Claimed 2013 01 02 13:01:09 (0daba55ff9bb3320810c8c59e7b2a44e6e7813f8ac190b286e7d4bfb8624cab6)
2013.01.10 01:00 ( BTC 0.14937388 @ 1L8aNgVMXA…)
2013.02.02 07:00 ( BTC 0.13454134 @ 1CavFuhbP6…)
2013.02.11 13:00 ( BTC 0.19772584 @ 14TTEQdoKy…)
2013.02.21 12:00 ( BTC 0.15633881 @ 1AdAbn33r1…)
2013.03.03 08:00 ( BTC 0.17725408 @ 1LiC8Uv1ht…)
2013.03.30 04:00 ( BTC 0.21993430 @ 13eUMwMaGZ…)
2013.04.07 03:00 ( BTC 0.05017415 @ 1GrYBTo5Zj…)
2013.04.09 17:00 ( BTC 0.15187733 @ 12FfPybc7K…)
2013.04.30 19:00 ( BTC 0.07834591 @ 17xAzXLLJJ…)
2013.05.11 05:00 ( BTC 0.14070220 @ 1HEbsMxoiv…)
2013.05.21 06:00 ( BTC 0.13054264 @ 17Z29eiF4v…)
2013.06.07 09:00 ( BTC 0.10659530 @ 1LapSpsLsR…)
2013.06.19 08:00 ( BTC 0.17071023 @ 1HS3sKYz8H…)
2013.06.20 11:00 ( BTC 0.13587414 @ 1C1qH6FJuG…)
2013.07.16 21:00 ( BTC 0.09786455 @ 16DXqzVzRt…)
2013.08.07 12:00 ( BTC 0.17260505 @ 19qCqG4Sjp…)
2013.08.18 09:00 ( BTC 0.02337728 @ 1HqJcJY5nY…)
2013.08.26 09:00 ( BTC 0.07256130 @ 1EaTETEacH…)
2013.09.20 10:00 ( BTC 0.24803214 @ 1G5f2qFBJg…)
2013.10.03 23:00 ( BTC 0.13558857 @ 1JRS18AiE8…)
2013.10.04 11:00 ( BTC 0.10482669 @ 19tivqEnG9…)
2013.10.27 12:00 ( BTC 0.18231765 @ 1H9urmN42U…)
2013.11.07 01:00 ( BTC 0.20127591 @ 18boDLn9ot…)
2013.11.21 19:00 ( BTC 0.10049777 @ 18u8CLrvFT…)
2013.12.15 06:00 ( BTC 0.10496045 @ 1Cc3cqwNxW…)
2014.01.05 20:00 ( BTC 0.19720575 @ 1MgNUCu91C…)
2014.01.31 01:00 ( BTC 0.16231348 @ 17Fvm4wnV2…)
2014.02.19 23:00 ( BTC 0.15928156 @ 1NZZnrj424…)
2014.03.11 09:00 ( BTC 0.04172486 @ 19JWNimzAv…)
2014.03.16 18:00 ( BTC 0.14886179 @ 17kuPDcc1Z…)
2014.03.19 22:00 ( BTC 0.16586439 @ 1JQufuRAxZ…)
2014.04.12 19:00 ( BTC 0.24051825 @ 16CxzsWZMR…)
2014.04.20 02:00 ( BTC 0.08650101 @ 13kYZur9vL…)
2014.05.17 20:00 ( BTC 0.11721316 @ 1ESxvrgbDc…)
2014.06.12 04:00 ( BTC 0.24236004 @ 1L5igpTkn7…)
2014.07.04 11:00 ( BTC 0.10876176 @ 1EwYgZypJd…)
2014.07.06 06:00 ( BTC 0.16989481 @ 13QLrseSPy…)
2014.07.15 18:00 ( BTC 0.15330195 @ 1E4bAAJc9p…)
2014.08.09 04:00 ( BTC 0.14879320 @ 1MRVQg2iF9…)
2014.08.20 19:00 ( BTC 0.01109019 @ 1FtjvG1ovL…)
2014.08.29 13:00 ( BTC 0.15039855 @ 17QnK4jWqs…)
2014.09.21 09:00 ( BTC 0.07278034 @ 1MSFQSC1Eb…)
2014.10.15 00:00 ( BTC 0.08274597 @ 1EV8tXeaxQ…)
2014.10.19 10:00 ( BTC 0.10229637 @ 1PMyyzSSvY…)
2014.10.25 00:00 ( BTC 0.10227570 @ 15hKSCeAqo…)
2014.10.28 02:00 ( BTC 0.13436847 @ 1N8HqLgUmj…)
2014.11.14 21:00 ( BTC 0.13117751 @ 19bavZt7ak…)
2014.11.24 18:00 ( BTC 0.12823507 @ 1FLswxR79x…)
2014.12.15 23:00 ( BTC 0.14399117 @ 1CDg49uLMG…)
2014.12.22 11:00 ( BTC 0.14832886 @ 1JJi2znYhJ…)
2015.01.16 19:00 ( BTC 0.22525825 @ 1H7LsuYXM7…)
2015.01.30 16:00 ( BTC 0.20385566 @ 1P4mo1tWdZ…)
2015.02.24 17:00 ( BTC 0.08675131 @ 1EKbWUNAeQ…)
2015.03.10 21:00 ( BTC 0.14433279 @ 1Dsn97DiCN…)
2015.03.14 04:00 ( BTC 0.06965176 @ 16FzAgbGaP…)
2015.04.03 17:00 ( BTC 0.14489684 @ 1732jNsoFR…)
2015.04.05 01:00 ( BTC 0.14564986 @ 1A5uqgi1hP…)
2015.04.17 02:00 ( BTC 0.08946232 @ 1nt3ecn9dK…)
2015.05.08 11:00 ( BTC 0.07180452 @ 1HcccZZsGA…)
2015.05.29 10:00 ( BTC 0.21312575 @ 1EaHNbCkAY…)
2015.06.16 09:00 ( BTC 0.15655103 @ 1B4sw9KswL…)
2015.06.20 23:00 ( BTC 0.20295450 @ 17fV2s23Tq…)
2015.06.23 22:00 ( BTC 0.15270331 @ 18PVVMT9Zw…)
2015.07.09 10:00 ( BTC 0.15388809 @ 1NBU2qPf4A…)
2015.07.21 14:00 ( BTC 0.08517948 @ 1E1PFZQAvt…)
2015.07.31 10:00 ( BTC 0.16136323 @ 1JTSarhS29…)
2015.08.23 10:00 ( BTC 0.12997181 @ 19EsMchF3e…)
2015.09.07 08:00 ( BTC 0.18812160 @ 13YwWEUXsB…)
2015.09.24 08:00 ( BTC 0.09098287 @ 136HCiuNqp…)
2015.10.09 18:00 ( BTC 0.23840699 @ 12EGTe8VRp…)
2015.10.17 17:00 ( BTC 0.14611599 @ 1Dvx8AtQge…)
2015.10.19 09:00 ( BTC 0.19029056 @ 1Kt21F99TV…)
2015.11.12 12:00 ( BTC 0.14514107 @ 13uTNdVoEi…)
2015.11.15 07:00 ( BTC 0.08085023 @ 1C27gLqvZH…)
2015.11.18 15:00 ( BTC 0.20961499 @ 1AXcC94Nw2…)
2015.12.04 04:00 ( BTC 0.16915857 @ 1A4Hkd9CfD…)
2015.12.11 08:00 ( BTC 0.13406852 @ 114sot1xgN…)
2015.12.16 05:00 ( BTC 0.09842571 @ 1PJ7i2unbf…)
2016.01.02 02:00 ( BTC 0.22620943 @ 1LcN22p52S…)
2016.01.04 15:00 ( BTC 0.19615823 @ 1KYWPrFLjN…)
2016.01.21 22:00 ( BTC 0.20498416 @ 1ec9ZhmSzD…)
2016.01.27 21:00 ( BTC 0.07912867 @ 143YAAzz7p…)
2016.02.23 14:00 ( BTC 0.19946785 @ 1JWW8ER7bw…)
2016.03.19 10:00 ( BTC 0.12676135 @ 1CJLHQXKU2…)
2016.04.02 22:00 ( BTC 0.12514775 @ 1CbAaFYPwU…)
2016.04.30 16:00 ( BTC 0.15496838 @ 1BYogoYghA…)
2016.05.22 09:00 ( BTC 0.12903373 @ 1HycvU4vCp…)
2016.06.02 10:00 ( BTC 0.22863883 @ 1C9kdbHx2t…)
2016.06.13 23:00 ( BTC 0.16417925 @ 13KhvJj2ts…)
2016.06.30 08:00 ( BTC 0.00295672 @ 17Y6w1VXer…)
2016.07.22 08:00 ( BTC 0.16371066 @ 18tfQS76Jf…)
2016.08.08 22:00 ( BTC 0.11025634 @ 1MzaTuXiH5…)
2016.09.04 17:00 ( BTC 0.08668744 @ 1CZGm3LLkE…)
2016.09.25 11:00 ( BTC 0.15083061 @ 188UDJJDmy…)
2016.10.19 22:00 ( BTC 0.17780913 @ 16J2LnP8UR…)
2016.11.10 00:00 ( BTC 0.11872289 @ 1BEX3sF6KP…)
2016.12.01 21:00 ( BTC 1.00000000 @ 1HxhG4y1HG…)
Private Key:
WIF: 5KMFa22QksQjRYnkErs6Agzd2tedj2ipYTaD9erCF5vxHSHjheS
RAW: ca01b35d68b393d419ac20bdc8c2136b802c71194fa7665190e35743e8ef2927
Public Key:
0462a36a3b67f4b5bf90dc6c48ac9030f7aaa2d31210e2d7c8274bc2c350d9857bd20ee5a15a261 791b1d8329a0a82ff3e374dffb07915630127aad5c6d135a2c9
This will help test LBAAT to see if the coins sent are secure in the future. Note the BTC 1.000 prize in December 2016. Fastest finger gets the coins. If coins are redeemed early, it is a sign that the information has been compromised. This will help test the service, no warranties. Good luck!
timepoint amount @ address
2012.12.05 14:00 ( BTC 0.22213465 @ 188Ygj43Js…) Claimed 2012 12 05 14:02:49
2012.12.16 12:00 ( BTC 0.10497890 @ 15jazmcwW8…) Claimed 2012 12 16 12:46:49
2013.01.02 13:00 ( BTC 0.12081314 @ 1G9HLxdb1o…) Claimed 2013 01 02 13:01:09 (0daba55ff9bb3320810c8c59e7b2a44e6e7813f8ac190b286e7d4bfb8624cab6)
2013.01.10 01:00 ( BTC 0.14937388 @ 1L8aNgVMXA…)
2013.02.02 07:00 ( BTC 0.13454134 @ 1CavFuhbP6…)
2013.02.11 13:00 ( BTC 0.19772584 @ 14TTEQdoKy…)
2013.02.21 12:00 ( BTC 0.15633881 @ 1AdAbn33r1…)
2013.03.03 08:00 ( BTC 0.17725408 @ 1LiC8Uv1ht…)
2013.03.30 04:00 ( BTC 0.21993430 @ 13eUMwMaGZ…)
2013.04.07 03:00 ( BTC 0.05017415 @ 1GrYBTo5Zj…)
2013.04.09 17:00 ( BTC 0.15187733 @ 12FfPybc7K…)
2013.04.30 19:00 ( BTC 0.07834591 @ 17xAzXLLJJ…)
2013.05.11 05:00 ( BTC 0.14070220 @ 1HEbsMxoiv…)
2013.05.21 06:00 ( BTC 0.13054264 @ 17Z29eiF4v…)
2013.06.07 09:00 ( BTC 0.10659530 @ 1LapSpsLsR…)
2013.06.19 08:00 ( BTC 0.17071023 @ 1HS3sKYz8H…)
2013.06.20 11:00 ( BTC 0.13587414 @ 1C1qH6FJuG…)
2013.07.16 21:00 ( BTC 0.09786455 @ 16DXqzVzRt…)
2013.08.07 12:00 ( BTC 0.17260505 @ 19qCqG4Sjp…)
2013.08.18 09:00 ( BTC 0.02337728 @ 1HqJcJY5nY…)
2013.08.26 09:00 ( BTC 0.07256130 @ 1EaTETEacH…)
2013.09.20 10:00 ( BTC 0.24803214 @ 1G5f2qFBJg…)
2013.10.03 23:00 ( BTC 0.13558857 @ 1JRS18AiE8…)
2013.10.04 11:00 ( BTC 0.10482669 @ 19tivqEnG9…)
2013.10.27 12:00 ( BTC 0.18231765 @ 1H9urmN42U…)
2013.11.07 01:00 ( BTC 0.20127591 @ 18boDLn9ot…)
2013.11.21 19:00 ( BTC 0.10049777 @ 18u8CLrvFT…)
2013.12.15 06:00 ( BTC 0.10496045 @ 1Cc3cqwNxW…)
2014.01.05 20:00 ( BTC 0.19720575 @ 1MgNUCu91C…)
2014.01.31 01:00 ( BTC 0.16231348 @ 17Fvm4wnV2…)
2014.02.19 23:00 ( BTC 0.15928156 @ 1NZZnrj424…)
2014.03.11 09:00 ( BTC 0.04172486 @ 19JWNimzAv…)
2014.03.16 18:00 ( BTC 0.14886179 @ 17kuPDcc1Z…)
2014.03.19 22:00 ( BTC 0.16586439 @ 1JQufuRAxZ…)
2014.04.12 19:00 ( BTC 0.24051825 @ 16CxzsWZMR…)
2014.04.20 02:00 ( BTC 0.08650101 @ 13kYZur9vL…)
2014.05.17 20:00 ( BTC 0.11721316 @ 1ESxvrgbDc…)
2014.06.12 04:00 ( BTC 0.24236004 @ 1L5igpTkn7…)
2014.07.04 11:00 ( BTC 0.10876176 @ 1EwYgZypJd…)
2014.07.06 06:00 ( BTC 0.16989481 @ 13QLrseSPy…)
2014.07.15 18:00 ( BTC 0.15330195 @ 1E4bAAJc9p…)
2014.08.09 04:00 ( BTC 0.14879320 @ 1MRVQg2iF9…)
2014.08.20 19:00 ( BTC 0.01109019 @ 1FtjvG1ovL…)
2014.08.29 13:00 ( BTC 0.15039855 @ 17QnK4jWqs…)
2014.09.21 09:00 ( BTC 0.07278034 @ 1MSFQSC1Eb…)
2014.10.15 00:00 ( BTC 0.08274597 @ 1EV8tXeaxQ…)
2014.10.19 10:00 ( BTC 0.10229637 @ 1PMyyzSSvY…)
2014.10.25 00:00 ( BTC 0.10227570 @ 15hKSCeAqo…)
2014.10.28 02:00 ( BTC 0.13436847 @ 1N8HqLgUmj…)
2014.11.14 21:00 ( BTC 0.13117751 @ 19bavZt7ak…)
2014.11.24 18:00 ( BTC 0.12823507 @ 1FLswxR79x…)
2014.12.15 23:00 ( BTC 0.14399117 @ 1CDg49uLMG…)
2014.12.22 11:00 ( BTC 0.14832886 @ 1JJi2znYhJ…)
2015.01.16 19:00 ( BTC 0.22525825 @ 1H7LsuYXM7…)
2015.01.30 16:00 ( BTC 0.20385566 @ 1P4mo1tWdZ…)
2015.02.24 17:00 ( BTC 0.08675131 @ 1EKbWUNAeQ…)
2015.03.10 21:00 ( BTC 0.14433279 @ 1Dsn97DiCN…)
2015.03.14 04:00 ( BTC 0.06965176 @ 16FzAgbGaP…)
2015.04.03 17:00 ( BTC 0.14489684 @ 1732jNsoFR…)
2015.04.05 01:00 ( BTC 0.14564986 @ 1A5uqgi1hP…)
2015.04.17 02:00 ( BTC 0.08946232 @ 1nt3ecn9dK…)
2015.05.08 11:00 ( BTC 0.07180452 @ 1HcccZZsGA…)
2015.05.29 10:00 ( BTC 0.21312575 @ 1EaHNbCkAY…)
2015.06.16 09:00 ( BTC 0.15655103 @ 1B4sw9KswL…)
2015.06.20 23:00 ( BTC 0.20295450 @ 17fV2s23Tq…)
2015.06.23 22:00 ( BTC 0.15270331 @ 18PVVMT9Zw…)
2015.07.09 10:00 ( BTC 0.15388809 @ 1NBU2qPf4A…)
2015.07.21 14:00 ( BTC 0.08517948 @ 1E1PFZQAvt…)
2015.07.31 10:00 ( BTC 0.16136323 @ 1JTSarhS29…)
2015.08.23 10:00 ( BTC 0.12997181 @ 19EsMchF3e…)
2015.09.07 08:00 ( BTC 0.18812160 @ 13YwWEUXsB…)
2015.09.24 08:00 ( BTC 0.09098287 @ 136HCiuNqp…)
2015.10.09 18:00 ( BTC 0.23840699 @ 12EGTe8VRp…)
2015.10.17 17:00 ( BTC 0.14611599 @ 1Dvx8AtQge…)
2015.10.19 09:00 ( BTC 0.19029056 @ 1Kt21F99TV…)
2015.11.12 12:00 ( BTC 0.14514107 @ 13uTNdVoEi…)
2015.11.15 07:00 ( BTC 0.08085023 @ 1C27gLqvZH…)
2015.11.18 15:00 ( BTC 0.20961499 @ 1AXcC94Nw2…)
2015.12.04 04:00 ( BTC 0.16915857 @ 1A4Hkd9CfD…)
2015.12.11 08:00 ( BTC 0.13406852 @ 114sot1xgN…)
2015.12.16 05:00 ( BTC 0.09842571 @ 1PJ7i2unbf…)
2016.01.02 02:00 ( BTC 0.22620943 @ 1LcN22p52S…)
2016.01.04 15:00 ( BTC 0.19615823 @ 1KYWPrFLjN…)
2016.01.21 22:00 ( BTC 0.20498416 @ 1ec9ZhmSzD…)
2016.01.27 21:00 ( BTC 0.07912867 @ 143YAAzz7p…)
2016.02.23 14:00 ( BTC 0.19946785 @ 1JWW8ER7bw…)
2016.03.19 10:00 ( BTC 0.12676135 @ 1CJLHQXKU2…)
2016.04.02 22:00 ( BTC 0.12514775 @ 1CbAaFYPwU…)
2016.04.30 16:00 ( BTC 0.15496838 @ 1BYogoYghA…)
2016.05.22 09:00 ( BTC 0.12903373 @ 1HycvU4vCp…)
2016.06.02 10:00 ( BTC 0.22863883 @ 1C9kdbHx2t…)
2016.06.13 23:00 ( BTC 0.16417925 @ 13KhvJj2ts…)
2016.06.30 08:00 ( BTC 0.00295672 @ 17Y6w1VXer…)
2016.07.22 08:00 ( BTC 0.16371066 @ 18tfQS76Jf…)
2016.08.08 22:00 ( BTC 0.11025634 @ 1MzaTuXiH5…)
2016.09.04 17:00 ( BTC 0.08668744 @ 1CZGm3LLkE…)
2016.09.25 11:00 ( BTC 0.15083061 @ 188UDJJDmy…)
2016.10.19 22:00 ( BTC 0.17780913 @ 16J2LnP8UR…)
2016.11.10 00:00 ( BTC 0.11872289 @ 1BEX3sF6KP…)
2016.12.01 21:00 ( BTC 1.00000000 @ 1HxhG4y1HG…)
Jump to: