trilemaossasepiatrinquetrilema-hanbotagriculturalsupremacyeuloraspykedlobbespizarro
146d 41m17h 28m32d 2h 54m58d 23h 28m16h 7m22h 17m22h 15m7d 23h 6m26d 22h 31m
krankendenken



feedbot: http://ztkfg.com/2020/07/spanish-practice-log-10-july-5th-2020/ << whaack -- Spanish Practice Log 10, July 5th 2020
feedbot: http://ztkfg.com/2020/07/spanish-practice-log-12-july-7th-2020/ << whaack -- Spanish Study Log 12, July 7th 2020
feedbot: http://ztkfg.com/2020/07/spanish-practice-log-11-july-6th-2020/ << whaack -- Spanish Practice Log 11, July 6th 2020
jfw: I'm alive, just in a bit of a hole owing to various accumulated sins against time. Light's on the horizon though.
jfw: whaack: much of the code in gbw-node would be directly useful for a block explorer, indeed. I would definitely suggest some schema tweaks though.
jfw: for example adding a table to track blocks and factoring block_hash and block_height out of tx into that, referenced by integer primary key
jfw: (32 byte hash -> 8 byte rowid, multiplied by every transaction in bitcoin would save quite some space I expect.)
jfw: and removing the "input" table (which I believe I mentioned in the schema article)
jfw: whaack: as is it can't be told to track "all" addresses; there's a list and that list won't fit all possible seen & unseen addresses. If you mean changing the code to remove the 'watched address' checks and index all seen addresses, then yes that's the way to go.
jfw: Possibly even the way gbw-node itself ought to be - though the full index will have a hefty size cost.
jfw: incidentally if TRB had used SQL this tradeoff would literally be a one-liner CREATE INDEX.
jfw: 2T/16G wouuld be plenty beefy enough, indeed 1T/4G probably fine
jfw: the extra ram can always be thrown at database cache though so won't hurt.
jfw: re make errors, haven't looked specifically but without my patch, repeating 'make' can indeed produce different errors because it gives 'make' no way to see that an openssl/bdb/boost build failed and it just proceeds.
jfw: python errors in trb build? that's a bit surprising, my guess would be Boost as it has some python binding thing, "shouldn't" be necessary for trb tho
jfw: however 2.7 is a hard requirement for gbw-node as I haven't found a non-glacial alternative to memoryviews given the volume of deserialization it has to do.
jfw: whaack: re block 170, I bet your problem is that the site you got the address from is revising history to imply that "1-addresses" were used back then. They weren't; the standard script was pay-to-pubkey, no hash. I dunno how it was presented in the early UI but at least would have been a longer string.
jfw: if you look at the 'disassembly' of the scriptPubKey on such a site, and compare to a more sample, you'll see the difference.
jfw: *more recent sample
jfw: "more recent" as in past the first couple 10k, iirc.
jfw: whaack: I un-lazied and clicked your link, this is indeed the situation.
jfw: gbw-node indexes only actual "1-addresses", i.e. scripts matching the standard p2pkh form. For a block explorer, a middle ground between that and writing special cases for all sorts of weird species of script would be indexing the script itself as a blob.
jfw: out_script_address is the filtering/extraction function there.
whaack: jfw: Addressing a few things: Yes I meant changing the code to remove watched addresses and index all seen addresses.
whaack: jfw: Indeed, I believe the problem was with building Boost.
jfw: whaack: cool. Off to sleep now but I should be back tomorrow.
whaack: jfw: gn
diana_coman: http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027648 - o.O *what* gnat did you ever install there to have such monstrosity as gcc 8.* ?
sonofawitch: 2020-07-07 22:50:20 (#ossasepia) whaack: Looks like the problem may have been that my path variable was wrong, setting my gcc to some gcc 8.x used by GNAT
diana_coman: http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027650 - I guess it's good to know it requires 2.7
sonofawitch: 2020-07-08 00:49:46 (#ossasepia) whaack: ^ This was the problem, I had a successful build by switching my python to 2.7
diana_coman: http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027656 - glad to hear you're alive! wondering if it's enough of a hole to keep you from repeating it in the future, too.
sonofawitch: 2020-07-08 04:57:33 (#ossasepia) jfw: I'm alive, just in a bit of a hole owing to various accumulated sins against time. Light's on the horizon though.
diana_coman: http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027663 - heh.
sonofawitch: 2020-07-08 05:13:57 (#ossasepia) jfw: incidentally if TRB had used SQL this tradeoff would literally be a one-liner CREATE INDEX.
whaack: jfw: Interesting, I did not know that once-upon-a-time outputs provided a script w/ a pub key that was not hashed. http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027674 seems like a good plan.
sonofawitch: 2020-07-08 05:35:48 (#ossasepia) jfw: gbw-node indexes only actual "1-addresses", i.e. scripts matching the standard p2pkh form. For a block explorer, a middle ground between that and writing special cases for all sorts of weird species of script would be indexing the script itself as a blob.
whaack: diana_coman: gnat --version gives "GNAT Community 2019 (20190517-83)" on the first line
diana_coman: whaack - ah, that explains it, yeah; but I would think you'd run into all sorts of other trouble trying to compile that client on that version of gcc, really; not like I don't have the 2016 gnat mirrored on my site and all that, even if you don't want to go through the more intricate steps of building one of ave1's versions, huh.
feedbot: http://ossasepia.com/2020/07/08/eucrypt-addition-keccak-file-hashing/ << Ossa Sepia -- EuCrypt addition: Keccak File Hashing
whaack: diana_coman: I am not quite sure why I wound up with that monster gnat, I believe it was from doing the eulora install hastily. In any case I made sure to compile bitcoind with gcc 4.4.7
feedbot: http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/ << whaack -- Building TRB on CentOS 6.9, Notes on a Few Gotchas
feedbot: http://trilema.com/2020/the-worlds-great-though-unfortunately-populated-sau-mula-n-beige/ << Trilema -- The world's great though unfortunately populated, sau mula-n beige
feedbot: http://ztkfg.com/2020/07/how-to-test-gbw-node-by-viewing-the-first-ever-transaction-containing-a-p2pkh-address/ << whaack -- How To Test gbw-node By Viewing The First Ever Transaction Containing a p2pkh Address
diana_coman: seems like whaack is having fun with jfw's gbw-node, not bad
jfw: :)
jfw: http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027656 - might even be. "woah, time management & communication skills aren't just for YH or TMSR but the outside world too?" kinda thing
sonofawitch: 2020-07-08 04:57:33 (#ossasepia) jfw: I'm alive, just in a bit of a hole owing to various accumulated sins against time. Light's on the horizon though.
jfw: ah wrong quote - http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027684
sonofawitch: 2020-07-08 09:55:52 (#ossasepia) diana_coman: http://ossasepia.com/2020/07/01/ossasepia-logs-for-Jul-2020/#1027656 - glad to hear you're alive! wondering if it's enough of a hole to keep you from repeating it in the future, too.
jfw: on the bright side, I got 4200 words out in two days or thereabouts.
diana_coman: jfw - was that sudden writing-productivity necessity induced? (little time, must-deliver thing)
jfw: yeah
jfw: whaack: what V are you using these days?
diana_coman: jfw - aha; basically there's too little real pressure here to deliver proper change, lol.
jfw: money's the best alternative I know of to actual whips in that regard
whaack: jfw: I'm using v.pl version 99991
jfw: "grades" stopped doing it for me around age 12
jfw: whaack: thought so. you might notice it's quite slow on pressing or anything else on the trb tree; I've since patched it for that
diana_coman: jfw - supposedly it was internal, hence wanting to be here in the first place; not "grades", certainly not; and for that matter, if a 30 yo was still after grades as motivation, ugh.
whaack: jfw: It wasn't instant, but also not very slow on my machine. Regardless I'll take a look at your article about fixing up v.pl
jfw: diana_coman: do you mean the "real pressure around here" as internal?
diana_coman: jfw - I mean that via an irc chan I can provide mainly feedback, not whips! and so it's unsurprising that it works only to the extent that there is internal motivation for that change; I guess previously, the missing-the-tmsr-boat provided additional whip but once that gone, it shows if there was anything else or to what extent.
jfw: I see I've gone silent here. I won't say I've had much internal motivation to write for example, otherwise sure, I'd have been doing it more already. As far as change as a whole, not sure what to make of it yet.
diana_coman: eh, internal motivation is more general than that sort of "to write" or "to do X", it's basically motivation to *improve*; the idiocy of compartmentalizing is just as much idiocy when/if applied to this as to anything else; other than that, "choice" comes into it only when indeed, there are so many opportunities identified and *taken* that there's just no time for another one - more of a mythical
diana_coman: situation than ever a real one.
jfw: I think I see.

Random(ossasepia) | Download daily DB snapshot | Get Source Code