Bitcoin Forum
September 19, 2021, 05:53:45 PM *
News: Latest Bitcoin Core release: 22.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 [186] 187 188 »
  Print  
Author Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22]  (Read 1148461 times)
ViqRa
Jr. Member
*
Offline Offline

Activity: 46
Merit: 36


View Profile
August 10, 2020, 04:12:04 PM
 #3701

Vanitygen is giving me a wrong private key for my IXC address. Is there a way to fix that without editing the source code?

Thanks in advance.

I just take a peek at IXC announcment thread and looks like the developer merely change the prefix from 1 to x.

Assuming my speculation is correct, it might be because vanitygen uses private key format (WIF with prefix 5) which indicate usage of uncompressed public key while most wallet would create compressed public key by default.
Thanks for answering.

The issue I see is that it gives me a wrong prefix for the private keys (i.e M, N and L) when it should be a 5 or K, L as you say. I believe the length is wrong also, 50 characters, when they should be either 51 or 52.
1632074025
Hero Member
*
Offline Offline

Posts: 1632074025

View Profile Personal Message (Offline)

Ignore
1632074025
Reply with quote  #2

1632074025
Report to moderator
1632074025
Hero Member
*
Offline Offline

Posts: 1632074025

View Profile Personal Message (Offline)

Ignore
1632074025
Reply with quote  #2

1632074025
Report to moderator
1632074025
Hero Member
*
Offline Offline

Posts: 1632074025

View Profile Personal Message (Offline)

Ignore
1632074025
Reply with quote  #2

1632074025
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1632074025
Hero Member
*
Offline Offline

Posts: 1632074025

View Profile Personal Message (Offline)

Ignore
1632074025
Reply with quote  #2

1632074025
Report to moderator
1632074025
Hero Member
*
Offline Offline

Posts: 1632074025

View Profile Personal Message (Offline)

Ignore
1632074025
Reply with quote  #2

1632074025
Report to moderator
nc50lc
Legendary
*
Offline Offline

Activity: 1442
Merit: 2196


Self-proclaimed Genius ㊙️


View Profile
August 11, 2020, 02:34:09 AM
 #3702

Vanitygen is giving me a wrong private key for my IXC address. Is there a way to fix that without editing the source code?
AFAIK, you should be able to use the result of vanitygen to IXC,
if '1' isn't useable, you should convert the address manually by 'BASE58 decode' the address then change the network bytes and checksum.
The private key should be the same as Bitcoin WIF prv key (uncompressed) based from an IXC paper wallet generator (link).

The issue I see is that it gives me a wrong prefix for the private keys (i.e M, N and L) when it should be a 5 or K, L as you say. I believe the length is wrong also, 50 characters, when they should be either 51 or 52.
Everything you said here aren't what vanitygen would produce. Vanitygen's result WIF prvkey for mainnet will always start with '5' consisting of 51-characters.
Are you sure that you're using the right binary (from OP) or commands?

Are you using this to bruteforce a private key? Bec. it's not recommended for that.

ViqRa
Jr. Member
*
Offline Offline

Activity: 46
Merit: 36


View Profile
August 11, 2020, 03:28:50 PM
 #3703

Vanitygen is giving me a wrong private key for my IXC address. Is there a way to fix that without editing the source code?
AFAIK, you should be able to use the result of vanitygen to IXC,
if '1' isn't useable, you should convert the address manually by 'BASE58 decode' the address then change the network bytes and checksum.
The private key should be the same as Bitcoin WIF prv key (uncompressed) based from an IXC paper wallet generator (link).

The issue I see is that it gives me a wrong prefix for the private keys (i.e M, N and L) when it should be a 5 or K, L as you say. I believe the length is wrong also, 50 characters, when they should be either 51 or 52.
Everything you said here aren't what vanitygen would produce. Vanitygen's result WIF prvkey for mainnet will always start with '5' consisting of 51-characters.
Are you sure that you're using the right binary (from OP) or commands?

Are you using this to bruteforce a private key? Bec. it's not recommended for that.
Well, that is what vanitygen is producing for IXC, other coins seem fine. Yes, I am using the right binary from the OP. No, I am not using it to bruteforce a private key.

This is the command I'm running: ./vanitygen -X 138 xabcd
nc50lc
Legendary
*
Offline Offline

Activity: 1442
Merit: 2196


Self-proclaimed Genius ㊙️


View Profile
August 12, 2020, 05:02:03 AM
Merited by ETFbitcoin (2)
 #3704

This is the command I'm running: ./vanitygen -X 138 xabcd
Okay, seems like there's something wrong with Vanitygen when it comes with Altcoins, but there's a workaround to that.

You can convert the result invalid WIF private key into the correct format by base58-decoding it into HEX, remove the checksum and network bytes,
and you got the private key.
Then covert that into WIF by doing vice-versa but this time, use "0x80" instead of '0x0A' in front.

This page automates all of that, displays an example and the steps: https://gobittest.appspot.com/PrivateKey,
Just paste the N, M or L WIF prvkey to the first text box, hit "send", and the result will be displayed under "Private key to wallet import format" at step #7.
But it's not available offline, if you want a secure method, find a script or something.

ViqRa
Jr. Member
*
Offline Offline

Activity: 46
Merit: 36


View Profile
August 13, 2020, 03:04:40 PM
 #3705

This is the command I'm running: ./vanitygen -X 138 xabcd
Okay, seems like there's something wrong with Vanitygen when it comes with Altcoins, but there's a workaround to that.

You can convert the result invalid WIF private key into the correct format by base58-decoding it into HEX, remove the checksum and network bytes,
and you got the private key.
Then covert that into WIF by doing vice-versa but this time, use "0x80" instead of '0x0A' in front.

This page automates all of that, displays an example and the steps: https://gobittest.appspot.com/PrivateKey,
Just paste the N, M or L WIF prvkey to the first text box, hit "send", and the result will be displayed under "Private key to wallet import format" at step #7.
But it's not available offline, if you want a secure method, find a script or something.

Thanks! I will try that.
alevlaslo
Hero Member
*****
Offline Offline

Activity: 1918
Merit: 591


View Profile
October 15, 2020, 02:49:16 PM
 #3706

1CounterpartyXXXXXXXXXXXXXXXUWLpVr

this address has more than 2000 bitcoins, it was created using this program? How long did the process take? If you can create such an address, can you use the full address to calculate the private key?  Roll Eyes

nullius
Copper Member
Hero Member
*****
Offline Offline

Activity: 588
Merit: 2335


There is only one Bitcoin.


View Profile WWW
October 15, 2020, 03:43:08 PM
Merited by xandry (2), BlackHatCoiner (1)
 #3707

1CounterpartyXXXXXXXXXXXXXXXUWLpVr

this address has more than 2000 bitcoins, it was created using this program? How long did the process take? If you can create such an address, can you use the full address to calculate the private key?  Roll Eyes

That is a burn address like 1BitcoinEaterAddressDontSendf59kuE, or 1111111111111111111114oLvT2 (all-zero Hash160).  It is constructed in such a way as to make it obvious that nobody has the private key.  Funds sent to such addresses are irretrievably lost.

Here is a valid Segwit burn address, with all-zero Hash160:  bc1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq9e75rsFunds sent to this address are irretrievably lost.

The 1CounterpartyXXXXXXXXXXXXXXXUWLpVr address was created specifically for Counterparty’s proof-of-burn protocol.

The supply of XCP was created in a process called ‘proof-of-burn’ that lasted from January 2nd to February 3rd 2014 (5000 Bitcoin blocks). During this period, anyone was able to exchange bitcoins for XCP automatically on a protocol level under the following conditions:

  • Users sent their BTC to a verifiably unspendable Bitcoin address with no known private key. (1CounterpartyXXXXXXXXXXXXXXXUWLpVr)
  • Each BTC was automatically exchanged for a number of XCP between 1000 and 1500, with more being rewarded the earlier the burn took place.

Stupid, in my opinion.  Nobody can ever spend that money.  It permanently spams the UTXO set for people who actually use Bitcoin.  But—well, now you know the purpose of that address.

No, Vanitygen cannot crack its private key.  You are welcome to try, with that or any other address.  Have fun. :-)

HTH.

BlackHatCoiner
Hero Member
*****
Offline Offline

Activity: 546
Merit: 1271


Not your node, not your rules.


View Profile WWW
October 15, 2020, 04:07:02 PM
 #3708

@alevlaslo, generally when you see coins on addresses that look like this: 1xxxxxxxxxxxxxxxxxxxxxxxxxy1kmdGr, they are gone forever. If we ever find a way to get the private key for that address (if there is any), we will face much more worse problems than those you can imagine.

Stupid, in my opinion.  Nobody can ever spend that money.
Let the stupid ones burn their bitcoins. They make them more valuable without knowing it.  Wink

xhomerx10
Legendary
*
Offline Offline

Activity: 2870
Merit: 4163


Go! BTC Go!


View Profile
October 15, 2020, 04:16:08 PM
 #3709

1CounterpartyXXXXXXXXXXXXXXXUWLpVr

this address has more than 2000 bitcoins, it was created using this program? How long did the process take? If you can create such an address, can you use the full address to calculate the private key?  Roll Eyes

 1a1ev1as1oyouareveryfunnyxy4cGdVr  <---That address is a valid Bitcoin address but nobody has the private key.

 I'm sure you already know this and you just need another cup of coffee to help refresh your memory:



edit: found my post on burner address creation - https://bitcointalk.org/index.php?topic=90982.msg46771759#msg46771759


############.########..##.....##.####.##.......########..####.##....##..######.........###.......########..########.########.########.########.########.....########.##..........###.....######..##.....##.##.......####..######...##.....##.########.#########..#######. +----
############.##.....##.##.....##..##..##.......##.....##..##..###...##.##....##.......##.##......##.....##.##..........##.......##....##.......##.....##....##.......##.........##.##...##....##.##.....##.##........##..##....##..##.....##....##....###########...##### +++++++
############.##.....##.##.....##..##..##.......##.....##..##..####..##.##............##...##.....##.....##.##..........##.......##....##.......##.....##....##.......##........##...##..##.......##.....##.##........##..##........##.....##....##....############...####+++++++++
############.########..##.....##..##..##.......##.....##..##..##.##.##.##...####....##.....##....########..######......##.......##....######...########.....######...##.......##.....##..######..#########.##........##..##...####.#########....##....############...####+++++++++
############.##.....##.##.....##..##..##.......##.....##..##..##..####.##....##.....#########....##.....##.##..........##.......##....##.......##...##......##.......##.......#########.......##.##.....##.##........##..##....##..##.....##....##....############...####+++++++++
############.##.....##.##.....##..##..##.......##.....##..##..##...###.##....##.....##.....##....##.....##.##..........##.......##....##.......##....##.....##.......##.......##.....##.##....##.##.....##.##........##..##....##..##.....##....##....###########...##### +++++++
############.########...#######..####.########.########..####.##....##..######......##.....##....########..########....##.......##....########.##.....##....##.......########.##.....##..######..##.....##.########.####..######...##.....##....##....#########..#######. +----
SIDEHACK
alevlaslo
Hero Member
*****
Offline Offline

Activity: 1918
Merit: 591


View Profile
October 16, 2020, 11:34:00 AM
 #3710

the private key can be calculated in a million years on a single processor or in 2 years one of the 590000 keys from addresses with a balance of more than 1 bitcoin https://github.com/traxm/Bitcoin-Micro-Collider/



@alevlaslo, generally when you see coins on addresses that look like this: 1xxxxxxxxxxxxxxxxxxxxxxxxxy1kmdGr, they are gone forever. If we ever find a way to get the private key for that address (if there is any), we will face much more worse problems than those you can imagine.

Stupid, in my opinion.  Nobody can ever spend that money.
Let the stupid ones burn their bitcoins. They make them more valuable without knowing it.  Wink

Yes, from these addresses, the signature does not fit on the graphic code or even in the text buffer

bigvito19
Full Member
***
Offline Offline

Activity: 633
Merit: 111


View Profile
October 16, 2020, 01:19:54 PM
 #3711

the private key can be calculated in a million years on a single processor or in 2 years one of the 590000 keys from addresses with a balance of more than 1 bitcoin https://github.com/traxm/Bitcoin-Micro-Collider/

I would rather use this, at least it wouldn't take a million years
https://github.com/JeanLucPons/Kangaroo
nullius
Copper Member
Hero Member
*****
Offline Offline

Activity: 588
Merit: 2335


There is only one Bitcoin.


View Profile WWW
October 16, 2020, 02:29:55 PM
 #3712

the private key can be calculated in a million years on a single processor or in 2 years one of the 590000 keys from addresses with a balance of more than 1 bitcoin https://github.com/traxm/Bitcoin-Micro-Collider/

Baloney.  Well, have fun trying, as I said.



I would rather use this, at least it wouldn't take a million years
https://github.com/JeanLucPons/Kangaroo

Good link (forum thread), but it needs the public key.  It will not work with a Bitcoin address.  Also, if you think that it will crack public keys in a reasonable time—as I said, have fun trying!

bigvito19
Full Member
***
Offline Offline

Activity: 633
Merit: 111


View Profile
October 16, 2020, 02:35:50 PM
 #3713

the private key can be calculated in a million years on a single processor or in 2 years one of the 590000 keys from addresses with a balance of more than 1 bitcoin https://github.com/traxm/Bitcoin-Micro-Collider/

Baloney.  Well, have fun trying, as I said.



I would rather use this, at least it wouldn't take a million years
https://github.com/JeanLucPons/Kangaroo

Good link (forum thread), but it needs the public key.  It will not work with a Bitcoin address.  Also, if you think that it will crack public keys in a reasonable time—as I said, have fun trying!

Who cares what you said, I said it wouldn't take a million years. I never said it it would crack in a reasonable time!
alevlaslo
Hero Member
*****
Offline Offline

Activity: 1918
Merit: 591


View Profile
October 16, 2020, 03:22:45 PM
 #3714

it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses

however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program?

bigvito19
Full Member
***
Offline Offline

Activity: 633
Merit: 111


View Profile
October 16, 2020, 03:48:47 PM
 #3715

it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses

however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program?


At 12000 keys per second, you're not hitting no address at that speed. Depends on where the program searching at. How did you come up with 2 years for 590k address because that's not enough addresses to check for in a big space.

And you do know 1+ btc addresses is no different than 100+ btc addresses.
alevlaslo
Hero Member
*****
Offline Offline

Activity: 1918
Merit: 591


View Profile
October 16, 2020, 04:36:44 PM
 #3716

for an average video card, it takes a million years for one address, I thought that my i5 processor is not much inferior to this video card

nullius
Copper Member
Hero Member
*****
Offline Offline

Activity: 588
Merit: 2335


There is only one Bitcoin.


View Profile WWW
October 16, 2020, 05:24:41 PM
Merited by LoyceV (4), ETFbitcoin (2), o_e_l_e_o (2), xhomerx10 (1), mikeywith (1)
 #3717

it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses

however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program?
[blah]

This discussion is off-topic on the Vanitygen thread; but I feel a need to stick a spike in what is essentially idiot-FUD over Bitcoin’s security.  To be clear, you are full of shit.

  • 2160 search space of Hash160s
  • 12000 trials per second
  • 590000 Bitcoin addresses with ≥ 1 BTC (assuming that your information is correct; I can’t be bothered to investigate, when it cannot make any appreciable difference)
  • 86400 seconds per day, 365.2425 days per year

Ignoring the question of how different script types are handled:  On average, what is the expected number of years for you to hit any one of the desired addresses?

Code:
$ bc -l
((2^160 / 590000) / 12000) / (86400 * 365.2425)
6541404408567194639988331071041.54191444061112656733

Well, have fun trying, as I said.

LoyceV
Legendary
*
Offline Offline

Activity: 2338
Merit: 8880


Thick-Skinned Gang Leader


View Profile WWW
October 16, 2020, 06:34:34 PM
Merited by xandry (2)
 #3718

590000 Bitcoin addresses with ≥ 1 BTC (assuming that your information is correct; I can’t be bothered to investigate, when it cannot make any appreciable difference)
Let's see: I count 815446 Bitcoin addresses ≥ 1 BTC.



If you want to take a shot to find the private key of a rich wallet, try those:
Code:
address     balance
35hK24tcLEWcgNA4JxpvbkNkoAcDGqQPsP  22750211349798
37XuVSEpWW4trkfmvWzegTHQt7BdktSKUs  9450583134507
34EiJfy4jGF32M37aQ2ZobupwiRQWa1Siy  9285724546987
1FeexV6bAHb8ybZjqQMjJrcCrHGW9sb6uF  7995720489764
3Kzh9qAqVWQhEsfQz7zEQL1EuSx5tyNLNS  7429382157655
34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo  7343627940660
1HQ3Go3ggs8pFnXuHVHRytPCq5fGG8Hbhx  6937022461903
37tRFZw7n94Jddq6TfVs3MbCXmDX6eMfeY  6810156631276
3JurbUwpsAPqvUkwLM5CtwnEWrNnUKJNoD  6523671378350
bc1qgdjqv0av3q56jvd82tkdjpy7gdp9ut8tlqmgrpmv24sq90ecnvqqjwvw97    6350099542777
1P5ZEDWTKTFGxQjZphgWPQUpe554WKDfHQ  5882565501662
385cR5DM96n1HvBDMzLHPYcw89fZAXULJP  5580189332845
1LdRcdxfbSnmCYYNdeYpUnztiYzVfBEQeC  5388005997485
386eAUqL3ZNZPmHeABXLo658DTQuJeLzUR  5228631583003
1AC4fMwgY8j9onSbXEWeH6Zan8QGMSdmtA  5183035806607
1LruNZjwamWJXThX2Y8C2d47QqhAkkc5os  4400007825417
38UmuUqPCrFmQo4khkomQwZ4VbY2nZMJ67  4323343648365
bc1q5shngj24323nsrmxv99st02na6srekfctt30ch      4000032739903
3D8qAoMkZ8F1b42btt2Mn5TyN7sWfa434A  3999991875357
1BX5MXZ95rMiQJBH9yKpcmbAt9VcfyAfHE  3748301367714
17hf5H8D6Yc4B7zHEg3orAtKn7Jhme7Adx  3600000232699
3LCGsSmfr24demGvriN4e3ft8wEcDuHFqh  3420039122238
13JQwoSLLR3ffXwswe2HCTK9oq4i8MWK3q  3101001173650
12ib7dApVFvg82TXKycWBNpN8kFyiAN1dr  3100006932578
12tkqA9xSoowkzoERHMWNKsTey55YEBqkv  2815105678199
3H5JTt42K7RmZtromfTSefcMEFMMe18pMD  2653231784217
3Pja5FPK1wFB9LkWWJai8XYL1qjbqqT9Ye  2616701098509
1NH8vuaJaMXbtj4Qx6iFaQY8btdVcAn9iz  2449535094560
1ANjYHibCQ6FzagLfeXubC8SQYDfUS5wAJ  2396900026383
1AnwDVbwsLBVwRfqN2x9Eo4YEJSPXo2cwG  2322761527043
1932eKraQ3Ad9MeNBHb14WFQbNrLaKeEpT  2289999034779
14eQD1QQb8QFVG8YFwGz7skyzsvBLWLwJS  2221116586406
3EcoyfYvsBXBwdbdf4SY6DAU84kqS6mNLs  2170000479732
1aXzEKiDJKzkPxTZy9zGc3y1nCDwDPub2   2120481013155
3HroDXv8hmzKRtaSfBffRgedKpru8fgy6M  2012449485992
17rm2dvb439dZqyMe2d4D6AQJSgg6yeNRn  2000800083113
1HEWtVTNHApfVsK923gYYAuLUzzwweQGWj  2000100106691
1PeizMg76Cf96nUQrYg8xuoZWLQozU5zGW  1941442998326
19iqYbeATe4RxghQZJnYVFU4mjUUu76EA6  1858662993936
3JPauiFhP4K3AevmgNMFfMSN7pLZbuADJQ  1800100011082
3JSssZCJ3PHEdgNv7hzNE26EEzzvYNjZLy  1700100006032
3EiEN1JJCudBgAwL7c6ajqnPzx9LrK1VT6  1688134484379
1GR9qNz7zgtaW5HwwVpEJWMnGWhsbsieCG  1574555580702
3BMEXqGpG4FxBA1KWhRFufXfSTRgzfDBhJ  1556323781534
3N9an8wv4SYi3FVXs3xR5k2AqXeNZiw2mf  1549989103483
38Md7BghVmV7XUUT1Vt9CvVcc5ssMD6ojt  1503326226463
1KUr81aewyTFUfnq4ZrpePZqXixd59ToNn  1499999858633
3DwVjwVeJa9Z5Pu15WHNfKcDxY5tFUGfdx  1450000014976
3FrM1He2ZDbsSKmYpEZQNGjFTLMgCZZkaf  1400001439816
1BZaYtmXka1y3Byi2yvXCDG92Tjz7ecwYj  1400000055945
1U3d67BaLpwudFEZRtDDAm7bTCQkygUcV   1388237690339
Good luck Tongue

mikeywith
Legendary
*
Offline Offline

Activity: 1260
Merit: 3780


be constructive or S.T.F.U


View Profile
October 17, 2020, 01:29:10 AM
Last edit: October 17, 2020, 12:19:12 PM by mikeywith
Merited by ETFbitcoin (2), joniboini (2)
 #3719

if it takes a million years for 1 video card to search, then a million video cards will be found in 1 year. Unlike mining, when it is extracted regularly for a little bit, the process of searching for keys takes a long time, but the reward is more significant.

The average video card would cost you about $200, so that's $200,000,000 in cards alone, it's safe to assume that you will need 30% of that in other pieces of equipment (apparently a GPU isn't a stand-alone device) so that is another $,60,000,000. You will also need a few million dollars in labor and shit.

The average GPU would consume about 120w per hour to do the "guessing" job, that will be 2.9kwh a day, the average electricity cost is 5 cents per kWh, so you will pay $0.145*1,000,000 = $145,000 daily, in other words, $52,925,000 a year.

A million GPUs would need 120 megawatts of power, and perhaps another 10MW to cool that down, you will need to get your own transformers and build your own infrastructure to attempt that kind of shit, you will be looking at close to 1 billion dollars in total by the end of the year including all the other expenses, that is close to 0.5% of the total value of bitcoin, you will spend a 100,000BTC in an "attempt" to hit a collision of some type, only to realize that those funds were moved to a thousand different addresses, or at best case scenario, whatever you may have found isn't worth a 100,000BTC anyway.

On the other hand, if you use those 1M GPUs for mining you make  $620,000 in profit (after the power bill of 5 cents per kWh), so in a year you make 1/4 of a billion-dollar that is clean money without the chance of actually "stealing" some else's bitcoin.

One-way hash functions are built in a way that makes them economically less incentive compared to when you harness the same resources to make money else way, so if profit is the only "goal" it makes no sense to attempt that unless you want to gamble.

alevlaslo
Hero Member
*****
Offline Offline

Activity: 1918
Merit: 591


View Profile
October 17, 2020, 05:10:37 AM
 #3720

it takes a million years to select one address, but 2 years is enough to select one of 590 thousands 1+ BTC addresses

however, 12000 keys per second is very small on the processor, how much will the video card give if you write the same program?
[blah]

This discussion is off-topic on the Vanitygen thread; but I feel a need to stick a spike in what is essentially idiot-FUD over Bitcoin’s security.  To be clear, you are full of shit.

  • 2160 search space of Hash160s
  • 12000 trials per second
  • 590000 Bitcoin addresses with ≥ 1 BTC (assuming that your information is correct; I can’t be bothered to investigate, when it cannot make any appreciable difference)
  • 86400 seconds per day, 365.2425 days per year

Ignoring the question of how different script types are handled:  On average, what is the expected number of years for you to hit any one of the desired addresses?

Code:
$ bc -l
((2^160 / 590000) / 12000) / (86400 * 365.2425)
6541404408567194639988331071041.54191444061112656733

Well, have fun trying, as I said.

you forgot to divide the result by 2^96 because there are so many private keys for each address

Pages: « 1 ... 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 [186] 187 188 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!