log☇︎
132300+ entries in 0.084s
BigTexasBingo: Perhaps the foundation could use some prb/trb bridges on boxen running both after the acceleration experiments bring more fruit.
ben_vulpes: no party in the streets?
BigTexasBingo: The feria was more crowded than los domingos pasados, but most other places closed
ben_vulpes: mas tranquilo?
BigTexasBingo: Also, congratulations on the acceleration progress
BigTexasBingo: Did you know, Montevideo can be even more tranquilo
mircea_popescu: (for bonus lulz, 12795/30/24 = 17.770833333 or roughly speaking 10 to the bitcent.)
a111: Logged on 2017-12-22 17:22 weevlos: 2) thats only close to a month of operations budget
a111: Logged on 2017-12-18 17:46 ben_vulpes: dude this is epic, girl would rather talk about calendar offsets than earn a bitcent an hour reading the log
mircea_popescu: in other absolutely-not-news, I suppose the isomorphism http://btcbase.org/log/2017-12-18#1753616 <<-=->> http://btcbase.org/log/2017-12-22#1757015 is evident to everyone except the "self-determined" freewilled parties in question. ☝︎☝︎☟︎
jhvh1: asciilifeform: The operation succeeded.
asciilifeform: !~later tell phf plox post your puzzle-hash as comment in ch4 ☟︎
asciilifeform: single-threaded, locking gossip, is a sad thing tho.
asciilifeform: ( if i know of a nextblock, and i'm peering with mircea_popescu , and he doesn't, or vice-versa -- the boxes oughta share )
asciilifeform: it ought not to be possible under the game rules
asciilifeform: incidentally, this is a pretty sad situation, if even 1 of us has a node at block B, but everybody else somehow floundering at B-k, for some positive k
mircea_popescu: i never ran this many computors in my lyf!
mircea_popescu: it's quite expensive, all this crap.
asciilifeform: where's the tip of the spear ?
asciilifeform: funnily enuff, the absolute all-time champ at never-lagging in asciilifeform's house of horrors is... an ancient (circa 2013..?) prb !! e.g. currently at 500849
mircea_popescu: ben_vulpes ftr that's ~10 hours ago, not 2.
ben_vulpes: lol that's right it comes out of SetBestChain
asciilifeform: 'os' without redirectable output , belongs in the oven.
trinque: what we have now is some snowflake saying "no but this is what printf means to me"
asciilifeform: yea i can't think of any reason whynot.
asciilifeform: it must remain useful when printing to stdio
asciilifeform: i can't speak for others, but asciilifeform often ( almost always, in fact ) runs trb during tests, in pure userland, making use of 0 systemwide loggings )
asciilifeform: trinque: i suspect that we already had this thread
trinque: I dunno a linux on earth that can't log the direct output of a service
trinque: be nice if the person fixing logging takes out the idiot printf macro
asciilifeform: i'd like to get a sense for where blocks come from.
asciilifeform: what i'd like to see is 'was it from a trb?'
asciilifeform: that already printed ( the latter , in classical trb, mutilated )
asciilifeform: ( also in the log )
asciilifeform: right up there with 'from-where-i-got-ACCEPTED-block'
ben_vulpes: i have another kiestered that i may as well unload at the same time, hash untrunculation
ben_vulpes: asciilifeform: the same thought occurred to me
asciilifeform: i'ma thinking already about next level of possible 'aggression' : namely to pushgetblocks() at ALL running peers, if >20min pass, say, without a new block received
trinque: a complicating factor of me testing the version string is that while ahead, I may be feeding other TRBs, while not, not.
ben_vulpes: node was booted with that yes
trinque: ben_vulpes: do you by chance have an active connection to 172.86.178.46 ? or did in past ?
ben_vulpes: this one block took me from 813 to 814
ben_vulpes: asciilifeform: one thing i do with logbot is to use postgres as a queue so that a background worker can do all of the thinking and crashing without thrashing the irc connection
asciilifeform: it isn't even impossible that there's only been 1 block in past 2hrs, say
ben_vulpes: anyways i must have an extra-thick layer of prb, as my node has found precisely one block in the past three hours
a111: Logged on 2017-12-24 16:46 asciilifeform: !~later tell trinque what do you recommend for a talking-in-chan bot-tron ? i'd like to hook up 'ffacalc'...
ben_vulpes: sorry, asciilifeform. i was focused on the logbot part, forgot about the ircbot and to update documentation.
asciilifeform: anyway , worx, now all i need is to think of how to properly cut the output so as not to straddle message breaks...
asciilifeform: only then, had to unsheath eyes.
asciilifeform: no eyes involved, i pressed and used trinque's original usage.txt and got barf
asciilifeform rewound to trinque's original, which in fact worx.
asciilifeform: you changed 'channel' slot in ircbot class to 'channels', but never bothered to change the corresponding line in make-ircbot !! ben_vulpes ) ☟︎
asciilifeform: ( how the fuck did it ever work , ben_vulpes ?? )
asciilifeform: oooh i think i see why. ben_vulpes's 'multiple-channels' patch mutilated it
jhvh1: asciilifeform: The operation succeeded.
asciilifeform: !~later tell trinque http://wotpaste.cascadianhacker.com/pastes/nxnWA/?raw=true << or for that matter anybody else using trinque-bot -- any idea what gives ? i followed the example in the readme...
asciilifeform: 'blockchain'ism is simply a very expensive means of approximating a solution to this problem.
a111: Logged on 2017-03-02 16:31 asciilifeform: it is worth recalling the gedankenexperiment where it turns out that all you'd need to build 'martian bank' on earth, is if martians merely supplied an infallible 'martian clock', a service whereby they take a string S , at regular, say, daily, interval, and return its hash H
asciilifeform: there is not, nor could there be, a fixed-star for existence proofs. even classical blockchain has the obvious limitations ( discussed numerously, see l0gz )
asciilifeform: how could it prove to anyone else.
mircea_popescu: or that weird geek from early pedo-pedia days, what's his name
asciilifeform: it proves only to him, naturally
mircea_popescu: asciilifeform what's that prove tho ? winklevoss tards periodically go into their basement/den where they "have" "their own" copy of fb.
mircea_popescu: an evident issue would be of course that if ownership is implemented as-to-specified-coin as seen in bitcoin, then E has a ready avenue -- "all txn including spends from my own addresses are mine". this is a somewhat weakening of the premise, but perhaps sufficient.
asciilifeform: 1 way, would be by going to his own cellar and fetching optical disk where he has ~his~ mpi
mircea_popescu: "especially because it agrees with logotron time oracles". sure...
mircea_popescu: "phf's time oracle". sure.
mircea_popescu: but in point of fact the hook to hang by is there : at the present time how would someone who is hostile (ie, does not trust what we say) discern who originated mpi ?
mircea_popescu: maybe that works.
asciilifeform: nah, there's a time parameter
mircea_popescu: much like "you can't repudiate signatures -- can't see whole space" discussion in that thread.
asciilifeform: consider, what do you do in your wot housekeeping ~today~ to people who habitually sign P ~and~ ~P
mircea_popescu: see, the SELECTION of .sigs you see is not promised to cover the whole space!
mircea_popescu: that they approve.
mircea_popescu: at t1, E perceives P', signed by l1...lk ; which is not an isomorphism of l1...lm, and might wel lnot even include E
mircea_popescu: at t0, E produces P and signs it. E shares P signed by E with l1...lm.
mircea_popescu: take it like this :
mircea_popescu: how would E know this ?
asciilifeform: dun tell me we gotta have the ring signatures thread again
mircea_popescu: at this point, how would E discern which party of l1..ln originated P ?
mircea_popescu: let observer E know l1...li of this wot. let observer E observe a P signed by a subset l1...lm of his wot.
mircea_popescu: asciilifeform let's model this. let "patch" be a bitfield ; let wot be comprised of l1...ln.
asciilifeform: maybe i'm thick, but i dun see the algo 'between the lines' here
mircea_popescu: ie, it's leveraged to fuck over the miner collusion properties of current pow.
mircea_popescu: this is a sort of gossipd-meets-the original "can't have signature repudiation" problem you encountered in comments there, but REVERSED.
asciilifeform: if mircea_popescu has thought of a meaning for it that doesn't 'a participating entity can recognize work done by itself as opposed to work done by others' -- i'm all ears
mircea_popescu: nobody can know WHO truly authored a patch. just what set of the signatories signed it that they're willing to share with him
mircea_popescu: consider the fundamental value of regrinding!
mircea_popescu: asciilifeform mining doesn't have to mean that.
mircea_popescu: (in fact it is perhaps obvious that was designed with a view to THIS, rather than "extant battlefield")
a111: Logged on 2017-12-02 16:22 mircea_popescu: anwyay, revisiting an ancient conversation re http://btcbase.org/log-search?q=mining+is+a+bug : i have to thoroughly concede this point to asciilifeform . the model is as follows : if a) a PoW system exists in which b) a participating entity can recognize work done by itself as opposed to work done by others then it NECESSARILY follow that entity can, and therefore it ALSO follows that it eventually will c) impose further con
asciilifeform: could, but then you get http://btcbase.org/log/2017-12-02#1745524 . ☝︎
mircea_popescu: scheme as described ftr works eminently well with http://trilema.com/2016/the-necessary-prerequisite-for-any-change-to-the-bitcoin-protocol/ in that "proof of knowing the txset" becomes meaningful past what's going on now
asciilifeform: ( asciilifeform's answer is 'first you pillage , ~then~ you burn, fughetabout it for the time being, have an algo for the basic mechanics that makes sense, first ! )
mircea_popescu: anyway, evidently the first [...] stands for what's currently termed "mining" while the second for actual spending.
mircea_popescu: (way way WAY worse than original optimistic estimates of "21mn divisible to 1e8". but what can you do.)
mircea_popescu: nobody asks this ; but anyway, if bitcoin prototyping is any guide, 1kb per entry should suffice ; in which case current computing could in principle actually support a coinset between 1mn and 1bn coins.
asciilifeform: ( for some reason everybody always asks 'how'll you pass out the coins', but this is orthogonal problem! )
asciilifeform: this is exactly the picture asciilifeform drew last yr, aha.
mircea_popescu: "new bitcoin has 1mn coins ; which can not be split ; to move a coin from nill address to your address you must [...] ; to move a coin from x address to y address you must [...]".