COBRAS (OP)
Member
Offline
Activity: 887
Merit: 22
|
|
July 18, 2020, 02:20:56 PM |
|
Good day ! How how long will it take brute force 64 Bytr privatekey ? 65 Byte privatekey ? 70 Byte privatekey ? If GPU power = 6 000 Mkeys/sec Big Thank you
|
[
|
|
|
bigvito19
|
|
July 18, 2020, 02:44:35 PM |
|
Good day ! How how long will it take brute force 64 Bytr privatekey ? 65 Byte privatekey ? 70 Byte privatekey ? If GPU power = 6 000 Mkeys/sec Big Thank you 2^64 = 98 years 2^65 = 195 years 2^70 = 6,239 years
|
|
|
|
TheArchaeologist
|
|
July 18, 2020, 06:07:20 PM |
|
Guess what? Bitcoin Private keys are only 32 byte (256 bit) in length. So happy hacking!
/sarcasm
|
Sooner or later you're going to realize, just as I did, that there's a difference between knowing the path and walking the path
|
|
|
bigvito19
|
|
July 18, 2020, 07:35:45 PM |
|
How how long will it take brute force 64 Bytr privatekey ? 65 Byte privatekey ? 70 Byte privatekey ? If GPU power = 6 000 Mkeys/sec
2^64 = 98 years 2^65 = 195 years 2^70 = 6,239 years You confused bits with bytes. Also, those are worst case. The average times are half. Using a naive search: Average time (in seconds) = 2 bytes x 8 - 1 / 6x10 964 bytes = 3.54x10 136 years 65 bytes = 9.06x10 138 years 70 bytes = 9.97x10 150 years 256 bits = 3.06x10 59 years If you use have a huge amount of memory you can use the method discussed here: https://bitcointalk.org/index.php?topic=5244940.0, and theoretically reduce the average times to: Average time (in seconds) = 2 bytes x 4 / 6x10 964 bytes = 6.12x10 59 years 65 bytes = 9.78x10 60 years 70 bytes = 1.03x10 67 years 256 bits = 1.80x10 21 years As you can see, attempting to crack a private key by brute force guessing is quite hopeless. No, he meant bits not bytes, he always call bits bytes
|
|
|
|
COBRAS (OP)
Member
Offline
Activity: 887
Merit: 22
|
|
July 19, 2020, 01:41:13 AM |
|
I not understand how long will take for ex 64 puzle ? I calc in exell and get 36 year, I was try brute and get 2^47 in 3 days. wtf what is happening, please explain to me how much time will it really take ? I can't figure out how 2^47 in 3 days goes with 32 years if 2^64 p.s. And fuck, I spent a lot of money to calc these 2^47 and more money to spend on brute is not possible, not knowing whether I will finish the puzzle or not.
|
[
|
|
|
WanderingPhilospher
Full Member
Offline
Activity: 1078
Merit: 223
Shooters Shoot...
|
|
July 19, 2020, 07:47:30 AM |
|
I not understand how long will take for ex 64 puzle ? I calc in exell and get 36 year, I was try brute and get 2^47 in 3 days. wtf what is happening, please explain to me how much time will it really take ? I can't figure out how 2^47 in 3 days goes with 32 years if 2^64 p.s. And fuck, I spent a lot of money to calc these 2^47 and more money to spend on brute is not possible, not knowing whether I will finish the puzzle or not. COBRAS, Worst case scenario: take 2^64 (18,446,744,073,709,551,616) divide that by how many Keys your equipment can check in an hour or day or whatever time; I'll use by day as an example (24 hours). You said you have 6 000 Mkeys/sec, so 6,000,000,000 keys per second equals 518,400,000,000,000 keys checked in a day. Now, divide 2^64 (18,446,744,073,709,551,616) by 518,400,000,000,000 keys per day = 35,583 days which = a little over 97 years.
|
|
|
|
COBRAS (OP)
Member
Offline
Activity: 887
Merit: 22
|
|
July 19, 2020, 07:52:45 AM |
|
I not understand how long will take for ex 64 puzle ? I calc in exell and get 36 year, I was try brute and get 2^47 in 3 days. wtf what is happening, please explain to me how much time will it really take ? I can't figure out how 2^47 in 3 days goes with 32 years if 2^64 p.s. And fuck, I spent a lot of money to calc these 2^47 and more money to spend on brute is not possible, not knowing whether I will finish the puzzle or not. COBRAS, Worst case scenario: take 2^64 (18,446,744,073,709,551,616) divide that by how many Keys your equipment can check in an hour or day or whatever time; I'll use by day as an example (24 hours). You said you have 6 000 Mkeys/sec, so 6,000,000,000 keys per second equals 518,400,000,000,000 keys checked in a day. Now, divide 2^64 (18,446,744,073,709,551,616) by 518,400,000,000,000 keys per day = 35,583 days which = a little over 97 years. Bro, but I use not 2^64, bat 2^64-2^63 . It will be too 97 years ? Thx, for your calc.
|
[
|
|
|
WanderingPhilospher
Full Member
Offline
Activity: 1078
Merit: 223
Shooters Shoot...
|
|
July 19, 2020, 07:58:13 AM |
|
I not understand how long will take for ex 64 puzle ? I calc in exell and get 36 year, I was try brute and get 2^47 in 3 days. wtf what is happening, please explain to me how much time will it really take ? I can't figure out how 2^47 in 3 days goes with 32 years if 2^64 p.s. And fuck, I spent a lot of money to calc these 2^47 and more money to spend on brute is not possible, not knowing whether I will finish the puzzle or not. COBRAS, Worst case scenario: take 2^64 (18,446,744,073,709,551,616) divide that by how many Keys your equipment can check in an hour or day or whatever time; I'll use by day as an example (24 hours). You said you have 6 000 Mkeys/sec, so 6,000,000,000 keys per second equals 518,400,000,000,000 keys checked in a day. Now, divide 2^64 (18,446,744,073,709,551,616) by 518,400,000,000,000 keys per day = 35,583 days which = a little over 97 years. Bro, but I use not 2^64, bat 2^64-2^63 . It will be too 97 years ? drop it down to 62, for good measure... 2 ^ 62 = 4,611,686,018,427,387,904; divide by your power per day (24 hours) 518,400,000,000,000 keys = 8,895 days = 24+ years. at 2^63, will take 48+ years.
|
|
|
|
TheArchaeologist
|
I calc in exell and get 36 year, I was try brute and get 2^47 in 3 days. wtf what is happening, please explain to me how much time will it really take ? I can't figure out how 2^47 in 3 days goes with 32 years if 2^64 It seems you are blinded by "getting rich" instead of understanding what you are trying to do. If you knew a few things about exponential math you would not keep on repeating questions like this. p.s. And fuck, I spent a lot of money to calc these 2^47 and more money to spend on brute is not possible, not knowing whether I will finish the puzzle or not.
It's not like you weren't told before this would not work. So now you have to make a decision: keep ignoring the answers you get or just give up. All I can say: any money you poor into this is lost. One last ting: I personally don't mind answering questions but all of your post are about how to "hack" bitcoin and get rich. You have been told a lot of times what you are trying to do simply won't work. But instead you keep going on your wild goose chase.
|
Sooner or later you're going to realize, just as I did, that there's a difference between knowing the path and walking the path
|
|
|
WanderingPhilospher
Full Member
Offline
Activity: 1078
Merit: 223
Shooters Shoot...
|
|
July 19, 2020, 08:13:05 AM |
|
I calc in exell and get 36 year, I was try brute and get 2^47 in 3 days. wtf what is happening, please explain to me how much time will it really take ? I can't figure out how 2^47 in 3 days goes with 32 years if 2^64 It seems you are blinded by "getting rich" instead of understanding what you are trying to do. If you knew a few things about exponential math you would not keep on repeating questions like this. p.s. And fuck, I spent a lot of money to calc these 2^47 and more money to spend on brute is not possible, not knowing whether I will finish the puzzle or not.
It's not like you weren't told before this would not work. So now you have to make a decision: keep ignoring the answers you get or just give up. All I can say: any money you poor into this is lost. One last ting: I personally don't mind answering questions but all of your post are about how to "hack" bitcoin and get rich. You have been told a lot of times what you are trying to do simply won't work. But instead you keep going on your wild goose chase. I wouldn't say "this would not work"...all depends on how many GPUs you have. And also how you attack it.
|
|
|
|
TheArchaeologist
|
|
July 19, 2020, 08:20:26 AM |
|
I wouldn't say "this would not work"...all depends on how many GPUs you have. And also how you attack it.
Trust me: in his case it wouldn't work. He posted before he is using a single Nvidia 2080ti. And since the "64 byte" puzzle he is trying to use has an unknown public key bruteforcing is the only way to attack it. But replies like yours just keep him going because all he reads is "hey, you see it is possible".
|
Sooner or later you're going to realize, just as I did, that there's a difference between knowing the path and walking the path
|
|
|
WanderingPhilospher
Full Member
Offline
Activity: 1078
Merit: 223
Shooters Shoot...
|
|
July 19, 2020, 08:30:23 AM |
|
I wouldn't say "this would not work"...all depends on how many GPUs you have. And also how you attack it.
Trust me: in his case it wouldn't work. He posted before he is using a single Nvidia 2080ti. And since the "64 byte" puzzle he is trying to use has an unknown public key bruteforcing is the only way to attack it. But replies like yours just keep him going because all he reads is "hey, you see it is possible". Ha! I didn't say it was or wasn't possible with 1 GPU; I merely said I wouldn't say it wouldn't work. He said he had 6,000 Mkey/s which is more than 1 GPU. To break Bitcoin is easy...it really is. If there was a dedicated pool, Bitcoin would fall. Look at all the hashing power on Nicehash. People renting their rigs. If a pool had 1/10th of that power (non asic algos) bitcoin would fall...meaning the pool could find any/all private coins. The problem is trust; no one trusts one another and no one would trust the pool operator/creator. But, if someone creates a pool, or site, like Nicehash, that runs bruteforce software, instead of mining software, and people are paid to "rent" their computing power, Bitcoin would fall...no quantum computer needed.
|
|
|
|
pooya87
Legendary
Offline
Activity: 3500
Merit: 10686
|
|
July 19, 2020, 08:51:53 AM |
|
To break Bitcoin is easy...it really is. If there was a dedicated pool, Bitcoin would fall. Look at all the hashing power on Nicehash. People renting their rigs. If a pool had 1/10th of that power (non asic algos) bitcoin would fall...meaning the pool could find any/all private coins.
you have zero understanding of bitcoin and the cryptography used by it, bro.
|
. .BLACKJACK ♠ FUN. | | | ███▄██████ ██████████████▀ ████████████ █████████████████ ████████████████▄▄ ░█████████████▀░▀▀ ██████████████████ ░██████████████ █████████████████▄ ░██████████████▀ ████████████ ███████████████░██ ██████████ | | CRYPTO CASINO & SPORTS BETTING | | │ | | │ | ▄▄███████▄▄ ▄███████████████▄ ███████████████████ █████████████████████ ███████████████████████ █████████████████████████ █████████████████████████ █████████████████████████ ███████████████████████ █████████████████████ ███████████████████ ▀███████████████▀ ███████████████████ | | .
|
|
|
|
WanderingPhilospher
Full Member
Offline
Activity: 1078
Merit: 223
Shooters Shoot...
|
|
July 19, 2020, 08:56:03 AM |
|
To break Bitcoin is easy...it really is. If there was a dedicated pool, Bitcoin would fall. Look at all the hashing power on Nicehash. People renting their rigs. If a pool had 1/10th of that power (non asic algos) bitcoin would fall...meaning the pool could find any/all private coins.
you have zero understanding of bitcoin and the cryptography used by it, bro. Ok...build the pool and let's see
|
|
|
|
TheArchaeologist
|
|
July 19, 2020, 08:56:22 AM |
|
To break Bitcoin is easy...it really is. If there was a dedicated pool, Bitcoin would fall. Look at all the hashing power on Nicehash. People renting their rigs. If a pool had 1/10th of that power (non asic algos) bitcoin would fall...meaning the pool could find any/all private coins.
The problem is trust; no one trusts one another and no one would trust the pool operator/creator. But, if someone creates a pool, or site, like Nicehash, that runs bruteforce software, instead of mining software, and people are paid to "rent" their computing power, Bitcoin would fall...no quantum computer needed.
Lol, if this was the case it would have been done already. You describe bitcoin like it is hackable in a way that is absolutely not. If you are so sure about this why don't you rent all that power to "hack" any/all private coins. Let's start with addresses with a couple of thousand coins as balance. This has nothing to do with "trust" it is just a simple matter of return on investment. If the investment is higher than your gain you simply won't do it. Edit: @pooya87, I typed my reply when you already submitted yours but I agree with you 100%
|
Sooner or later you're going to realize, just as I did, that there's a difference between knowing the path and walking the path
|
|
|
WanderingPhilospher
Full Member
Offline
Activity: 1078
Merit: 223
Shooters Shoot...
|
|
July 19, 2020, 09:18:58 AM |
|
To break Bitcoin is easy...it really is. If there was a dedicated pool, Bitcoin would fall. Look at all the hashing power on Nicehash. People renting their rigs. If a pool had 1/10th of that power (non asic algos) bitcoin would fall...meaning the pool could find any/all private coins.
The problem is trust; no one trusts one another and no one would trust the pool operator/creator. But, if someone creates a pool, or site, like Nicehash, that runs bruteforce software, instead of mining software, and people are paid to "rent" their computing power, Bitcoin would fall...no quantum computer needed.
Lol, if this was the case it would have been done already. You describe bitcoin like it is hackable in a way that is absolutely not. If you are so sure about this why don't you rent all that power to "hack" any/all private coins. Let's start with addresses with a couple of thousand coins as balance. This has nothing to do with "trust" it is just a simple matter of return on investment. If the investment is higher than your gain you simply won't do it. Edit: @pooya87, I typed my reply when you already submitted yours but I agree with you 100% There is no power to rent to "hack" as of now, like Nicehash. If there was, I would. But there's not. I believe it could be done by brute force, but let's talk about the most recent find in the 32BTC challenge/puzzle. The 2^115 key was just found, in 11-13 days, using 256 V100s. Now, imagine what you could do with 4,700,000 V100s. (rough numbers using hash power of 1 V100, compared to hashing power that is available for 1 algo on Nicehash) You can say I don't know the cryptography of BTC and that's fine...but all it would take is to "hack" one private key with a substantial amount of BTC and I believe people would start to sell/move their crypto elsewhere.
|
|
|
|
TheArchaeologist
|
The 2^115 key was just found, in 11-13 days, using 256 V100s. Now, imagine what you could do with 4,700,000 V100s. (rough numbers using hash power of 1 V100, compared to hashing power that is available for 1 algo on Nicehash)
You can say I don't know the cryptography of BTC and that's fine...but all it would take is to "hack" one private key with a substantial amount of BTC and I believe people would start to sell/move their crypto elsewhere.
You just prove the point we make that you just don't understand this enough. There is a huge difference between a private key made specifically for the purpose of a brute force puzzle/check with a very limited search space and where the public key is known versus a regular private key based upon a random true number. The point is in that last case you could indeed rent 4,700,000 V100s pay for that for the next billion years and still fail. And we are talking about a single address, not all of bitcoin as you claim.
|
Sooner or later you're going to realize, just as I did, that there's a difference between knowing the path and walking the path
|
|
|
TheArchaeologist
|
|
July 19, 2020, 03:27:44 PM |
|
Which altcoin uses private key with size of 64, 65 or 70 byte?
None. OP meant a private key for bitcoin with a limited search space for the private key of 64, 65, or 70 bits. Or in other words the bruteforce challange from this topic: https://bitcointalk.org/index.php?topic=1306983.0.
|
Sooner or later you're going to realize, just as I did, that there's a difference between knowing the path and walking the path
|
|
|
|