log☇︎
101700+ entries in 0.022s
asciilifeform: all of the various types of broken promises, would still be detectable, but 1) strictly to those whom they immediately affected and 2) unopposably.
asciilifeform: those who were issued H(H(....)) of the outputs of Q, will see whether what they got rolled corresponded to one of these, or was a sham; or that they were rolled a particular ticket, but it ended up carrying ~someone else's~ tx as cask fill.
asciilifeform: the miner's publication of W in the block will suffice then.
asciilifeform: it is not strictly necessary to transmit rsa-signed tickets (and then store the bulky stuff in casks for all time.) if you are content to have promise-keeping be ~measurable~ at each particular level of the pyramid, and to the children and parents of that level strictly, and that it not be opposable -- then you do not in fact need these signatures
asciilifeform: here we have another piece where i used a nail instead of a hinge.
asciilifeform: which brings us to http://btcbase.org/log/2017-02-28#1619776 : ☝︎
asciilifeform: whereas here you can keep tabs on kept/unkept promises.
asciilifeform: with unmeasurable and hidden failures, most egregiously, selective mining of tx.
asciilifeform: only 1 pill against this - meet people.
asciilifeform: 'i wanna play chess, but i know 0 chessplayers'
asciilifeform: 'i wanna fuck, but i know 0 chix'
asciilifeform: the only solution is 'know some nodes', srsly
asciilifeform: 'what if i know no nodes' was a problem there as well.
asciilifeform: http://btcbase.org/log/2017-02-28#1619766 << classical bitcoin likewise makes 0 guarantees to the user. ☝︎
asciilifeform: possibly.
asciilifeform: but to demonstrate to woman that she is unfit for husbands, and ought to proceed to cat accumulation, can be a valuable gift.
asciilifeform: tru!
asciilifeform: can show that it is simply part of the existing unsolvable heat death problem.
asciilifeform: or that it is a solvable problem any more so than heat death.
asciilifeform: so it is not clear to me that 'dust' would become a problem at any rate separate from the rate of heat death.
asciilifeform: complexity heat death.
asciilifeform: aaah yes. wasn't this the earlier thread, where we determined that we already have a 'proton decay' going, and that the usable lifespan of a blockchain is -- likely -- finite ?
asciilifeform: this'd be the 'deflation' thread again, neh. if it ever turns into a palpable problem -- add moar decimal places.
asciilifeform: unrecoverable dust is a fact of life, not only in bitcoin.
asciilifeform: now you ~could~ boil the thing in nitric acid, try to recover it. but most folx don't -- and sleep well at night
asciilifeform: btw i'd argue that the fixation on 'collecting the dust' is peculiar. everyone who has ever thrown away, e.g., old mobo, or whichever electronic rubbish, has discarded many milligram of Au and more or less whole mendeleev table of rarities.
asciilifeform: consider how we ended up with our wallets-with-dust in classical bitcoin.
asciilifeform: because you then need db, which will ~necessarily~ grow slower-to-lookup in geometric progression as tx table grows.
asciilifeform: the fixed-width-tx is a provable component of any long-term-sane trb-i. regardless of what other parts are included or excluded. without it, you get rapid rot.
asciilifeform: as a 'proper ring signature'.
asciilifeform: there is no such thing, and i suspect that it can be proven that there can be no such thing
asciilifeform: (rather than db idiocy)
asciilifeform: so it can be addressed by block and offset, in O(1).
asciilifeform: mircea_popescu: i'm ok with 11 in, 11 out. so long the byte block for them is FIXED.
asciilifeform: by n tx.
asciilifeform: at the cost of multiply txing.
asciilifeform: you can replicate the effects of multi-in-multi-out using multiple single-in-single-out.
asciilifeform: for what do you need it ?
asciilifeform: it results in nonlocality and massive thrashing.
asciilifeform: likewise, and perhaps less obviously, multi-input and multi-output is braindamage.
asciilifeform: http://btcbase.org/log/2017-02-28#1619760 << this is the biggie. you ~gotta~ have fixed-width TX, ruat caelum, because it is the only way to not have the system grind to an exponential halt over ~decade. because it makes O(1) input verification ( http://btcbase.org/log/2017-02-25#1618145 thread ) possible -- and - provably - no other geometry does. ☝︎☝︎
asciilifeform: i'll repaste, damn it
asciilifeform: *fixed-width tx, rather from 2 lines up
asciilifeform: *fixed-width tx, rather
asciilifeform: variable-width tx is braindamage.
asciilifeform: http://btcbase.org/log/2017-02-28#1619760 << this is the biggie. you ~gotta~ have fixed-width blocks, ruat caelum, because it is the only way to not have the system grind to an exponential halt over ~decade. because it makes O(1) input verification ( http://btcbase.org/log/2017-02-25#1618145 thread ) possible -- and - provably - no other geometry does. ☝︎☝︎
asciilifeform: and this also addresses http://btcbase.org/log/2017-02-28#1619762 , i think ☝︎
asciilifeform: tru
asciilifeform: i'm with mircea_popescu on this one
asciilifeform: earlier it was 'fill this or you spilled'
asciilifeform: well now that casks can be floated empty, this is practical.
asciilifeform: aaaah
asciilifeform: how do you have a market, with fixed fee ?
asciilifeform: fixed ?
asciilifeform: so these are both verifiable at the immediately preceding-the-leaf level.
asciilifeform: just like he knows if the sig is invalid.
asciilifeform: a tx, recall, is finalized (from egg to larva) ~upon receipt of rolled cask~, which means that the immediate parent immediately knows if the fee suffices.
asciilifeform: http://btcbase.org/log/2017-02-28#1619756 << the 'rotten fill' thing was simply a restatement of 'a tx is not a tx unless it is valid, and a block is not a valid block unless it consists wholly of valid tx.' cribbed straight from classical bitcoin. phrasing was, evidently, confusing. ☝︎
asciilifeform: it is an inevitable occurrence at all levels of the pyramid, and is not fraudulent per se.
asciilifeform: not disavowed. probably ought to have described 'fib' more neutrally.
asciilifeform: the design specifies that the rate of promise-breaking is measurable. which is a prerequisite to any wotronic approach to incentivizing promise-keeping.
asciilifeform: it is not removable, sadly.
asciilifeform: the inevitable other side of the promise-making medal, is that the maker can break the promise.
asciilifeform: there is a reason why i specified 'fib' as a fact of life.
asciilifeform: if he oversells excessively, he gets nailed by his downstream. which is as it ought to be.
asciilifeform: so he oversells. just like airline.
asciilifeform: he can self-fill a %.
asciilifeform: miner does not ~have~ to roll all 1k casks.
asciilifeform: this is same problem that airline solves
asciilifeform: aite, continue
asciilifeform: you are working on N blocks , with 1k holes each . can issue 1k * N casks, with various promiseheights.
asciilifeform: ( recall that casks have time parameters. they do not have to be promiseheighted 'for currentheight+1' immediate fill! )
asciilifeform looks...
asciilifeform: this is, note, unlikely to be the top
asciilifeform: at whichever level of the pyramid where the '4th roll' happens - is where a child's head rolls.
asciilifeform: not randon hans.
asciilifeform: ultimately guderian answers if the tank attack failed.
asciilifeform: unconditionally.
asciilifeform: all children are responsible for their children.
asciilifeform: the responsible child's, who else
asciilifeform: why impossible ?
asciilifeform: (cask'd be sent down to a child for an interval, if it fails to float, gets reissued)
asciilifeform: http://btcbase.org/log/2017-02-28#1619755 << later realized that the protocol ought to permit returning an unfilled cask to the parent, so he can reissue it to another child. this would make for a less unforgivably-tightly-coupled system ☝︎
asciilifeform: let's come back to this part; i'ma walk the list.
asciilifeform: whole thing is about 'marketize timely tx-gathering'.
asciilifeform: miner cannot reproduce the tx-maker, with his fee.
asciilifeform: there is nothing inherently virile about the miner.
asciilifeform: the algo put miners in the saddle. another algo can put them into the latrine where they belong.
asciilifeform: it is possible to flip his decision around, just the same.
asciilifeform: satoshi -- decided.
asciilifeform: this now being said:
asciilifeform: asciilifeform's aim was to consider gedankexperiment trb-i where this cock is turned around radially, at the miner. who, reaping most of the cake, ought to also absorb the cock.
asciilifeform: classical bitcoin is a massive cock, with the sharp end pointed at the node.
asciilifeform: and also oughta have expanded re the motivating factor. which, possibly, was apparent from the thread context, but ought to have been explicit:
asciilifeform: second, while sleeping asciilifeform did realize that he had nailed down a few parts that ought to have been hinged, and hinged some parts that oughta have been nailed.
asciilifeform: if it was even half as painful to read, as to write.
asciilifeform: sooo first of all, hats off to mircea_popescu for actually digesting this piece
asciilifeform: aite, i'ma wait
asciilifeform: mircea_popescu: ready for some answrs?
asciilifeform: trinque this is the casks thing.