448100+ entries in 0.296s
assbot: Logged on 21-01-2015 02:48:11; Luke-Jr: it can't, if you don't have
the 0.8.1 hardfork patched in..
ben_vulpes is amused, but not honored. if ye'd only had actual management once upon a
time,
this'd not be a notable achievement.
ben_vulpes: looks like
the shitgnomes have been working overtime
to address my complaints.
ben_vulpes was looking
through recent "bitcoin-core" pull requests, found many integration
testing scripts
ben_vulpes: an informal signoff from y'bosses would be nice before i deposit
this in
the white porcelain
turdotron
decimation: asciilifeform: I can already hear jwz saying
that he doesn't want politics, just
to do
the right
thing
decimation: although as I've noted,
they already incremented
this machine
decimation: 'please sir, accept my resonable patch in exchange for agreeing
to forever accept what 'our mechanism' brings'
mod6 doublechecks
the SoBAs
ben_vulpes: what was
the version number of openssl we determined necessary
to validate
the full chain?
ben_vulpes: well
this signature issue is
tricky as shit already - openssl is already blowing up validating
the chain with anything other
than...
decimation: yeah, it's not
the bip66 issue, it's
the mechanism
they inserted for forcing change
decimation: but
the way it's being forced is pretty stupid
decimation: I would say
that on its face, bip66 isn't such a
terrible idea
☟︎ ben_vulpes: perhaps a hash of
the codebase instead of
the semver crap?
decimation: better
to say less until we know wtf is going on
ben_vulpes: mircea_popescu, mod6, asciilifeform: i don't see a reason
to make
this much more
than 25 words. do you
think much detail or polemic is necessary here?
ben_vulpes: this is almost as bad as defining a word with
the word
to be defined
ben_vulpes: "the chain
that is
the real chain is
the chain
that verifies under 0.5.3"
trinque: would
the logs be interesting in any way?
trinque: I am, how is it handling what
though
ben_vulpes: i
thought you were running a conformal impl somewhere
trinque: got
to like 150k I
think before I stopped
trinque: was syncing pretty quick, but I stopped and deleted for
to be syncing against mircea_popescu's node
trinque: just deleted muh blockchain
to resync
mod6: the hope was
to find if he can verify if v0.5.3.1 rejected or accepted
the blocks in question; 363738
mircea_popescu: anyway, having been duly amused for
the evening, i retire
to my eulorean empire.
mircea_popescu: i don't
think any sane nodes can be up
to date atm, until
this resolves.
mod6: shinohai: is your v0.5.3.1-RELEASE node up
to dayte?
☟︎ mircea_popescu: but
the "we'll make wallet a plaintext file" and
the "we'll
target windows" and
the "you know what's better
than boost ? qt!" were pretty epic
turn points
too
ben_vulpes: meaning adopt
the power ranger braindamage again?
mircea_popescu: nah,
the "we'll move
to
this new db system one schmuck
that gofer'd coffee at google wrote with his chest hairs and nobody
tested in any way" was
the stupidest sahit
decimation: if
there's any reason why bitcoin will never be adopted, it's
this kind of shit
decimation: this is
the dumbest fucking
thing I've seen in all my years with bitcoin
mircea_popescu: "Current status: F2Pool still broken; Antpool fixed (but no promise
they won't intentionally re-break in
the future)." is really all
that one needs
to lol
mircea_popescu: Uh oh all
these block explorers just flipped over
to
the invalid chain:
☟︎ ben_vulpes: i want a man in
the ground, i don't make
that dependent on his wife squirting or w/e
ben_vulpes: man all i can do is nail
this coffin closed
mircea_popescu: on
the record having lied for profit and all
that good stuff, but why should anything matter.
ben_vulpes: ;;later
tell lukejr listen you gotta stop it wiht
this "i can
tell miners what's right and wrong" bs
ben_vulpes: "Most likely
this is caused by broken-by-design-for-profit mining code, but none of
their stuff is open source AFAIK. Maybe more details will be known with
time."
ben_vulpes: reddit, for all
the silencing and muting of
the actual bitcoin foundation, seems
to be
turning
the corner on sense
ben_vulpes: "They're not running full nodes because
the current 500KB blocks are
too big.
mircea_popescu: anyway,
this is jit
to lay kakobrekla's wonderments
to rest.
ben_vulpes: "Updating
to
the latest when what you have works is how you break
things.
ben_vulpes: i never did anything, we all know
that. joke's almost
too easy.
ben_vulpes is also curious
to see how much "political capital"
the derpdation burns
today
mircea_popescu: i dun see it.
the rule is "come
to school dressed". if you all agree
to wear skirts or all agree
to wear cardigans, it's still school.
ben_vulpes: mircea_popescu: anyone can narrow
the rules, but whether
that's "bitcoin" is an open question.
decimation: I'm not sure if
there are enough blocks
to
trigger it
decimation: because
they already did a 'softfork' on
the nVersion
mircea_popescu: decimation provided
their "mine support" actually materializes
decimation: the problem is
that 0.5.3 blocks generated by 0.5.3 won't validate if
those IfSuperMajority rules check
mod6: <+ben_vulpes> Bitcoin 0.5.3 is
the canonical reference implementation. If a fork occurs and one side validates on
the 0.5.3 codebase while
the other does not,
the chain
that validates under 0.5.3 is
the only valid chain. << I have nothing further
to add
to
this at
this
time.
mircea_popescu: the idea is
they don't want
to see some stuff
that validates anymore
decimation: actually I
think
this is gonna be fine on 0.5
mircea_popescu: well, any people can at any
time decide
to narrow
the rules.
this makes some sense.
ben_vulpes: things either validate under 0.5.whatever or
they don't.
ben_vulpes: i've not yet accepted
this soft/hardfork duality.
mircea_popescu: i have nfi how
the power rangers imagine
they'll manage a hardfork when
they can't as much as get a "relevant support" softwork
that's fairly uncontroversial.
ben_vulpes: i have a porch of meatwot and babes
that actually need attending
to.
ben_vulpes: mod6 if you feel compelled
to elaborate on
this, go ahead.
mircea_popescu: anyway,
todd is right.
the only way
this affects us is
that we don't really give much of a shit.
mircea_popescu: Bitcoin Core (after 0.10.0) rejects
these invalid blocks, but a lot of other stuff doesn't. SPV Bitcoinj wallets do no validation what-so-ever, blindly following
the longest chain. blockchain.info doesn't appear
to do validation as well; who knows what else? <<
ben_vulpes: Bitcoin 0.5.3 is
the canonical reference implementation. If a fork occurs and one side validates on
the 0.5.3 codebase while
the other does not,
the chain
that validates under 0.5.3 is
the only valid chain.
mircea_popescu: BIP66 protocol rule changes have gone active in part
thanks
to Antpool and F2Pool's support of it - but
their pool appears
to not actually be enforcing
the new rules, and is now mining invalid blocks << lulzy.