skylord56
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 01, 2019, 06:25:47 PM |
|
So, right now only this BTC addresses left ? 1Me6EfpwZK5kQziBwBfvLiHjaPGxCKLoJi 0.062 BTC 1NpYjtLira16LfGbGwZJ5JbDPh3ai9bjf4 0.063 BTC 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 0.064 BTC 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 0.066 BTC 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9 0.067 BTC 1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ 0.068 BTC 19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG 0.069 BTC 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU 0.071 BTC 1JTK7s9YVYywfm5XUH7RNhHJH1LshCaRFR 0.072 BTC 12VVRNPi4SJqUTsp6FmqDqY5sGosDtysn4 0.073 BTC 1FWGcVDK3JGzCC3WtkYetULPszMaK2Jksv 0.074 BTC 1DJh2eHFYQfACPmrvpyWc8MSTYKh7w9eRF 0.076 BTC 1Bxk4CQdqL9p22JEtDfdXMsng1XacifUtE 0.077 BTC 15qF6X51huDjqTmF9BJgxXdt1xcj46Jmhb 0.078 BTC 1ARk8HWJMn8js8tQmGUJeQHjSE7KRkn2t8 0.079 BTC 15qsCm78whspNQFydGJQk5rexzxTQopnHZ 0.081 BTC 13zYrYhhJxp6Ui1VV7pqa5WDhNWM45ARAC 0.082 BTC 14MdEb4eFcT3MVG5sPFG4jGLuHJSnt1Dk2 0.083 BTC 1CMq3SvFcVEcpLMuuH8PUcNiqsK1oicG2D 0.084 BTC 1K3x5L6G57Y494fDqBfrojD28UJv4s5JcK 0.086 BTC 1PxH3K1Shdjb7gSEoTX7UPDZ6SH4qGPrvq 0.087 BTC 16AbnZjZZipwHMkYKBSfswGWKDmXHjEpSf 0.088 BTC 19QciEHbGVNY4hrhfKXmcBBCrJSBZ6TaVt 0.089 BTC 1EzVHtmbN4fs4MiNk3ppEnKKhsmXYJ4s74 0.091 BTC 1AE8NzzgKE7Yhz7BWtAcAAxiFMbPo82NB5 0.092 BTC 17Q7tuG2JwFFU9rXVj3uZqRtioH3mx2Jad 0.093 BTC 1K6xGMUbs6ZTXBnhw1pippqwK6wjBWtNpL 0.094 BTC 19eVSDuizydXxhohGh8Ki9WY9KsHdSwoQC 0.095 BTC 15ANYzzCp5BFHcCnVFzXqyibpzgPLWaD8b 0.096 BTC 18ywPwj39nGjqBrQJSzZVq2izR12MDpDr8 0.097 BTC 1CaBVPrwUxbQYYswu32w7Mj4HR4maNoJSX 0.098 BTC 1JWnE6p6UN7ZJBN7TtcbNDoRcjFtuDWoNL 0.099 BTC 1KCgMv8fo2TPBpddVi9jqmMmcne9uSNJ5F 0.1 BTC 1CKCVdbDJasYmhswB6HKZHEAnNaDpK7W4n 0.101 BTC 1PXv28YxmYMaB8zxrKeZBW8dt2HK7RkRPX 0.102 BTC 1AcAmB6jmtU6AiEcXkmiNE9TNVPsj9DULf 0.103 BTC 1EQJvpsmhazYCcKX5Au6AZmZKRnzarMVZu 0.104 BTC 1CMjscKB3QW7SDyQ4c3C3DEUHiHRhiZVib 0.105 BTC 18KsfuHuzQaBTNLASyj15hy4LuqPUo1FNB 0.106 BTC 15EJFC5ZTs9nhsdvSUeBXjLAuYq3SWaxTc 0.107 BTC 1HB1iKUqeffnVsvQsbpC6dNi1XKbyNuqao 0.108 BTC 1GvgAXVCbA8FBjXfWiAms4ytFeJcKsoyhL 0.109 BTC 12JzYkkN76xkwvcPT6AWKZtGX6w2LAgsJg 0.11 BTC 1824ZJQ7nKJ9QFTRBqn7z7dHV5EGpzUpH3 0.111 BTC 18A7NA9FTsnJxWgkoFfPAFbQzuQxpRtCos 0.112 BTC 1NeGn21dUDDeqFQ63xb2SpgUuXuBLA4WT4 0.113 BTC 174SNxfqpdMGYy5YQcfLbSTK3MRNZEePoy 0.114 BTC 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv 0.115 BTC 1MnJ6hdhvK37VLmqcdEwqC3iFxyWH2PHUV 0.116 BTC 1KNRfGWw7Q9Rmwsc6NT5zsdvEb9M2Wkj5Z 0.117 BTC 1PJZPzvGX19a7twf5HyD2VvNiPdHLzm9F6 0.118 BTC 1GuBBhf61rnvRe4K8zu8vdQB3kHzwFqSy7 0.119 BTC 17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT 0.12 BTC 1GDSuiThEV64c166LUFC9uDcVdGjqkxKyh 0.121 BTC 1Me3ASYt5JCTAK2XaC32RMeH34PdprrfDx 0.122 BTC 1CdufMQL892A69KXgv6UNBD17ywWqYpKut 0.123 BTC 1BkkGsX9ZM6iwL3zbqs7HWBV7SvosR6m8N 0.124 BTC 1PXAyUB8ZoH3WD8n5zoAthYjN15yN5CVq5 0.125 BTC 1AWCLZAjKbV1P7AHvaPNCKiB7ZWVDMxFiz 0.126 BTC 1G6EFyBRU86sThN3SSt3GrHu1sA7w7nzi4 0.127 BTC 1MZ2L1gFrCtkkn6DnTT2e4PFUTHw9gNwaj 0.128 BTC 1Hz3uv3nNZzBVMXLGadCucgjiCs5W9vaGz 0.129 BTC 1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua 0.13 BTC 16zRPnT8znwq42q7XeMkZUhb1bKqgRogyy 0.131 BTC 1KrU4dHE5WrW8rhWDsTRjR21r8t3dsrS3R 0.132 BTC 17uDfp5r4n441xkgLFmhNoSW1KWp6xVLD 0.133 BTC 13A3JrvXmvg5w9XGvyyR4JEJqiLz8ZySY3 0.134 BTC 16RGFo6hjq9ym6Pj7N5H7L1NR1rVPJyw2v 0.135 BTC 1UDHPdovvR985NrWSkdWQDEQ1xuRiTALq 0.136 BTC 15nf31J46iLuK1ZkTnqHo7WgN5cARFK3RA 0.137 BTC 1Ab4vzG6wEQBDNQM1B2bvUz4fqXXdFk2WT 0.138 BTC 1Fz63c775VV9fNyj25d9Xfw3YHE6sKCxbt 0.139 BTC 1QKBaU6WAeycb3DbKbLBkX7vJiaS8r42Xo 0.14 BTC 1CD91Vm97mLQvXhrnoMChhJx4TP9MaQkJo 0.141 BTC 15MnK2jXPqTMURX4xC3h4mAZxyCcaWWEDD 0.142 BTC 13N66gCzWWHEZBxhVxG18P8wyjEWF9Yoi1 0.143 BTC 1NevxKDYuDcCh1ZMMi6ftmWwGrZKC6j7Ux 0.144 BTC 19GpszRNUej5yYqxXoLnbZWKew3KdVLkXg 0.145 BTC 1M7ipcdYHey2Y5RZM34MBbpugghmjaV89P 0.146 BTC 18aNhurEAJsw6BAgtANpexk5ob1aGTwSeL 0.147 BTC 1FwZXt6EpRT7Fkndzv6K4b4DFoT4trbMrV 0.148 BTC 1CXvTzR6qv8wJ7eprzUKeWxyGcHwDYP1i2 0.149 BTC 1MUJSJYtGPVGkBCTqGspnxyHahpt5Te8jy 0.15 BTC 13Q84TNNvgcL3HJiqQPvyBb9m4hxjS3jkV 0.151 BTC 1LuUHyrQr8PKSvbcY1v1PiuGuqFjWpDumN 0.152 BTC 18192XpzzdDi2K11QVHR7td2HcPS6Qs5vg 0.153 BTC 1NgVmsCCJaKLzGyKLFJfVequnFW9ZvnMLN 0.154 BTC 1AoeP37TmHdFh8uN72fu9AqgtLrUwcv2wJ 0.155 BTC 1FTpAbQa4h8trvhQXjXnmNhqdiGBd1oraE 0.156 BTC 14JHoRAdmJg3XR4RjMDh6Wed6ft6hzbQe9 0.157 BTC 19z6waranEf8CcP8FqNgdwUe1QRxvUNKBG 0.158 BTC 14u4nA5sugaswb6SZgn5av2vuChdMnD9E5 0.159 BTC 1NBC8uXJy1GiJ6drkiZa1WuKn51ps7EPTv 0.16 BTC Are they using same algo with the first 50 one ?
|
|
|
|
BurtW
Legendary
Offline
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 01, 2019, 06:28:30 PM Last edit: July 01, 2019, 06:39:33 PM by BurtW |
|
Yes, like I read everything, you can link to a certain post.
You sure a a lazy shit. Sure, I will give you the link for a fee. How much is it worth to you? I will accept BTC for payment. Looks like someone has found some kind of trick or regularity in calculations. Not really Definitely it can't be luck with stepping 5 No, it is not luck and and can't be hashing or brute-forcing. no hashing needed on these anymore, faster algorithm available for every fifth one Just only if pentagon's admin decided to test the most powerful PC in the world with this puzzle address Probably not but, well maybe
https://bitcointalk.org/index.php?topic=1306983.msg51466379#msg51466379https://bitcointalk.org/index.php?topic=1306983.msg51474410#msg51474410
|
Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated!
|
|
|
BurtW
Legendary
Offline
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 01, 2019, 06:30:16 PM |
|
So, right now only this BTC addresses left ? 1Me6EfpwZK5kQziBwBfvLiHjaPGxCKLoJi 0.062 BTC 1NpYjtLira16LfGbGwZJ5JbDPh3ai9bjf4 0.063 BTC 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN 0.064 BTC 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so 0.066 BTC 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9 0.067 BTC 1MVDYgVaSN6iKKEsbzRUAYFrYJadLYZvvZ 0.068 BTC 19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG 0.069 BTC 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU 0.071 BTC 1JTK7s9YVYywfm5XUH7RNhHJH1LshCaRFR 0.072 BTC 12VVRNPi4SJqUTsp6FmqDqY5sGosDtysn4 0.073 BTC 1FWGcVDK3JGzCC3WtkYetULPszMaK2Jksv 0.074 BTC 1DJh2eHFYQfACPmrvpyWc8MSTYKh7w9eRF 0.076 BTC 1Bxk4CQdqL9p22JEtDfdXMsng1XacifUtE 0.077 BTC 15qF6X51huDjqTmF9BJgxXdt1xcj46Jmhb 0.078 BTC 1ARk8HWJMn8js8tQmGUJeQHjSE7KRkn2t8 0.079 BTC 15qsCm78whspNQFydGJQk5rexzxTQopnHZ 0.081 BTC 13zYrYhhJxp6Ui1VV7pqa5WDhNWM45ARAC 0.082 BTC 14MdEb4eFcT3MVG5sPFG4jGLuHJSnt1Dk2 0.083 BTC 1CMq3SvFcVEcpLMuuH8PUcNiqsK1oicG2D 0.084 BTC 1K3x5L6G57Y494fDqBfrojD28UJv4s5JcK 0.086 BTC 1PxH3K1Shdjb7gSEoTX7UPDZ6SH4qGPrvq 0.087 BTC 16AbnZjZZipwHMkYKBSfswGWKDmXHjEpSf 0.088 BTC 19QciEHbGVNY4hrhfKXmcBBCrJSBZ6TaVt 0.089 BTC 1EzVHtmbN4fs4MiNk3ppEnKKhsmXYJ4s74 0.091 BTC 1AE8NzzgKE7Yhz7BWtAcAAxiFMbPo82NB5 0.092 BTC 17Q7tuG2JwFFU9rXVj3uZqRtioH3mx2Jad 0.093 BTC 1K6xGMUbs6ZTXBnhw1pippqwK6wjBWtNpL 0.094 BTC 19eVSDuizydXxhohGh8Ki9WY9KsHdSwoQC 0.095 BTC 15ANYzzCp5BFHcCnVFzXqyibpzgPLWaD8b 0.096 BTC 18ywPwj39nGjqBrQJSzZVq2izR12MDpDr8 0.097 BTC 1CaBVPrwUxbQYYswu32w7Mj4HR4maNoJSX 0.098 BTC 1JWnE6p6UN7ZJBN7TtcbNDoRcjFtuDWoNL 0.099 BTC 1KCgMv8fo2TPBpddVi9jqmMmcne9uSNJ5F 0.1 BTC 1CKCVdbDJasYmhswB6HKZHEAnNaDpK7W4n 0.101 BTC 1PXv28YxmYMaB8zxrKeZBW8dt2HK7RkRPX 0.102 BTC 1AcAmB6jmtU6AiEcXkmiNE9TNVPsj9DULf 0.103 BTC 1EQJvpsmhazYCcKX5Au6AZmZKRnzarMVZu 0.104 BTC 1CMjscKB3QW7SDyQ4c3C3DEUHiHRhiZVib 0.105 BTC 18KsfuHuzQaBTNLASyj15hy4LuqPUo1FNB 0.106 BTC 15EJFC5ZTs9nhsdvSUeBXjLAuYq3SWaxTc 0.107 BTC 1HB1iKUqeffnVsvQsbpC6dNi1XKbyNuqao 0.108 BTC 1GvgAXVCbA8FBjXfWiAms4ytFeJcKsoyhL 0.109 BTC 12JzYkkN76xkwvcPT6AWKZtGX6w2LAgsJg 0.11 BTC 1824ZJQ7nKJ9QFTRBqn7z7dHV5EGpzUpH3 0.111 BTC 18A7NA9FTsnJxWgkoFfPAFbQzuQxpRtCos 0.112 BTC 1NeGn21dUDDeqFQ63xb2SpgUuXuBLA4WT4 0.113 BTC 174SNxfqpdMGYy5YQcfLbSTK3MRNZEePoy 0.114 BTC 1NLbHuJebVwUZ1XqDjsAyfTRUPwDQbemfv 0.115 BTC 1MnJ6hdhvK37VLmqcdEwqC3iFxyWH2PHUV 0.116 BTC 1KNRfGWw7Q9Rmwsc6NT5zsdvEb9M2Wkj5Z 0.117 BTC 1PJZPzvGX19a7twf5HyD2VvNiPdHLzm9F6 0.118 BTC 1GuBBhf61rnvRe4K8zu8vdQB3kHzwFqSy7 0.119 BTC 17s2b9ksz5y7abUm92cHwG8jEPCzK3dLnT 0.12 BTC 1GDSuiThEV64c166LUFC9uDcVdGjqkxKyh 0.121 BTC 1Me3ASYt5JCTAK2XaC32RMeH34PdprrfDx 0.122 BTC 1CdufMQL892A69KXgv6UNBD17ywWqYpKut 0.123 BTC 1BkkGsX9ZM6iwL3zbqs7HWBV7SvosR6m8N 0.124 BTC 1PXAyUB8ZoH3WD8n5zoAthYjN15yN5CVq5 0.125 BTC 1AWCLZAjKbV1P7AHvaPNCKiB7ZWVDMxFiz 0.126 BTC 1G6EFyBRU86sThN3SSt3GrHu1sA7w7nzi4 0.127 BTC 1MZ2L1gFrCtkkn6DnTT2e4PFUTHw9gNwaj 0.128 BTC 1Hz3uv3nNZzBVMXLGadCucgjiCs5W9vaGz 0.129 BTC 1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua 0.13 BTC 16zRPnT8znwq42q7XeMkZUhb1bKqgRogyy 0.131 BTC 1KrU4dHE5WrW8rhWDsTRjR21r8t3dsrS3R 0.132 BTC 17uDfp5r4n441xkgLFmhNoSW1KWp6xVLD 0.133 BTC 13A3JrvXmvg5w9XGvyyR4JEJqiLz8ZySY3 0.134 BTC 16RGFo6hjq9ym6Pj7N5H7L1NR1rVPJyw2v 0.135 BTC 1UDHPdovvR985NrWSkdWQDEQ1xuRiTALq 0.136 BTC 15nf31J46iLuK1ZkTnqHo7WgN5cARFK3RA 0.137 BTC 1Ab4vzG6wEQBDNQM1B2bvUz4fqXXdFk2WT 0.138 BTC 1Fz63c775VV9fNyj25d9Xfw3YHE6sKCxbt 0.139 BTC 1QKBaU6WAeycb3DbKbLBkX7vJiaS8r42Xo 0.14 BTC 1CD91Vm97mLQvXhrnoMChhJx4TP9MaQkJo 0.141 BTC 15MnK2jXPqTMURX4xC3h4mAZxyCcaWWEDD 0.142 BTC 13N66gCzWWHEZBxhVxG18P8wyjEWF9Yoi1 0.143 BTC 1NevxKDYuDcCh1ZMMi6ftmWwGrZKC6j7Ux 0.144 BTC 19GpszRNUej5yYqxXoLnbZWKew3KdVLkXg 0.145 BTC 1M7ipcdYHey2Y5RZM34MBbpugghmjaV89P 0.146 BTC 18aNhurEAJsw6BAgtANpexk5ob1aGTwSeL 0.147 BTC 1FwZXt6EpRT7Fkndzv6K4b4DFoT4trbMrV 0.148 BTC 1CXvTzR6qv8wJ7eprzUKeWxyGcHwDYP1i2 0.149 BTC 1MUJSJYtGPVGkBCTqGspnxyHahpt5Te8jy 0.15 BTC 13Q84TNNvgcL3HJiqQPvyBb9m4hxjS3jkV 0.151 BTC 1LuUHyrQr8PKSvbcY1v1PiuGuqFjWpDumN 0.152 BTC 18192XpzzdDi2K11QVHR7td2HcPS6Qs5vg 0.153 BTC 1NgVmsCCJaKLzGyKLFJfVequnFW9ZvnMLN 0.154 BTC 1AoeP37TmHdFh8uN72fu9AqgtLrUwcv2wJ 0.155 BTC 1FTpAbQa4h8trvhQXjXnmNhqdiGBd1oraE 0.156 BTC 14JHoRAdmJg3XR4RjMDh6Wed6ft6hzbQe9 0.157 BTC 19z6waranEf8CcP8FqNgdwUe1QRxvUNKBG 0.158 BTC 14u4nA5sugaswb6SZgn5av2vuChdMnD9E5 0.159 BTC 1NBC8uXJy1GiJ6drkiZa1WuKn51ps7EPTv 0.16 BTC Are they using same algo with the first 50 one ? The algorithm used to produce the private keys is the same for all addresses. Most likely #95 will be the next one claimed - but it may take a while for that to happen.
|
Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated!
|
|
|
mrxtraf
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 01, 2019, 06:48:18 PM |
|
Yes, like I read everything, you can link to a certain post.
You sure a a lazy shit. Sure, I will give you the link for a fee. How much is it worth to you? I will accept BTC for payment. Looks like someone has found some kind of trick or regularity in calculations. Not really Definitely it can't be luck with stepping 5 No, it is not luck and and can't be hashing or brute-forcing. no hashing needed on these anymore, faster algorithm available for every fifth one Just only if pentagon's admin decided to test the most powerful PC in the world with this puzzle address Probably not but, well maybe
https://bitcointalk.org/index.php?topic=1306983.msg51466379#msg51466379https://bitcointalk.org/index.php?topic=1306983.msg51474410#msg51474410Sorry. I forgot that the public keys are open there by the author himself. Head brewed from the numbers.
|
|
|
|
AndreuSmetanin
Jr. Member
Offline
Activity: 138
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 01, 2019, 08:07:58 PM |
|
|
|
|
|
olamidey
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 798
Merit: 104
Buy, sell and store real cryptocurrencies
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 01, 2019, 08:36:22 PM |
|
What a complicated puzzle. Guess mega computing could be the only one to solve that. 32btc prize money is bigger than we think considering the fact that BTC is going bull currently. Let's continue our trading and make money trading altcoins. No time to check time
|
|
|
|
AndreuSmetanin
Jr. Member
Offline
Activity: 138
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2019, 06:01:18 AM |
|
What a complicated puzzle. Guess mega computing could be the only one to solve that. 32btc prize money is bigger than we think considering the fact that BTC is going bull currently. Let's continue our trading and make money trading altcoins. No time to check time
Not go big money in altcoins now ,all their age ends.The maximum that could slightly dispersed bitcoin,and then not much and it will soon be blown away again .Everyone is waiting for new technologies based on quantum entanglement and neural networks .There will be no place for primitive mathematics and outdated crypto-algorithms developed in the 60s of the 20th century. ![Grin](https://bitcointalk.org/Smileys/default/grin.gif)
|
|
|
|
adaseb
Legendary
Offline
Activity: 3864
Merit: 1732
Up to 300% + 200 FS deposit bonuses
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2019, 06:26:50 AM |
|
I used to be a regular in this thread. I actually used vanitygen on my R9 280X to try and solve the #54 or #55 key a few years back before someone beat me to it. I only got like 20 MH/s with my 280X while the Nvidia's with Bitcrack got multiples of that and I just gave up.
Anyways regarding the dangers of reusing BTC addresses. I know you shouldn't reuse BTC addresses ever. However why do many exchanges like Bitfinex and Binanace reuse their addresses.
It seems that since these private keys have a low entropy its possible to solve quick with enough RAM as long as the public key is shown. However would this even be possible if the private key is actually completely random and has high entropy. You would need Terabytes and Terabytes of RAM which is not possible these days.
|
|
|
|
BurtW
Legendary
Offline
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2019, 01:29:17 PM |
|
My understanding is there is a bit of a trade off here.
When there is no spend transaction the search method is:
Next Private Key -> Public Key -> Hash -> Bitcoin Address -> Compare Bitcoin Address, repeat until found
Note that due to the hashing functions used the Bitcoin Address is expected within a private key range of only 2160
When there is a spend transaction the search method is:
Next Private Key -> Public Key -> Compare Public Key, repeat until found
Note that the private key range in this case is the full 2256 but there are ways to speed up the process
So, I think full entropy 256 bit private keys are still safe even with multiple spend transactions, but they may be less safe than a 160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions.
Even better yet is a longer full 256 bit Bitcoin address based on a full entropy 256 bit private key with no spend transactions.
|
Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated!
|
|
|
adaseb
Legendary
Offline
Activity: 3864
Merit: 1732
Up to 300% + 200 FS deposit bonuses
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2019, 07:11:52 PM |
|
My understanding is there is a bit of a trade off here.
When there is no spend transaction the search method is:
Next Private Key -> Public Key -> Hash -> Bitcoin Address -> Compare Bitcoin Address, repeat until found
Note that due to the hashing functions used the Bitcoin Address is expected within a private key range of only 2160
When there is a spend transaction the search method is:
Next Private Key -> Public Key -> Compare Public Key, repeat until found
Note that the private key range in this case is the full 2256 but there are ways to speed up the process
So, I think full entropy 256 bit private keys are still safe even with multiple spend transactions, but they may be less safe than a 160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions.
Even better yet is a longer full 256 bit Bitcoin address based on a full entropy 256 bit private key with no spend transactions.
I understand but why can't a HBM2 16GB GPU do this faster than a system with a fast CPU + loads of system RAM. I am not too technical on the details here but I understand that if you know the private key you can easily compute the public key, but not the other way around. So since the search space is small, basically most of the private key starts with 0's then you can easily start a range at the small private keys basically something like " 000000000000000000000000000000000000000000000001A838B13505B26867 " So the GPU would take that and increment it and compute the public key very fast and just compare it to the public key with the funds inside it.
|
|
|
|
BurtW
Legendary
Offline
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 02, 2019, 09:28:39 PM |
|
My understanding is there is a bit of a trade off here.
When there is no spend transaction the search method is:
Next Private Key -> Public Key -> Hash -> Bitcoin Address -> Compare Bitcoin Address, repeat until found
Note that due to the hashing functions used the Bitcoin Address is expected within a private key range of only 2160
When there is a spend transaction the search method is:
Next Private Key -> Public Key -> Compare Public Key, repeat until found
Note that the private key range in this case is the full 2256 but there are ways to speed up the process
So, I think full entropy 256 bit private keys are still safe even with multiple spend transactions, but they may be less safe than a 160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions.
Even better yet is a longer full 256 bit Bitcoin address based on a full entropy 256 bit private key with no spend transactions.
I understand but why can't a HBM2 16GB GPU do this faster than a system with a fast CPU + loads of system RAM. I am not too technical on the details here but I understand that if you know the private key you can easily compute the public key, but not the other way around. So since the search space is small, basically most of the private key starts with 0's then you can easily start a range at the small private keys basically something like " 000000000000000000000000000000000000000000000001A838B13505B26867 " So the GPU would take that and increment it and compute the public key very fast and just compare it to the public key with the funds inside it. What you are describing is the "brute force" method which can be done even faster than you think. Since the PublicKey = PrivateKey * G (where G is an agreed to point on the elliptic curve and * is the defined scalar multiplication operation over the finite field of points on the elliptic curve) you can do the following: 0) Initialize PrivateKey to the start of the range you are interested in 1) Calculate the first PublicKey = PrivateKey * G 2) Compare the PublicKey to the target PublicKey, if they match then you are done and PrivateKey is the private key you are looking for 3) PrivateKey = PrivateKey + 1 4) PublicKey = PublicKey + G (instead of PublicKey = PrivateKey * G because adding the point G to the current PublicKey point is faster than calculating the PublicKey point from PublicKey = PrivateKey * G "from scratch" every time through the loop) 5) Goto step 2) However, people that are doing this search are not using this "brute force" method. They are using a much faster method. This much faster method requires a lot of RAM. This faster method is described in detail in a very large post withing the last few pages of this thread. Check it out.
|
Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated!
|
|
|
|
AndreuSmetanin
Jr. Member
Offline
Activity: 138
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2019, 08:13:36 AM |
|
It's fantastic !!!! Congratulations to the winner !! Can he share with us how he was able to put this into practice.
|
|
|
|
virus-cyber
Newbie
Offline
Activity: 22
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2019, 08:19:55 AM Last edit: July 06, 2019, 08:32:58 AM by virus-cyber |
|
Nothing will be shared by them, but they will not forget what more they can solve, and then it will be possible and I will think it will be silenced ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) I think this they solve the problem pikachunakapika or arulbero simply didn’t have been done anyway anyway arulbero said that it could search for a key to be 160 sorry my english translate
|
|
|
|
virus-cyber
Newbie
Offline
Activity: 22
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2019, 08:40:55 AM |
|
from transactions it is clear that these are 3 different people ![Cool](https://bitcointalk.org/Smileys/default/cool.gif)
|
|
|
|
aplistir
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2019, 08:46:30 AM |
|
When there is a spend transaction the search method is:
Next Private Key -> Public Key -> Compare Public Key, repeat until found
Note that the private key range in this case is the full 2256 but there are ways to speed up the process
So, I think full entropy 256 bit private keys are still safe even with multiple spend transactions, but they may be less safe than a 160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions.
When the public key is known, there is a BIG speed up. With the fastest known algorithm the bit strength is cut to HALF so it is only 128bit security. Which is indeed a lot less than the 160 bit of hashed addresses. But even 128 bits is secure. There is no way to brute force 128 bits, That is unless someone comes up with a new additional way to speed up the calculations
|
My Address: 121f7zb2U4g9iM4MiJTDhEzqeZGHzq5wLh
|
|
|
BurtW
Legendary
Offline
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2019, 02:16:22 PM |
|
I don't know why but I'm smelling a big scam.
You are smelling a big scam because you did not bother to read the thread and came in here and dumped a stinking pile of your uninformed opinion on the thread. What you are smelling is not a scam but your own steaming pile of opinion.
|
Our family was terrorized by Homeland Security. Read all about it here: http://www.jmwagner.com/ and http://www.burtw.com/ Any donations to help us recover from the $300,000 in legal fees and forced donations to the Federal Asset Forfeiture slush fund are greatly appreciated!
|
|
|
adaseb
Legendary
Offline
Activity: 3864
Merit: 1732
Up to 300% + 200 FS deposit bonuses
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2019, 11:04:02 PM |
|
So how secure are satoshi's coins which were mined directly and put in a public address instead of a BTC address.
Because you are saying that reusing addresses is not good because its not as secure but if this was the case why wouldn't this person who is solving all these puzzles for less than <1 BTC instead try and crack Satoshi's early coins which are sitting in all those public key addresses?
I think why its faster is because the search space is much small compared to the entire 128 bit search space, so its still safe to re-use addresses since as far as we know ECDSA hasn't been cracked yet or some exploit found.
|
|
|
|
AndreuSmetanin
Jr. Member
Offline
Activity: 138
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2019, 04:42:39 AM |
|
So how secure are satoshi's coins which were mined directly and put in a public address instead of a BTC address.
Because you are saying that reusing addresses is not good because its not as secure but if this was the case why wouldn't this person who is solving all these puzzles for less than <1 BTC instead try and crack Satoshi's early coins which are sitting in all those public key addresses?
I think why its faster is because the search space is much small compared to the entire 128 bit search space, so its still safe to re-use addresses since as far as we know ECDSA hasn't been cracked yet or some exploit found.
Few people deal with this issue, as soon as it is put on stream then This standard ECDSA will quickly split. ![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif)
|
|
|
|
Firebox
Jr. Member
Offline
Activity: 59
Merit: 3
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 07, 2019, 10:52:34 PM |
|
from transactions it is clear that these are 3 different people ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) How you may know, Mate, that it was three different people? Because all that transactions to three different addresses? ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) ---- I'm still pretty sure that someone had found some weakness or tricky way in how to recover private keys. But the way is not really easy because it takes several days to Mr. X to recover the private key, OR theway is really easy but the Mr. X has an ancient type PC and so it takes him several days to recover the private key. Step "5" is not a sudden one, there is definetely something behind it! Otherwise if you have a way to recover the private key from four addresses with total amount of 3.7 BTC why wouldn't you do it??? ---- Also could be that there is a group of Mr. Xs who rent several VPSs with a huge RAM and distribute keyspaces between each other to search. That would be quite an easy way for thouse who have money to invest and if the BS GS really the one which helps to find the private keys. ---- In any way that Mr. X is genius compared to us, guys! ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) And 99.9% sure that Mr. X or Xs was/were here on this forum reading this topic. ---- Dear Mr. X pls share with us at least the recently found private keys for our records.
|
|
|
|
|