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.
BigTexasBingo: The feria was more crowded
than los domingos pasados, but most other places closed
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
jhvh1: asciilifeform:
The operation succeeded.
ben_vulpes: lol
that's right it comes out of SetBestChain
trinque: what we have now is some snowflake saying "no but
this is what printf means
to me"
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
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
trinque: a complicating factor of me
testing
the version string is
that while ahead, I may be feeding other
TRBs, while not, not.
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
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.
jhvh1: asciilifeform:
The operation succeeded.
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
mircea_popescu: or
that weird geek from early pedo-pedia days, what's his name
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.
mircea_popescu: "especially because it agrees with logotron
time oracles". 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: much like "you can't repudiate signatures -- can't see whole space" discussion in
that
thread.
mircea_popescu: see,
the SELECTION of .sigs you see is not promised
to cover
the whole space!
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: 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.
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.
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: (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
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.
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 [...]".