Matches for $maxint, 320 total results Sorted by newest | relevance
Thu Mar 10 21:37:45 UTC 2016 <asciilifeform> $MAXINT for rusty iron, but not a penny for hiring folks
Sun Mar 06 14:39:22 UTC 2016 <mircea_popescu> bitcoin was fine, and would continue to be fine, as is, for any maxint.
Sun Mar 06 14:38:58 UTC 2016 <asciilifeform> well, he naively thought that nobody would throw $maxint at it.
Fri Mar 04 20:27:37 UTC 2016 <jurov> but ALL the conflicts have same $maxint fee
Wed Feb 24 23:28:43 UTC 2016 <asciilifeform> the mineral rights are with the city, or the original developer of the street, who won't part with them even for maxint.
Sat Feb 20 19:56:10 UTC 2016 <assbot> Logged on 13-02-2016 23:22:01; mod6: oh, because the leaf ordering is different. if you want a press of "all" patches as they exist in the mirror, currently, you need to press up through asciilifeform_maxint_locks_corrected.vpatch
Sat Feb 20 17:53:06 UTC 2016 <asciilifeform> maxint
Wed Feb 17 03:30:02 UTC 2016 <mod6> so what would be great here, is if you apply the patch, or use the v.pl attached to the email (check the sigs ofc), then start clean, do a fresh `./v.pl i http://thebitcoin.foundation`, and then press out the entire tree, `./v.pl p v v054 asciilifeform_maxint_locks_corrected.vpatch`, then `cd v054` and run that find command at the top of this pastehttp://dpaste.com/2SQ1VZ7.txt
Sun Feb 14 01:07:49 UTC 2016 <asciilifeform> anyway this notion that plebes could steal serious money without official approval is lunacy. if $maxint grows legs, it is because lizards had a shadow payment to make, a la isis, and not because some uppity kid was rewarded for nietzschian 'will' or wtf else.
Sat Feb 13 23:22:01 UTC 2016 <mod6> oh, because the leaf ordering is different. if you want a press of "all" patches as they exist in the mirror, currently, you need to press up through asciilifeform_maxint_locks_corrected.vpatch
Sat Feb 13 23:20:33 UTC 2016 <pete_dushenski> http://log.bitcoin-assets.com/?date=13-02-2016#1405086 << why does line 46 have asciilifeform_maxint_locks_corrected.vpatch instead latest vpatch as on previous 99996 and 99997 iterations ?
Sat Feb 06 16:50:47 UTC 2016 <asciilifeform> there is NEVER any shortage of folks who will do $work for $maxint. they will fly down from mars if you pay enough.
Thu Feb 04 20:07:38 UTC 2016 <mircea_popescu> maxint in there is quite literally, maxint. currently pi is computed up to about 2*10^13 or so digits. signed 64 bit max is ~10^19
Thu Feb 04 20:06:22 UTC 2016 <mircea_popescu> to decipher you calculate the maxint+key to maxint+key+block digits of e with a plouffe-like algo (not here included) which you ?' with the ciphered message yielding the original plaintext.
Thu Feb 04 20:06:21 UTC 2016 <mircea_popescu> you need a proper "destructive multiplication" item, which i'll discuss later, noted here ?. you proceed to calculate the maxint+key to maxint+key+block digits of pi via repeated applications of the original plouffe algo, and you ? the result with the plaintext message which yields the ciphered message.
Wed Feb 03 16:47:07 UTC 2016 <assbot> Satoshi asciilifeform_maxint_locks_corrected/src/serialize.h ... ( http://bit.ly/1JYjxeI )
Wed Feb 03 16:47:05 UTC 2016 <mircea_popescu> click on definition, see http://btc.yt/lxr/satoshi/source/src/serialize.h?v=asciilifeform_maxint_locks_corrected#0023
Wed Feb 03 16:46:59 UTC 2016 <assbot> Satoshi asciilifeform_maxint_locks_corrected identifier search: uint64 ... ( http://bit.ly/1JYjwHJ )
Wed Feb 03 16:46:58 UTC 2016 <mircea_popescu> srsly ascii_butugychag : http://btc.yt/lxr/satoshi/ident?v=asciilifeform_maxint_locks_corrected&_i=uint64
Wed Feb 03 16:42:35 UTC 2016 <assbot> Satoshi asciilifeform_maxint_locks_corrected/ ... ( http://bit.ly/1SaeKaR )