Bitcoin Forum
May 14, 2024, 01:14:53 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 [8] 9 »
141  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 30, 2015, 05:07:35 PM
I made some research and I believe that the numbers are results of a polynomial (ring) function.

It also seems that someone already got into this in February 2015. Probably the guy who cashed out the first addresses.
http://pastebin.com/erN0F1ce

Quote
-673909/1307674368000*x^15 + 5004253/87178291200*x^14 - 151337/52254720*x^13 + 9320029/106444800*x^12 - 25409989753/14370048000*x^11 + 2192506957/87091200*x^10 - 19011117413/73156608*x^9 + 1200887962891/609638400*x^8 - 3585932821063/326592000*x^7 + 647416874047/14515200*x^6 - 18586394742863/143700480*x^5 + 30899291755337/119750400*x^4 - 274137631043849/825552000*x^3 + 36933161067083/151351200*x^2 - 87781079/1155*x

If you put for x the values 0 to 15, you will get exactly the first 16 numbers.

Quote
1
3
7
8
21
49
76
224
467
514
1155
2683
5216
10544
26867
51510

When you put x = 17 then you got -1514935. This is probably because the formula is not complete. There is x^16 to x^256 missing.
The callange is to find out what formula generates the -673909/1307674368000, 5004253/87178291200,... values.

Very nice finding tyz, this gives us some hope that this puzzle will still be solved during our lifetime  Cheesy

Yes the problem are those divisions like -673909/1307674368000, not sure whats the formula behind this, will have a look on it.
142  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 30, 2015, 10:28:37 AM
I am comfortable in my use of "never" since it is based on the most fundamental laws of thermodynamics.

At any rate if a computer ever does simply count from 1 to 2256 look dig me up so you can tell me "I told you so".

We all will be long gone when that happens to tell you "I told you so"  Cheesy

About the puzzle, the final verdict is that it is unsolvable without brute force, same opinion all?
143  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 29, 2015, 06:26:19 PM
After some analysis I believe the underlying sequence is probably random.  It may have been a PRNG instead of a RNG but that would not help us much.  It would be great if we had all 50 actual values to work with.

Code:
  BTC   Actual      Range of Values                        Location
Value  Value       Low                    High            in Range
-----  ----------  -------------------------------------  ---------
0.001  1           0                      1               100.0000%
0.002  3           2                      3               100.0000%
0.003  7           4                      7               100.0000%
0.004  8           8                      15                0.0000%
0.005  21          16                     31               33.3333%
0.006  49          32                     63               54.8387%
0.007  76          64                     127              19.0476%
0.008  224         128                    255              75.5906%
0.009  467         256                    511              82.7451%
0.010  514         512                    1,023             0.3914%
0.011  1,155       1,024                  2,047            12.8055%
0.012  2,683       2,048                  4,095            31.0210%
0.013  5,216       4,096                  8,191            27.3504%
0.014  10,544      8,192                  16,383           28.7144%
0.015  26,867      16,384                 32,767           63.9871%
0.016  51,510      32,768                 65,535           57.1978%
0.017  95,823      65,536                 131,071          46.2150%
0.018  198,669     131,072                262,143          51.5728%
0.019  357,535     262,144                524,287          36.3889%
0.020  863,317     524,288                1,048,575        64.6648%
0.021  1,811,764   1,048,576              2,097,151        72.7833%
0.022  3,007,503   2,097,152              4,194,303        43.4089%
0.023  5,598,802   4,194,304              8,388,607        33.4858%
0.024  14,428,676  8,388,608              16,777,215       72.0032%
0.025              16,777,216             33,554,431
0.026              33,554,432             67,108,863
0.027              67,108,864             134,217,727
0.028              134,217,728            268,435,455
0.029              268,435,456            536,870,911
0.030              536,870,912            1,073,741,823
0.031              1,073,741,824          2,147,483,647
0.032              2,147,483,648          4,294,967,295
0.033              4,294,967,296          8,589,934,591
0.034              8,589,934,592          17,179,869,183
0.035              17,179,869,184         34,359,738,367
0.036              34,359,738,368         68,719,476,735
0.037              68,719,476,736         137,438,953,471
0.038              137,438,953,472        274,877,906,943
0.039              274,877,906,944        549,755,813,887
0.040              549,755,813,888        1,099,511,627,775
0.041              1,099,511,627,776      2,199,023,255,551
0.042              2,199,023,255,552      4,398,046,511,103
0.043              4,398,046,511,104      8,796,093,022,207
0.044              8,796,093,022,208      17,592,186,044,415
0.045              17,592,186,044,416     35,184,372,088,831
0.046              35,184,372,088,832     70,368,744,177,663
0.047              70,368,744,177,664     140,737,488,355,327
0.048              140,737,488,355,328    281,474,976,710,655
0.049              281,474,976,710,656    562,949,953,421,311
0.050              562,949,953,421,312    1,125,899,906,842,620
0.051              1,125,899,906,842,620  2,251,799,813,685,250
0.052              2,251,799,813,685,250  4,503,599,627,370,490

Very good info, thanks.

I also got to similar conclusion, doesn't look like this will be solvable without years of brute force.

It would be great if the guy that cracked the #50 shows up here and tell us the results.

With regards to the future, we never know what will be possible tomorrow.

Not exactly true.  With respect to brute forcing a private key we know it will never be possible because we can calculate how much energy it would take for a theoretical best possible computer from a thermodynamics point of view to do the task of just counting from 1 to 2160 or 2256.

Since any possible actual computer will be less efficient than the best possible computer we know it will take any possible actual computer more energy than the theoretical machine - which is already too much energy.

Carefully reread the description next to the picture of the sun that is posted every single time this question is posed.

In your previous thread it was posted here:

https://bitcointalk.org/index.php?topic=1305887.msg13377953#msg13377953

mmh, "never" is a strong statement, you can't be sure about a very distant future. 1-10 thousand years or more, maybe the laws that we know today will be reviewed, because new things will be discovered in the unknown universe

even satoshi said that if something will broke sha256 in the future, it will be a completely new thing, not imaginable today

Exactly, was going to reply similar post.

There are many laws in the universe that we still don't know, finding them can completely rewrite everything.

Just look at all the quantum field and you will see how many unanswered questions are there.

Off topic but interesting:

https://www.youtube.com/watch?v=DfPeprQ7oGc
144  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 29, 2015, 10:59:59 AM
-snip-

It will not, however, ever be possible to brute-force attempt 2256 possibilities.

-snip-

2^256   115792089237316000000000000000000000000000000000000000000000000000000000000000   <- And this is how safe bitcoin is.

Nope.

That's how secure an ECDSA public key is, but version 1 bitcoin addresses use a 160 bit hash of that public key, so the security is reduced to 2160.

Effectively yes.

My analogy was based on the fact that there are 2^256 private keys.

With regards to the future, we never know what will be possible tomorrow.

I believe somehow there will be some kind of evolution in computation that will make all the current encryption algorithms useless, but surely not during our life time.

I know its hard to believe, but if back in 1700 you'd tell Isaac Newton that one day mankind would have something called computers at home doing millions of instructions per second using his formulas, it would also be hard to believe.
145  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 11:08:36 PM
50 addresses have been cleaned out so far. The integers for the first 24 private keys have been posted.
Could anyone post the pvks for 25 to 50?

Probably only two guys know that (who cracked and who owns), and they are probably not among us in this forum.
146  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 10:58:37 PM
they seem to be always close to the double of the previous value, excluding the first few values.

There may, or may not be an actual pattern to the values, but that "close to the double of the previous value" would occur if you simply chose a completely random number from a set with 1 additional binary digit at each level.

Effectively each new private key would be a number of binary digits equivalent to the number of milibitcoins stored at the address with the first digit being a 1.


Let us assume that there is some sort of mathematical formula to solve this puzzle.

That's the only way we will ever be able to solve this puzzle during our lifetime.

I strongly recommend to all the mathematical experts out there to have a look at this sequence, maybe they are able to find something.
147  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 10:49:22 PM
All of this story tell us something.

We now know that someone out there is able to crack aprox. 2^50 private keys in about 1 year.

(in a worst case scenario, also assuming that the one who cracked the 50 addresses brute forced all the possible addresses sequential)

As time goes by this capability will increase, it may take decades and decades or centuries but eventually it will be possible to crack 2^256 pvks.

The transaction referenced in this thread is a good reference to test how far the mankind cracking capabilities are.

As of now, we can enjoy the safety of bitcoin for a long long time Smiley

2^1   2   
2^2   4   
2^3   8   
2^4   16   
2^5   32   
2^6   64   
2^7   128   
2^8   256   
2^9   512   
2^10   1024   
2^11   2048   
2^12   4096   
2^13   8192   
2^14   16384   
2^15   32768   
2^16   65536   
2^17   131072   
2^18   262144   
2^19   524288   
2^20   1048576   
2^21   2097152   
2^22   4194304   
2^23   8388608   
2^24   16777216   
2^25   33554432   
2^26   67108864   
2^27   134217728   
2^28   268435456   
2^29   536870912   
2^30   1073741824   
2^31   2147483648   
2^32   4294967296   
2^33   8589934592   
2^34   17179869184   
2^35   34359738368   
2^36   68719476736   
2^37   137438953472   
2^38   274877906944   
2^39   549755813888   
2^40   1099511627776   
2^41   2199023255552   
2^42   4398046511104   
2^43   8796093022208   
2^44   17592186044416   
2^45   35184372088832   
2^46   70368744177664   
2^47   140737488355328   
2^48   281474976710656   
2^49   562949953421312   
2^50   1125899906842620   <- This is aprox. the number of bitcoins private keys someone is able to crack in about 1 year
2^51   2251799813685250   
2^52   4503599627370500   
2^53   9007199254740990   
2^54   18014398509482000   
2^55   36028797018964000   
2^56   72057594037927900   
2^57   144115188075856000   
2^58   288230376151712000   
2^59   576460752303423000   
2^60   1152921504606850000   
2^61   2305843009213690000   
2^62   4611686018427390000   
2^63   9223372036854780000   
2^64   18446744073709600000   
2^65   36893488147419100000   
2^66   73786976294838200000   
2^67   147573952589676000000   
2^68   295147905179353000000   
2^69   590295810358706000000   
2^70   1180591620717410000000   
2^71   2361183241434820000000   
2^72   4722366482869650000000   
2^73   9444732965739290000000   
2^74   18889465931478600000000   
2^75   37778931862957200000000   
2^76   75557863725914300000000   
2^77   151115727451829000000000   
2^78   302231454903657000000000   
2^79   604462909807315000000000   
2^80   1208925819614630000000000   
2^81   2417851639229260000000000   
2^82   4835703278458520000000000   
2^83   9671406556917030000000000   
2^84   19342813113834100000000000   
2^85   38685626227668100000000000   
2^86   77371252455336300000000000   
2^87   154742504910673000000000000   
2^88   309485009821345000000000000   
2^89   618970019642690000000000000   
2^90   1237940039285380000000000000   
2^91   2475880078570760000000000000   
2^92   4951760157141520000000000000   
2^93   9903520314283040000000000000   
2^94   19807040628566100000000000000   
2^95   39614081257132200000000000000   
2^96   79228162514264300000000000000   
2^97   158456325028529000000000000000   
2^98   316912650057057000000000000000   
2^99   633825300114115000000000000000   
2^100   1267650600228230000000000000000   
2^101   2535301200456460000000000000000   
2^102   5070602400912920000000000000000   
2^103   10141204801825800000000000000000   
2^104   20282409603651700000000000000000   
2^105   40564819207303300000000000000000   
2^106   81129638414606700000000000000000   
2^107   162259276829213000000000000000000   
2^108   324518553658427000000000000000000   
2^109   649037107316853000000000000000000   
2^110   1298074214633710000000000000000000   
2^111   2596148429267410000000000000000000   
2^112   5192296858534830000000000000000000   
2^113   10384593717069700000000000000000000   
2^114   20769187434139300000000000000000000   
2^115   41538374868278600000000000000000000   
2^116   83076749736557200000000000000000000   
2^117   166153499473114000000000000000000000   
2^118   332306998946229000000000000000000000   
2^119   664613997892458000000000000000000000   
2^120   1329227995784920000000000000000000000   
2^121   2658455991569830000000000000000000000   
2^122   5316911983139660000000000000000000000   
2^123   10633823966279300000000000000000000000   
2^124   21267647932558700000000000000000000000   
2^125   42535295865117300000000000000000000000   
2^126   85070591730234600000000000000000000000   
2^127   170141183460469000000000000000000000000   
2^128   340282366920938000000000000000000000000   
2^129   680564733841877000000000000000000000000   
2^130   1361129467683750000000000000000000000000   
2^131   2722258935367510000000000000000000000000   
2^132   5444517870735020000000000000000000000000   
2^133   10889035741470000000000000000000000000000   
2^134   21778071482940100000000000000000000000000   
2^135   43556142965880100000000000000000000000000   
2^136   87112285931760200000000000000000000000000   
2^137   174224571863520000000000000000000000000000   
2^138   348449143727041000000000000000000000000000   
2^139   696898287454082000000000000000000000000000   
2^140   1393796574908160000000000000000000000000000   
2^141   2787593149816330000000000000000000000000000   
2^142   5575186299632660000000000000000000000000000   
2^143   11150372599265300000000000000000000000000000   
2^144   22300745198530600000000000000000000000000000   
2^145   44601490397061200000000000000000000000000000   
2^146   89202980794122500000000000000000000000000000   
2^147   178405961588245000000000000000000000000000000   
2^148   356811923176490000000000000000000000000000000   
2^149   713623846352980000000000000000000000000000000   
2^150   1427247692705960000000000000000000000000000000   
2^151   2854495385411920000000000000000000000000000000   
2^152   5708990770823840000000000000000000000000000000   
2^153   11417981541647700000000000000000000000000000000   
2^154   22835963083295400000000000000000000000000000000   
2^155   45671926166590700000000000000000000000000000000   
2^156   91343852333181400000000000000000000000000000000   
2^157   182687704666363000000000000000000000000000000000   
2^158   365375409332726000000000000000000000000000000000   
2^159   730750818665451000000000000000000000000000000000   
2^160   1461501637330900000000000000000000000000000000000   
2^161   2923003274661810000000000000000000000000000000000   
2^162   5846006549323610000000000000000000000000000000000   
2^163   11692013098647200000000000000000000000000000000000   
2^164   23384026197294400000000000000000000000000000000000   
2^165   46768052394588900000000000000000000000000000000000   
2^166   93536104789177800000000000000000000000000000000000   
2^167   187072209578356000000000000000000000000000000000000   
2^168   374144419156711000000000000000000000000000000000000   
2^169   748288838313422000000000000000000000000000000000000   
2^170   1496577676626840000000000000000000000000000000000000   
2^171   2993155353253690000000000000000000000000000000000000   
2^172   5986310706507380000000000000000000000000000000000000   
2^173   11972621413014800000000000000000000000000000000000000   
2^174   23945242826029500000000000000000000000000000000000000   
2^175   47890485652059000000000000000000000000000000000000000   
2^176   95780971304118100000000000000000000000000000000000000   
2^177   191561942608236000000000000000000000000000000000000000   
2^178   383123885216472000000000000000000000000000000000000000   
2^179   766247770432944000000000000000000000000000000000000000   
2^180   1532495540865890000000000000000000000000000000000000000   
2^181   3064991081731780000000000000000000000000000000000000000   
2^182   6129982163463560000000000000000000000000000000000000000   
2^183   12259964326927100000000000000000000000000000000000000000   
2^184   24519928653854200000000000000000000000000000000000000000   
2^185   49039857307708400000000000000000000000000000000000000000   
2^186   98079714615416900000000000000000000000000000000000000000   
2^187   196159429230834000000000000000000000000000000000000000000   
2^188   392318858461668000000000000000000000000000000000000000000   
2^189   784637716923335000000000000000000000000000000000000000000   
2^190   1569275433846670000000000000000000000000000000000000000000   
2^191   3138550867693340000000000000000000000000000000000000000000   
2^192   6277101735386680000000000000000000000000000000000000000000   
2^193   12554203470773400000000000000000000000000000000000000000000   
2^194   25108406941546700000000000000000000000000000000000000000000   
2^195   50216813883093400000000000000000000000000000000000000000000   
2^196   100433627766187000000000000000000000000000000000000000000000   
2^197   200867255532374000000000000000000000000000000000000000000000   
2^198   401734511064748000000000000000000000000000000000000000000000   
2^199   803469022129495000000000000000000000000000000000000000000000   
2^200   1606938044258990000000000000000000000000000000000000000000000   
2^201   3213876088517980000000000000000000000000000000000000000000000   
2^202   6427752177035960000000000000000000000000000000000000000000000   
2^203   12855504354071900000000000000000000000000000000000000000000000   
2^204   25711008708143800000000000000000000000000000000000000000000000   
2^205   51422017416287700000000000000000000000000000000000000000000000   
2^206   102844034832575000000000000000000000000000000000000000000000000   
2^207   205688069665151000000000000000000000000000000000000000000000000   
2^208   411376139330302000000000000000000000000000000000000000000000000   
2^209   822752278660603000000000000000000000000000000000000000000000000   
2^210   1645504557321210000000000000000000000000000000000000000000000000   
2^211   3291009114642410000000000000000000000000000000000000000000000000   
2^212   6582018229284820000000000000000000000000000000000000000000000000   
2^213   13164036458569600000000000000000000000000000000000000000000000000   
2^214   26328072917139300000000000000000000000000000000000000000000000000   
2^215   52656145834278600000000000000000000000000000000000000000000000000   
2^216   105312291668557000000000000000000000000000000000000000000000000000   
2^217   210624583337114000000000000000000000000000000000000000000000000000   
2^218   421249166674229000000000000000000000000000000000000000000000000000   
2^219   842498333348457000000000000000000000000000000000000000000000000000   
2^220   1684996666696910000000000000000000000000000000000000000000000000000   
2^221   3369993333393830000000000000000000000000000000000000000000000000000   
2^222   6739986666787660000000000000000000000000000000000000000000000000000   
2^223   13479973333575300000000000000000000000000000000000000000000000000000   
2^224   26959946667150600000000000000000000000000000000000000000000000000000   
2^225   53919893334301300000000000000000000000000000000000000000000000000000   
2^226   107839786668603000000000000000000000000000000000000000000000000000000   
2^227   215679573337205000000000000000000000000000000000000000000000000000000   
2^228   431359146674410000000000000000000000000000000000000000000000000000000   
2^229   862718293348820000000000000000000000000000000000000000000000000000000   
2^230   1725436586697640000000000000000000000000000000000000000000000000000000   
2^231   3450873173395280000000000000000000000000000000000000000000000000000000   
2^232   6901746346790560000000000000000000000000000000000000000000000000000000   
2^233   13803492693581100000000000000000000000000000000000000000000000000000000   
2^234   27606985387162300000000000000000000000000000000000000000000000000000000   
2^235   55213970774324500000000000000000000000000000000000000000000000000000000   
2^236   110427941548649000000000000000000000000000000000000000000000000000000000   
2^237   220855883097298000000000000000000000000000000000000000000000000000000000   
2^238   441711766194596000000000000000000000000000000000000000000000000000000000   
2^239   883423532389192000000000000000000000000000000000000000000000000000000000   
2^240   1766847064778380000000000000000000000000000000000000000000000000000000000   
2^241   3533694129556770000000000000000000000000000000000000000000000000000000000   
2^242   7067388259113540000000000000000000000000000000000000000000000000000000000   
2^243   14134776518227100000000000000000000000000000000000000000000000000000000000   
2^244   28269553036454100000000000000000000000000000000000000000000000000000000000   
2^245   56539106072908300000000000000000000000000000000000000000000000000000000000   
2^246   113078212145817000000000000000000000000000000000000000000000000000000000000   
2^247   226156424291633000000000000000000000000000000000000000000000000000000000000   
2^248   452312848583266000000000000000000000000000000000000000000000000000000000000   
2^249   904625697166533000000000000000000000000000000000000000000000000000000000000   
2^250   1809251394333070000000000000000000000000000000000000000000000000000000000000   
2^251   3618502788666130000000000000000000000000000000000000000000000000000000000000   
2^252   7237005577332260000000000000000000000000000000000000000000000000000000000000   
2^253   14474011154664500000000000000000000000000000000000000000000000000000000000000   
2^254   28948022309329000000000000000000000000000000000000000000000000000000000000000   
2^255   57896044618658100000000000000000000000000000000000000000000000000000000000000   
2^256   115792089237316000000000000000000000000000000000000000000000000000000000000000   <- And this is how safe bitcoin is.
148  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 08:44:52 PM
I posted this puzzle transaction in January'15
https://bitcointalk.org/index.php?topic=932434.0

(This tx was not sent by me)

Let me translate from Russian into English the main point in my prevoius post:

First output: take random number from 20 upto 21-1, use it as private key
Second output: take random number from 21 upto 22-1, use it as private key
Third output: take random number from 22 upto 23-1, use it as private key
And so on...


The Russians always get it first Wink

-snip-
Code:
"1 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73sVHnoWn 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH (1)"
"2 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU74sHUHy8S 1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb (3)"
"3 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU76rnZwVdz 19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA (7)"
"4 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU77MfhviY5 1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e (8)"
"5 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Dq8Au4Pv 1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k (21)"
"6 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Tmu6qHxS 1PitScNLyp2HCygzadCh7FveTnfmpPbfp8 (49)"
"7 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7hDgvu64y 1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC (76)"
"8 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU8xvGK1zpm 1M92tSqNmQLYw33fuBvjmeadirh1ysMBxK (224)"
"9 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUB3vfDKcxZ 1CQFwcjw1dwhtkVWBttNLDtqL7ivBonGPV (467)"
"10 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUBTL67V6dE 1LeBZP5QCwwgXRtmVUvTVrraqPUokyLHqe (514)"
"11 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUGxXgtm63M 1PgQVLmst3Z314JrQn5TNiys8Hc38TcXJu (1155)"
"12 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUW5RtS2JN1 1DBaumZxUkM4qMQRt2LVWyFJq5kDtSZQot (2683)"
"13 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUspniiQZds 1Pie8JkxBT6MGPz9Nvi3fsPkr2D8q3GBc1 (5216)"
"14 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFVfZyiN5iEG 1ErZWg5cFCe4Vw5BzgfzB74VNLaXEiEkhk (10544)"
"15 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFY5iMZbuRxj 1QCbW9HWnwQWiQqVo5exhAnmfqKRrCRsvW (26867)"
"16 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFbjHrFMWzJp 1BDyrQ6WoF8VN3g9SAS1iKZcPzFfnDVieY (51510)"
"17 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFiHkRsp99uC 1HduPEXZRdG26SUT5Yk83mLkPyjnZuJ7Bm (95823)"
"18 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFyWkjT5fywW 1GnNTmTVLZiqQfLbAdp9DVdicEnB5GoERE (198669)"
"19 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rGP2jMrxCfX3 1NWmZRpHH4XSPwsW6dsS3nrNWfL1yrJj4w (357535)"
"20 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rHfuE2Tg4nJW 1HsMJxNiV7TLxmoF6uJNkydxPFDog4NQum (863317)"
"21 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rL6JJvw6XUry 14oFNXucftsHiUMY8uctg6N487riuyXs4h (1811764)"
"22 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rP9Ja2dhtxoh 1CfZWK1QTQE3eS9qn61dQjV89KDjZzfNcv (3007503)"
"23 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rVkthFNsQ6i7 1L2GM8eE7mJWLdo3HZS6su1832NX2txaac (5598802)"
"24 KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rtHyNcFoApRd 1rSnXMr63jdCuegJFuidJqWxUPV7AtUf7 (14428676)"


You got all the work done right there until the #24, nicely done
149  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 08:38:31 PM
Assuming my pattern assumption is correct then the underlying sequence was masked off to create the private keys.

Now if the underlying sequence before masking came from a cryptographically secure random number generator there is no hope of predicting the 51st private key and brute force or random chance in 51 bits is the only chance.

However if the underlying sequence was mathematically generated then maybe the keys are predictable.

Exactly.

I think the best is if we find a mathematical formula for the sequence (if it really exists).

For example, if you look at the decimal values, they seem to be always close to the double of the previous value, excluding the first few values.

So how were the results on the OP reached? Simply luck?

I'm pretty sure that the results that have been found by the OP so far were found with brute force attempting every value between 1 and 220.

The problem is that finding each subsequent result requires exponentially more attempts than the current result, so as the number of bits increases it becomes much, Much, MUCH more difficult to check the entire search space.

Exactly.

By the way, address 20:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rHfuE2Tg4nJW
1HsMJxNiV7TLxmoF6uJNkydxPFDog4NQum
pvk decimal value: 863317
pvk hex value: D2C55

So these are the decimal values we have:

Address 2: 3
Address 3: 7
Address 4: 8
Address 5: 21
Address 6: 49
Address 7: 76
Address 8: 224
Address 9: 467
Address 10: 514
Address 11: 1155
Address 12: 2683
Address 13: 5216
Address 14: 10544
Address 15: 26867
Address 16: 51510
Address 17: 95823
Address 18: 198669
Address 19: 357535
Address 20: 863317
Address 21: ?

-snip-
If that is what's going on here, then there may not be a "formula" or "pattern" that can be used.  To get the 51st address, you'd just have to brute force try all addresses associated with private keys between 1125899906842624 and 2251799813685248 (which is only about 1.126 X 1015 addresses).

Yes, that's a lot of brute force right there  Grin
150  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 07:46:51 PM
-snip-
Suggestions are always welcome.

The brute force way: Start @ ~607809 (multiplied the last known value by 1.7) convert to hex, create addresses, check if one address matches the next in turn.



What would be the best tool to attack this in a brute force way while we all think on something better or discover a easier way?

Some GPU bot would be the best to brute force it, like shorena was saying.

Need to code one, but I'm not in the mood now Smiley

Anyone out there doing it? Or maybe there is something existing?

I think the best existing tool currently is yours or otherwise private. I would think the best way would be to modify (ocl)vanitygen according to BurtW's suggestion. You would need to limit the random number generator to a certain amount of bits and keep the rest.

I don't think brute force is going to solve this puzzle.

A GPU bot would increase the performance much higher but still we would be here forever trying it.

The only way to solve this efficiently is to try to find a mathematical formula to break the sequence.

If a formula is not found, I think this puzzle will be as unbreakable as bitcoin itself.
151  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 07:26:29 PM
-snip-
Suggestions are always welcome.

The brute force way: Start @ ~607809 (multiplied the last known value by 1.7) convert to hex, create addresses, check if one address matches the next in turn.



What would be the best tool to attack this in a brute force way while we all think on something better or discover a easier way?

Some GPU bot would be the best to brute force it, like shorena was saying.

Need to code one, but I'm not in the mood now Smiley

Anyone out there doing it? Or maybe there is something existing?
152  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 06:49:31 PM
looks really easy to crack

why would reward be so high

It's not easy, trust me.

But go ahead, maybe you can crack it.
153  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 06:42:37 PM
The transactions seem to originate from address 173ujrhEVGqaZvPHXLqwXiSmPVMo225cqT  which had a Total received amount of   56,457.80848111 BTC and a Final Balance of    312.04932734 BTC

Definitely a very big player of some kind.

Well spotted.

Also it looks active, there are daily transactions there.

Probably some exchange?
154  Bitcoin / Bitcoin Discussion / Re: brute force on Bitcoin Addresses - Video of the action on: December 28, 2015, 06:34:41 PM
I'm not looking for any treasure, I'm just playing around with PVKs, you have a problem with that?

A little. I mean, it's kind of an ethical quandary. If you run across a wallet lying in someone's driveway, do you scoop it up and continue on your way? Or do you consider it the rightful property of the homeowner? That's pretty clearly analogous to running across someone's poorly-constructed brainwallet address with funds in it.

Quote
And to be honest with you I don't really care about the 32 BTC, I'm just in for the challenge.

And to be honest with you, I don't believe you. I believe you're just in to dupe those that know less than you into buying your 'app + database' for 1 BTC each.

Oh man, I don't really care about that. Look, I will edit the post and remove that line.

Fortunately enough, 1 BTC is irrelevant in my total net worth.
155  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 06:25:09 PM
Any info on who published this puzzle and what's their goal? Also, how would one go on about calculating those pvk decimal values and covert them to the private keys?

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...

The OP is not offering anything

I have no idea about who created this transactions, I was just playing around with the bot and stumbled upon it.

After reviewing a bunch of pvks found by the bot I noticed that many of the addresses were on the same transaction, after checking closely I found those kind of sequence patterns.

Looks tempting to crack Smiley

One thing I noticed:

The first address in the transaction is tagged on blockchain.info with "1st Bitcoin Address Compressed".

So probably this transaction was done by the Bitcoin devs? or even... satoshi?
156  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 06:18:01 PM
More details of the new values, including pvks and publics

Address 15:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFY5iMZbuRxj
1QCbW9HWnwQWiQqVo5exhAnmfqKRrCRsvW
pvk decimal value: 26867
pvk hex value: 68F3

Address 16:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFbjHrFMWzJp
1BDyrQ6WoF8VN3g9SAS1iKZcPzFfnDVieY
pvk decimal value: 51510
pvk hex value: C936

Address 17:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFiHkRsp99uC
1HduPEXZRdG26SUT5Yk83mLkPyjnZuJ7Bm
pvk decimal value: 95823
pvk hex value: 1764F

Address 18:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFyWkjT5fywW
1GnNTmTVLZiqQfLbAdp9DVdicEnB5GoERE
pvk decimal value: 198669
pvk hex value: 3080D

Address 19:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rGP2jMrxCfX3
1NWmZRpHH4XSPwsW6dsS3nrNWfL1yrJj4w
pvk decimal value: 357535
pvk hex value: 5749F
157  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 06:06:43 PM
As BurtW also pointed out the transaction values increase from from 0.001 to 0.256, according to the address position.

Lets start by what we know:

The BTC values of the outputs (0.001 through 0.256) are obviously the sequence numbers and the private keys are the sequence values.

How many of the sequence values do we already know (have been found by brute force)?  

Is the list in this thread the entire list of known values from the sequence?

here are the other pvk decimal values I was able to find:

Address 15: 26867
Address 16: 51510
Address 17: 95823
Address 18: 198669
Address 19: 357535
Address 20: ?
158  Bitcoin / Bitcoin Discussion / Re: brute force on Bitcoin Addresses - Video of the action on: December 28, 2015, 04:19:49 PM
Looks like you have lots of free time, don't you?

But, rather than doing that without any leads, i think you better try to brute-force bitcoin address which created using brain wallet.
In past some people collected some dust at brainwallet.org, they just use common words to did it.

Would be great to see someone can steal someone bitcoin in this way Roll Eyes
Since most people, especially those with paid signatures, don't read entire or even part of a thread before they blurt out a comment or opinion maybe we move the puzzle to a new thread?

New thread: https://bitcointalk.org/index.php?topic=1306983

Btw, I have more values of the sequence, but not at the moment.

I will post them in the new thread soon
159  Bitcoin / Bitcoin Discussion / Bitcoin puzzle transaction ~32 BTC prize to who solves it on: December 28, 2015, 04:12:47 PM
Hi guys,

In continuation to this thread: https://bitcointalk.org/index.php?topic=1305887.0

While playing around with my bot, I found out this mysterious transaction:

https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15

those 32.896 BTC were sent to multiple addresses, all the private keys of those addresses seem to be generated by some kind of formula.

For example:

Address 2:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU74sHUHy8S
1CUNEBjYrCn2y1SdiUMohaKUi4wpP326Lb
Biginteger PVK value: 3
Hex PVK value: 3

Address 3:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU76rnZwVdz
19ZewH8Kk1PDbSNdJ97FP4EiCjTRaZMZQA
Biginteger PVK value: 7
Hex PVK value: 7

Address 4:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU77MfhviY5
1EhqbyUMvvs7BfL8goY6qcPbD6YKfPqb7e
Biginteger PVK value: 8
Hex PVK value: 8

Address 5:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Dq8Au4Pv
1E6NuFjCi27W5zoXg8TRdcSRq84zJeBW3k
Biginteger PVK value: 21
Hex PVK value: 15

Address 6:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7Tmu6qHxS
1PitScNLyp2HCygzadCh7FveTnfmpPbfp8
Biginteger PVK value: 49
Hex PVK value: 31

Address 7:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU7hDgvu64y
1McVt1vMtCC7yn5b9wgX1833yCcLXzueeC
Biginteger PVK value: 76
Hex PVK value: 4C

Address 8:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU8xvGK1zpm
1M92tSqNmQLYw33fuBvjmeadirh1ysMBxK
Biginteger PVK value: 224
Hex PVK value: E0

Address 9:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUB3vfDKcxZ
1CQFwcjw1dwhtkVWBttNLDtqL7ivBonGPV
Biginteger PVK value: 467
Hex PVK value: 1d3

Address 10:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUBTL67V6dE
1LeBZP5QCwwgXRtmVUvTVrraqPUokyLHqe
Biginteger PVK value: 514
Hex PVK value: 202

Address 11:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUGxXgtm63M
1PgQVLmst3Z314JrQn5TNiys8Hc38TcXJu
Biginteger PVK value: 1155
Hex PVK value: 483

Address 12:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUW5RtS2JN1
1DBaumZxUkM4qMQRt2LVWyFJq5kDtSZQot
Biginteger PVK value: 2683
Hex PVK value: a7b

Address 13:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFUspniiQZds
1Pie8JkxBT6MGPz9Nvi3fsPkr2D8q3GBc1
Biginteger PVK value: 5216
Hex PVK value: 1460

Address 14:

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFVfZyiN5iEG
1ErZWg5cFCe4Vw5BzgfzB74VNLaXEiEkhk
Biginteger PVK value: 10544
Hex PVK value: 2930

and so on...

until the addresses 50 (1MEzite4ReNuWaL5Ds17ePKt2dCxWEofwk) it was already cracked by someone.

Any ideas what's the formula behind the generation of these addresses?

Address 2, pvk decimal value: 3
Address 3, pvk decimal value: 7
Address 4, pvk decimal value: 8
Address 5, pvk decimal value: 21
Address 6, pvk decimal value: 49
Address 7, pvk decimal value: 76
Address 8, pvk decimal value: 224
Address 9, pvk decimal value: 467
Address 10, pvk decimal value: 514
Address 11, pvk decimal value: 1155
Address 12, pvk decimal value: 2683
Address 13, pvk decimal value: 5216
Address 14, pvk decimal value: 10544
Address 15 and after, pvk decimal value: ?

The prize would be ~32 BTC Smiley

EDIT: If you find the solution feel free to leave a tip Smiley 1DPUhjHvd2K4ZkycVHEJiN6wba79j5V1u3
160  Bitcoin / Bitcoin Discussion / Re: brute force on Bitcoin Addresses - Video of the action on: December 28, 2015, 03:49:26 PM
https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15

Does look like someone placed an interesting puzzle in the blockchain for us.

It appears to me to be a game of some sort:  if you crack the sequence you can get the BTC.

Exactly.

Finally someone that listened to my words.

So, how to crack it?
Easy, figure out the sequence, follow it, take the BTC off the generated addresses as you go along.

OK, so figuring out the sequence may actually be hard, but then if it wasn't hard it would not be worth doing, right?

Smiley

I already tried everything I could, no success.

I give up on it, but I'm curious if someone else can break it.
Pages: « 1 2 3 4 5 6 7 [8] 9 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!