log☇︎
220000+ entries in 0.14s
trinque: and now we're on the n-th conversation fork
trinque: guy was using the sign-message as an example for a smaller cut than the wallet
asciilifeform: the even faint implication that i ought to so much as consider heathen nontrb wallets.
trinque: you gotta communicate more on-subj man; this is exasperating.
asciilifeform: and it is 99% of my rage, re 'lose the wallet'.
ben_vulpes: heh who was that?
asciilifeform: and the last time, someone DID IN FACT SAY 'use python wallet'
asciilifeform: this is not the first thread of this kind, either.
davout: asciilifeform: no, was this comparison ever contemplated?
trinque: I don't think anyone brought his cock into the matter
asciilifeform: or to the orphanages ?
asciilifeform: srsly davout , trinque , you would compare 'verifymessage' to winblowz #ifdef crapolade ?
asciilifeform: but to lose functionality, however uncommonly needed, that does exactly 0 harm, and the loss of which reduces by no amount the labour of a trb code reader, is at best a snore.
asciilifeform: i get it, folx watched asciilifeform swing the axe, and it looked like great fun, nao everybody wants.
davout: it's in the "bells and whistles" box, not the "hot wire functionality" one
davout: asciilifeform: you're conflating signatures on txes with signatures on arbitrary messages
davout: if you ~must~ verify one of those sigs you pull up a trb that can ~fin~
asciilifeform: that enemy shoved in as attempt to exploit the node.
asciilifeform: suppose i gotta verify the signature on a malformed tx.
davout: asciilifeform: we're talking about verifymessage and signmessage
davout: maybe we can have trb-classic then trollface.jpg
asciilifeform: davout: a walletron is pointedly ~not~ 'a knob turn away'
trinque: it'd probably be better to be hollering at a patch than all this
davout: and i really don't understand how keeping stuff around is sane when the functionality is an operator knob-turn away anyway
asciilifeform: it means that -- yes -- if i need to , i can open an ancient wallet.
asciilifeform: cutting-apart is a great thing.
trinque: this ends up meaning slashing probably everything that doesn't keep the current network protocol running
davout: asciilifeform: well, maybe for forensic purpose you want to open up an accounts-enabled legacy wallet? i don't know, sounds equally likely as "want to check signature some derp made in weird ways during ancient times"
trinque: there are goals at odds here. to fix the nightmare that is current trb, gotta start slashing til you have something that's able to be comprehended
asciilifeform: or somehow this was implied in my patches ? (where, note, i cut out entire useless subsystems, and shrank memory drain eightfold ?)
asciilifeform: i said this ?
trinque: it does proceed that way
trinque: "nothing but this particular arrangement of driftwood counts as actual reference trb"
davout: asciilifeform: well, if you want to "keep everything" you end up keeping everything
asciilifeform: davout: can you draw a scenario where you might say 'now if only we had not thrown out idiot accounts...'
trinque: and eventually there's a process of regrinding and so on
asciilifeform: davout: how's that follow?
trinque: I don't think it's a sin for davout to go slashing and cauterizing in one direction, meanwhile reference client proceeds in another
davout: ben_vulpes: ty
davout: asciilifeform: with this kind of reasoning we'd end up keeping the "accounting" feature around
trinque: asciilifeform: http://logs.bvulpes.com/trilema-mod6?d=2016-12-19#ca75f916-f2c1-46a7-b3ba-27b0ac6f3e26 << thereabouts
ben_vulpes: davout: consider #!/bin/bash and set -e to make the thing die if any subprocesses return non-zero
davout: asciilifeform: the trb tree has a "continuity-preserving" mission, not "current trb official version"
trinque: asciilifeform: consider our conversation about the openbsd patches in another castle
asciilifeform: davout: yes, they could 'rebuild historical trb' but imho if this is a kind of thing that ever becomes necessary, trb will have failed in its continuity-preserving mission.
davout: what version of gnu-awk are asciilifeform, trinque et al. using to have a usable vdiff.sh ?
trinque: I am aware of that, or what I said next would make no sense
thestringpuller: davout: that's why I think the UTXO probing is interesting. Easier to search ~2GB and ~100GB for the information you want.
davout: asciilifeform: archaeologists can build a verifymessage-capable trb, couldn't they?
trinque: the former might help clear up the latter
ben_vulpes: perhaps a low-dough point: vpatches ensure that functionality will always be available, regardless of weight of "current" version ☟︎
asciilifeform: trinque: trb already exists in multiple branches, such is the nature of vtronics.
trinque: one of which strips the thing bare; another which is the reference
trinque: I don't see that it'd be a terrible sin to have multiple branches descending from current trb
davout: asciilifeform: my emulated mp would answer that a dork that signed that way can't possibly sign something important
asciilifeform: using the routine that the author of said signature intended.
asciilifeform: there are historical signatures floating about, and one might wish to verify them ☟︎
asciilifeform: while it is imho stupid to generate such signatures and rely on them for any practical use,
davout: lighter trb?
asciilifeform: i disagree that this would do any good.
davout: asciilifeform: well for example, the "remove signmessage and verifymessage" patch could very well be considered ready for production, it cuts something, not something anyone sane would actually depend on
thestringpuller: s/with bitcoin/with trb*
thestringpuller: i'm using the blockchain itself to get the UTXO for forming new transaction when creating raw TX with bitcoin, this requires searching teh blockchain or using ben_vulpes tool
asciilifeform: davout: it is good, and healthy, to 'target practice' with the toolchain. but please try to clearly note this.
thestringpuller: probing is more accurate a term
davout: thestringpuller: i'm not sure what you mean by "scraping the UTXO" ?
davout: but appreciate that i'm a fucking noob and i need to have something to get started, at least with the toolchain, not that it has to make official release until it's actually done you know
asciilifeform: then i have nothing else to disagree with
asciilifeform: cut old liver ~when new one is sitting on the table, steaming, ready to transplant~
asciilifeform: but it is strange to begin with removing old one.
asciilifeform: and cutting out the old one , does not add up to even 0.1% of the work.
thestringpuller: davout: no. I'm just curious if there is a way to scrape UTXO's now, cause for my wallet tron I'm scraping blocks themselves. Def not O(n). (don't laugh)
asciilifeform: and should not turn on at all.
davout: asciilifeform: a sane wallet would make it very easy to avoid dust fragmentation
asciilifeform: davout: my point was solely that a car sans-brakes is not a car
davout: thestringpuller: you're asking me what trajectory i'm going to take at 200mph for that turn, i'm at the point where i'm still wondering how to turn the goddamn car on
asciilifeform: davout: this is theoretically possible. in practice it seems like the direct opposite happens ?
davout: asciilifeform: take 20 UTXOs spend them in one go to a single address, poof! UTXO set has shrunk
thestringpuller: is there a way to scrape the UTXO set in TRB or do you have to do that manually as of now?
davout: asciilifeform: yeah well, if we're going to debate what "we don't have yet" we're not going to get very far
asciilifeform: nor is there any promise from any god that it will stay below 2GB, or 20, or 20,000, it is doomed to increase
davout: also the UTXO set might very well decrease
asciilifeform: davout: afaik we do not have this cache.
davout: asciilifeform: tbh i haven't measured it, but scanning 2gb of ram shouldn't really take that long
asciilifeform: davout: if you're happy to wait for 30 min to an hour every time you unsheath the 'launch codes' -- then yes.
trinque: were you going to interrogate the utxos every block or something?
davout: trinque: text files with private keys sounds like the sane approach to me
trinque: there was a decent thread on how 'wallet' end up being 'arbitrary declared index of declared addresses'
asciilifeform: i.e. half hour or so (and destined to linearly increase forever) per shot.
davout: thestringpuller: UTXO set is ~2gb tops, indexing might be nice but necessary to scan for UTXOs that match a given set of addresses, also the wallet part can cache them if that particular wallet is the only one able to actually spend those UTXIs ☟︎☟︎
thestringpuller: davout: wallet has keys, asks for unspent outputs to bitcoin << don't you have to be "watching" an address while indexing to get this info?
trinque: I can't find davout saying he refused to provide such a thing in his patch
asciilifeform: prior to a replacement being ready.
asciilifeform: but not only will i not sign such a thing, i question the sanity of anyone who would.
asciilifeform: trinque: that part is quite obvious and goes without saying
trinque: this whole thead could've been "I will not sign the excision unless it brings also the replacement wallet" ... "k" ... fin
asciilifeform: snipping old wallet is a trivial patch, i suspect that any and each of trb folx could re-create it in half hour
trinque: and you're making it out to be something he never argued
trinque: guy's entirely ready to discuss the thing
asciilifeform: why not throw out all of bitcoin ? oh we'll make new one next year.