446300+ entries in 0.269s
ascii_field: ;;later
tell mircea_popescu please consider posting your blkxxxx which encompass
the
two most recent forks
ascii_field: incidentally, for anyone who missed,
the public node is working and synced
ascii_field: punkman: keyserver is presumably for use as a keyserver, rather
than place
to hang
the severed heads of pwned folks ?
punkman: ascii_field: maybe better place for
that in new keyserver?
ascii_field: speaking of which, i've often
thought of adding an 'i know a private key!' box
to phuctor
assbot: Logged on 06-07-2015 21:11:18;
thestringpuller: ascii_field: did you get past
the wedge yet in 0.5.3.x? or do you still not have access
to a node?
gribble: Next Price Estimate: 219.968 | Next Price In About 3 days, 0 hours, 20 minutes, and 24 seconds | It's
tanking!
gribble: Bitfinex BTCUSD
ticker | Best bid: 274.96, Best ask: 274.99, Bid-ask spread: 0.03000, Last
trade: 274.98, 24 hour volume: 56638.18757788, 24 hour low: 267.33, 24 hour high: 278.69, 24 hour vwap: None
pete_dushenski: BingoBoingo seems
that
the "yanis gaming industry" link was added
twice in
the same (3rd) paragraph
punkman: pete_dushenski: "in which Greek citizens refused
to accept austerity measures" in case it wasn't clear,
the referendum question was "do you like
this deal? answer yes or no". and
the next deal won't be much different either.
thestringpuller: ascii_field: did you get past
the wedge yet in 0.5.3.x? or do you still not have access
to a node?
☟︎ punkman: I don't even want
to know how much
tax
the owner is paying on
that
ascii_field: who hasn't seen
the rivers (literally) of
toxic sludge
pete_dushenski: "Most of
those new lines of code come from “the new amd gpu register description header”, code
that
Torvalds says comprises “41 per cent of
the entire patch” and has created a “... somewhat odd situation where a single driver is about half of
the whole rc1 in number of lines.”"
ascii_field: seems like collectively chinese see bitcoin
the same way
they saw crimea
ascii_field: i suppose all
the 'proper confucians' with millenium-long
time cocks are employed as colonels in pla or whatnot
ascii_field: these folks'
time horizon is perhaps... 2 weeks long ?
assbot: Logged on 04-07-2015 22:28:31; mircea_popescu: anyway,
the main sufferance in my head atm is
that reading
the chinese stuff (in
translation) clarifies in my head an objection
that may well be a second major flaw
to
the protocol, after
the "relay nodes gotta do it for
the glory" : its altogether unclear a purely financial incentive is
the correct solution for miners.
ascii_field: 'you can make engineer's wages doing what you're doing. or you can do exactly same
thing, but use spv and give us root, and your swiss account will grow by 100k/mo.'
ascii_field: incidentally, does anyone else suspect
that cn miners, on account of
their microscopic profit margins, are ripe for usgization ?
decimation: I wonder if someone could make money by 'brokering'
txns on behalf of miners
ascii_field: trinque: because
then you can be attacked in various ways
trinque: is
this a worthwhile experiment?
trinque: so why can't my node's
time just be far-future?
jurov: even if multicore,
there's still i/o
ascii_field: to help
their collective iq move into
the double digits at least
jurov: estimated
time
to fully verify a block is 20 seconds
ascii_field: as (i
think it was) mircea_popescu pointed out, it looks like
the miners have not been sufficiently darwined yet
decimation: does SPV mining really give you
that much 'edge'? It seems dubious
to me
ascii_field: 'Note
that
the roughly 50% of
the network
that was SPV mining...' << can haz network without 50% hash power belonging
to diagnosable retarded folks plz ??!!
ascii_field: assuming
that nuclear war doesn't send us back
to cpu mining
ascii_field: the reward could still follow
the same asymptotic
ascii_field: why couldn't
the difficulty be set based on accumulated work ?
mircea_popescu: because bitcoin is secured by mining which happens irl and
the difficulty of mining is set on
the basis of irl entropy.
trinque: "disconnect if we connected
to ourself" << LOL
ascii_field: mircea_popescu: why so certain
that impossible ?
assbot: Logged on 06-07-2015 20:03:11; ascii_field: probably
the only Right
Thing (tm) solution is
to somehow cleanse bitcoin of its dependence on wall
time entirely
mircea_popescu: very useful,
this network
that
takes 5 hours
to confirm
txn
pete_dushenski: "Reports
that
the situation has passed are not correct. Please continue
to wait 30 more confirmations
than you usually would wait before accepting a
transaction."
pete_dushenski: "6 July 04:00: A new fork occurred starting 5 July at 21:30 with
three blocks before
the valid chain again became
the strongest chain."
mircea_popescu: just as long as we put
THE REAL
TIME as a
txn in every block, pogos can be fine
assbot: Logged on 06-07-2015 18:30:13; ben_vulpes: ;;later
tell pete_dushenski whaddaya know about
this glynn-ward character?
assbot: Logged on 06-07-2015 19:59:08;
trinque: some way of signaling current
time via invalid
transactions?
decimation: it's come up a couple of
times here, but not in
the context of
the 2h epoch
mircea_popescu: <mike_c> markets break over
the stupid leap second << no
they don't.
ascii_field: did nobody ever discuss
the
time
thing? i have
trouble believing
this
decimation puts 'celesial navigation' on
the library list
mircea_popescu: he
thought
that everyone will run one and so it'll be
too noisy
to follow
them.
decimation: rather
than
the blatent centralizing points
that
they actually are?
decimation: ascii_field: I wonder if satoshi
thought
that
these nodes would be anonymous?
trinque goes
to inspect
the function which does
this
ascii_field: but we already established
that miners are clinically retarded
decimation: who knew
that we needed a #b-a astronomer
decimation: in
the existing network, I suspect 99% of
the miners are using ntpd
traceable
to some usg organ
decimation: right, but
that requires a
trusted way
to ask a bitcoind "what's
the
timestamp of
the last verified block'
decimation: for whatever reason nobody has
thought
to scratch
that itch
decimation: essentially
there isn't such a
thing as p2p
time
mike_c: markets break over
the stupid leap second
decimation: ascii_field: but
that would come at
the cost of fucking *all clocks for all users*
trinque: vs if you are set
to yesterday and I give you a block from
tomorrow
mike_c: but if
they muck with ntp
they'll break
themselves
too
trinque: say I
though a block from last year at your node, I don't see why it would matter
that your clock is set
to
tomorrow
ascii_field: because right now, hitler has, essentially, a button
that makes just about
the whole btc network shit its pants
trinque: you can of course accept a block from
the past
decimation: if lizard hitler pwn's everyone's ntp servers, I
think we all have bigger problems
than block
time epoch in bitcoin
trinque: ascii_field: is it +/- 2hrs or is it no more
than 2hrs in
the future?
punkman: fried ice cream is a
thing
ascii_field: mike_c: all
the signs point
to us
trying
to solve
the utterly wrong problem.
mike_c: i was
trying
to
think of some way
to use
the block hash
to determine "who" you ask for
timestamps, but
the list of "who" is unknowable/proveable.. ends up in
the same place.