log☇︎
132 entries in 0.671s
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*0000 4)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*11111111 8)
ben_vulpes: kinda thinking i should just maintain a "mpfhf currently backing candi" on that page
ben_vulpes: candi_lustt: (mpfhf:mpfhf #*1001101101000010000011010111101001110001111010111110011100000110000111100111110011100001 10)
sina: https://github.com/sinner-/mpfhf-python
sina: candi_lustt: (mpfhf:mpfhf #*1001101101000010000011010111101001110001111010111110011100000110000111100111110011100001 64)
sina: candi_lustt: (mpfhf:mpfhf #*1001101101000010000011010111101001110001111010111110011100000110000111100111110011100001 64)
mircea_popescu: cool. seeing how ben_vulpes ' lisp implementation ain't working yet, you have a shot at becoming the first cannonical mpfhf
sina: can you confirm my intepretation of the spec for mpfhf is correct or not?
ben_vulpes: !~later tell sina mircea_popescu wants mpfhf commentary on his blog
sina: shinohai: do you know anything about mpfhf?
ben_vulpes: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111111111111111111111111111111111111 64)
ben_vulpes: candi_lustt: (mpfhf:mpfhf #*0000000000000000000000000000000000000000000000000000000000000000000000000000000 64)
ben_vulpes: (mpfhf:mpfhf #*0000000000000000000000000000000000000000000000000000000000000000000000000000000 64)
sina: mpfhf?
mircea_popescu: but! if you're looking for something to sink teeth in right now, either a c or python mpfhf impl is prolly a ghood moive
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111111111111111111111111111111111101 32)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111111111111111111111111111111111110 32)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111011111111111111111111111111111111 32)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111101111111111111111111111111111111111111 32)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111111111111111111111111111111111111 31)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111111111111111111111111111111111111 33)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111111111111111111111111111111111111 32)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*101010101010101010101010101010101010101010101010101010101010101010101010101010101010101 32)
mircea_popescu: candi_lustt: (mpfhf:mpfhf #*101010101010101010101010101010101010101010101010101010101010101010101010101010101010101 32)
ben_vulpes: candi_lustt: (mpfhf:mpfhf #*1111111111111111111111111111111111111111111111111111111111111111 64)
a111: 4 results for "MPFHF", http://btcbase.org/log-search?q=MPFHF
asciilifeform: !#s MPFHF
mircea_popescu points out wholly disinterestedly at this point that the eponymous mpfhf allows for variable length output, and could be made to do say log (blockheight) bits!
mircea_popescu: this is a fundamental and inescapable problem of usg-style hash functions. stuff like mpfhf mitigate THAT problem, but at a humongous cost.
mircea_popescu: asciilifeform anyway, as an entirely idle example : the set of numbers with mpfhf defined on it is actually a fine example in this vein. it ISNT an algebraic structure ; but an algorithmic structure.
mircea_popescu: anyway, to get back to the wallet : i would fucking love to see a mpfhf collision on 513 byte input.