Author

Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 278. (Read 229416 times)

jr. member
Activity: 34
Merit: 5
Quote
the equation solver...
https://qalculate.github.io/

thank you

view profile good luck

To anyone who considers buying this:
Generate a public key with the private key in the 75 bit range and ask drotika to give you the private key for this public key.

Regards
newbie
Activity: 18
Merit: 1
can anyone know, or explain to me please,

how it will be easy to find private keys which has spend transaction for the wallet  in compare to wallet which hasn't spend transaction ?
please explain if anybody know , i am confused so, thanks.

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 match is expected within a private key range of only 2160

A spend transaction exposes the public key so 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 the effective security is reduced to only 128 bits.

See the following:

Quote

So the two situations are:

     Full entropy 256 bit private keys with multiple spend transactions have 128 bits of security

     160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions have 160 bits of security

So Bitcoins kept on a Bitcoin address with no spend transactions are safer (160 bits of security) than Bitcoins kept on a Bitcoin address that has spend transactions (only 128 bits of security).




thanks, let's say we got a spend transaction on bitcoin puzzle wallet #120, we got hash of it, so how do we calculate with bitcrack for 2^128 possibles?
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
can anyone know, or explain to me please,

how it will be easy to find private keys which has spend transaction for the wallet  in compare to wallet which hasn't spend transaction ?
please explain if anybody know , i am confused so, thanks.

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 match is expected within a private key range of only 2160

A spend transaction exposes the public key so 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 the effective security is reduced to only 128 bits.

See the following:

Quote

So the two situations are:

     Full entropy 256 bit private keys with multiple spend transactions have 128 bits of security

     160 bit Bitcoin address from a full entropy 256 bit private key with no spend transactions have 160 bits of security

So Bitcoins kept on a Bitcoin address with no spend transactions are safer (160 bits of security) than Bitcoins kept on a Bitcoin address that has spend transactions (only 128 bits of security).
member
Activity: 255
Merit: 27
Hello to all. Sorry for previous reports about the script and high speed search. There was a mistake in the calculations. And considered impossible keys. I checked the script on the already found keys, these are the results.

Code:
    16 bits - V1(Middle) - 9 seconds
    17 bits - V1(Middle) - 7 seconds
    18 bits - V1(Middle) - 0 second
    19 bits - V1(Middle) - 25 seconds
    20 bits - V1(Middle) - 157 seconds
    21 bits - V1(Middle) - 323 seconds
    22 bits - V1(Middle) - 43 seconds
    23 bits - V1(Middle) - 1317 seconds
    24 bits - V1(Middle) - 440 seconds
    25 bits - V1(Middle) - 914 seconds
    26 bits - V1(Middle) - 358 seconds
    27 bits - V1(Middle) - 14465 seconds (241 minuts) (about 4 hours)
    28 bits - V1(Middle) - 44409 seconds (740 minuts) (about 13 hours)
    29 bits - V1(Middle) - 20295 seconds (338 minuts) (about 6 hours)
    30 bits - V2(Direct) - 25304 seconds (422 minuts) (about 7 hours)
newbie
Activity: 18
Merit: 1
can anyone know, or explain to me please,

how it will be easy to find private keys which has spend transaction for the wallet  in compare to wallet which hasn't spend transaction ?
please explain if anybody know , i am confused so, thanks.
full member
Activity: 706
Merit: 111
01 0000000000000000000000000000000000000000000000000000000000000001 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH
02 0000000000000000000000000000000000000000000000000000000000000003 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
03 0000000000000000000000000000000000000000000000000000000000000007 19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
04 0000000000000000000000000000000000000000000000000000000000000008 1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
05 0000000000000000000000000000000000000000000000000000000000000015 1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k
06 0000000000000000000000000000000000000000000000000000000000000031 1PitScNLyp2HCygzadCh7FveTnfmpPbfp8
07 000000000000000000000000000000000000000000000000000000000000004c 1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC
08 00000000000000000000000000000000000000000000000000000000000000e0 1M92tSqNmQLYw33fuBvjmeadirh1ysMBxK
09 00000000000000000000000000000000000000000000000000000000000001d3 1CQFwcjw1dwhtkVWBttNLDtqL7ivBonGPV
10 0000000000000000000000000000000000000000000000000000000000000202 1LeBZP5QCwwgXRtmVUvTVrraqPUokyLHqe
11 0000000000000000000000000000000000000000000000000000000000000483 1PgQVLmst3Z314JrQn5TNiys8Hc38TcXJu
12 0000000000000000000000000000000000000000000000000000000000000a7b 1DBaumZxUkM4qMQRt2LVWyFJq5kDtSZQot
13 0000000000000000000000000000000000000000000000000000000000001460 1Pie8JkxBT6MGPz9Nvi3fsPkr2D8q3GBc1
14 0000000000000000000000000000000000000000000000000000000000002930 1ErZWg5cFCe4Vw5BzgfzB74VNLaXEiEkhk
15 00000000000000000000000000000000000000000000000000000000000068f3 1QCbW9HWnwQWiQqVo5exhAnmfqKRrCRsvW
16 000000000000000000000000000000000000000000000000000000000000c936 1BDyrQ6WoF8VN3g9SAS1iKZcPzFfnDVieY
17 000000000000000000000000000000000000000000000000000000000001764f 1HduPEXZRdG26SUT5Yk83mLkPyjnZuJ7Bm
18 000000000000000000000000000000000000000000000000000000000003080d 1GnNTmTVLZiqQfLbAdp9DVdicEnB5GoERE
19 000000000000000000000000000000000000000000000000000000000005749f 1NWmZRpHH4XSPwsW6dsS3nrNWfL1yrJj4w
20 00000000000000000000000000000000000000000000000000000000000d2c55 1HsMJxNiV7TLxmoF6uJNkydxPFDog4NQum
21 00000000000000000000000000000000000000000000000000000000001ba534 14oFNXucftsHiUMY8uctg6N487riuyXs4h
22 00000000000000000000000000000000000000000000000000000000002de40f 1CfZWK1QTQE3eS9qn61dQjV89KDjZzfNcv
23 0000000000000000000000000000000000000000000000000000000000556e52 1L2GM8eE7mJWLdo3HZS6su1832NX2txaac
24 0000000000000000000000000000000000000000000000000000000000dc2a04 1rSnXMr63jdCuegJFuidJqWxUPV7AtUf7
25 0000000000000000000000000000000000000000000000000000000001fa5ee5 15JhYXn6Mx3oF4Y7PcTAv2wVVAuCFFQNiP
26 000000000000000000000000000000000000000000000000000000000340326e 1JVnST957hGztonaWK6FougdtjxzHzRMMg
27 0000000000000000000000000000000000000000000000000000000006ac3875 128z5d7nN7PkCuX5qoA4Ys6pmxUYnEy86k
28 000000000000000000000000000000000000000000000000000000000d916ce8 12jbtzBb54r97TCwW3G1gCFoumpckRAPdY
29 0000000000000000000000000000000000000000000000000000000017e2551e 19EEC52krRUK1RkUAEZmQdjTyHT7Gp1TYT
30 000000000000000000000000000000000000000000000000000000003d94cd64 1LHtnpd8nU5VHEMkG2TMYYNUjjLc992bps
31 000000000000000000000000000000000000000000000000000000007d4fe747 1LhE6sCTuGae42Axu1L1ZB7L96yi9irEBE
32 00000000000000000000000000000000000000000000000000000000b862a62e 1FRoHA9xewq7DjrZ1psWJVeTer8gHRqEvR
33 00000000000000000000000000000000000000000000000000000001a96ca8d8 187swFMjz1G54ycVU56B7jZFHFTNVQFDiu
34 000000000000000000000000000000000000000000000000000000034a65911d 1PWABE7oUahG2AFFQhhvViQovnCr4rEv7Q
35 00000000000000000000000000000000000000000000000000000004aed21170 1PWCx5fovoEaoBowAvF5k91m2Xat9bMgwb
36 00000000000000000000000000000000000000000000000000000009de820a7c 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1
37 0000000000000000000000000000000000000000000000000000001757756a93 14iXhn8bGajVWegZHJ18vJLHhntcpL4dex
38 00000000000000000000000000000000000000000000000000000022382facd0 1HBtApAFA9B2YZw3G2YKSMCtb3dVnjuNe2
39 0000000000000000000000000000000000000000000000000000004b5f8303e9 122AJhKLEfkFBaGAd84pLp1kfE7xK3GdT8
40 000000000000000000000000000000000000000000000000000000e9ae4933d6 1EeAxcprB2PpCnr34VfZdFrkUWuxyiNEFv
41 00000000000000000000000000000000000000000000000000000153869acc5b 1L5sU9qvJeuwQUdt4y1eiLmquFxKjtHr3E
42 000000000000000000000000000000000000000000000000000002a221c58d8f 1E32GPWgDyeyQac4aJxm9HVoLrrEYPnM4N
43 000000000000000000000000000000000000000000000000000006bd3b27c591 1PiFuqGpG8yGM5v6rNHWS3TjsG6awgEGA1
44 00000000000000000000000000000000000000000000000000000e02b35a358f 1CkR2uS7LmFwc3T2jV8C1BhWb5mQaoxedF
45 0000000000000000000000000000000000000000000000000000122fca143c05  1NtiLNGegHWE3Mp9g2JPkgx6wUg4TW7bbk
46 00000000000000000000000000000000000000000000000000002ec18388d544 1F3JRMWudBaj48EhwcHDdpeuy2jwACNxjP
47 00000000000000000000000000000000000000000000000000006cd610b53cba 1Pd8VvT49sHKsmqrQiP61RsVwmXCZ6ay7Z
48 0000000000000000000000000000000000000000000000000000ade6d7ce3b9b 1DFYhaB2J9q1LLZJWKTnscPWos9VBqDHzv
49 000000000000000000000000000000000000000000000000000174176b015f4d 12CiUhYVTTH33w3SPUBqcpMoqnApAV4WCF
50 00000000000000000000000000000000000000000000000000022bd43c2e9354 1MEzite4ReNuWaL5Ds17ePKt2dCxWEofwk
51 00000000000000000000000000000000000000000000000000075070a1a009d4 1NpnQyZ7x24ud82b7WiRNvPm6N8bqGQnaS
52 000000000000000000000000000000000000000000000000000efae164cb9e3c  15z9c9sVpu6fwNiK7dMAFgMYSK4GqsGZim
53 00000000000000000000000000000000000000000000000000180788e47e326c 15K1YKJMiJ4fpesTVUcByoz334rHmknxmT
54 00000000000000000000000000000000000000000000000000236fb6d5ad1f43  1KYUv7nSvXx4642TKeuC2SNdTk326uUpFy
55 000000000000000000000000000000000000000000000000006abe1f9b67e114 1LzhS3k3e9Ub8i2W1V8xQFdB8n2MYCHPCa
56 000000000000000000000000000000000000000000000000009d18b63ac4ffdf   17aPYR1m6pVAacXg1PTDDU7XafvK1dxvhi
57 00000000000000000000000000000000000000000000000001eb25c90795d61c 15c9mPGLku1HuW9LRtBf4jcHVpBUt8txKz
58 00000000000000000000000000000000000000000000000002c675b852189a21 1Dn8NF8qDyyfHMktmuoQLGyjWmZXgvosXf
59 00000000000000000000000000000000000000000000000007496cbb87cab44f  1HAX2n9Uruu9YDt4cqRgYcvtGvZj1rbUyt
60 0000000000000000000000000000000000000000000000000fc07a1825367bbe  1Kn5h2qpgw9mWE5jKpk8PP4qvvJ1QVy8su
61 00000000000000000000000000000000000000000000000013C96A3742F64906 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB

63 0000000000000000000000000000000000000000000000007CCE5EFDACCF6808 1NpYjtLira16LfGbGwZJ5JbDPh3ai9bjf4

65 000000000000000000000000000000000000000000000001A838B13505B26867 18ZMbwUFLMHoZBbfpCjUJQTCMCbktshgpe

70 0000000000000000000000000000000000000000000000349B84B6431A6C4EF1 19YZECXj3SxEZMoUeJ1yiPsw8xANe7M7QR

75 0000000000000000000000000000000000000000000004C5CE114686A1336E07 1J36UjUByGroXcCvmj13U6uwaVv9caEeAt
 
80 00000000000000000000000000000000000000000000ea1a5c66dcc11b5ad180  1BCf6rHUW6m3iH2ptsvnjgLruAiPQQepLe

85 00000000000000000000000000000000000000000011720c4f018d51b8cebba8  1Kh22PvXERd2xpTQk3ur6pPEqFeckCJfAr

90 000000000000000000000000000000000000000002ce00bb2136a445c71e85bf  1L12FHH2FHjvTviyanuiFVfmzCy46RRATU

95 0000000000000000000000000000000000000000527a792b183c7f64a0e8b1f4  19eVSDuizydXxhohGh8Ki9WY9KsHdSwoQC

100 000000000000000000000000000000000000000af55fc59c335c8ec67ed24826 1KCgMv8fo2TPBpddVi9jqmMmcne9uSNJ5F
member
Activity: 206
Merit: 16
I not generate every key.
Private key checked of samples template. And if passed, generated publick key and address. I write upped. Passed priv key 2-3 in second (from 280 trillions).
No. I not multiplier  at hash table or bloom table.

just example.
Quote
privkey:00000..0001 not passed template
privkey:00000..0002 not passed template
privkey:00000..0003 not passed template
privkey:00000..0005 PASSED TEMPLATe!
privkey:00000..0006 not passed template
privkey:00000..0007 not passed template
privkey:00000..0008 not passed template
In example, checked 8 private key. Found 1 pretendent. From him generated an checked publick key and address.
And special algoritm generated next private key.

Example
Quote
privkey:00000..000000001 not passed template
privkey:00000..000000025 not passed template
privkey:00000..000000178 not passed template
privkey:00000..000000225 PASSED TEMPLATe!
privkey:00000..000000226 not passed template
privkey:00000..000001025 not passed template
privkey:00000..000001026 not passed template
privkey:00000..000005103 PASSED TEMPLATe!
privkey:00000..001355367 not passed template
privkey:00000..001355457 not passed template
In this example, I believe that I checked 1355457 keys. Since the missing ranges can not be the key satisfying my templates. But found only 2 pretendents for generate publick key and address.





why not share this script to enrich it ?
member
Activity: 255
Merit: 27
I not generate every key.
Private key checked of samples template. And if passed, generated publick key and address. I write upped. Passed priv key 2-3 in second (from 280 trillions).
No. I not multiplier  at hash table or bloom table.

just example.
Quote
privkey:00000..0001 not passed template
privkey:00000..0002 not passed template
privkey:00000..0003 not passed template
privkey:00000..0005 PASSED TEMPLATe!
privkey:00000..0006 not passed template
privkey:00000..0007 not passed template
privkey:00000..0008 not passed template
In example, checked 8 private key. Found 1 pretendent. From him generated an checked publick key and address.
And special algoritm generated next private key.

Example
Quote
privkey:00000..000000001 not passed template
privkey:00000..000000025 not passed template
privkey:00000..000000178 not passed template
privkey:00000..000000225 PASSED TEMPLATe!
privkey:00000..000000226 not passed template
privkey:00000..000001025 not passed template
privkey:00000..000001026 not passed template
privkey:00000..000005103 PASSED TEMPLATe!
privkey:00000..001355367 not passed template
privkey:00000..001355457 not passed template
In this example, I believe that I checked 1355457 keys. Since the missing ranges can not be the key satisfying my templates. But found only 2 pretendents for generate publick key and address.



newbie
Activity: 22
Merit: 3
Code:
2019-07-19 13:53:38     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373261       Str='11111111122222889a1111111112228a1a19111921811a511119'      Av1:2.359 in sec        Av2:290692446961262 in sec:     CurDec:142042932044673649537278731434510563946471548172750992
2019-07-19 13:56:56     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373267       Str='11111111122222889a1111111112228a1a1911192911811a1115'      Av1:2.3561 in sec       Av2:290329139949209 in sec:     CurDec:142042932044673649537278731434510563946471739286467672
2019-07-19 13:59:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373559       Str='11111111122222889a1111111112228a1a19112111181111959a'      Av1:2.3561 in sec       Av2:290102131961043 in sec:     CurDec:142042932044673649537278731434510563946480663124511842
2019-07-19 14:01:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374096       Str='11111111122222889a1111111112228a1a1911211119a8111159'      Av1:2.3577 in sec       Av2:289882730216322 in sec:     CurDec:142042932044673649537278731434510563946480663526645012
2019-07-19 14:04:09     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374319       Str='11111111122222889a1111111112228a1a19112111811a911159'      Av1:2.3563 in sec       Av2:289537844712345 in sec:     CurDec:142042932044673649537278731434510563946480678146854792
Searcing in range from 62 to 161 bits. Speead over 280 Trillion addresses in second. Finding more than 2 addresses per second, matching a specific pattern. Found applicants are compared with more than 6 thousand addresses. And then sent to another thread to search the current block. PHP and one core on cpu.  Grin
PS. Str not hex priv key. This is own format data. And CurDec not deceminal priv key.

what script is this? can you share? thanks!
Own development. Still in development. Raw to publish in public.

how can you generate trillions of keys with a simple cpu and php ?

He's likely using a hash table or bloom filter and multiplying the size of that by how many queries he can make per second.
member
Activity: 206
Merit: 16
Code:
2019-07-19 13:53:38     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373261       Str='11111111122222889a1111111112228a1a19111921811a511119'      Av1:2.359 in sec        Av2:290692446961262 in sec:     CurDec:142042932044673649537278731434510563946471548172750992
2019-07-19 13:56:56     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373267       Str='11111111122222889a1111111112228a1a1911192911811a1115'      Av1:2.3561 in sec       Av2:290329139949209 in sec:     CurDec:142042932044673649537278731434510563946471739286467672
2019-07-19 13:59:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373559       Str='11111111122222889a1111111112228a1a19112111181111959a'      Av1:2.3561 in sec       Av2:290102131961043 in sec:     CurDec:142042932044673649537278731434510563946480663124511842
2019-07-19 14:01:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374096       Str='11111111122222889a1111111112228a1a1911211119a8111159'      Av1:2.3577 in sec       Av2:289882730216322 in sec:     CurDec:142042932044673649537278731434510563946480663526645012
2019-07-19 14:04:09     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374319       Str='11111111122222889a1111111112228a1a19112111811a911159'      Av1:2.3563 in sec       Av2:289537844712345 in sec:     CurDec:142042932044673649537278731434510563946480678146854792
Searcing in range from 62 to 161 bits. Speead over 280 Trillion addresses in second. Finding more than 2 addresses per second, matching a specific pattern. Found applicants are compared with more than 6 thousand addresses. And then sent to another thread to search the current block. PHP and one core on cpu.  Grin
PS. Str not hex priv key. This is own format data. And CurDec not deceminal priv key.

what script is this? can you share? thanks!
Own development. Still in development. Raw to publish in public.

how can you generate trillions of keys with a simple cpu and php ?
member
Activity: 255
Merit: 27
Code:
2019-07-19 13:53:38     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373261       Str='11111111122222889a1111111112228a1a19111921811a511119'      Av1:2.359 in sec        Av2:290692446961262 in sec:     CurDec:142042932044673649537278731434510563946471548172750992
2019-07-19 13:56:56     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373267       Str='11111111122222889a1111111112228a1a1911192911811a1115'      Av1:2.3561 in sec       Av2:290329139949209 in sec:     CurDec:142042932044673649537278731434510563946471739286467672
2019-07-19 13:59:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373559       Str='11111111122222889a1111111112228a1a19112111181111959a'      Av1:2.3561 in sec       Av2:290102131961043 in sec:     CurDec:142042932044673649537278731434510563946480663124511842
2019-07-19 14:01:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374096       Str='11111111122222889a1111111112228a1a1911211119a8111159'      Av1:2.3577 in sec       Av2:289882730216322 in sec:     CurDec:142042932044673649537278731434510563946480663526645012
2019-07-19 14:04:09     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374319       Str='11111111122222889a1111111112228a1a19112111811a911159'      Av1:2.3563 in sec       Av2:289537844712345 in sec:     CurDec:142042932044673649537278731434510563946480678146854792
Searcing in range from 62 to 161 bits. Speead over 280 Trillion addresses in second. Finding more than 2 addresses per second, matching a specific pattern. Found applicants are compared with more than 6 thousand addresses. And then sent to another thread to search the current block. PHP and one core on cpu.  Grin
PS. Str not hex priv key. This is own format data. And CurDec not deceminal priv key.

what script is this? can you share? thanks!
Own development. Still in development. Raw to publish in public.
newbie
Activity: 43
Merit: 0
Code:
2019-07-19 13:53:38     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373261       Str='11111111122222889a1111111112228a1a19111921811a511119'      Av1:2.359 in sec        Av2:290692446961262 in sec:     CurDec:142042932044673649537278731434510563946471548172750992
2019-07-19 13:56:56     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373267       Str='11111111122222889a1111111112228a1a1911192911811a1115'      Av1:2.3561 in sec       Av2:290329139949209 in sec:     CurDec:142042932044673649537278731434510563946471739286467672
2019-07-19 13:59:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373559       Str='11111111122222889a1111111112228a1a19112111181111959a'      Av1:2.3561 in sec       Av2:290102131961043 in sec:     CurDec:142042932044673649537278731434510563946480663124511842
2019-07-19 14:01:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374096       Str='11111111122222889a1111111112228a1a1911211119a8111159'      Av1:2.3577 in sec       Av2:289882730216322 in sec:     CurDec:142042932044673649537278731434510563946480663526645012
2019-07-19 14:04:09     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374319       Str='11111111122222889a1111111112228a1a19112111811a911159'      Av1:2.3563 in sec       Av2:289537844712345 in sec:     CurDec:142042932044673649537278731434510563946480678146854792
Searcing in range from 62 to 161 bits. Speead over 280 Trillion addresses in second. Finding more than 2 addresses per second, matching a specific pattern. Found applicants are compared with more than 6 thousand addresses. And then sent to another thread to search the current block. PHP and one core on cpu.  Grin
PS. Str not hex priv key. This is own format data. And CurDec not deceminal priv key.

what script is this? can you share? thanks!
member
Activity: 255
Merit: 27
Code:
2019-07-19 13:53:38     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373261       Str='11111111122222889a1111111112228a1a19111921811a511119'      Av1:2.359 in sec        Av2:290692446961262 in sec:     CurDec:142042932044673649537278731434510563946471548172750992
2019-07-19 13:56:56     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373267       Str='11111111122222889a1111111112228a1a1911192911811a1115'      Av1:2.3561 in sec       Av2:290329139949209 in sec:     CurDec:142042932044673649537278731434510563946471739286467672
2019-07-19 13:59:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:373559       Str='11111111122222889a1111111112228a1a19112111181111959a'      Av1:2.3561 in sec       Av2:290102131961043 in sec:     CurDec:142042932044673649537278731434510563946480663124511842
2019-07-19 14:01:00     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374096       Str='11111111122222889a1111111112228a1a1911211119a8111159'      Av1:2.3577 in sec       Av2:289882730216322 in sec:     CurDec:142042932044673649537278731434510563946480663526645012
2019-07-19 14:04:09     62:161##a:0(4)##9:0(4)##8:6(4)##5:28(1)##2:98(9)##1:127(30)     C1:374319       Str='11111111122222889a1111111112228a1a19112111811a911159'      Av1:2.3563 in sec       Av2:289537844712345 in sec:     CurDec:142042932044673649537278731434510563946480678146854792
Searcing in range from 62 to 161 bits. Speead over 280 Trillion addresses in second. Finding more than 2 addresses per second, matching a specific pattern. Found applicants are compared with more than 6 thousand addresses. And then sent to another thread to search the current block. PHP and one core on cpu.  Grin
PS. Str not hex priv key. This is own format data. And CurDec not deceminal priv key.
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Now this will blow your mind:

For every Bitcoin Address there are about 296 = 79,228,162,514,264,337,593,543,950,336 valid possible Public/Private key pairs!

No it doesn't. It is well known, that many private keys map to the same address due to RIPEMD-160.

But the converse is not well known: That one private key generates multiple addresses. In the current case exactly two addresses.

So, for address generation, one uses only the x coordinate with the sign, but the algorithm for address generation stays the same?

https://www.freecodecamp.org/news/how-to-create-a-bitcoin-wallet-address-from-a-private-key-eca3ddd9c05f/
The algorithm for generating a Bitcoin address from a public key never changes.  What changes is the value that is input into the Bitcoin address generation algorithm. 

In one case (uncompressed) the input value is both the X and Y coordinates, in the other case (compressed) it it just the X coordinate and the sign of the Y coordinate.

Thanks for the explanation. Again I learned something.  Smiley

Anyhow, why do you think, that the number sequence for the private keys can be generated by some rule? The canary bird hypothesis sounds convincing to me.
There is a very good explanation, which I agree with, here:  https://bitcointalksearch.org/topic/archive-bitcoin-challenge-discusion-5166284
hero member
Activity: 784
Merit: 544
Now this will blow your mind:

For every Bitcoin Address there are about 296 = 79,228,162,514,264,337,593,543,950,336 valid possible Public/Private key pairs!

No it doesn't. It is well known, that many private keys map to the same address due to RIPEMD-160.

But the converse is not well known: That one private key generates multiple addresses. In the current case exactly two addresses.

So, for address generation, one uses only the x coordinate with the sign, but the algorithm for address generation stays the same?

https://www.freecodecamp.org/news/how-to-create-a-bitcoin-wallet-address-from-a-private-key-eca3ddd9c05f/
The algorithm for generating a Bitcoin address from a public key never changes.  What changes is the value that is input into the Bitcoin address generation algorithm. 

In one case (uncompressed) the input value is both the X and Y coordinates, in the other case (compressed) it it just the X coordinate and the sign of the Y coordinate.

Thanks for the explanation. Again I learned something.  Smiley

Anyhow, why do you think, that the number sequence for the private keys can be generated by some rule? The canary bird hypothesis sounds convincing to me.
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Now this will blow your mind:

For every Bitcoin Address there are about 296 = 79,228,162,514,264,337,593,543,950,336 valid possible Public/Private key pairs!

No it doesn't. It is well known, that many private keys map to the same address due to RIPEMD-160.

But the converse is not well known: That one private key generates multiple addresses. In the current case exactly two addresses.

So, for address generation, one uses only the x coordinate with the sign, but the algorithm for address generation stays the same?

https://www.freecodecamp.org/news/how-to-create-a-bitcoin-wallet-address-from-a-private-key-eca3ddd9c05f/
The algorithm for generating a Bitcoin address from a public key never changes.  What changes is the value that is input into the Bitcoin address generation algorithm. 

In one case (uncompressed) the input value is both the X and Y coordinates, in the other case (compressed) it it just the X coordinate and the sign of the Y coordinate.
full member
Activity: 840
Merit: 117
I don't know why but I'm smelling a big scam. Because a newbie that offer more than 12 000€ to solve a following of numbers this is strange...
Yeah I can also smell that newbie is on big mission to scam people and newbies have better ideas for scamming people.
Many people attracting to this because the prize amount is bigger than whole life income but seems like scam something..
Let's try to solve this puzzle!!  Grin
hero member
Activity: 784
Merit: 544
Now this will blow your mind:

For every Bitcoin Address there are about 296 = 79,228,162,514,264,337,593,543,950,336 valid possible Public/Private key pairs!

No it doesn't. It is well known, that many private keys map to the same address due to RIPEMD-160.

But the converse is not well known: That one private key generates multiple addresses. In the current case exactly two addresses.

So, for address generation, one uses only the x coordinate with the sign, but the algorithm for address generation stays the same?

https://www.freecodecamp.org/news/how-to-create-a-bitcoin-wallet-address-from-a-private-key-eca3ddd9c05f/
member
Activity: 255
Merit: 27
https://brainwalletx.github.io/
Select "Secret exponent"
Enter in input "Secret exponent" 3
Uncompresed 1NZUP3JAc9JkmbvmoTv7nVgZGtyJjirKV1
Compressed 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb

And view all variable, Public Key, Privat Key, hash160 and etc.
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
It's bullshit (or I compute the addresses wrongly).

It is not bullshit, you just do not understand that for every private key there are two formats for the public key.  They are the uncompressed format and the compressed format.

From these two formats of the public key you get two different Bitcoin addresses.

Private Key: 0000000000000000000000000000000000000000000000000000000000000003

Uncompressed format of the Pubic Key (both the X and Y coordinates of the point on the elliptic curve):

04F9308A019258C31049344F85F89D5229B531C845836F99B08601F113BCE036F9388F7B0F632DE 8140FE337E62A37F3566500A99934C2231B6CB9FD7584B8E672

Bitcoin Address from the uncompressed format of the public key:  1NZUP3JAc9JkmbvmoTv7nVgZGtyJjirKV1

Compressed format of the Public Key (the X coordinate only and a sign bit for the Y coordinate):  

02F9308A019258C31049344F85F89D5229B531C845836F99B08601F113BCE036F9

Bitcoin Address from the compressed format of the public key:  1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb

Now this will blow your mind:

For every Bitcoin Address there are about 296 = 79,228,162,514,264,337,593,543,950,336 valid possible Public/Private key pairs!

[EDIT: fixed, I did not have my coffee before I wrote the first version of this and it was totally backwards and wrong.]
Jump to: