Results 35751 ... 36000 for 'f:ben'...

ben_vulpes: "oh my noes i can feel my brain wilting all the way over here! a scent of gasoline! in the warehouse we rent! we're all about to keel over!"

ben_vulpes: * mircea_popescu kinda likes the smell of gasoline << various engineers went on red alert over a faint whiff of gasoline earlier today

ben_vulpes: https://p.gr-assets.com/540x540/fit/hostedimages/1381361152/4761785.jpg

ben_vulpes: vino tinto

ben_vulpes: mircea_popescu: ojo de bife y vino

ben_vulpes: boats and cars aside i think i get the "computer enforcement of human language contract"

ben_vulpes: that's too big a leap for my tiny brain

ben_vulpes: insurance policy?

ben_vulpes: merchant and processor sign agreement that proceeds shall be divvied thusly.

ben_vulpes: let's try the wot.

ben_vulpes: i'm not savvy to this story.

ben_vulpes: i was going for the wot

ben_vulpes weeps in ignorance

ben_vulpes: the incentives are aligned! merchant and payment processor must agree to get anything out.

ben_vulpes: please

ben_vulpes: go on

ben_vulpes: okay, so my derpitude re: m/n aside, the thing has a stable solutino.

ben_vulpes: "either we agree, or nobody gets anything."

ben_vulpes: both keys must sign for outputs to be valid.

ben_vulpes: pardon?

ben_vulpes: m=n

ben_vulpes: lol wat

ben_vulpes: what if there's no third?

ben_vulpes: no, thy enlightenment please

ben_vulpes: mind you, this is a pure-btc play.

ben_vulpes: funds sent to M/N address, both merchant and payment solution provider must agree upon processor fee and merchant share to disburse funds to each.

ben_vulpes: our solution: one of the few actual uses for M/N signatures.

ben_vulpes: cazalla: i was derping with a colleague about btc payment processing recently. the topic: how to ensure the payment processor (he who tells the taco-delivery mechanism to release tacos) gets paid?

ben_vulpes: mircea_popescu: welcome to my hell.

ben_vulpes: wallets should be built atop bitcoind or equivalent.

ben_vulpes: decimation: a fantastic idea.

ben_vulpes: what is the bitcoinating? the part that attaches to the network, downloads and verifies the blockchain?

ben_vulpes: <asciilifeform> decimation: bitcoind begs to be split into at least 3 programs << of which only 1 is necessary ! << for the record, what are the three and which the one?

ben_vulpes: signed patches will released.

ben_vulpes: there will be a base.

ben_vulpes: i think then this discussion is settled.

ben_vulpes: undata: staaaahp

ben_vulpes: or rather

ben_vulpes: no db necessary

ben_vulpes: m ah

ben_vulpes: <undata> anyhow, horse is starting to stink << what is this a reference to?

ben_vulpes: but for releases, history of changes to bitcoin x

ben_vulpes: that's not a problem

ben_vulpes: undata: git can be used for development

ben_vulpes: name of the game being dependency minimization.

ben_vulpes: base plus patchlist?

ben_vulpes: <asciilifeform> forsaking version control systems entirely! << i cannot conscience this.

ben_vulpes: was someone hosting some git repos?

ben_vulpes: <nubbins`> bitcoin x << ah, this

ben_vulpes: http://www.nhplace.com/kent/CL/x3j13-sd-05.html

ben_vulpes: i've never written a charter, are there good examples out there?

ben_vulpes: it's fine and great i mean to say

ben_vulpes: ugh amenable

ben_vulpes: mod6, othernubs`: i'm behind on logs, but this is amenable.

ben_vulpes: it initially ended with :=0/d so as to rip the relevant line out. that'll still work.

ben_vulpes: nice! care to share?

ben_vulpes: mm.

ben_vulpes: mod6: create an address and send coins to it?

ben_vulpes: what's the use case there?

ben_vulpes: othernubs`: i'm not even sold on importprivkey

ben_vulpes: at this point i'm running the node stock to see what happens

ben_vulpes: Apocalyptic: indeed. piles of work.

ben_vulpes: still caffinating can't keep up already

ben_vulpes has no idea

ben_vulpes: Apocalyptic: semantics indeed, but not the reddit-style attempted-argument-ender kind. rather the important kind that conveys significance.

ben_vulpes: mod6: plenty of sense. i was a little startled to see that your debian dist didn't come with sudo.

ben_vulpes: Apocalyptic: i have to clear up that it's not a *commit* summary but a changelog summary.

ben_vulpes: didja get it running eventually?

ben_vulpes: thoughts for bed.

ben_vulpes: how though to reconcile noise suppression with -asset logreading...

ben_vulpes: taleb's really on to something with his noise suppression routine.

ben_vulpes: i had to get scamsniped AGAIN.

ben_vulpes: but noooo

ben_vulpes: i *was* being productive and booting historical versions of bitcoin to run locally.

ben_vulpes: well it's cost the future one night of my time.

ben_vulpes: anyways, here, ether wallet lulz: http://cascadianhacker.com/blog/2014/10/22_technical-flaws-in-early-ether-wallet-implementations.html

ben_vulpes: ether

ben_vulpes: but

ben_vulpes: i

ben_vulpes: you're shitbanned

ben_vulpes: fuck you medium

ben_vulpes: who nerdsniped me with the etherscam again

ben_vulpes: okay who did this to me

ben_vulpes: WHY

ben_vulpes: A REASONABLY AFFORDABLE POSSIBLITY

ben_vulpes: using their considerable expertise in implementing a just-in-time (JIT) compiled version of the Ethereum virtual machine and making computationally-complex contracts a reasonably affordable possibility

ben_vulpes: neat keyfob i guess

ben_vulpes: but you know

ben_vulpes: plus a screwdriver. maybe.

ben_vulpes: looks like i could get it open in about a minute with a decent vise

ben_vulpes: fluffypony: now there's an interesting thing to put up someone's pooper

ben_vulpes: http://rajensanghvi.com/ << fuck yeah default wpengine template

ben_vulpes: my brain's calling it quit

ben_vulpes: now i want to see the power draw of the btc network.

ben_vulpes: not that novel.

ben_vulpes thinks

ben_vulpes: this suggests a novel attack vector: depress price strategically to drive miners out, drop large amounts of hashpower to rewrite blockchain.

ben_vulpes: i'm too tired and too deep in unix horseshit to know what to say about ether anymore

ben_vulpes: dude

ben_vulpes: https://medium.com/@abrkn/obtaining-and-offline-securing-ether-for-the-upcoming-ethereum-launch-157963b6a456 << so one actually downloads wallets from the etherfolk?

ben_vulpes: lol i wish i had that kind of budget

ben_vulpes: full time you say

ben_vulpes: :P

ben_vulpes: 'cept for the rapier betwixt yer ribs

ben_vulpes: nothing personal

ben_vulpes: "i can read java and stuff, but can't handle cli programs"

ben_vulpes: that's a pretty funny self-indictment of javaland if you don't mind my saying so.

ben_vulpes: you make the baby satoshi cry

ben_vulpes: bawww really RagnarDanneskjol ?

ben_vulpes: it's a forging of some kind. trial by fire.

ben_vulpes: gangster-rapper

ben_vulpes: should la serenissima publish a torrent?

ben_vulpes: mhm.

ben_vulpes: this has been educational indeed.

ben_vulpes: hm.

ben_vulpes: provided set_lk_max_locks type configs are in place?

ben_vulpes: but if you supply the entire datadir, you can boot one install with another's blockchain?

ben_vulpes: i'm thinking in terms of bits on disk

ben_vulpes: so every blockchain could be a snowflake.

ben_vulpes: right.

ben_vulpes: although if you'd be willing to share your tarball and a version number against which i could build that might show some interesting things on a block-by-block diffing

ben_vulpes: i'm not concerned about the speed nearly as much as i am the thing working correctly with the network.

ben_vulpes: mhm precisely.

ben_vulpes: i agree, yeah.

ben_vulpes: none that can't wait for the morrow

ben_vulpes thinks

ben_vulpes: well, first words in -assets as proxy for initial blockchain dl

ben_vulpes: hm

ben_vulpes: http://search.bitcoin-assets.com/?q=mircea_popescu&start=5000 << mthreat wouldja be so kind as to expand how far back the search goes?

← | →