Results 31001 ... 31250 for 'f:ben

ben_vulpes: anyways, how does this work in practice: 2 mining pools release a block (B, C), building off the prev (A) - do miners arbitrarily choose which child block to continue building on?

ben_vulpes: i'm rarin to go harin' after herrin herring

ben_vulpes: YOU KNOW IT

ben_vulpes: aw i fucked the genders there didn't i

ben_vulpes: that's how the staff'll address my she-spawn

ben_vulpes: herr heiress!

ben_vulpes: just stay clear of her heirs

ben_vulpes: a plural of one?

ben_vulpes: no females in that set

ben_vulpes: i ain't eating programmers

ben_vulpes: oh god not programmers

ben_vulpes: gets me every time

ben_vulpes: 100% canadian lol

ben_vulpes: pete_dushenski: https://www.cavirtex.com/home << but but that's the old site!

ben_vulpes: "dick surgery"?

ben_vulpes: i thought he was going under the knife to get rid of the spear

ben_vulpes: only counts if it comes with wings

ben_vulpes: no crusading valkyrie

ben_vulpes: they're already cut loose. can't get into b-a

ben_vulpes: srsly, woodchopper?

ben_vulpes: can we stop caring about scams yet?

ben_vulpes: lol will wonders never cease

ben_vulpes: was i right for once?

ben_vulpes: wait, cavirtex is virtex?

ben_vulpes: mod6: my contacts are gumming up too :)

ben_vulpes: ah it's the whole gang

ben_vulpes: nm

ben_vulpes: oh is there a CaVirtEx and VirtEx?

ben_vulpes: heh. "one".

ben_vulpes: the one who did a runner with a Havelock "raise"

ben_vulpes: CaVirtEx

ben_vulpes: David Joseph?

ben_vulpes: how was the strip club, hanbot?

ben_vulpes: ah, he's a Joseph David stoolie

ben_vulpes: https://www.linkedin.com/in/mitchellcallahan << mod6 i found this one

ben_vulpes: perhaps a lonely registered participant?

ben_vulpes: 'tis all i got

ben_vulpes shrugs

ben_vulpes: mircea_popescu: http://www.saucal.com/

ben_vulpes: thestringpuller: you flappin

ben_vulpes: i discovered recently that "baby" carrots aren't so much "lathed" as they are knocked around in a conical abrasive vessel

ben_vulpes: my eyes :(

ben_vulpes is but a humble student of the trade

ben_vulpes: secondary to?

ben_vulpes: if you'll forgive the glib response, figure out what can be riven from the satoshi codebase

ben_vulpes: spec a node, i guess.

ben_vulpes: then this implies a requirement that a bitcoind-node know about and be able to return data about the various chains of which it knows.

ben_vulpes: "antipattern" << lol

ben_vulpes: "there is only one chain" as well.

ben_vulpes: i see it.

ben_vulpes: ofc. central concern, this.

ben_vulpes: hm.

ben_vulpes: because of multiple chains?

ben_vulpes: (or N-1, or N-M)

ben_vulpes: mircea_popescu: if i know that the most recent block was of height N, I can ask bitcoind-node for the hash of the block at height N

ben_vulpes: idiomatic cpp aside, thoughts on the list?

ben_vulpes: f'r instance, the thing should cough up on the command line, a block if given a hash

ben_vulpes: but there are subspaces, if you'll allow the floppiness of wording.

ben_vulpes: true enough

ben_vulpes: (fin)

ben_vulpes: - relay transactions to the network

ben_vulpes: - return a block corresponding to a given hash

ben_vulpes: - return the height of the current best-known chain

ben_vulpes: - translate block height to block hash

ben_vulpes: translate block height to block hash

ben_vulpes: - download and validate blocks

ben_vulpes: here's a proposed list

ben_vulpes: on a previous topic, eg bitcoinating

ben_vulpes: mthreat this is almost worse than useless

ben_vulpes: !s bitcoinate

ben_vulpes: re dogillionaires, that was fluffypony

ben_vulpes: asciilifeform: i refer of course to the quoted price of attendance.

ben_vulpes: for the record, attendance declarations are only binding on those who wish to attend, not his unimpeachable lordship mircea_popescu

ben_vulpes: hatchu.

ben_vulpes: worst story.

ben_vulpes: too bad i'm too bad of a scammer to pull it off

ben_vulpes: almost*

ben_vulpes: almos

ben_vulpes: amusingly, i was confirmed without paying.

ben_vulpes: assuming they're any good of course

ben_vulpes: arbitrated by...humans.

ben_vulpes: buttonwood_: ^^ that bet right there is a good example of best-in-class contracts.

ben_vulpes: anyways, buttonwood_ are you still interested in working this thread?

ben_vulpes: https://twitter.com/_youhadonejob/status/559174647309021187 << this town

ben_vulpes: anyways, there was one. are you aware of why it shut down?

ben_vulpes: !up buttonwood_

ben_vulpes: that'd be the one, yeah.

ben_vulpes: there was an options exchange for a while, buttonwood_.

ben_vulpes is an incompetent hacker

ben_vulpes: boo

ben_vulpes: ;;echo /msg ben_vulpes hello

ben_vulpes: ;;echo /msg assbot amazing

ben_vulpes: you're clearly in a good position to be talking about how business should be done around here.

ben_vulpes: ;;gettrust buttonwood_

ben_vulpes: !gettrust assbot buttonwood_

ben_vulpes: trust is built over time, and can't be abstracted out.

ben_vulpes: buttonwood_: you can't trust people that you don't trust. end of story.

ben_vulpes: <mats> use the ratings and talk to the raters << this. again and again, this.

ben_vulpes: and all of this because i asked about what should bear responsibility for creating and signing transactions.

ben_vulpes: much like if you want a > 1m transaction that's your problem

ben_vulpes: if i want to spend my low-priority outputs, that's my problem.

ben_vulpes: perhaps i don't understand what all gets signed. more than likely.

ben_vulpes: how is my signature even valid in that scenario?

ben_vulpes: but you're saying that if i cook up a transaction that has 1march29th as an input, the miners should actually rewrite that to use 1march15th as an input?

ben_vulpes: what miners do is...unknowable?

ben_vulpes: i'm talking about the reference implementation.

ben_vulpes: !up buttonwood_

ben_vulpes: so they actually troll through the whole blockchain

ben_vulpes: how are miners doing it?

ben_vulpes: s/do/should

ben_vulpes: do bitcoind-node and bitcoind-wallet share a db?

ben_vulpes: new topic!

ben_vulpes: great

ben_vulpes: got it

ben_vulpes: ah ah but check that a transaction is in a block

ben_vulpes: s/./?

ben_vulpes: all that must be done is check that a tx input comes from a previous block.

ben_vulpes: the bitcoind *node* doesn't give a whit about transaction creation

ben_vulpes: you're proposing a new "wallet" that knows how to create transactions.

ben_vulpes: i guess a step backwards is in order first

ben_vulpes: if i'm reading correctly, you propose moving transaction creation *out* of bitcoind.

ben_vulpes: which is the transaction creation process.

ben_vulpes: if i can interrupt, i'm coming at this problem from an entirely different angle.

ben_vulpes: jurov: a transaction in a block contains the public key iirc

ben_vulpes: i guess this implies maintaining an index of txn hashes -> block hashes for lookup and validity checking

ben_vulpes: from *its* blockchain (database).

ben_vulpes: so then the thing *does* need to retrieve arbitrary transactions.

ben_vulpes: to verify a new transaction, one needs the previous transaction in hand, in entirety.

ben_vulpes: like i'm 5, please.

ben_vulpes: do you want me to say "not at all"?

ben_vulpes: <mircea_popescu> txn are verifiable aren't they. << not really. transaction only includes txid of previous transaction which itself has the pubkey required for validation.

ben_vulpes: bitcoind-wallet should generate and sign transactions.

ben_vulpes: bitcoind should not maintain a wallet

ben_vulpes: another claim, for your consideration

ben_vulpes: <kakobrekla> ... something wrong << what is best practice? feedback from industry leaders would be useful here.

ben_vulpes: b) bitcoind *should* be able to return transactions with unspent outputs

ben_vulpes: a) bitcoind should not return arbitrary transactions by id

ben_vulpes: so i made two claims, let's treat them seperately

ben_vulpes: okay okay

ben_vulpes: mircea_popescu: how long does a "rescan" take these days?

ben_vulpes: and why?

ben_vulpes: with the utxo list in hand, a node could create a raw transaction for signing by an offline node.

ben_vulpes: i think that maintaining the utxo list is a good idea.

ben_vulpes: correct me if i'm wrong, but address balance is the sum of unspent transactions to that public key.

ben_vulpes: it's a much more tractable problem to find transactions relevant to a given address out of that list than it is to walk the blockchain for same.

ben_vulpes: if the node were to maintain the list of unspent transaction outputs, it would also have a list of the TXID's with unspent outputs.

ben_vulpes: -> LOTSAH3X

ben_vulpes: ./bitcoind getrawtransaction TXID

ben_vulpes: are you agreeing or what?

ben_vulpes frowns

ben_vulpes: not the best english, but what american knows how to write well anyways?

ben_vulpes: dunno

ben_vulpes: derpy guy?

ben_vulpes: http://globalguerrillas.typepad.com/globalguerrillas/2015/01/the-wahhabi-wet-dream.html << related

ben_vulpes: kakobrekla gets it

ben_vulpes: when i made furniture, we went out of our way to put cunts into the woodworking.

ben_vulpes: "a single machine acting as a full node" << conformal has yet to answer any questions re: what the specs of this "machine" were.

ben_vulpes: anything in particular about that, mats?

ben_vulpes: another netsplit?

ben_vulpes: my reasoning being that iterating through the blocks is adequate to get complex information out of the thing, and that producing unspent outputs is adequate for "bitcoinating" - eg, producing and signing transactions.

ben_vulpes: any *unspent output*, yes.

ben_vulpes: any *block*, yes.

ben_vulpes: asciilifeform: i don't know that the thing needs to cough up *any* transaction on demand.

ben_vulpes: unqualified 'till i die

ben_vulpes: a pauper is i

ben_vulpes: oh as if its even a question at this point

ben_vulpes: have some tits: https://www.youtube.com/watch?v=d2RZXeQc5HU

ben_vulpes: salud, pete_dushenski

ben_vulpes: man seconds really crawl by when one's fucking with cron scripts

ben_vulpes: davout: yeah let me tell you about the manual checks in the billing process to catch rounding errors

ben_vulpes: we were like 14? 15? derping around on livejournal.

ben_vulpes: yeah!

ben_vulpes: <jurov> [] hanbot rather a pickup line, maybe. "wanna write my eulogy?" << i have actually used this one

ben_vulpes: nah. nuffin.

ben_vulpes: *crickets*

ben_vulpes: "uh, /etc/hosts?"

ben_vulpes: *seasoned* apple users totally boggled - "what did you use for that?!"

ben_vulpes: thirty second task.

ben_vulpes: i was entreated by a girl to "block some sites" on her computer. jezebel, gawker, others.

ben_vulpes: <asciilifeform> [] this is the thing that always blew my mind about serious apple aficionados - they will pay, 20-100 usd, for a proggy that ought to be a 3-line perl script << funny, this

ben_vulpes: <mircea_popescu> [] "the people" are simply stupider than they were even twenty years ago. << stupider? or more?

ben_vulpes: "american small"

ben_vulpes: "oh hang on let me take out my tablet to take this call"

ben_vulpes: *embarrasingly* large

ben_vulpes: the new iphones are lolariously large

ben_vulpes: it was an entirely serviceable music library manager, until someone decided that it needed more features.

ben_vulpes: itunes has been rotting since 10.4, at least

ben_vulpes: the mourning cry is "steve is dead"

ben_vulpes: and so...can't actually do math anymore.

ben_vulpes: the "calculator" in 10.10 uses javascript

ben_vulpes: references get dropped constantly.

ben_vulpes: can't handle trivial column shooping.

ben_vulpes: horrid.

ben_vulpes: they have this hilarious "spreadsheet" program "Numbers" that not just disregards 20 years of spreadsheet UI finessing, but also disregards their own text input conventions.

ben_vulpes: <asciilifeform> [] ben_vulpes, possibly other folks who work on apple machines: http://www.mondaynote.com/2015/01/18/apple-software-quality-questions << tell me about it

ben_vulpes: prevailing opinion being that there's no point in making a high quality computing product...yet

ben_vulpes: i don't think though that we've extended this to computational substrate yet.

ben_vulpes: (the notion that a high grade product like coffee, or chocolate can be made in bulk, in such a way to appeal to the masses...well, this is old hat around here, right?)

← | →