Show Idle (>14 d.) Chans

← 2022-02-15 | 2022-02-17 →
asciilifeform: whaack: a++
asciilifeform: whaack: the ultimate test of course will be whether a fully cemented sync results in a usable noad.
asciilifeform has a half-done cement-mode vpatch, not rdy for primetime justyet
whaack: asciilifeform: i'm looking at hosting options to get another node up with my block explorer, to get a little more geographical diversification going
whaack: so it'd be mighty nice to get the cement vpatch running in the near future
verisimilitude: Sure, but it's interesting that ``Computer Science'' is a field of mathematics in which most ``laws'' have naught to do with the math itself.
dulapbot: Logged on 2022-02-15 11:09:13 asciilifeform: << imho is worth to make effort to prevent astrologers from ruining yer appetite for astronomy.
verisimilitude: I referred more to the part implying an upper bound to efficiency, to small minds incapable of rewriting problems.
dulapbot: Logged on 2022-02-15 11:11:19 asciilifeform: << 'cycle shaving only shortens the time spent in the shaved part' aint a lie. tho arguably not worth the pompous sticker of 'law'
scoopbot: New article on A Syndication of Verisimilitudes: A Review of the ISO APL Standard
asciilifeform: << indeed will be useful for standing up nodes 'quickly' (will still be limited by $machine's bw, and by the time to verify blox, imho it'd be suicidally foolish to skip verification even for 'cemented' blox)
dulapbot: Logged on 2022-02-16 00:31:42 whaack: so it'd be mighty nice to get the cement vpatch running in the near future
whaack: !e view-height
trbexplorer: block_height: 723615
trbexplorer: mins_since_last_block: 3
whaack: morning asciilifeform
whaack: and i think every1 not in the prb crowd agrees that verification has to be done everytime one syncs a node
asciilifeform: whaack: well, ideally, not stop there, an' do it errytime ~boots~ the noad ( what if disk rot? ) but sadly impractical (at least on current snail's pace db)
whaack: asciilifeform: good point
whaack: just did a check, 3.15 mn BTC are in UTXOs that a trb node would allow anyone to use as an input.
whaack: note this doesn't include all the BTC in P2SH addresses, which is likely another 5.2mn more
whaack: P2SH addresses being pay-to-scripthash, where to spend one needs to provide x s.t. that h(x) = y for a given y
whaack: miners can take the P2SH coins as well, but they cannot take them until the owner attempts to spend them
asciilifeform: whaack: i'd expect enuff spends of these in mempool to make for a fat bag
asciilifeform: esp. if yer patient.
asciilifeform: (e.g. wait for the day when massive spend from 1 of these)
billymg: whaack: i've had your explorer running constantly since the initial start, now at height ~364k (around mid 2015), no issues yet
whaack: billymg: nice, glad to hear it hasn't choked
whaack: billymg: this was the cmd i used to grab the anyone-can-spend UTXOs: (took a couple of hours to run)
whaack: SELECT SUM(VALUE) FROM output_input JOIN address ON output_input.address_id = address.address_id WHERE spending_tx_id IS NULL AND hex(address.address) like '00%';
billymg: multi-hour query!
billymg: impressive feat imo
whaack: it's a blessing when it completes, haha
whaack: billymg: what's the predicted completition time saying now?
whaack: you also have enough blocks now to run the full test suite (not a very large one, but it covers basic use of all the commands) `python`
billymg: the most recent estimate i just got at 365150 was 4 days, 4 hours, 24 mins
billymg: ah cool
billymg: i actually just ran that query for the fun of it but then killed it when i realized it's still in 2015, no segwit yet
whaack: well billymg it'd be interesting to see if there were any coins in those types of addresses presegwit
asciilifeform: there was at least 1 'anyone can spend puzzle' iirc
whaack: bbl, 20 mins
billymg also bbl
whaack: bk
whaack: asciilifeform: do you know if it's possible to create a multisig address without using P2SH?
whaack: it looks like trb has the capability with OP_CHECKMULTSIG but i'm not sure if that's a reality
shinohai: Perhaps I'm a dunce here, but let's say I want to sign a message with BTC addy using bare openssl. Converted my addy to pem, sha256 hashed message to sign, then signed and converted to hex like so: `openssl dgst -sha256 -sign privkey.pem msg.sha256 |xxd -c 74 -ps` ... how does one arrive at the base64 output that bitcoind spits out when signing?
asciilifeform: whaack: can verify'em but afaik not includes any way to bake'em
whaack: shinohai: i believe you mean base58?
whaack: trbexplorer has base58 conversion in the source, written by jfw, it's a bit of a headache, idk any command line tool that does it
whaack: asciilifeform: ah ok, makes sense
shinohai: whaack: For instance, if I sign the message "Hi whaack!" with address it outputs sig of HyH93YCEmfFXamlfbuYbiV0omZG6hH+i0cyd5kXs8EodCc+PmLol/tAazfAQlTtH9THF33VwX/mfLwIue+n9gac=
shinohai: ("it" being standard trb )
whaack: ah, i didn't know
asciilifeform: shinohai: you can do it but 1) the openssl utils hash the thing, you want to sign raw turd 2) they dun enforce the 'low-S' thing
shinohai: asciilifeform: I dun need to double hash input before signing (like you would if it was a BTC tx) ?
crtdaydreams: morn' all.
dulapbot: Logged on 2022-02-15 14:32:08 asciilifeform: crtdaydreams: reiser
← 2022-02-15 | 2022-02-17 →