Search content
Sort by
Showing 20 of 95 results by Tepan
tepan@MacBook-Pro %
result :
RANGE 49
1000000000000:1ffffffffffff
start = 281474976710656
end = 562949953421311
k = 79985852346388
319943409385552 = 122FCA143C050 #1
337535595429968 = 132FCA143C050 #2
399929261731940 = 16BBBC994B064 #1
417521447776356 = 17BBBC994B064 #2
479915114078328 = 1B47AF1E5A078 #1
497507300122744 = 1C47AF1E5A078 #2
key = 174176B015F4D <- answer
RANGE 53
10000000000000:1fffffffffffff
start = 4503599627370496
end = 9007199254740991
k = 1636475620130100
5190901837100956 = 1271190410779C #1
6827377457231056 = 184176B015F4D0 #2
8463853077361156 = 1E11D45C1B7204 #1
8745328054071812 = 1F11D45C1B7204 #2
key = 180788E47E326C <- answer
i just play around with math, by using simple decimal multiplications combined with logarithmic insights, you can systematically determine key values within a numerical range.
fun fact the unique thing is that the key is indeed located right in the area that has been measured using mathematics, I am using 2 pieces of evidence for now.
for now i'm just doing this thing work, thanks for read and respect my post about puzzle.
result :
RANGE 49
1000000000000:1ffffffffffff
start = 281474976710656
end = 562949953421311
k = 79985852346388
319943409385552 = 122FCA143C050 #1
337535595429968 = 132FCA143C050 #2
399929261731940 = 16BBBC994B064 #1
417521447776356 = 17BBBC994B064 #2
479915114078328 = 1B47AF1E5A078 #1
497507300122744 = 1C47AF1E5A078 #2
key = 174176B015F4D <- answer
RANGE 53
10000000000000:1fffffffffffff
start = 4503599627370496
end = 9007199254740991
k = 1636475620130100
5190901837100956 = 1271190410779C #1
6827377457231056 = 184176B015F4D0 #2
8463853077361156 = 1E11D45C1B7204 #1
8745328054071812 = 1F11D45C1B7204 #2
key = 180788E47E326C <- answer
i just play around with math, by using simple decimal multiplications combined with logarithmic insights, you can systematically determine key values within a numerical range.
fun fact the unique thing is that the key is indeed located right in the area that has been measured using mathematics, I am using 2 pieces of evidence for now.
for now i'm just doing this thing work, thanks for read and respect my post about puzzle.
But that has nothing to do with puzzles. He needed a privkey (recalculated divided whatever) to get the private key. What is the point.
[/quote]
ye i know, no step 5-6, cannot do anything.
But that has nothing to do with puzzles. He needed a privkey (recalculated divided whatever) to get the private key. What is the point.
[/quote]
ye i know, no step 5-6, cannot do anything.
Hello everyone,
I need to show you something I was working on for a few months and because I am actually addicted of this, you have to see it.
So basically the case is I want to verify If I am that "smart" or it is just pure coincidence.
I have just now registered first ever account.
I am working with a very interesting python script that basically get's the private key directly from the hash160 of basically any address up to puzzle 130...sounds crazy isn't it?
So basically what I need to decode private key of the hash160 of an p2pkh bitcoin address? hah a private key
Seriously..
1.Chose whatever range, like I said, for the moment I have tested until puzzle 130, generate Yourself a hex private key in between chosen range and get the compressed address.
2 Convert the hash160 of that address to decimal string.
3.Convert the hexadecimal private key to decimal as well,
4 Now using a big integer calculator for example http://www.javascripter.net/math/calculators/100digitbigintcalculator.htm ( I am also using it ) divide the decimal string of hash160 by decimal version of private key
5.The resulting string now You have to multiply times decimal private key.
6 That multiplication will result with a long string of course but quite similar with the first digits like so basically that string will be required by me.
That is pretty obvious that having only hash160 string we cannot see the private key directly can we?
So what I need actually to decode private key then?
I need a hex range boundary of Your address choice and the the resulting decimal string from step 6. or as You want convert it to an address back using brainwallet converter, so range boundary and an compressed address
Time to get the private key? Instant, 0.1 sec.
The most important: I don't need a private key
, I will get one to verify what I say and second read carefully so You have zero questions about the steps.
Don't forget to pick up the range and address with that private key You don't use personally, that is just a test. Wanna see the results reply with what I ask for.
When I have the private key I will reply with signed message so You can verify Yourself.
I guarantee you will be intrigued.
I need to show you something I was working on for a few months and because I am actually addicted of this, you have to see it.
So basically the case is I want to verify If I am that "smart" or it is just pure coincidence.
I have just now registered first ever account.
I am working with a very interesting python script that basically get's the private key directly from the hash160 of basically any address up to puzzle 130...sounds crazy isn't it?
So basically what I need to decode private key of the hash160 of an p2pkh bitcoin address? hah a private key
Seriously..
1.Chose whatever range, like I said, for the moment I have tested until puzzle 130, generate Yourself a hex private key in between chosen range and get the compressed address.
2 Convert the hash160 of that address to decimal string.
3.Convert the hexadecimal private key to decimal as well,
4 Now using a big integer calculator for example http://www.javascripter.net/math/calculators/100digitbigintcalculator.htm ( I am also using it ) divide the decimal string of hash160 by decimal version of private key
5.The resulting string now You have to multiply times decimal private key.
6 That multiplication will result with a long string of course but quite similar with the first digits like so basically that string will be required by me.
That is pretty obvious that having only hash160 string we cannot see the private key directly can we?
So what I need actually to decode private key then?
I need a hex range boundary of Your address choice and the the resulting decimal string from step 6. or as You want convert it to an address back using brainwallet converter, so range boundary and an compressed address
Time to get the private key? Instant, 0.1 sec.
The most important: I don't need a private key
, I will get one to verify what I say and second read carefully so You have zero questions about the steps.Don't forget to pick up the range and address with that private key You don't use personally, that is just a test. Wanna see the results reply with what I ask for.
When I have the private key I will reply with signed message so You can verify Yourself.
I guarantee you will be intrigued.
this guy nailed it
Puzzle #60 with a MacBook M1 Max
4.01e+03 seconds is 4010 seconds. So 1 hour and 11 minutes
I'm curious how much would it be with multithreading.
4.01e+03 seconds is 4010 seconds. So 1 hour and 11 minutes
I'm curious how much would it be with multithreading.
Code:
Ops: 1640142848 Table size: 25626624 Speed: 408909 ops/s
Ops: 1640964096 Table size: 25639463 Speed: 408910 ops/s
Private Key: 0xfc07a1825367bbe
Ops: 1641142272 Stored: 25642283
Speed: 408885 ops/s
Finished in 4.01e+03 s
Ops: 1640964096 Table size: 25639463 Speed: 408910 ops/s
Private Key: 0xfc07a1825367bbe
Ops: 1641142272 Stored: 25642283
Speed: 408885 ops/s
Finished in 4.01e+03 s
can i try your script code ?
120, 125 and 130.
captured by hacker ? because this address is 1DiegoU6ETJXK9hNWVTeuK4Y8fkksPnEnK seem fishy with 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs
and he's announce this "https://www.blockchain.com/explorer/transactions/btc/69888f5e55d414b8de65f3a9307a1f414d7035cf9142239045300ce018984bd4"
captured by hacker ? because this address is 1DiegoU6ETJXK9hNWVTeuK4Y8fkksPnEnK seem fishy with 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs
and he's announce this "https://www.blockchain.com/explorer/transactions/btc/69888f5e55d414b8de65f3a9307a1f414d7035cf9142239045300ce018984bd4"
Holy snappers, guys! How could we forget about this?
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
Now we can officially transition to #67.
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
Now we can officially transition to #67.
for real, i forgot who's make that wheel of fortune HAHAHAH.
PHP Notice: Undefined index: HTTP_HOST in /root/tahcoin-blockchain/init.php on line 8
PHP Notice: Undefined index: REQUEST_URI in /root/tahcoin-blockchain/init.php on line 8
Blocks saved successfully from bootriver.
PHP Fatal error: Uncaught Error: Call to undefined function curl_init() in /root/tahcoin-blockchain/init.php:8
Stack trace:
#0 {main}
thrown in /root/tahcoin-blockchain/init.php on line 8
PHP Notice: Undefined index: REQUEST_URI in /root/tahcoin-blockchain/init.php on line 8
Blocks saved successfully from bootriver.
PHP Fatal error: Uncaught Error: Call to undefined function curl_init() in /root/tahcoin-blockchain/init.php:8
Stack trace:
#0 {main}
thrown in /root/tahcoin-blockchain/init.php on line 8
Let me fix that graph for you
Before judging, note that all your % and etc. are inside the red line and even if it weren't it would need a very high amount of zoom-in in to actually be noticeable.
okay bro, thankyou for sharing your thoughts.
SolveKeyCPU Thread 254: 1024 kangaroos
SolveKeyCPU Thread 251: 1024 kangaroos
GPU: GPU #0 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(56x256) (147.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
someone please help me, why it took so long ?, i'm stuck on this like 5 minutes.
SolveKeyCPU Thread 251: 1024 kangaroos
GPU: GPU #0 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(56x256) (147.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
someone please help me, why it took so long ?, i'm stuck on this like 5 minutes.
then "Segmentation fault (core dumped)"
SolveKeyCPU Thread 254: 1024 kangaroos
SolveKeyCPU Thread 251: 1024 kangaroos
GPU: GPU #0 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(56x256) (147.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
someone please help me, why it took so long ?, i'm stuck on this like 5 minutes.
SolveKeyCPU Thread 251: 1024 kangaroos
GPU: GPU #0 NVIDIA GeForce RTX 3060 (28x128 cores) Grid(56x256) (147.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
someone please help me, why it took so long ?, i'm stuck on this like 5 minutes.
don't waste your time to Digarans' substraction crazyness.
Are you jealous and daydream to get those wallet ?, but in reality you cannot do it ? so you blame yourself and people who's have right about their opinion ? childish, period.
[...snipped...]
[/quote]
Thanks for explaining it but i dont get what is the number 95823 from your first line
Code:
old_key = 4563 -- was from "95823/21"
[/quote]95823 was from 1764F on 17 bit puzzle, 17 bit into 21 bit.
"How many multiples are there from 95823 to 2097151?"
95823/2097151 = 21 = 4563.
Calculate the far distance when the decimal is multiplied by 1.05
1811511 * 1.05 = 1902086.55 (depends on your settings).
1902086.55 results are rounded to 1902087
so the search is 1811511 to 1902087
1811511 * 1.05 = 1902086.55 (depends on your settings).
1902086.55 results are rounded to 1902087
so the search is 1811511 to 1902087
How do you determine the exact range to multiply by 1.05 in a puzzle that does not have a solved private key?
it's simple, if you do multipler with large value, it's gonna be exceed, 1.01 - 1.05 it's quietly large.
I'm fully convinced that with math and databases the public key range can be reduced, so I'm not surprised that it was solved. Whoever did it simply reduced the range enough to a manageable level for their computing power.
I don't think there is a backdoor in secp256k1, but rather shortcuts for insecure private keys.
I don't think there is a backdoor in secp256k1, but rather shortcuts for insecure private keys.
this!
"Whoever did it simply reduced the range enough to a manageable level for their computing power."
@Tepan
Can you explain a little bit more your formula ?
First thing first it's funny someone really spend their time to this like Mr.AKITO.
I want to explain but I'm afraid of appearing smarter than my friends who are great at spending their time creating and ensuring programs like search using the hash of public key 160 and even compressed public keys, will feel offensive to them, this is just my thoughts for 2 years paying more attention to this forum and puzzle.
but okay if you want to.
old_key = 4563 -- was from "95823/21" 21 is divided by count the 95823 into 2097151, have 2 option 22 or 21, 21 is precisely with target.
old_range = (65536, 131071)
new_range = (1048576, 2097151)
result :
[1245699, 1660932, 2076165, 1400841, 1816074, 1140750, 1555983, 1971216, 1295892, 1711125, 1451034, 1866267, 1190943, 1606176, 2021409, 1346085, 1761318, 1085994, 1501227, 1916460, 1241136, 1656369, 2071602, 1396278, 1811511, 1136187, 1551420, 1966653, 1291329, 1706562, 1446471, 1861704, 1186380, 1601613, 2016846, 1341522, 1756755, 1081431, 1496664, 1911897, 1236573, 1651806, 2067039, 1391715, 1806948, 1131624, 1546857, 1962090, 1286766, 1701999, 1441908, 1857141, 1181817, 1597050, 2012283, 1336959, 1752192, 1076868, 1492101, 1907334, 1232010, 1647243, 2062476, 1387152, 1802385, 1127061, 1542294, 1957527, 1282203, 1697436, 1437345, 1852578, 1177254, 1592487, 2007720, 1332396, 1747629, 1072305, 1487538, 1902771, 1227447, 1642680, 2057913, 1382589, 1797822, 1122498, 1537731, 1952964, 1277640, 1692873, 1432782, 1848015, 1172691, 1587924, 2003157, 1327833, 1743066, 1067742, 1482975, 1898208, 1222884, 1638117, 2053350, 1378026, 1793259, 1117935, 1533168, 1948401, 1273077, 1688310, 1428219, 1843452, 1168128, 1583361, 1998594, 1323270, 1738503, 1063179, 1478412, 1893645, 1218321, 1633554, 2048787, 1373463, 1788696, 1113372, 1528605, 1943838, 1268514, 1683747, 1423656, 1838889, 1163565, 1578798, 1994031, 1318707, 1733940, 1058616, 1473849, 1889082, 1213758, 1628991, 2044224, 1368900, 1784133, 1108809, 1524042, 1939275, 1263951, 1679184, 2094417, 1419093, 1834326, 1159002, 1574235, 1989468, 1314144, 1729377, 1054053, 1469286, 1884519, 1209195, 1624428, 2039661, 1364337, 1779570, 1104246, 1519479, 1934712, 1259388, 1674621, 2089854, 1414530, 1829763, 1154439, 1569672, 1984905, 1309581, 1724814, 1049490, 1464723, 1879956, 1204632, 1619865, 2035098, 1359774, 1775007, 1099683, 1514916, 1930149, 1254825, 1670058, 2085291, 1409967, 1825200, 1149876, 1565109, 1980342, 1305018, 1720251, 1460160, 1875393, 1200069, 1615302, 2030535, 1355211, 1770444, 1095120, 1510353, 1925586, 1250262, 1665495, 2080728, 1405404, 1820637, 1145313, 1560546, 1975779, 1300455, 1715688, 1455597, 1870830, 1195506, 1610739, 2025972, 1350648, 1765881, 2097151, 1090557, 1505790, 1921023]
searching puzzle #21 key 1BA534 > 1811764.
Find the nearest decimal number.
Calculate the far distance when the decimal is multiplied by 1.05
1811511 * 1.05 = 1902086.55
1902086.55 results are rounded to 1902087
just simple logic, if someone doesn’t like, step the f out to learn.
I don't think is puzzle creator messing with us but someone with huge GPU farm that is now dedicated puzzle hunter 
@Tepan
for next 67 Bit.
67 BIT PUZZLE
46346217550346335726 | XXXXXXXXX8929167990784 | XXXXXXXX868880000 |
46346217550346335726 | XXXXXXXXX146718502912 | XXXXXXXXc12500000 |
46346217550346335726 | XXXXXXXXX364268752896 | XXXXXXXXfbc140000 |
46346217550346335726 | XXXXXXXXX581819002880 | XXXXXXXX365d80000 |
any of these close to your range formula prediction?
000000000000000000000000000000000000000000000005C07854E9A752E2B7
000000000000000000000000000000000000000000000005CE2BEFE8ECF8155E
000000000000000000000000000000000000000000000006816CC8B49ABBF2E5
0000000000000000000000000000000000000000000000068F2063B3E061258C
000000000000000000000000000000000000000000000007020FC0913D01FDAE
0000000000000000000000000000000000000000000000070FC35B9082A73055
000000000000000000000000000000000000000000000007C9C2ABE149EE5411
Prediction apps is what I'm messing around with..
@Tepan
for next 67 Bit.
67 BIT PUZZLE
46346217550346335726 | XXXXXXXXX8929167990784 | XXXXXXXX868880000 |
46346217550346335726 | XXXXXXXXX146718502912 | XXXXXXXXc12500000 |
46346217550346335726 | XXXXXXXXX364268752896 | XXXXXXXXfbc140000 |
46346217550346335726 | XXXXXXXXX581819002880 | XXXXXXXX365d80000 |
any of these close to your range formula prediction?
000000000000000000000000000000000000000000000005C07854E9A752E2B7
000000000000000000000000000000000000000000000005CE2BEFE8ECF8155E
000000000000000000000000000000000000000000000006816CC8B49ABBF2E5
0000000000000000000000000000000000000000000000068F2063B3E061258C
000000000000000000000000000000000000000000000007020FC0913D01FDAE
0000000000000000000000000000000000000000000000070FC35B9082A73055
000000000000000000000000000000000000000000000007C9C2ABE149EE5411
Prediction apps is what I'm messing around with..
no its below than that.