log☇︎
545700+ entries in 0.303s
assbot: Prúdové rozmrazovače | Traťové stroje ... ( http://bit.ly/1Dd0wwn )
punkman: I've seen nlocktime mentioned in various microtransaction derpage, needed to help fill those 20mb blocks
davout: why would they hang out in the mempool?
asciilifeform: chumpatronics aside, they also have the more pedestrian objective of creating GBs of turdsactions that bob about in mempool indefinitely, blowing up memory footprint in non-mitigable ways
ben_vulpes: i dislike them
asciilifeform: these two misfeatures are not accidental 'derperies' but have very specific, well-thought-out purpose.
pete_dushenski: asciilifeform that bashed quote is a clean cut, nicely done
assbot: blog.reddit -- what's new on reddit: reddit’s first transparency report ... ( http://bit.ly/1DcX4BP )
assbot: Logged on 28-01-2015 05:23:30; *: decimation would prefer to humbly submit to the silent dance of the celestial spheres, as man has done for all known time
trinque: jurov: heh, I think decimation did
jurov: mhm, did anyone already suggest time synchronization by actually tracking heavenly bodies by outdoor camera?
jurov: no need to invent the effects of dark matter on subatomic particles
jurov: in fact, since earth is noninertial frame, even atomic time depends on latitude
jurov: lol @ that time discussion
davout: and nlocktime only in the original way, not in gmaxwell's/todd's way
davout: multisig in two different ways
pete_dushenski: ^for those like me who didn't know
pete_dushenski: nLockTime is a parameter that can be attached to a transaction, that mandates a minimal time (specified in either unix time or block height), that before this time, the transaction cannot be accepted into a block.
mircea_popescu: mod6 where's this banner anyway ?
mircea_popescu: davout, fluffypony < i don't think bitcoin reference supports either nlocktime or multisig.
mircea_popescu: in case it's not clear, no anything authored by hearn may ever be merged into anything. i don't care what it is. the dog learns to shine shoes or do carpentry or whatever, but he does not work wioth computers anymore.
mircea_popescu: just take that idiot out and shoot him already.
mircea_popescu: "The BIP was authored by Mike Hearn who also provided the implementation for Bitcoin Core."
mircea_popescu: hings necessary to implement this functionality in a secure fashion are already in place, which Bitcoin Core should have done as well."
mircea_popescu: "btcd won’t be supporting the command because it is completely unauthenticated and insecure as pointed out numerous times on the initial pull request. In response to these concerns, a section entitled “Authentication” was added to the BIP which attempts to address the concerns by simply calling them out along with some potential modifications that could happen in the future. However, we prefer to wait until the t
cazalla: maybe the spanish kid 2 doors down as a kid was not spanish then, nfi, that is what he use to call his grandfather
trinque: mircea_popescu: open source is dead to me
mircea_popescu: the woodcollector guy spending weeks producing 10s of k's of words a day on the topic of nothing at all being the prototype for how that works.
kakobrekla: well good music is like a drug if thats what you meant
mircea_popescu: but if you let people off the street do system design you get systems designed by people off the street.
trinque: just expose the damn data; let the thing using the data decide what questions are interesting
trinque: this "oh hey we added getutxos" thing... no!
trinque: mircea_popescu: 'tis what caused it; not working on the sqlite thing atm tho
mircea_popescu: trinque: I'm starting to itch for a sqlite+deturdolatedbitcoind experiment <<< wha happened to deedbot ?
mircea_popescu: you fighting the malice mice /
ben_vulpes: it's malice! all malice, i tell you.
TheNewDeal: he's saying your on the weed
mircea_popescu: kakobrekla: anyway, back to ganja << FIFY
davout: ben_vulpes: bitcoind doesn't provide any way to retrieve a list of unspent outs for a key that's not in your wallet
mats: think of the poor souls that are red green colorblind
ben_vulpes: <davout> but it's not possible to get the list of unspent outs given an arbitrary private key << wat
davout: if you're not using the wallet you just know the first out you spend, and you know the next one from the raw tx you create, you still need 'gettxout' to not have to follow the balance around
mod6: think we should switch to the black & hacker-green motif?
davout: but it's not possible to get the list of unspent outs given an arbitrary private key
davout: trinque: if you import a private key into bitcoind you'll get the 'listunspent' call, don't know about btcd
ben_vulpes: yeah i've lost the btcd documentation
trinque: davout: we did not find a way to just "get all utxos" from btcd, could've overlooked something obvious. barring that, I can roll forward from the block where it was first funded and just chew on all the transactions from there forward looking for relevant ones
jurov: mod6 i like the banner. not sure we're all necessarily cryptoanarchists, tho
davout: trinque: so you keep the txid around, query your client for the txout and work from there? not very clear on what you mean
trinque: each time it's funded the starting point will advance, too
trinque: since the thing publishes once an hour, rolling forward doesn't seem that big a deal
davout: TheNewDeal: blockchain.info failed miserably at detecting them for a while, don't know if that's changed since, but afaik it's perfectly standard, and nodes will relay them
trinque: anyhow that's what I'll do for now
trinque: and then back to my rant re: holy shit this is a trivial query with well-structured data
trinque: yup, that's where the "roll forward from first funding transaction's block" comes from
davout: TheNewDeal: i don't think so
davout: hrm yeah, i forgot about keeping count of the balance, for that you should be able to use the gettxout call though
trinque: say I send a transaction, get one confirmation, then the thing still ended up on the losing fork
trinque: davout: I'm hesitant to keep my own count of btc when the correct value can be pulled from the node
davout: that way you keep one private key around, and you just need to track one txid that you reuse in the next tx
davout: when i have the addy to spend to for notarization, create a raw tx spending from that, and sending all the change back to the original address
trinque: has the same wad 'o json api
davout: i don't know shit about this one
trinque: using btcd at the moment
davout: trinque: do you intend to run a full client for deedbot's needs?
trinque: simple funding transactions, simple "publishing" transactions
trinque: so I can constrain the domain of things I care about
trinque: fluffypony: right, the subject being this bot, in this instance
davout: there's also multisig, that you can do with the dedicated script, or in the p2sh fashion
fluffypony: if you receive a transaction with an NLOCKTIME in the future is that part of your balance or the sender's balance?
trinque: and would that be a concern of something trying to ascertain a balance
trinque: davout: what kind of transaction does not involve a pubkey?
trinque: ben_vulpes tells me there's one that pulls it into postgresql too
davout: https://github.com/lian/bitcoin-ruby/blob/master/doc/STORAGE.rdoc <-- this would let you use a SQL backend
trinque: davout: right, but the balance would be "that which has been spent to me, and not subsequently spent elsewhere"
davout: some implementations will let you store the DB in a SQL store iirc
davout: not all transactions are a transaction to a pubkey
trinque: davout: what did I overlook? that was assuming everything that got stored in sql was validated by say an insert trigger
davout: trinque: "you'd just query the outputs table for your pubkey where none are referenced by an input's output_id field" <<< it's a bit more complicated than that
cazalla: trinque, yeah that is what i thought after that episode
trinque: I actually thought lorde was a made-up singer until recently
TheNewDeal: lorde was played by one of the main character's fathers, dressed in drag
cazalla: dunno, thestringpuller only know that one song of hers but then only because weird al did it first
gribble: You rated user danielpbarron on Tue Jan 20 11:03:44 2015, with a rating of 2, and supplied these additional notes: crypto-priest.
cazalla: miss me thestringpuller? ya lack of emails suggest not :\
danielpbarron: ;;later tell Blazedout419 wtf dude ^
assbot: Successfully updated the rating for Blazedout419 from -1 to -5 with note: maliciously stupid https://bitcointalk.org/index.php?topic=846683.msg9448130#msg9448130
cazalla: mircea_popescu: BingoBoingo fwiw, you're both prolly making too much of this. <<< not reary, i don't think anyone made a big deal of it, but i'm thankful BingoBoingo and danielpbarron were able to point out this guy's lies same day i left for holidays
mod6: we appreciate all the help that the attendants of #b-a have given to the foundation & the effort to decruft the R.I.
mod6: thanks for the help mike_c!
danielpbarron: is it seriously block # 144k? or is that approx?
mod6: well, for instance if you received the blocks out of order, and then you got the child of 144,000 a few after some others, then it can't continue
mike_c: if the chain split off where, at 144k?
mod6: not sure what the specifics were there.
mod6: well, if he removed the entire orphanMap, then it if the chain split off and became the new best chain, it can't move forward.
ben_vulpes: <mike_c> no, it stayed stuck at 144k where it was when i made the change << my experience is in line with asciilifeform's: once wedged, it never unwedges
ben_vulpes: i don't have a contract with those people, i'm not bound by any line of text they write.
mod6: i think all of 'em say that now
TheNewDeal: apparently a line of text at the top of a file
mod6: at the top of that file