1700+ entries in 0.153s
a111: Logged on 2017-05-14 22:11 ben_vulpes: one wrinkle that occurred to me as i tested this
patch against a not-completely synced node this afternoon is that satoshi's early transactions were all of the "pay to pubkey" variety, and not today's standard "pay to pubkey hash" breed.
mircea_popescu: man gotta know, if / when doing
patch work, wtf his stylistic choices are required, expected, desired to be
ben_vulpes: one wrinkle that occurred to me as i tested this
patch against a not-completely synced node this afternoon is that satoshi's early transactions were all of the "pay to pubkey" variety, and not today's standard "pay to pubkey hash" breed.
☟︎ ben_vulpes: relatedly, i have a
patch in abeyance that fixes the test target. i'll bring that out of the refrigerator and start wiring this new IsMine implementation into it.
ben_vulpes: lolyes, also worth pointing out that the
patch is indented at 2 spaces when the rest of trb is indented at 4
ben_vulpes: the
patch adds a struct to use during the indexing, and a new overload of IsMine that uses the script solver to find outputs relevant to the given address.
ben_vulpes: once this
patch works (which it almost certainly does not, as i have only finished drafting it), it will serialize unspent outputs to disk in a simple format for...later use.
ben_vulpes: this
patch adds an rpc command that eats as input one address, and walks the blockchain for outputs that spend to the address.
pete_dushenski: mod6, asciilifeform : re : 'from whom'
patch : it would definitely be a useful tool for mapping network connectivity.
a111: Logged on 2017-05-11 17:27 asciilifeform: incidentally this'd be a good adjunct to pete_dushenski et al's 'peers'
patch : see FROM WHOM a fresh node got each block.
ben_vulpes: you may now proceed to quest 3 in the Infiltrate TMSR~ saga: write a
patch demonstrating rust interop with TRB
mircea_popescu: "In future, it would be great if I could just accept any old
patch, from any urbit down to the merest comet, as long as it was sealed by ~zod. In general, I would find it comfortable, knowing that everything my urbit was running was a collection of patches, each of which had a signature, or a chain of them, originating in the urbit claiming authorship of that
patch." << wtf.
ben_vulpes: might be fun to distribute large fabric squares to bike scum that say something like "THIS
PATCH HACKS ROBOCARS" with a nonsense illustration below
mod6: <+asciilifeform> not a big deal, read+write ~= total ProcessBlock time << makes sense. stangely, i overlooked that last
patch a111: Logged on 2016-02-05 21:55 ascii_butugychag: 'A post to a technical forum discovered that the non-prime parameter was introduced more than a year ago. A note in the commit indicates that Socat was not working in FIPS mode because it requires a 1024 Diffie-Hellman prime, and added that a developer named Zhiang Wang provided a
patch with the new prime. The poster revealed that Wang works at Oracle and contributes to Socat.'
Framedragger: mircea_popescu: i don't think so, and i thought about linking this, too heh (need to update/
patch kernels if they are < 4.5)
mircea_popescu: because if "
patch after used" then it's created a partition which i can use ; and if "predict" then the inf-in-being is rightthere.
phf: mircea_popescu: if rotor4 comes out, must
patch again. there's no inf on our side despite the process being potentially inf, because we're limited by time/energy
diana_coman: mod6, list of deps for trb from what I gathered on a fresh, minimal centos box: bc, gcc, g++, gpg, wget, perl,
patch, rsync, sha512sum, unzip
mod6: meanwhile, I'll see what i can do in the next few days about putting together alf's suggested
patch a111: Logged on 2017-03-17 07:21 davout: in other TRB news, my node is happily bitcoining, doesn't seem too bothered by working with a regular HDD, and that's without asciilifeform's cache
patch davout: in other TRB news, my node is happily bitcoining, doesn't seem too bothered by working with a regular HDD, and that's without asciilifeform's cache
patch ☟︎ pete_dushenski: in other news, i'm happy to report that i've successfully run alf's wire
patch. hooray!1
a111: Logged on 2017-03-15 16:12 asciilifeform: also if you have a consistent empty 4GB of memory, you can apply my cache
patch (not yet an official vpatch, but it is a 1liner, ups bdb's cache to max)
mircea_popescu: honestly, it should just be a
patch. there's no serious reason to allow the usage of trb on tiny boxes
a111: Logged on 2017-03-15 06:47 davout: is the 'wires'
patch still considered useful?
davout: is the 'wires'
patch still considered useful?
☟︎ a111: Logged on 2017-03-14 14:36 asciilifeform: ( but to make alt-udp you gotta
patch the kernel. )
trinque: I tend to have a couple trees pressed right next to each other, when testing a
patch, when writing my own
a111: Logged on 2015-09-24 00:25 mod6: <+phf> shinohai: you probably have rm_gitignore.
patch applied, which removes .gitignore files from src/obj/nogui and nukes the folders along the way? << i said to disregard this
patch. reason is, it wipes out output dirs required by the bitcoin makefile.
mircea_popescu: asciilifeform in fact i can't actually
patch it out as it won't match the correct file huh, it does line by line removal
mircea_popescu: meanwhile /me will go research how to write a
patch to take out .gitignore altogether.
ben_vulpes: so before even thinking about CI the testing strategy needs some actual thought, planning, and likely at least one
patch. maybe more.
phf: ok, so experimental features on btcbase is that in memory presser now works. each
patch has a "tree" link, that shows you a list of files (ones that are explicitly touched by the
patch are marked as "modified"), and can look at each individual file
mod6: <+trinque>
http://btcbase.org/log/2015-02-05#1008972 << mod6, is that why this
patch did not make it in? << i don't think it was because of any such wedge. i think we held off because it was proposed that there might have been a better way to handle that through configuration files. it's all in the logs if you look in around the time that email was sent; december of '14.
☝︎ ben_vulpes: stack, for the curious: moar tests for v.pl (i'm writing them because my personal heap is too fragmented to make me a useful manual tester), read and compile a large and a small
patch from asciilifeform, ops tasks in support of WIRES, gaze into the writhing horror diana_coman needs a lasso around, and somewhere find an hour to finish up the import of phf's logs back to early 2016
phf: i kind of want a way to link useful assets to a
patch on btcbase. right now if you have a readme.txt inside a patches folder you get that included as a prelude for a patchset (
http://btcbase.org/patches?patchset=fg). i think it would be handy to include wires over ssh link somewhere on the wires
patch page..
a111: Logged on 2017-02-03 15:52 mircea_popescu: we should prolly publish a kernel
patch veen: consider a kernel
patch to bypass /dev/*random insanity with say "just open and read such-and-such file which i trust has acceptably random bytes in it"
a111: Logged on 2017-02-03 15:53 asciilifeform: not a difficult
patch, but remains to ask, for which kernel.
shinohai: Also, as side note, last night's
patch produced no different behaviour
shinohai likes to minagine this `wires`
patch as G for trb
mod6: im gonna build in your
patch and deploy. see how it goes, thank you for your submission to the ML.
BingoBoingo: asciilifeform: Bastard 0.7 ish node corrected will
patch trb nodes at convenient time, tyvm
mircea_popescu: ben_vulpes do try the above
patch, may actually bring you back above waterline.
thestringpuller: mod6 asciilifeform dunno if just weird artifact along with bad luck or actual potential problem, but my node running on slowest hardware is only receiving BASTARD BLOCK s. I'm connected to deedbot (a trusted node) with -addnode. using same
patch tree as hanbot
BingoBoingo: Coding
patch to simply say "no" to compact blocks and restore TRB/PRB communion would likely be trivial, BUT setting that precedent is impossibru
BingoBoingo: <asciilifeform> also note that if you built with malleus
patch, you will be kickbanning prb peers as soon as they disgorge a prbism of any kind (e.g., 'bloom filter' command) << Bloom isn't what disconnects most PRB nowadays. It is "BIP 151 compact blocks".