356700+ entries in 0.194s
massiro: mircea_popescu, sorry, i'm not familiar with
trb nodes.
mircea_popescu: ironically,
this is known of exponentials,
they're "too low" in
the early middle and
too high in
the end. but
then again, it is known by people who know shit, such as how
to design games
that people enjoy playing, not by people who don't know jack, such as microsoft-excel based cryptographer-hermits.
assbot: Logged on 09-01-2016 05:46:31; ben_vulpes: solution imho is
to make not mining
these
transactions economically suicidal
mircea_popescu: you're not supposed
to use "txids" for anything, but whatever. as discussed yest,
this goes up all
the way.
thestringpuller: cause if
tx is malleable and
txid changes, you'll see it change in real
time
mircea_popescu: yeah, until karpeles lied about an imaginary cause of stealing people's bitcoin,
the other dudes working on wrecking bitcoin didn't have a good excuse. hurr durr.
thestringpuller: I don't recall
this being a problem
till Mt.Gox and Coinkite complianed.
mircea_popescu: i've been broadcasting it all night
to
the
trb nodes, you can ask any of
them,
they should still have it in
the memory.
mircea_popescu: that's what we're currently
trying
to debug. why
the e6b8 one, which spends a single input from
the 83e2 one, is not making it
through.
assbot: Logged on 09-01-2016 02:17:52; mircea_popescu: e6b8aa9dedef74a7e8961e0d997aebc35aae3c8e762a715336d84b39507c9773 is chained off 83e2b80e96919cb0b0186ff8ba7225d25535ad722ec5e2343a3a5927ef85d735 and you do see
that.
massiro: "there's a
transaction
that has 100 confirms" << what is
the
txid?
this? : 09e82c06cc5fbe3c0f2c2b6a1f575e8ecbb2a92bb493ca3a318525b1eeabe2bd
mircea_popescu: fucking stop and
think about sometime before you agree with usg's moles about ever novel ways
to fuck up
the one
thing
that
threatens
their continuous existence.
mircea_popescu: hey everyone : do you realise NEXT
time you all "consensus" idly over some stupidity, it may mean MORE
than 600 btc delayed for MORE
than a week because of your agreement
to "changes" ?
mircea_popescu: thestringpuller
that was kakobrekla's
theory as
to what
the problem was previously. however currently,
there's a
transaction
that has 100 confirms, and it's being spent, and it still doesn't get
through. so no,
that couldn't be it.
thestringpuller: i wonder if
that caused
the wallet issue? spend
tx, confirmed under different hash, wallet is now borked?
massiro: consensus is unchanged but
the latest nodes never relay/mine high-S
tx.
thestringpuller: wait, if a high-S value
transaction is written
to block does
that affect future
tx's?
assbot: Logged on 09-01-2016 05:10:42; massiro: latest nodes never accept high-S value
transactions and never relays it.
thestringpuller: is
there a way
to coredump bitcoind without having
to recompile with GDB symbols? I've recompiled it, but it's giving me "illegal instruction" error
then closes out. No crash log.
gabriel_laddel: That said, I've not really poked around
the call stack. Could be missing something obvious.
gabriel_laddel: Unfortunately I may need
to poke around "under
the hood".
There are
two showstopping bugs in CLIM
that crash
the connection
to
the X server, and it is unclear why.
phf: gabriel_laddel: perhaps if you stated your problem! xlib is a handful of operations on
top of blit, where zen emulates
those same operations using opengl. exact details of x
talking
to hardware is completely outside of scope of xlib, since
the whole point is abstract
those away.
gabriel_laddel: sciencemadness.org is really cool btw,
thanks for
the link.
gabriel_laddel: phf: I've browsed
through it, but didn't find what I was looking for. Perhaps if I state my problem someone will know what I need.
The goal is
to 'fold'
the whole notion of X client / server directly into CL function calls. I would like details of how *exactly* X
talks
to
the hardware (Cee sources, yeah) and a large, obvious
table as
to what all
the error codes / X requests are.
☟︎ gabriel_laddel: Has anyone played around with Zen,
the CL X server, or does anyone have links
to OLD X documentation / proggies
that would be useful for debugging issues deep(?) in
the X server / help me understand wtf
the X protocol is? I googled around for X docs and found a mess.
trinque: I am pleased with
the fact
that I ran an installer, and now I have a unix
that actually does everything of which it claims
to be capable.
trinque: have yet
to run into any such
punkman: my
tv runs on freebsd, but can't do anything
there
trinque: gabriel_laddel │ I've
tried, a few
times now
to get a handle on linux and... << leave gentoo for dead; I couldn't be more pleased with OpenBSD.
punkman: and if "prevout" is e6b8aa9ded why
the hell does "if (!mapTransactions.count(prevout.hash))" fail??? you just received
the
thing
punkman: how does something called "prevout" refer
to e6b8aa9ded and
the bare GetHash()
to 20421a3f19?
punkman: where
the fuck does "vin" come from for example
punkman: and good god, all
this implicitness is code is enough
to drive a man crazy
☟︎ punkman: asciilifeform: ERROR: ConnectInputs() : 20421a3f19 mapTransactions prev not found e6b8aa9ded << I only have half a clue what's going on when I look at
the code, but perhaps e6b8aa9ded is not actually chained off 83e2b80e96? I can't find 20421a3f19 on any block explorer, maybe it's another
transaction only existing in mp's wallet.
gabriel_laddel: Oh, and ben do you have any good reading material re rockets? I'm in
the mood for something new.
☟︎ gabriel_laddel: I've
tried, a few
times now
to get a handle on linux and...
ben_vulpes: it's possible
that lispy power-magnifying
tentacles are
the best way
to wrap hands around big ugly workpiles like linux
ben_vulpes: i am very much looking forward
to experimenting with
this
massiro: and I
think I'm conservative side such as a block size.
massiro: I have known
the politics at some extent...
danielpbarron: blissfully unware of
the politics of bitcoin until it gets in
the way of a payout?
☟︎ massiro: If we don't want
to use
the latest client, we could do "createrawtransaction" and "signrawtransaction", check whether is has high-S or not by our eyes, and do "sendrawtransaction"
to
the network.
massiro: <danielpbarron>, i know it a little...
that may create high-S.
ben_vulpes: solution imho is
to make not mining
these
transactions economically suicidal
☟︎ massiro: So
the solution is
to use
the latest client.
massiro: in fact ebc5d768... was a "high-S"
tx and
the-eth-scam payout used ebc5d768 as input.
massiro: i cannot see
the content of e6b8aa9d... but it may have a high-S value.
massiro: and somebody will modify high-S
to low-S. and
the wallet will be corrupted.
massiro: If we make high-S
txes, it never be relayed/mined by latest nodes.
massiro: S should be less
than 0x7FFFFFFF...
to be relayed by
the network now.
massiro: in
the past,
the-eth-scam payout with
txid ebc5d768... was using high-S, and modified/accepted
txid 09e82c06... was with low-S.
massiro: low-S is in
the signature <R,S>
massiro: i'm suspecting <mircea_popescu> is using an old client and
the old client makes
txes with high-S values.
massiro: latest nodes never accept high-S value
transactions and never relays it.
☟︎ massiro: this reminds me of sending
tx with a high-S value.
massiro: <mircea_popescu> said "isolated from
the network".
assbot: Logged on 09-01-2016 03:08:08; mircea_popescu: so basically, my node sent
to
trb nodes,
trb nodes have it in memory but it's not being broadcast past
them.
assbot: Logged on 09-01-2016 02:17:52; mircea_popescu: e6b8aa9dedef74a7e8961e0d997aebc35aae3c8e762a715336d84b39507c9773 is chained off 83e2b80e96919cb0b0186ff8ba7225d25535ad722ec5e2343a3a5927ef85d735 and you do see
that.
mircea_popescu: ima keep
the present situation up, where
they have monopoly on a juicy
tx for a little longer in case anyone wants
to
trace
the network/debug/whatever. but i can't keep it forever like
this.
mircea_popescu: i would say
this is proof positive
that
they are in fact isolated on
the network, somehow.
mircea_popescu: so basically, my node sent
to
trb nodes,
trb nodes have it in memory but it's not being broadcast past
them.
☟︎ mod6: was 83e2b80e96919cb0b0186ff8ba7225d25535ad722ec5e2343a3a5927ef85d735 sent by
trb?
mircea_popescu: asciilifeform never you mind
the complaint of 20421a3f19.
the point is, e6b8aa9ded itself.
mircea_popescu: this
time,
the antecedent
transaction is clearly in
the chain