57800+ entries in 0.451s
mircea_popescu: ben_vulpes and block depth. if you make segwit tx a to me at height 1 and
i put it into a normal tx at block 2,
i can spend it from block 3 as my bitcoin, the segwitnmess is gone out of it. to steal it from me, one has to rewind all the way to block 1 again. which is possible, but expensive as the chain builds.
☟︎ ben_vulpes: trinque:
i wouldn't go so far as to say they pulled it off
trinque: yeah
I guess by mass, if not proportion
ben_vulpes: in reading some commentary on seattle's new tax on the rich,
i learn that a sales tax is regressive because rich people pay a smaller fraction of their income in taxes than poors
mircea_popescu:
i'm vaguely curious if/when guy manages to escape his worm form.
ben_vulpes: and you know, "if
i ain't fuckin you,
i ain't fixin your head neither"
ben_vulpes:
i'm waiting for age and failure to mature me into a nice ball of hate
ben_vulpes: BingoBoingo: gotta realize,
i'm a sucker for cuddles
ben_vulpes: BingoBoingo:
i appreciate the exhortation
ben_vulpes: that level of shiv/word density is far beyond what
i can accomplish, BingoBoingo has been practicing
ben_vulpes: while
i'm on the topic, can confirm that 'modern' asdf is all sorts of royal pita as well, although that thread has been well hashed in the logs
a111: Logged on 2017-07-13 15:18 phf: for the longest time
i thought that common lisp spec is a magic paper against modernization. not so, and you can see it with the recent evolution of sbcl. for example they made it an error to locally shadow cl package symbols, e.g. (flet ((first (...))) ...) will fail, breaking a lot of reasonable old code. many historic idioms likewise produce compilation warnings, etc.
mircea_popescu:
i didn't by any means aim to produce an exhaustive or practical list!
mircea_popescu:
i dun have the datasheets to give better numbers with, but anyway.
a111: Logged on 2017-08-11 00:18 mircea_popescu:
http://btcbase.org/log/2017-08-10#1696875 << it is conceivable you can reuse prb blockchains, if you care. not that there's anything wrong with rechecking the chain if oyu're in no hurry. expect a coupla months tho. and
i suppose look into eatblock etc while at it.
a111: Logged on 2017-08-10 21:46 edivad: in the case of segwit, this means that trb won't care about segwit blocks and as long as they will complies with the "hard rules" (
I really don't know how to explain myself better) they will be accepted?
a111: Logged on 2017-08-10 21:38 edivad: in my case
i've recycled a previous bitcoin core blockchain and fired up TRB
a111: Logged on 2017-08-10 21:35 edivad:
i was doing the process in a 8gb container and at a point
i wasn't so confortable continuing refreshing df to check my free space
trinque: oh
I got one: segregated witless
edivad: ok
I'll read it before asking political questions
edivad: in the case of segwit, this means that trb won't care about segwit blocks and as long as they will complies with the "hard rules" (
I really don't know how to explain myself better) they will be accepted?
☟︎ edivad:
i've understood that TRB = purity
mod6:
I'll say 20G, that should suffice, for now.
edivad:
i need to ask something more political than technical
edivad: ok perfect, the third time that
i've restarted the node there weren't no problem at all
mod6: <+trinque> ah well sure, suppose mod6 could mention the build environment is going to be big. << While
I'm at it on the updates;
i think, let's say, you need a minimum of what? 20Gb ?
mod6: <+edivad>
i was doing the process in a 8gb container and at a point
i wasn't so confortable continuing refreshing df to check my free space << oh sure.
I didn't even think to ask. Next time
I will.
mod6: <+edivad>
i have a super good news, node is compiled, up and running << yay!
edivad: 2nd) the second time that
i've started TRB, it was complaining that wallet.dat was corrupted (this wallet.dat was generated from latest core, so
i suppose is deterministic, is this the reason for being rejected?)
edivad: the 1st) when
i started for the first time TRB, he was bitching that myip=something wasn't present on my .conf. Is this a TRB specific requirement?
edivad: in my case
i've recycled a previous bitcoin core blockchain and fired up TRB
☟︎ edivad:
i keep the blockchain stored separatedly
edivad:
i was doing the process in a 8gb container and at a point
i wasn't so confortable continuing refreshing df to check my free space
☟︎ edivad:
i think that is important to add to the guide that the average joe will need at least 6 gb of space in his hard disk to be able to compile from scratch TRB
edivad: now that
i run a node
i can consider myself truly part of tmsr?
edivad:
i have a super good news, node is compiled, up and running
mircea_popescu: the bitch with any such approach, as
i realised last night. there is NO WAY to protect yourself from downstream cache. no way.
mircea_popescu: my intuitions while useless are entirely correct!
i feel much better about self.
edivad: can
i read something about lattice?
i haven't understood well the message
mircea_popescu: we have some expectations about security, they do not include the self-diddle that is "deterministic signatures", ie,
i'll sign with a shitton of mathematically related privkeys.
a111: Logged on 2017-08-10 18:33 edivad:
i thought that dice was great for cheap and safe cold storage, if done it right
shinohai:
I did: shinohai@trb locate CheckIncludeFiles.cmake
shinohai: edivad: If it isn't in /usr/share then you may have to grep for it .... tbh
I rarely used Ubuntu so
a111: Logged on 2017-08-10 18:16 shinohai: ^ That pthread issue
I solved on Debian by going to /usr/share/cmake and changing a line in CheckIncludeFiles.cmake
mod6: <+shinohai> mircea_popescu: The cmake in Debian/Ubuntu repositories used to have that pthread bug, first time
I built a trb with `V` that happened. <<
i don't remember ever having this issue fwiw
edivad: so
i can change the line that you have posted
edivad: shinohai: may
I ask how
I can find CheckIncludeFiles under Ubuntu?
mircea_popescu: o yeah, recall that ? "reality diverged from comfortable model thereof, but it has been denied with appropriate incantations and can now go back to bed.
i wonder what's on tv ?"
hanbot: mircea_popescu :
i seem to remember a period in which the .ro line went that you were "illegal", yeah.
shinohai: mircea_popescu: The cmake in Debian/Ubuntu repositories used to have that pthread bug, first time
I built a trb with `V` that happened.
edivad: ok
i will use the other pastebin no problem
mircea_popescu: this was very noticeable even when
i was organising conferences for local bloggers / getting romania's new right party a headquarters etc. "oh, this doesn't really happen, mp can't really exist" etc bla bla.
mircea_popescu: hanbot heh.
i expect it's deeper than that, though. dork is romanian, and that country had a ~50 year period of enforced equality-through-poverty the likes of which the us can only dream of. this has the side benefit of every kid expecting every other kid be you know, a goat of ~same size. maybe this other guy has a slightly newer car, that's the accepteable limit of it.
edivad:
i'm abusing of it in some way that
i haven't noticed?
edivad: going to do the third clean run, since
i have generated the locale in the middle of the process
a111: Logged on 2017-08-10 15:31 mod6: Hi,
I've updated the howto, it's not "finalized" yet. Please take a look and let me know if this doesn't read quite right, or if
I've left something out:
edivad: and
i must admit,
i grown up with deterministic wallets in my heart and in just a couple of minutes realized how a dumb move it was
edivad:
i was in a mint system without generated locales
edivad:
i could even try with pornstar names
edivad: yes
i know what you mean
edivad: this is where
i'm stuck now
edivad: well veneto is quite far from where
i live
edivad: since
i'm not yet capable to remember my 64 characters hex private key, there is a way to convert it in a seed without decreasing the security, and maybe being able to memorize it?
edivad: using deterministic shit,
I'm reducing the entropy of my keys, correct?
edivad: so basically, tell me if
I'm wrong
a111: Logged on 2016-02-04 01:12 asciilifeform: why the FUCK would
i edivad: and one thing that
i haven't learnt yet is how to generate a bip 44 compliant seed with dice
edivad:
i thought that dice was great for cheap and safe cold storage, if done it right
☟︎ edivad: so, back to the question, is the fuckgoats device meant to be, for instance, if
i run a bitcoin service that constantly need to generate private keys, let's say, for example, for an hot wallet?
edivad: basically,
i recently learned how to generate private keys with a D16 + paper and pencil, and
i thought that was a great way to have low cost true entropy
edivad: that maybe someone can answer later and
i will check on the logs
edivad: is now downloading again boost, meanwhile
i would like to ask some questions about the fuckgoats device
edivad:
i'm gonna leave the actual dir for future forensics analysis when
i'll be moar expert and now
i'm going to create another one
mod6:
i would blow everything away and start over following exact instructions in the howto
edivad: can
i keep the .wot folder?
edivad: so should
i delete everything and start from scratch?
shinohai: ^ That pthread issue
I solved on Debian by going to /usr/share/cmake and changing a line in CheckIncludeFiles.cmake
☟︎ edivad: but
i really cannot figure out what
i could try before running again the make command
edivad: since gcc is present
i think that is some kind of env problem
edivad:
i feel that
i'm very near of a succesful compiling of bitcoind, especially after the update of the guide
edivad:
i promise that this will be the last emergency troubleshooting about TRB
mod6: Ok,
I think it's better now.
mod6:
I think it was patch, but yeah, maybe
I'm mis-remembering that.
shinohai: Yeah
I forgot you had a guy with some sort of linux that didn't have diff
mod6: maybe
i aught to add 'diff' on that list. it is inexplicable to me that it wouldn't be there, but then again, lol.