kakobrekla: its not impossible you will make a tx from some inputs, which will be 'forgotten' and say fuck you [i only a slight problem so far as long as the tx hex is published and can be rebroadcast] and then later on use those same inputs for another tx [i have a larger problem with that]
kakobrekla: because you leave it the bitcoind to select the inputs.
assbot: BitBet - Jeb Bush will be Republicans' 2016 Presidential Nominee :: 1.63 B (9%) on Yes, 16.49 B (91%) on No | closed 1 week 2 days ago ... (
http://bit.ly/1KJwPbF )
mircea_popescu: later throughout the weekend, tx A1 was not visible in the bitcoin network, in spite of being broadcast to 100s of peers.
mircea_popescu: as a result, tx A2 was created, monday, spending the same inputs, paying a fee, and was broadcast.
mircea_popescu: throughout the following 48 hours, neither A1 or A2 were visible on the network.
mircea_popescu: a flurry of other txn, all spending the same inputs and paying ever more in fee were broadcast up until, most recently, march 1st (~16 hours ago).
kakobrekla: you pay out bet A with inputs Ia and sufficient fee. tx gets 'lost', not confirmed. people bitch. you post the tx hex so people them selfs can re-broadcast it. however for as long as that tx is not included in the block you can not spend those same Ia inputs.
mircea_popescu: about three hours ago, tx B, with the same outputs as An, but with different inputs was broadcast. this tx was visible in the mempool throujghout the network as normal, and was included in a block in half an hour.
mircea_popescu: about half an hour AFTER that inclusion, transaction A1 was REBROADCAST, and within 20 minutes of its rebroadcasting, in spite of no fee, low miner priority etc, was included in a block.
mircea_popescu: a) a majority of miners (ie, pool operators) on the bitcoin network conspire together to selectively deny valid transactions
mircea_popescu: b) the same majority of miners is running a withdheld block scheme, where they keep about a half hour time differential between the ACTUAL head of the bitcoin chain and what they published.
mircea_popescu: both of these are serious concerns, and both of these are, strictu sensu, sufficient to prove, not to propose, that bitcoin is not actually functional.
mircea_popescu: moroever, both of these are factual matters, on the basis of observed behaviour.
kakobrekla: thats one explanation however taking in account my own experiences with it - i am by your definition insane.
kakobrekla: anyway, for as long as the original tx is not included you must be careful not to spend those inputs in another tx. even if that means forever.
mircea_popescu: look, i know oodles of people have observed what to them seems "just normal wierdness"
assbot: Logged on 01-03-2016 23:16:38; mircea_popescu: the problem is broadly speaking that bitcoin is not actually fit for commerce, and that fixing it necessarily requires changing the pow to exclude f2pool/antpool/etc.
mircea_popescu: this is fine and good. however - i nicely structured this specifically to satisfy my own inquisitive mind. i am satisfied.
kakobrekla: i guess its time to add 'raw hex tx' data for re-broadcasting to bitbet resolved bets
☟︎ mircea_popescu: asciilifeform pretty much. i don't see what else is there. this is the fabled hour of reckoning, best i can tell
assbot: Logged on 01-03-2016 23:27:41; mircea_popescu: anyway. miners must be broken, burned and the land fucking salted.
mircea_popescu: kakobrekla im still thinking what the best solution to this would be, but as far as bitbet is concerned quite likely something like that.
mircea_popescu: kakobrekla not that it'd actually do anything, just adds a gauge.
mircea_popescu: whatever mining may be, it's not jsut the codebase that's broken. bitcoin, per se, is not currently functional.
mircea_popescu: anyway. at present the best short-term course is, of course, publicizing the matter.
mircea_popescu: i suppose we're at the chinese phase of exchanging insults.
mircea_popescu: nah, usg doesn't figure into this as much as a prince albert.
mircea_popescu: why what ? why b) ? because it's way the fuck safer for them if any would-be competing cartel starts with a half hour disadvantage.
mircea_popescu: typical behaviour of spider unaware that what it's trying to catch is a wasp. that eats spiders.
assbot: Logged on 29-02-2016 23:31:57; asciilifeform: (adlai ?)
assbot: Logged on 11-10-2014 14:12:44; Adlai: kakobrekla (~kako@unaffiliated/kakobrekla): o hey lisp and bitcoins. you might wanna check out #bitcoin-assets
trinque: jurov: adlai: deedbot- node chewed his wallet.dat into pieces again, re-importing key. on my list of tasks for this week is to look into using shiva interfaces for this.
trinque: your deeds will go out soon as he's able
trinque: actually it looks like jurov's already has
assbot: [MPEX] [S.MPOE] 21990 @ 0.00056937 = 12.5204 BTC [+] {2}
jurov: mircea_popescu: mpex.biz does not recognize my sig and mpex.site threw error 500
assbot: [MPEX] [S.MPOE] 15200 @ 0.00056821 = 8.6368 BTC [-] {2}
BingoBoingo: <asciilifeform> wake me up when it's time for the keccak knife. << Is there a possibru lAb project here?
BingoBoingo: Of course not, but mebbe keccak miner can be pet project for pet to play with? Every cat needs string, or in their absence lasers.
mircea_popescu: BingoBoingo im writing a qntra piece re the thing, gimme an hour.
BingoBoingo: asciilifeform: Pretty much the definition of pet is gets to do what it wants, but many pets take suggestions.
assbot: uchi is not registered in WoT.
gribble: Error: For identification purposes, you must be authenticated to use the rating system.
gribble: Error: User doesn't exist in the Rating or GPG databases. User must be GPG-registered to receive ratings.
assbot: [MPEX] [S.MPOE] 9000 @ 0.00056927 = 5.1234 BTC [+]
BingoBoingo: mircea_popescu: Apparently the dude sold the site to another dude and retroactively converted the sale into a lease by claiming US copyright law.
BingoBoingo: The scammed dude asked me how to present his dilemma in a way that makes sense that this was the distillation I found most obvious
BingoBoingo: Of course the solution in the long run is to stop trying to do the kind of deals which make this wankery a possibility
BingoBoingo: The WoT, many thought they could find an easier, softer way...
mod6: Good evening Gentlemen.
jurov: BingoBoingo: In my reports I prefer to have duplicate numbers instead of omitting, so that I'm sure I don't forget something.
jurov: i mean just something like "....total of 8335 words. Total 8335 S.QNTR shares are issued to:"
assbot: GitHub - fulldecent/system-bus-radio: This program transmits radio on computers without radio transmitting hardware. ... (
http://bit.ly/1RFk7xN )
assbot: Logged on 02-03-2016 01:38:12; asciilifeform: supposing that anyone gives a fuck.
assbot: Logged on 01-03-2016 08:54:01; ben_vulpes: i am also curious to hear about how long the bitcoind recompile is in your various workflows, asciilifeform, phf, mod6, punkman, jurov
mod6: Again, this is for -recompile- only. Not for initial build. Not for newbs either.
mod6: mircea_popescu: interesting day re-betbet txn & miner witholding.
BingoBoingo: mircea_popescu: It's how the html you submitted parses. Looks legible even if some line spacing is weird. I just assumed you did that for emphasis.
mircea_popescu: BingoBoingo you have two uls in there in succession, wipe one
mod6: the 99997 one were were talkin about yesterday asciilifeform ?
mod6: or the rotor script?
punkman: mircea_popescu: were the disappeared transactions low-s btw?
mod6: ah cool - yeah maybe post in here at some point. builders may fnd it helpful if they haven't made their own already.
mod6: asciilifeform: also, cool work you started with gossip in asm on a eth card.
mod6: ah. ok, just looking for more time or for someone to pick up where you left off?
assbot: Logged on 02-03-2016 00:11:53; kakobrekla: i guess its time to add 'raw hex tx' data for re-broadcasting to bitbet resolved bets
mod6: yeah, this stuff has gone too far.
mod6: weird, i thought that was in '12
mod6: im gonna re-read that whole thread
mod6: oh there's even a qntra post.
assbot: Logged on 13-11-2014 19:06:33; asciilifeform: bip64, aside from complicating the protocol and giving relevance to the gavin shitgang, is also a jam-tomorrow chumpatronic engineering structural element
ben_vulpes: mod6: this is 'rotor_bitcoin_only.sh' in the rotor tarball
assbot: Logged on 02-03-2016 03:20:58; mod6:
http://log.bitcoin-assets.com/?date=01-03-2016#1418803 << i usually just modify the rotor script so that it just builds bitcoind with all of the necessary environment vars set, but comment out the building of BDB/SSL/Boost. The re-compile usually takes a few minutes. Not more than say 15.
ben_vulpes: i have no idea if this is an abnormally long or short time
ben_vulpes: i have no idea if this is fast or slow
mod6: ben_vulpes: ahh. ok
mod6: <+ben_vulpes>
http://log.bitcoin-assets.com/?date=02-03-2016#1419829 << with phf's patch (are you going to post that to the ML or shall i?), my post-clean compile takes 1m 16s << im not aware of phf's patch. i did recompile with shiva when it was first introduced, didn't add or subtract any compile time as far as I could tell.
☝︎ assbot: Logged on 02-03-2016 03:20:58; mod6:
http://log.bitcoin-assets.com/?date=01-03-2016#1418803 << i usually just modify the rotor script so that it just builds bitcoind with all of the necessary environment vars set, but comment out the building of BDB/SSL/Boost. The re-compile usually takes a few minutes. Not more than say 15.
ben_vulpes: mod6: phf dumped a patch in the logs for compiling under gcc
mod6: ah, ok. will have to check it out.
mod6: anyway, gn all. will check back in later.
ben_vulpes: mircea_popescu: why would the cartel have picked up the original 0 fee transaction instead of the feeful later?
mircea_popescu: ftr ben_vulpes the c spelling is antiquated but english!
ben_vulpes: since when is english a supported language
ben_vulpes: BingoBoingo: plz to replace 'o' with '0' in my comment if possible
assbot: Logged on 02-03-2016 03:27:37; asciilifeform: and maybe time for high-S miner?!
mircea_popescu: samsung ? the fabled garage miner that hasn't existed since 2013 ?
mircea_popescu: bitcoin got a problem, and it ain't no stinkin' "scalability". au contraire.
mircea_popescu: ben_vulpes understand, this isn't a field that takes well to distribution.
ben_vulpes: the fiat competition was supposed to solve this, but unfortunately the trumpenreich is just TOO GODDAMN INCOMPETENT TO EVEN COMPETE WITH THE CHICOMS
mircea_popescu: pretty much the only way to handle centralization in mining as it is designed is through periodically picking up the fattest pig and throwing it through a glass pane.
mircea_popescu: ben_vulpes aha. the americans did what they do best - lost.
mircea_popescu: fabulously, utterly, completely, 18 months they're wiped.
ben_vulpes experimenting with two-line popescu/datstoievsky fusions
mircea_popescu: a problem which to my eye looms a lot larger than whatever, "the last time english speaker wrote usable code was before they had electric typewriters"
mircea_popescu: BingoBoingo so is teh buttcoin crowd all giddy with excited shock ?
BingoBoingo: mircea_popescu: Haven't really noticed it yet
assbot: [MPEX] [S.MPOE] 13000 @ 0.00056821 = 7.3867 BTC [-]
ben_vulpes: double right angles means 'put this value over here', right? but how does it make sense to put nBits into...24?
punkman: you can never know with c++ :P
mircea_popescu: it's either "shift bits by this many", "output to this entity" or else "pleasure my wife"
ben_vulpes: i have had two beers and a glass of wine since 5pm and none of that has made me nearly as ill as this line of cpp
punkman: except someone overrode "pleasure my wife" and it's now "rape my mouth with 12 inch dildo"
ben_vulpes: right because '>>' can be overridden at the...object(?) level in c++
hanbot: hey mircea_popescu, is it okay if i defer this month's pc4 report and combine in april?
☟︎ punkman: bitbet idea: "will mpif find a new PC in 2016?"
mircea_popescu: punkman we were always at war with mouth and dildoasia!
ben_vulpes: and have always been allies with buttlandia
ben_vulpes: were simple sensible human mathematics too dirty for satoshi and company?
ben_vulpes: bit twiddling for motherfucking arithmetic?
ben_vulpes: c++ is an american programming language all right
ben_vulpes: BingoBoingo: what does all of this mean
ben_vulpes gives up, falls over, dies, rots, blows away
BingoBoingo: Every derpism like RBF is a new starfish blighting heretic client forks
mircea_popescu: ben_vulpes> BingoBoingo: what does all of this mean << replace byt fee, sorta a poor man's version of your original "run a pool!"
mircea_popescu: somehow this "majority miner changes everything" thing is very hard to see.
assbot: [MPEX] [S.MPOE] 11800 @ 0.00056821 = 6.7049 BTC [-]
assbot: sciencehatesyou comments on Potential Evidence of Miner Collusion Or An Active 51+ Percent Cartel ... (
http://bit.ly/1LU4iyK )
BingoBoingo: That's what, cockpuppet 691 or 692 she called out. Someone needs some Thorazine
mircea_popescu: and the most ... snore, i suppose, aspect of this is that other than the few dedicated philiphinos caught without talking points, the general redditard population is amply incapable of even understanding what was said. at all.
mircea_popescu: "the network will be safe because the miners won't shit in the soup because they'll be too afraid of the public reaction"
mircea_popescu: "yeah, except they'll try it a little sooner or later, and then a little more. and the public is mostly made up of the same public that thought Britney Spears is a singer."
gribble: Error: This is not one of the supported markets. Please choose one of ['bcent', 'okc', 'btcn', 'coinbase', 'cbx', 'btce', 'bfx', 'btcavg', 'btcde', 'krk', 'bitmynt', 'btsp'] or 'all'
gribble: (ticker [--bid|--ask|--last|--high|--low|--avg|--vol] [--currency XXX] [--market <market>|all]) -- Return pretty-printed ticker. Default market is Bitfinex. If one of the result options is given, returns only that numeric result (useful for nesting in calculations). If '--currency XXX' option is given, returns ticker for that three-letter currency code. It is up to you to make sure (1 more message)
gribble: Bitstamp BTCUSD last: 433.0, vol: 6784.34911547 | Bitfinex BTCUSD last: 433.88, vol: 17762.93680826 | CampBX BTCUSD last: 444.99, vol: 1.91867027 | BTCChina BTCUSD last: 441.744954, vol: 78079.43140000 | Kraken BTCUSD last: 429.3, vol: 1789.99641091 | Bitcoin-Central BTCUSD last: 430.865683, vol: 50.712731 | Volume-weighted last average: 439.621312697
assbot: [MPEX] [S.MPOE] 69682 @ 0.0005664 = 39.4679 BTC [-] {4}
assbot: [MPEX] [S.MPOE] 122800 @ 0.00056531 = 69.4201 BTC [-] {3}
assbot: [MPEX] [S.MPOE] 24150 @ 0.00056468 = 13.637 BTC [-] {2}
assbot: [MPEX] [S.MPOE] 28721 @ 0.00056439 = 16.2098 BTC [-]
assbot: [MPEX] [S.MPOE] 47036 @ 0.00056431 = 26.5429 BTC [-] {2}
jurov: huh wtf happened to lxr
jurov: debugging left on? ofc
jurov: fghj: mod6: also, do you have any hints as what leaves to press and add into lxr?
assbot: [MPEX] [S.MPOE] 14350 @ 0.00056409 = 8.0947 BTC [-] {2}
assbot: [MPEX] [S.MPOE] 17500 @ 0.00056392 = 9.8686 BTC [-]
assbot: [MPEX] [S.MPOE] 1800 @ 0.00056392 = 1.0151 BTC [-]
assbot: [MPEX] [S.MPOE] 20800 @ 0.00056392 = 11.7295 BTC [-]
PeterL: mircea_popescu: so the Jeb Bush bet winners were sent their winnings twice? Does that 16 btc go as a loss on the bitbet books?
assbot: [MPEX] [S.MPOE] 46600 @ 0.0005635 = 26.2591 BTC [-] {2}
PeterL: Or are you expecting everybody to nicely send back the mistaken funds?
PeterL: maybe if you ask really nicely?
PeterL: none, none of it makes sense
PeterL: to me, it seems like it was just a miner holding onto a zero fee txn, and it happened to move to the top of the 0 fee txn pile right after you resent the txn
mircea_popescu: you're a college man, right ? tokenize the events, assets probabilities per token, calculate the overal chance of this happening.
PeterL: have you timed how long it normally takes a 0 fee txn of that size to get into a block?
mircea_popescu: yes we have! it takes it over a week to NOT get into a block :)
PeterL: okay, so getting into a block right after your other txn is a bit of a coincidence, but not inconceivable
PeterL: I think you are just being paranoid
mircea_popescu: this is fine, but also rather irrelevant. migth as well tell darwin he's just being anticlerical.
mircea_popescu: there's actual science work to be done, for they able and willing.
mircea_popescu: it's one of those "you think you're buying a fine piece of american engineering, but otherwise it's made in china" things.
mircea_popescu: you think you're using the bitcoin network, but in fact you're using the chicoin network.
mircea_popescu: well for starters, deleting this "must hardfork to prove we can do it" nonsense and replace it with the much more sensible "must brick miners to prove we can do it", at the very least.
PeterL: I guess I can't complain too much about this bitbet blunder, the "extra winnings" I got from the bet was higher than my proportion of the loss as a bitbet shareholder (unless this tanks the share price too)
PeterL: I mean, uh, hypothetically, if I was one of the bettors ... uh.. nevermind
PeterL: unless this exposes some flaw in the bitcoin system, and the btc price crashes, and then we are all fucked
PeterL: I am not thoroughly convinced
mircea_popescu: miners can attack any user, with an unsolvable "either doublepay or never pay" dilemma.
PeterL: you just need your own miner to doublespend the inputs to cancel the first txn
kakobrekla: or move the inputs of the first tx beforehand and invalidate the doublespend possibility
PeterL: weren't you already talking about setting up your own pool?
mircea_popescu: what do you do, make ANOTHER tx to go in the An delayed-forever pile ?
mircea_popescu: and to fix this then your advice is to what, make An+1 ? because then surely ? for how long ?
kakobrekla: so you are saying you are unable to make any further txes on bitcoin network at all?
mircea_popescu: i am saying that i spent OVER A WEEK making transactions from those inputs.
kakobrekla: and for the next tx will it again take a week and not be done again ?
mircea_popescu: and, ironically, the substantial proof that there was nothing wrong with any of them PER SE, was that a tx that, as per the protocol, should not even have been relayable made it into a fucking block
mircea_popescu: within "minutes", where "minutes" just neatly fits in the cartel head-of-best-chain report delay.
kakobrekla: 0 fee txes are quite relayable, tried not a week ago.
PeterL: how do you know they are delaying?
assbot: Logged on 01-03-2016 23:32:18; mircea_popescu: i personally think the only reason it's not mined yet is that there hasn't been a block.
mircea_popescu: asciilifeform was it sourced from bitbet payouts ? i recall pete_dushenski saying the same happened to him, originally blamed it on multibit.
assbot: Logged on 02-03-2016 15:54:27; mircea_popescu: asciilifeform i do not believe in singlehandedness.
assbot: [MPEX] [S.MPOE] 20100 @ 0.00056345 = 11.3253 BTC [-]
PeterL: I still dun see why you jump to the conclusion of miner holding blocks, maybe they rebroadcast the transaction as they moved it from "0fee waiting line" to "now including these txen" when they had held it long enough for the wait time to increase its priority?
PeterL: if it had been two days instead of two hours after the other transaction, would you still have concluded miner collusion?
mircea_popescu: PeterL the operative part there is, txn was "broadcast" and then "included in a block" within 20-odd minutes.
PeterL: maybe it was the miner who had been holding it who broadcast it?
mircea_popescu: that happens to be, involuntarily i guess, and impredictably for the attackingside, i guess, a passive timing of their capabilities.
PeterL: which is why none of the other txn that followed it were included, they were invalidated by the first txn which was in the miners' mempool
PeterL: you asked the miners specifically?
mircea_popescu: i didn'taskl anything of anyone. i listen to a large cross-section of the bitcoin relay network.
PeterL: maybe a mine who likes to listen instead of talk held onto the first transaction?
mircea_popescu: for a week or so, in preference of higher fee replacements ? sure. why ?
mircea_popescu: it is breaking the protocol inasmuch as a protocol exists.
mircea_popescu: it's certainly not a behaviour supported or even possible by any codebase so far published, if you think code=protocol instead.
PeterL: why not hold onto a 0fee txn until later?
mircea_popescu: because it's part of a set of mutually incompatible txn, and some of the others have better fees, for instance. if you're am iner, you want the higher fee.
PeterL: but is the protocol to keep older txn or newer, does fee size matter?
PeterL: what if it is just somebody trying to scam by getting a party to accept a 0conf txn, and then double spending it?
kakobrekla: 0 fee txn can't even be relayed. < this is not true
mircea_popescu: write down what a party would need in order to do this.
mircea_popescu: but yes, because "the protocol" is not even written down, endless arguments of this nature can be had. by and large...
PeterL: ok, I buy some egold from bob, send him 1 btc. He sees the 0conf txn, transferes the egold to me, then I doublespend the inputs with a higher fee, sucks to be him
kakobrekla: there are many different version of nodes and implementations abiding by different rules on bitcoin network.
mircea_popescu: PeterL this is miserable "writing down". what are you, a consumer ? HOW do you doublespend.
kakobrekla: and this makes it, to an extent, unpredictable.
mircea_popescu: kakobrekla or so we thought. but it turns out that no, there's exactly one, covered in a cloud of buzzing shit.
PeterL: and the miners in your scheme see the higher fee and put the second txn in a block
kakobrekla: there isnt one. trb behaves differently than prb if nothing else.
kakobrekla: even different trb build do different stuff.
mircea_popescu: kakobrekla and guess what - trb gets blackholed now and again. prb never mattered.
PeterL: you seem to think you can just send a new txn with a higher fee and expect it to get processed faster
mircea_popescu: the miners are running their own shit, and it's centralized.
mircea_popescu: PeterL this is not what was said! didja read the qntra piece ?
kakobrekla: it matter for propagation for instance.
PeterL: while I am saying the iners are just going to keep the older txn, regardless of fee
assbot: Logged on 02-03-2016 16:20:40; mircea_popescu: the protocol is that 0 fee txn can't even be relayed.
punkman: so one thing that hasn't been mentioned, does trb even replace transactions when new one comes in with higher fee?
mircea_popescu: asciilifeform looky, this isn't how this sort of discussion works, by giving counterexample.
mircea_popescu: punkman iirc no, but the plan was to get the pool sorted by per/kb tx fee
mircea_popescu: more importantly, "the protocol is X" "no because implementation y" "implementation Y is noncompliant" "no" "because ?" "uhhh"
PeterL: Where is the protocol documented?
kakobrekla: hm qntra just fucked up my comment. apparently you cant use < and > in comments huh
mircea_popescu: by and large, very broadly speaking, and insasmuch as a "bitcoin protocol" even exists at all - it says that 0 fee txn aren't relayed or included. now, how this is implemented in practice... w/e.
punkman: which implementations do you think would accept the subsequent higher-fee transactions (putting aside the fact that you couldn't see the first 0fee tx in anyone's mempool)?
mircea_popescu: PeterL ask vessenes and the merry friends/captains of industry/power rangers/etc
kakobrekla: who here has control over approving the comments ?
mircea_popescu: punkman you mean which implementations would accept a tx with a fee ? seeing how they wouldn't see the other one ? or what ?
punkman: mircea_popescu: which implementations would accept a replacement tx with a fee, assuming they still have the 0fee tx in mempool
mircea_popescu: from experience, the stuff the chinese miners run would, at least most of the time. historically i thought this is just random variance between divergent implementations, but now i think it's a single unit behaviour modulated somehow. also, this is essentially what "Replace by fee" is all about, iirc.
punkman: relevant: "Bitcoin Core will only allow replacement of transactions which have any of their inputs’ nSequence number set to less than 0xffffffff - 1." (in 0.12 release)
mircea_popescu: you have to understand that the direct correlate of "bitcoin protocol is nowhere" is that i'm stuck sitting here wasting tons of resources and various people's time doing an endless array of stupid or plain weird shit to see what happens to try and understand what's what.
☟︎ mircea_popescu: the advantage being, of course, that i have a whole lot of canaries in all sorts of apparently unexpected places. the drawbacks... heh, let's not talk about that, i'll just get angry.
mircea_popescu: punkman the notion that prb is relevant to this discussion is shocking/ridiculous, depending on your mood.
kakobrekla: prb is what relayed your txes to the miner gates.
mircea_popescu: kakobrekla not even. prb is more or less the random noise.
kakobrekla: who else is then connected to the miners? do tell?
mircea_popescu: kakobrekla "that is not a bridge" "please build me a bridge over here so i can see this" "orly"
mircea_popescu: looky, not like you have to accept or not accept anything.
mircea_popescu: things are what they are, you make of them what you will.
kakobrekla: hence i dont agree with your interpretation of events (that bbet/you is targeted here - in which case its game over)
PeterL: I guess you cold test whether you are directly connected to miners or bridged by prb nodes: send a txn which prb does not like, see if it gets included in a block
mircea_popescu: well, you have a large pile of stuff to explain away then. i'd be curious to read the alt theory kakobrekla
PeterL: or did we do that and that is why we had to add the high/low s thing?
BingoBoingo: !up Luke-Jr May get an ack if "brick chicom miners" goes with it? Been hanging out with stroke victims recently and my brian is having sympathy deficits so I gotta defer to the peerage.
mircea_popescu: a lot of fingerprinting you can do by just listening. it's a large topic, this.
kakobrekla: im afraid you wont go for that because you dismiss things with "notion that $item is relevant to this discussion is shocking/ridiculous"
mircea_popescu: kakobrekla but it's not about me, per se, it's about the thing, such as it is.
kakobrekla: or " this isn't how this sort of discussion works, by giving counterexample."
mircea_popescu: what, you think asciilifeform accepted it as stated because he's afraid of me or something ?
punkman: has anyone else observed cases of tx being in mempool but not advertised to peers?
kakobrekla: arguably i have more actual experience with sending txes than alf.
punkman: asciilifeform: did you manage to bet 5btc twice when your tx got stuck?
BingoBoingo: <kakobrekla> who here has control over approving the comments ? Approved nao
mircea_popescu: more generally, you can't bring arguments as to what the standard is on the basis of "look what this implementation does". the illustrative case of this being the four men in a dark room with an elephant.
kakobrekla: BingoBoingo one should be removed and one approved, hopefully you noticed that
mircea_popescu: kakobrekla> arguably i have more actual experience with sending txes than alf. << well, that was a discussion of mempools i thought, so i'm not sure this reduction is relevant.
kakobrekla: i have seend weird shit happen with mempools with my own very eyes.
Luke-Jr: BingoBoingo: "brick chicom miners" ?
mircea_popescu: the problem is that "weird shit" just coallesced into everyone's worst nightmare.
kakobrekla: i dont see the events that took place as randomly impossible
mircea_popescu: nothing is randomly impossible. i have no argument there.
kakobrekla: the odds of that are less than the odds of what we observed. and i think the odds of ko
kakobrekla: spiracy are also less than randomness.
mircea_popescu: well, incredibly enough, nobody has actually calculated the fucking odds, to support this view.
mircea_popescu: i suppose you know, gut feeling. can go either way. which is why i said, doesn't have to accept anything.
mircea_popescu: asciilifeform the first set was ~arguably~ due to the malleator magically failing on select txn
mircea_popescu: which at the time i did buy as a sufficient explanation.
BingoBoingo: <mircea_popescu> historically i thought this is just random variance between divergent implementations, but now i think it's a single unit behaviour modulated somehow << Could be turdacious relay network or it's replacement's evil
assbot: [MPEX] [S.MPOE] 16315 @ 0.00056605 = 9.2351 BTC [+]
BingoBoingo: <kakobrekla> BingoBoingo one should be removed and one approved, hopefully you noticed that << But you submitted two!
kakobrekla: one thing that goes through my mind is that trb/mps infrastructure is on the border of 'consensus' behavior of most nodes. this makes it more susceptible to odd/unwanted shit happening.
kakobrekla: most nodes are idiots that run prb as built by core team
mircea_popescu: these "most nodes" don't even fucking figure in the node count.
kakobrekla: BingoBoingo one however does not validat :p
kakobrekla: the 40% uptime nodes bring your tx to the miners, news at 11 or when are those.
kakobrekla: BingoBoingo feel free to remove the one that is br0ken and does not validate as far as im concerned.
BingoBoingo: Ok, will remove bad one once I make a pot of coffee and identify it
mircea_popescu: kakobrekla> one thing that goes through my mind is that trb/mps << this is true, but let me clarify that An set of txn were broadcast through a set of > 1k distinct peers. most of which i don't regard as peers in any sense, but nevertheless they did get to hear about them from my own nodes.
mircea_popescu: which aren't, at the present time, trb-tethered. it's a goal, but into the future.
mircea_popescu: if only. protocols would be so much easier to both design and implement, if this were true.
mircea_popescu: one of the many protocol items that turned to be promises was - i shouldn't NEED any defense.
assbot: [MPEX] [S.MPOE] 7885 @ 0.0005673 = 4.4732 BTC [+] {2}
assbot: [MPEX] [S.MPOE] 7000 @ 0.00056743 = 3.972 BTC [+]
mircea_popescu: other than the obvious "they're getting sloppy" there is, of course, the alternative explanation that the current crop of miners roughly speaking stopped giving a shit.
mircea_popescu: the reward's halving, they regard their capital investment as ~worthless, and we have crossed bitcoin event horizon.
mircea_popescu: i distinctly recal trb nearly sunk in the other incident, while mpb provided the magic constants. why was that ?
kakobrekla: anyway paying out the bet with a different set of inputs after you have made a broadcast of the signed tx from the first inputs even to a single node, without moving those inputs elsewhere first, is a noobish mistake. why you were unable to do that is a different matter.
mircea_popescu: you think i'd rather have 18 btc than know all this ? i wouldn't.
kakobrekla: becase i assume you know once you put out a signed statement of spending some outputs those can actually be spent at a later time if they are still there.
kakobrekla: or should i say inputs. i always get confused with the two.
kakobrekla: its like gpg signing "i give you half of pile x" the reciever says "didnt get the message at all" and then you go ok nvm "i give you half of pile y" now.
kakobrekla: actually, to put it in another way, im surprised you are surprised over the events that happened given your set actions.
mircea_popescu: whether i am surprised or not is not included in this discussion. i don't recall saying i was surprised, nor does over-the-lan telepathy historically work. moreover, my own state is deeply irrelevant : the problem is there, and it's grinning at you.
PeterL: I don't see a problem, you signed two transactions and they both were mined, where is the problem?
kakobrekla: if you arent/werent surprised means you sort of expected it?
mircea_popescu: kakobrekla yes, by the time the 4th txn trying to pay out bitbet vanished without a trace, i was sort-of expecting it.
☟︎☟︎ kakobrekla: why go then sign another tx with fresh inputs to seal the deal ??
mircea_popescu: or at any rate something-like-it. of the vast array of various nonsense readily available in ample stores on this networked currency of the future.
mircea_popescu: so that the problem can be fully exposed, in detailed, solid fact, so as to be handwaved by people.
PeterL: but what is the problem? seems the networked worked as advertised?
mircea_popescu: PeterL looky, i'm not going to carry on this conversation. i get it, you wish to be dense and stonewall. fine, but stop derping at me about it.
PeterL: tx1 was sent, included in a block at t1, tx2 was sent, included in a block at t2, the fact t1 and t2 are close together is just a coincidence, not a problem
mircea_popescu: did you get the part where tx2 is really tx1 and was sent 8 days prior to what you insanely call tx1 ?
PeterL: no, tx2 is not tx 1 because they have different inputs
mircea_popescu: asciilifeform i've been thinking about it, but i don't think this is actually resolvable. as it happens - the "magically working network - we don't know how it works" thing is much more appealing to the average joe than you know, "this is my node. i will defend it with my life". what life, are you kidding, got sitcoms to watch and shit.
☟︎ PeterL: t1 is after t2 makes sense since tx1 had 0 fee, while tx2 had a fee and was therefore included faster
mircea_popescu: so... no. you can't solve the problem of fiat through technological means, be they bitcoin or anything else. the same people that abandoned the fiat to "mysterious entity" will just as readily abandon bitcoin, and their own asshole.
PeterL: so the lesson here is "don't send 0 fee txen if you are not patient enough to wait a few weeks"
mircea_popescu: i am not in the slightest proposing this. i am saying however that the toilet may be part of the solution, but can't be THE solution.
PeterL: what does it mean by b? what does this entail?
kakobrekla: as i mentioned before, if you really believe that miners are conspiring against bitbet (via known outputs and amounts) then its game over for bb.
kakobrekla: however my tin foil seems to be thick enough, for now.
kakobrekla: BingoBoingo regular tin foil works for now where im sitting.
BingoBoingo: kakobrekla: Ok, are you sure you used the clip to connect it to ground though?
assbot: [MPEX] [S.MPOE] 29700 @ 0.00056345 = 16.7345 BTC [-]
kakobrekla: yes, goes right to the water pipe under bathroom sink.
assbot: Logged on 02-03-2016 17:15:50; mircea_popescu: kakobrekla yes, by the time the 4th txn trying to pay out bitbet vanished without a trace, i was sort-of expecting it.
jurov: actually, i am surprised that nobody of bitbet shareholders was loud about this
☟︎ mircea_popescu: lmao. why the fuck would you, or anyone else, expect me to spend my own money to resolve bitbet's problems ? what is this company, a charity conduit ?
jurov: people are sheep everywhere, i guess.
PeterL: jurov what do you think we have been complaining about?
mircea_popescu: this is what it does for its living : tries to extract value out of the greatly economically valuable bitcoin thing.
jurov: when had transaction problem with coinbr withdrawal, i did not risk
jurov: and instead moved thhe change with big fee
jurov: and it wen mined eventually
jurov: yes, because as opposed to mircea_popescu i did read the code closely and it does maintain chains of unconfirmed transactions
mircea_popescu: asciilifeform he asked about it, i saw no problem republishing.
mircea_popescu: i dunno what code you read or what you did when, but good for you!
jurov: all the code there is, does it
kakobrekla: needles to say i dont agree with mps actions or interpretation of the results, even if you take out the qntra comment.
mircea_popescu: jurov looky, this thing whereby in reaction to a "this guy is accused of having killed that guy and here's the smoking gun" you come up with a "hey, i fired a gun once, and the smoke went so and so" is a waste of time. you wish to construct an alternate theory, please, by all means, i would wish to hear it. but you must take ALL the points, and show that your path crossing them is cheaper than the one detailed on qntra
mircea_popescu: . you wish to contradict numeric results, fine, but show your own calculations in doing so.
mircea_popescu: i can appreciate gut feel, but it's no sort of argument as to anything.
mircea_popescu: other than that, obviously whenever something blows up everyone wishes to not have to be in the way. sure.
jurov: no, you constructed and pushed forward your notion of "bitcoin protocol" wich led to stupid actions with a money that was not even yours
jurov: that someone used the stupidity against you, no wonder
mircea_popescu: and you're a poopynose!! ha-HA!!! calling names is how you solve problems you don't wish to consider! YAY KINDERGARTEN
mircea_popescu: consider it a sort of coke machine for miner rigs. inasmuch as you do exactly what they'd have done, you can keep it. else - reorg.
jurov: no it's "lalalala all i did was very right and proper, it's YOU who have to come up with theory"
mircea_popescu: that's my priviledge. i'm the one actually doing things, there.
assbot: Logged on 02-03-2016 16:35:04; mircea_popescu: you have to understand that the direct correlate of "bitcoin protocol is nowhere" is that i'm stuck sitting here wasting tons of resources and various people's time doing an endless array of stupid or plain weird shit to see what happens to try and understand what's what.
mircea_popescu: you know how it sometimes happens that a platoon gets sent on a random patrol, ends up surprising a moving contingent of enemy, a flurry of radioing and reinforcing and whatnot happens and suddenly the front is in a new place ?
☟︎ jurov: so, if in course if this recon you manage to completely obliterate bitbet's fund, you'll invoke your privilege and tell everyone to stfu??
thestringpuller: asciilifeform: re: reactor test << like how they tested the reactor in Chernobyl with a "stress test"
jurov: *during course of this recon
assbot: [MPEX] [S.MPOE] 19700 @ 0.00056344 = 11.0998 BTC [-] {2}
jurov: let me at least know im funding the war?
jurov: best to put straight into the contract: "This venture's funds may be used to enforce bitcoin protocol"
BingoBoingo: <jurov> let me at least know im funding the war? << Seems reasonable though BitBet particularly gets for the lesser versions of this shennanigans in the past. Perhaps something to do with its auditability.
punkman: so bitbet has to resolve 1800 btc of bets to cover the damage?
jurov: mircea surely has shown them!!!
BingoBoingo: <punkman> so bitbet has to resolve 1800 btc of bets to cover the damage? << MP would only have to bet a few hundred "No" on Trump to likely get money coming out of the woodwork to match it.
mircea_popescu: or whatever, give away a grand to the general public so that buffet can pretend like there are no berkshire shorts. or other stuff.
mircea_popescu: jurov companies fold all the time. this is a thing. if in the course of their business they fail to make money, they'll lose exactly as much money as they lost.
mircea_popescu: jurov> let me at least know im funding the war? << i'm sorry, you thought bitcoin WORKED ?
jurov: i'm living off it for some years, that's "works" for me.
mircea_popescu: the problem with broken things is exactly that - they "work" for you until they don't. at which point...
jurov: well, you keep asking people to wake you up when it stops working
jurov: so far i don't remember it happen
jurov: someday everything stops working, so what.
jurov: the pray tell mr. datskovskiy, why aren't s.nsa funds used to poke this house of cards?
jurov: it's business is much closer to this goal than bitbet
BingoBoingo likes where this is going. S.NSA acquisition of BitBet to test miner turderations.
BingoBoingo: because for this purpose the valuable part of BitBet is the public addresses
BingoBoingo: asciilifeform: I've been hanging out at the hospital with Grandpa while he rehabs from his stroke. I think I might have a touch of sympathy cognitive impairment.
BingoBoingo: There's no cure for being 91, but it is amazing the work physical and occupational therapists can do
mircea_popescu: jurov> it's business is much closer to this goal than bitbet << the argument, while in itself respectable, very much sadly not how things work. the jew on a ship, should the ship catch fire, will be a fireman whether he signed up for voyage as jew or as fireman.
mircea_popescu: but i'm first in line to say i'd much prefer a bitcoin protocol that was actually specified, and actually worked.
mircea_popescu: well, maybe not first in line, but anyway. somewhere in that line.
mircea_popescu: and now, if teh esteemed peerage may excuse me for a bit, i really gotta eat and make this smg report. so bbs.
jurov: *shrug* i know you want some insights as to the actual war, but whatever ricocheted shots came my way (ddos, tx problems), i solved myself in anti-#b-a ways without learning anything about the enemy
jurov: for example the ddos was solved leveraging aws infrastructure. but if the ddosers had half a brain, they'd have drowned me in aws bills
jurov: nope, so far largest attack was maybe $2
jurov: so i have my reservations about these scenarios you and alf present here
BingoBoingo: jurov: If it makes you feel any better as an embedded reporter in this conflict I sometimes wonder if, like those reporters Bush sent into Iraq and coming away with a polished view because I am not yet made to sleep in the hills with nagant and donkey.
punkman: I don't think "working" protocol means being able to assume signed and broadcasted tx has been forgotten and won't come back to bite you in the ass. What's in who's mempool is unknowable.
☟︎ PeterL: even if it was removed from all mempools, would it be wrong for somebody to rebroadcast the txn, it was signed after all
assbot: Logged on 02-03-2016 18:40:06; punkman: I don't think "working" protocol means being able to assume signed and broadcasted tx has been forgotten and won't come back to bite you in the ass. What's in who's mempool is unknowable.
PeterL: are you saying mircea_popescu is an idiot?
PeterL: Is it strange that we have had 10 empty blocks today?
assbot: [MPEX] [S.MPOE] 24200 @ 0.0005634 = 13.6343 BTC [-] {2}
danielpbarron:
http://log.bitcoin-assets.com/?date=02-03-2016#1420349 << perhaps my holdings aren't significant enough to have any weight on the issue, but nontheless I as a BitBet shareholder agree with the decision to draw attention to whatever issue at the expense of a few months of dividends. At the very least it can be seen as a marketing expense, BitBet being the catalyst to war against something truly rotten in bitcoin, something th
☝︎ assbot: Logged on 02-03-2016 17:41:15; jurov: actually, i am surprised that nobody of bitbet shareholders was loud about this
PeterL: danielpbarron yes, but that would require there to be something rotten to fight against, I think mircea_popescu is just jumping at shadows
danielpbarron: i think he knows more than I do about this matter, and I trust him when he says something is u
PeterL: I'm just a minor shareholder, my opinion doesn't count for much
danielpbarron: not that these are voting shares anyway, if you don't like it, sell.
punkman: I don't think this experiment is worth, say ~6 months of profits, but that's strictly the BB's board discretion.
assbot: [MPEX:S.BBET] 1D: 0 / 0 / 0 (0 shares, 0 BTC), 7D: / / ( shares, BTC), 30D: 0.00007821 / 0.00008412 / 0.000121 (3930 shares, 0.33 BTC)
ben_vulpes: so far none of the bag^H^H^Hshareholders seem to give a shit
mircea_popescu:
http://log.bitcoin-assets.com/?date=02-03-2016#1420457 << this is specifically NOT the assumption. bitcoin being a working protocol however DOES mean that you should be able to assume that if a transaction is rejected, or not included, or delayed, or in any way treated or not treated it is solely on the basis of data COMPLETELY contained in that transaction.
☝︎ mircea_popescu: that's tghe problem here. something wasn't good for an entire week that suddenly became good. this selective-bitcoin is in no sense bitcoin,
☟︎ mircea_popescu: and trivially can be shown to map exactly on paypal-usd.
mircea_popescu: which, youj know... also many people make a living on.
mircea_popescu: same ocean will sink same boat every time and float same boat every time.
PeterL: but if there is wait-time-weighting being done by miners, then sitting for a week would make the transaction viable when it was not before
mircea_popescu: i don't want a fucking big-brother-bitcoin-from-china-san to pray to.
mircea_popescu: i'm sure you could live with it. but that's a different question.
mircea_popescu: PeterL that's an anachronistic argument. merely because they included it once B, you infer that they would have included it wherher B or non-B. this both fails tgo explain all the points prior to B that didn't include it (standard lifetime of mempool tx is about half the interval contemplated here) and the fact that you're drawing in the conclusion in the presumptions.
ben_vulpes: mircea_popescu: did you pay to have a block mined including your transaction before sending the dup?
mircea_popescu: because you can't measure all things at the same time, basically.
assbot: Logged on 02-03-2016 19:14:47; mircea_popescu: that's tghe problem here. something wasn't good for an entire week that suddenly became good. this selective-bitcoin is in no sense bitcoin,
mircea_popescu: there's a significant difference between "this cave is infested with spiders" and "this cave is home to a spider queen the size of a camper van". at least to my eyes.
assbot: The IRS is using a system that was hacked to protect victims of a hack—and it was just hacked - Quartz ... (
http://bit.ly/1nietXu )
mircea_popescu: spiders in 1st case you handle on a case by case basis. organized spider hive, you bring out a flamethrowing tank and sear it.
PeterL: wasn't the bitcoin foundation going to produce a protocol spec at some point, or is that on the list after the reference implementation is more developed?
mircea_popescu: anyone writing up that irs story for qntra ? juices flowing every which way lol
trinque: As long as they keep their PINs secret, they should be safe from fraud. For this master plan to work, though, the IRS would also have to keep the PINs secret. << oh my god the win
mircea_popescu: in other news at 4:42 - all money systems significantly more broken than previously realised.
trinque: bot didn't eat it for some reason
mircea_popescu: trinque doesn't like that there's multiples ? or what did i do wrong ?
mircea_popescu: anyway, i've been working on that thing for two days in 30 second installments in between nutty bitcoin shit that shouldn't happen anyway.
mircea_popescu: in general, unspecified, in particular cases, as agreed with the previously living.
PeterL: asciilifeform presumably they go to the estate of the decesed?
ben_vulpes: and only if the estate controls the key!
PeterL: put the dispensation of your shares into a will, stick it in deedbot?
ben_vulpes: that'd be a contract between you and your broken, no?
ben_vulpes: mircea_popescu's thing doesn't care about what's in deedbot-, does it?
PeterL: so really, asciilifeform's question is: what happens to shares if the key is lost?
ben_vulpes: the account persists on mpex until mircea_popescu cleans it out
ben_vulpes: where in the log might inquiring minds read this caselaw, mircea_popescu ?
mircea_popescu: wasn't there some guy with a lucrative eth contract that lost his key ?
mircea_popescu: recall the case of that woman that had a child with the dead ?
mircea_popescu: trophy slut of old man who died, had kid, claimed inheritance.
mircea_popescu: incidentally, anyone know the joke with the rabbit and the bear ? the one with the beret
assbot: Logged on 21-08-2014 01:31:44; mircea_popescu: mkay. so in th forest there lived this very horny, huge schlong bear. sort of like one eye pete of the beardom.
mircea_popescu: so wolf and fox walk around the forest and they see a rabbit. fox : "let's beat the shit out of this loser" wolf : "we need a reason..." fox : "we'll ask him where's his beret... and if he has none, we beat the shit out of him!"
mircea_popescu: next the two meet him, they ask for a cigarette. which he gives them. so they ask for a light. rabbit is all like "sure, what'd you like, match, ligther ?"
assbot: [MPEX] [S.MPOE] 27600 @ 0.00056431 = 15.575 BTC [+]
assbot: [MPEX] [S.MPOE] 100321 @ 0.00056259 = 56.4396 BTC [-] {4}
assbot: [MPEX] [S.MPOE] 10809 @ 0.00056211 = 6.0758 BTC [-]
pete_dushenski: if i may summarise the last 24 hours of logs, which i must say were eminently enjoyable save the lack of practical recourse discussed : bitcoin remains the world's worst payment network... except for all the others. and even still, not by much.
☟︎ BingoBoingo: pete_dushenski: Practical recourse was discussed in older threads
shinohai: I am cursing bitcoin today - had my first trb database crash ... evidently I did not back up *everything* required and must now start my first node from scratch.
pete_dushenski: BingoBoingo: for users, sure. i found my own workarounds last month when i misattributed tx propogation failure to bitcoinj instead of bitbet taint. but for businesses ?
trinque: never a bad thing to have a weekly cron which stops trb gently, rsync's blockchain elsewhere, restarts
BingoBoingo: asciilifeform: Then we will fend off the second round of rats with sticks
mircea_popescu: asciilifeform the difference between kernel-mediated closedown and crash is that there's better handling of buffers.
mircea_popescu: but yes, what trinque said is a very useful protective measure.
shinohai: This time I am backing up the entire .bitcoin folder, space be damned
shinohai: I'm up to 2 nodes, but one is remote so isn't feasible to sync that way at this time I guess. Hopefully project budget allows for an extra dedi box this year sometimes.
trinque: so then they all hit the same bug and chew their blockchains at once
trinque: that's exactly what I said
shinohai: I have a UPS that runs node. My problem occured today when I attempted to import a private key into wallet.dat
BingoBoingo: shinohai: That generally slows down node for entire blockchain rescan
shinohai: I didn't even get to the rescan part, just db error :/
trinque: the whole wallet is severely fucked in a number of ways
assbot: [MPEX] [S.MPOE] 32268 @ 0.00056185 = 18.1298 BTC [-] {3}
shinohai: It isn't very useful as a wallet unfortunately.
pete_dushenski: shinohai: may we all benefit from your mistake! /me scurries to make backups of backups
pete_dushenski: shinohai: and were you using polarbeard patch for the privkey import ?
trinque: !s polarbeard importprivkey
shinohai: No I was using the pywallet method I have used before. Today it just decided it didn't like it.
trinque: !s funkenstein importprivkey
trinque: pete_dushenski: I think it was herr funkenstein
trinque: I used funkenstein's, worked but the wallet's still unusable
shinohai: Now it works ok as a wallet if you use the generated keys, but that isn't practical on a live node.
shinohai: Must have way to import cold/paper wllets
pete_dushenski: shinohai: there's always (whisper it) bc.info. from there you can zip off the coins to whatever live wallet or other address you might so desire
mircea_popescu: trinque> so then they all hit the same bug and chew their blockchains at once << no because heterogenous :D
trinque: to live in such days as the era of software!
trinque: I will need at least a sendrawtxn command soon lest I go mad with deedbot-, will most likely take a crack at it soon
mircea_popescu: with tools like these, who needs a horde of stampeding bulls on ecstasy.
shinohai: I forgot about the heathen bc,info allowing that pete_dushenski. Unfortunately too late now, my client went elsewhere and I do not have my coveted BTC today.
assbot: Logged on 02-03-2016 17:21:53; mircea_popescu: asciilifeform i've been thinking about it, but i don't think this is actually resolvable. as it happens - the "magically working network - we don't know how it works" thing is much more appealing to the average joe than you know, "this is my node. i will defend it with my life". what life, are you kidding, got sitcoms to watch and shit.
shinohai: Seinfeld plays happily in the background as i do trb work.
pete_dushenski: to 9% average annual inflation before you even account for the 11% greater production supply of the new model.
pete_dushenski: the chiron is basically as close as one can come to riding in the atomic dirigible of land travel.
pete_dushenski: no word, however, on how much chicom in chiron. almost certainly non-zero.
punkman: pete_dushenski: the chiron is basically as close as one can come to riding in the atomic dirigible of land travel. << I'd take a UNICAT over the bugatti
pete_dushenski: punkman: for living, all day. for a-->b, depends on road quality!
assbot: Logged on 29-02-2016 21:52:34; ben_vulpes:
http://log.bitcoin-assets.com/?date=25-02-2016#1415503 << mount her on a bicycle, pilfer a bottle from the office, mash around the city on bikes, break onto the in-decomissionment sellwood bridge and fuck on it? iono man what does one do with random girls anyways