253700+ entries in 0.066s
mircea_popescu: the bitcoind node makes sure it did what it pleased within bounds, and off it goes.
mircea_popescu: the bitcoind node keeps a db, the bitcoind wallet selects what it wants and does what it pleases.
mircea_popescu: <kakobrekla> first runs on airgap, second on my server in dc and third on my desktop << seems txn are logically created on 1.
mircea_popescu: if you know that block 2 is verified, and you know that 1testadress1 is the 1testaddress1, what more do you need to check ?
mircea_popescu: so you see this 0 conf tx that's being proposed references an input in block 2. which you have and you verify and that's that.
mircea_popescu: well the block 3 tx i named as "proposed" is a 0 conf.
mircea_popescu: we see in block 3 a tx that proposes to take 10 btc from 1testaddress1 to 1 testaddress2. you propose we can't verify what ?
mircea_popescu: in block 2, a tx takes 20 btc from 1block1coinbase to 1testaddress1 ; 50 btc > 1block2coinbase
mircea_popescu: jurov i thought we were discussing bitcoin as a spec, rather than bitcoin as a hack.
mircea_popescu: you can, for the sake of being silly, talk of "transactions included in valud blocks" but it really doens';t mean anythinmg. a block is a block.
mircea_popescu: there's no such thing as "a valid transaction". merely, a valid block.
mircea_popescu: maybe these other words work better : "transactions" is a useful notion when adding data to blocks. it is in no way useful, or even existent, when verifying anything. all you can verify, both the most and the least you can verify, are BLOCKS.
mircea_popescu: you can't have a valid txn in an otherwise invalid block.
mircea_popescu: ben_vulpes it needs to retrieve arbitrary blocks. why txn specifically ?
mircea_popescu doesn't understand why this is contentious and will re-read.
mircea_popescu: by looking at their inputs, an the inputs for those inputs, all the way to the valid coinbases involved.
mircea_popescu: if you check you check. if you don't check, then don't check.
mircea_popescu: and i don't give a shit how convenient it is. let userland cut down the correct implementation for the sake of convenience.
mircea_popescu: ben_vulpes once a transaction is proposed, the software has two options. 1) "oh , this looks like a tx involving inputs i remember were valid" and 2) "these are the inputs. check. these are their sources. check. these are their sources. check. this is the coinbase. check. ok."
mircea_popescu: <mircea_popescu> bitcoind should broadcast verifiable txn submitted to it. <<
mircea_popescu: like linux. i don't have to get a new version of lindows to get rid of fucking notepad
mircea_popescu: modular fucking design, so you doin't have to change the whole thing every time a part sucks [for your usecase]
mircea_popescu: bitcoind should broadcast verifiable txn submitted to it.
mircea_popescu: trying to invent a "this is the right way" because we're the power rangers isn't the way
mircea_popescu: there's no ready way to know hat the user will want the index to be.
mircea_popescu: bitcoind should put the blocks into an accessible database. the querying of that thing is the job of the user.
mircea_popescu: suppose you somehow DO actually want 32mb blocks. how long does a rescan take then ?
mircea_popescu: design is not a consideratio nof "how long does it take to bale the water out"
mircea_popescu: if every phone had to maintain 6bn phone numbers ? that's terrabit memory on any phone ?
mircea_popescu: notwithstanding that in order to call someone, having the phone number is not a big deal. having a passing answer for "who's this ?" is.
mircea_popescu: it's not unlike the "idea" to maintain a list of the phone numbers of the entire planet.
mircea_popescu: Cubs in the Islamic State, the generation that will conquer Rome in shā Allah << boys are wearing the stupid face veil thing too now ?!
mircea_popescu: "a CPU profile of the time spent processing a 32 MB block by a full node is dominated by ECDSA signature verification, meaning that with the current infrastructure and computer hardware, scaling above 300 tps would require a clustered full node where ECDSA signature checking is load balanced across multiple machines."
mircea_popescu: ben_vulpes: asciilifeform: i don't know that the thing needs to cough up *any* transaction on demand. << one can make his own emacs scripts do whatever one wants. notthe job of emacs to provide a preloaded button for arbitrary tasks.
mircea_popescu: davout: "you want to do some btc related accounting? well, fuck you, the decimals after the second are a $1.99 in-app purchase" << seriously ? like a power chord that's not six inches long ?
mircea_popescu: hanbot if you eventually decide to sue for creation of a sexually harassful working environment, pls to direct it at jurov
mircea_popescu: omfg that's not what that article said, and wtf spouse!
mircea_popescu: only to the eyes of someone who has no idea what men act like.
mircea_popescu: Bagels7 yes, i believe there is strict and unbreachable difference between the sexes.
mircea_popescu: because, obviously, water and soap doesn't exist and who could ever wash!