log☇︎
1900+ entries in 0.152s
trinque: http://btcbase.org/log/2017-06-30#1677141 << hadn't had a chance to pick it up for a bit; got time this weekend though. item I've got can maintain balances, send and mark-paid invoices. I think I'll handle deposits manually and call that a first cut, trb address tracking without a privkey isn't there yet. ☝︎☟︎
mod6: (to update the makefiles. http://thebitcoin.foundation/tickets/trb_tickets.html#36)
sina: hows trb stuff comin along
asciilifeform: afaik deedbot is currently the only thing auto-signing ( inside its tx-issuing trb )
asciilifeform: hey, they gotta keep inmat^H^H^H^H^Hstudents from hosting warez/trb/etc terrorisms somehow!1111
mod6: ah right on. just doing trb related testing :]
shinohai: Cool ... that trb Makefiles thing ?
pete_dushenski: at least i like it. always wondered what versions were connecting to trb nodes before.
mod6: <+shinohai> trb node should be back up soon, motherboard still boots up, replaced nic with external model. << good deal :]
shinohai: trb node should be back up soon, motherboard still boots up, replaced nic with external model.
shinohai: Looks like box running my trb node was a casualty of the storm ... fried nic despite my best efforts to revive.
asciilifeform: it will have to be confiscated from the monkeys, like trb was.
shinohai: np, glad to help and love to see trb progressing and more peeps contributing.
mod6: and I started working on ticket #36 for trb, possible move of the deps folder for trb
sina: trb?
mircea_popescu: allows you a trb editing environment at any rate
mod6: root@trb-dev:/home/mod6/fg1# dd iflag=fullblock if=/dev/ttyUSB0 of=fg1.fg1.bin
mod6: root@trb-dev:/home/mod6/fg1# stty -F /dev/ttyUSB0 115200 raw -echo -echoe -echok
ben_vulpes: estos functionan: http://thebitcoin.foundation/trb-howto.html
ben_vulpes: CluelessNoob: solamente usandolo http://thebitcoin.foundation/trb-howto.html
asciilifeform: what trb item have you tested, IamAGirlsoInever ?
mod6: http://btcbase.org/log/2017-05-25#1661674 << was thinking there, for those who would want it, a model where guy asks for N bytes of entropy via FG. would generate N bytes. base64 encode the binary entropy file (similar to trb deps), place the sha512 output hash of the base64 decoded file along with the ent & dieharder output in a clearsigned message, then PGP encrypt it to the requester. ☝︎
asciilifeform: unrelatedly, i have nfi who trb node 208.94.240.42 belongs to, but it's been stuck in the 300,000s for ~ages~
mircea_popescu: once that is in place, a proper p2p mechanism can be built and trb will work way the fuck better than prb ever could.
mircea_popescu: wires patch is not different ; still same trb.
asciilifeform: meanwhile, in the world of sad prototypes : asciilifeform discovered ( and why did it have to be ' asciilifeform discovered ...' when other folx were nominally also testing...) that trb node with 'wires' still happily falls behind by 100s of blox, and never catches up,
a111: Logged on 2017-05-23 03:39 mod6: http://btcbase.org/log/2017-03-10#1624240 << regarding alf's suggestion here, is there any objection to adding this log link to ticket: http://thebitcoin.foundation/tickets/trb_tickets.html#6
mod6: !%a trb C "Move the deps folder" "Move trb deps directory which contains frozen artifacts outside of the bitcoin project directory. This will avoid unwanted removal of artifacts upon a `make clean`."
mod6: re: http://thebitcoin.foundation/tickets/trb_tickets.html#1 << this one seems to be resolved with the use of -lows. I hesitate to remove the ticket, but a link to the patch might be worthwhile here.
mod6: http://btcbase.org/log/2017-03-10#1624240 << regarding alf's suggestion here, is there any objection to adding this log link to ticket: http://thebitcoin.foundation/tickets/trb_tickets.html#6 ☝︎☟︎
danielpbarron: i'm doing this one http://thebitcoin.foundation/trb-howto.html
shinohai: Well despite the fact it took me what felt like eons, i did read ref client src when I started fiddling with trb.
asciilifeform: at one time he grudgingly tested some trb
mod6: altogether, i'm trying to stay focused on trb too. and learn these other topics as I go.
ben_vulpes: lolyes, also worth pointing out that the patch is indented at 2 spaces when the rest of trb is indented at 4
a111: Logged on 2017-05-14 03:54 ben_vulpes: any objections to a vpatch doing away with the truncation of hashes in the trb log?
asciilifeform: reference trb gotta keep working, uninterrupted,
asciilifeform: idea , however, is that it will run blox past trad trb ( netless , mempoolless trb ) as 'final court'
asciilifeform: hence why all of asciilifeform's trb work from month or so ago and forever more, is about losing the cpp hairball.
ben_vulpes: any objections to a vpatch doing away with the truncation of hashes in the trb log? ☟︎
trinque: trb has been running on this apu2 for about 20min, ~100k blox
pete_dushenski: i'd like to take this opportunity to introduce 'constantine' (37.59.43.190) as an infrastructure trb node. he will be replacing 'laocoon' (62.113.203.216), who will be henceforth relegated to testing duties. cheers!
trinque: I dunno what strategic sense it makes to as yet have no mechanical way to stamp out a full trb node
asciilifeform: it syncs when hits a fellow trb by accident and that's mostly it.
asciilifeform: if you believe the heathen chart ('bitnodes'), 'falcon' mega-relay-network etc has ~same number of nodes as... their count of trb.
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 the sense that rather make that, best make new comp. trb-i all over again.
asciilifeform: achtung, panzers! anyone who noticed that his trb wire to dulap dropped last night -- the thing was rebooted (without my permission) ~13 hours ago.
asciilifeform: and lol , mircea_popescu's lament is ~exactly asciilifeform's ~yearly 'when i stop writing trb fixes, they stop getting written'...
mod6: i'm pretty excited about tmsr~ / trb/trbi things upcoming.
Framedragger: re. per minute, i guess i should reach out to consult first eh - this was borne from a solipsistic "me as a customer" consideration: e.g. i want to test out some trb feature across multiple different instances, i need good i/o and memory; monthly costs would not be trivial (for the purpose at hand), so i wish to be charged on smaller timescales.
mircea_popescu: nitpick : move 2016 to 2017 on trb.org main page
trinque: obviously I'll also make special cases for things like trb deeds.
deedbot: http://cascadianhacker.com/a-brief-foray-into-the-swamp-of-trb-boost-usage << CH - A Brief Foray Into The Swamp of TRB Boost Usage
mod6: I've been meaning all month to get to do some ticket reorg for trb. I'm still going to try to it this week here.
mircea_popescu: what i was looking for was, supposing the whole of trb looks like : http://wotpaste.cascadianhacker.com/pastes/YOK7i/?raw=true then something like : http://wotpaste.cascadianhacker.com/pastes/qGO07/?raw=true
mod6: It wouldn't take much more effort to add the AcceptBlock values into the trb_offline_eatblock.png if that's wanted.
mod6: if you're looking at this chart: http://www.mod6.net/eatblock-test/trb_offline_eatblock.png
asciilifeform: it resembles trb 'wires' .
trinque: but yeah, not required to have musltronic trb
lobbes: Well, I'm just trying to stand up a gentoo that'll run trb. Seems like my kernel choice may not be as important as I thought as long as gcc is musltronic?
ben_vulpes: trb builds with buildroot though, does that with which the kernel is compiled affect that pipeline?
asciilifeform: glibc is also not supported for trb.
asciilifeform: for trb, that is.
lobbes: Perhaps musl is better option? Fwiw, I posted over on gentoo forumz with my specifics, but am not versed enough to know if the suggestions they gave (e.g. using glibc) will fuck me over building trb or not: https://forums.gentoo.org/viewtopic-t-1062324.html?sid=c3ea68da31445ec3e870e5344a443dd3
lobbes: So, I'm midway through my first gentoo adventure. Currently on the compile kernel step (genkernel), but running into funkiness with uClibc errors. My question is: if I abandon uClibc for, say, glibc, will I have issues building trb? (I remember reading in logz that trb doesn't use glibc)
asciilifeform: y'know, when trb sits like idiot and waits for bdb to disk i/o.
asciilifeform: ^ all but the last is mostly wasted on trb
mircea_popescu: which is how trb-i even became an item.
asciilifeform: today - 'trb-i', ciphers of known strength, a few others.
ben_vulpes: all sorts of interesting and amusing barf compiling trb with -std=c+=11
ben_vulpes: unrelatedly, anyone besides me ever try compiling trb with -std=c++11?
ben_vulpes: asciilifeform: what was the reasoning behind your call that replacing trb's boostisms with c++11isms was an assault on grandfathers pistols? trb mustest compile with old gcc's?
mircea_popescu: this might even fix it, but it's not certain, given the festival of adhoc magic numbers trb is also known as.
trinque: looks like trb was not pleased with python's json.dumps() taking upon itself to use scientific notation after I changed fee and deed amounts.
trinque: ^ PSA: I'm looking at some kind of trb wallet bug which is reporting suffient balance, but insufficient when trying to send a tx
mircea_popescu: well, hopefully this problem gets resolved by crap not making it into trb-i
BingoBoingo: pete_dushenski: When do we get G5 trb sync stats?
ben_vulpes: anyone ever see a trb/buildroot run hang at `checking for gcc float-conversion bug...` ?
shinohai: I was gonna say, all those trb artifacts were huge
shinohai: trb blocks, now individually wrapped for your convenience.
asciilifeform: i find it slightly outrageous that i have a pressed aluminum ratheadlinux from 1990s but not a pressed aluminum gcc4.9 or trb-genesis etc
mircea_popescu: merv, or generally the mongol reduction of persia from a coupla million to a coupla hundred thousand is the fundamental civilisational act. not the building of the scum, but the purging of it. much like "writing prb" is not an achievement in computer science ; but purging it into trb is. ☟︎
asciilifeform: i propose a declaration of 'tx replacement is an attack against sane bitcoin and whoever does it, is the forker, and not us, who thereafter ban it in trb and subsequent proggies.'
ben_vulpes: http://btcbase.org/log/2017-04-04#1636874 << directly relevant. afaict, producing a transaction with trb code boils down to making a 'ctransaction' with 'vin's shaped per the constructor http://btc.yt/lxr/satoshi/source/src/main.h?v=wires_rev1#0261 ☝︎
pete_dushenski: http://www.gereports.com/object-sprayed-worlds-blackest-material-freaking-us/ << ok vantablack is fucking cool. makes me want to paint trb node with it. 'capable of absorbing 99.96% of ultraviolet, visible, and infrared light'
asciilifeform: let's say we find that, e.g., gcc past 3.x embeds an off-by-one-ization in memcpy() , dependant on payload, and that it is triggerable specifically in trb tx processing.
trinque: just caught, like trb, here's how it was
trinque: we discussed this for trb openbsd patches
ben_vulpes: well yes i'm familiar with how the bits are laid down, but i am less familiar with how trb handles it internally
asciilifeform: i have plenty of 'c machines' right here that cannot run trb (on account of 'too small addr space' or 'too slow clock', take your pick.)
mircea_popescu: asciilifeform not trb's identity was being defined. the c machine's was.
asciilifeform: at any rate this is a bizarre line of thought. trb (or rather, bitcoin, the existing network) has any kind of long term future ~strictly~ if it can be entirely separated from the cpp abortion.
mircea_popescu: yes. definition of "lisp machine" ALSO IS "item which runs trb"
asciilifeform: trb (the currently existing item) could quite conceivably run on entirely different type of machine, under emulation (smbx , for instance, shipped... believe -- a c compiler, in genera. along with fortran, ada..)
mircea_popescu: c machine does have a specific meaning, and it is "item which runs trb."
asciilifeform: ( this also ignores the -- screamingly evident -- fact of trb being ~algorithmically~ defective. as explored on several occasions here. )
mircea_popescu: "c machine" defined as "item that runs trb" is thereby fixed through becoming more apparent than it previously was.
mircea_popescu: at the very least things were learned about how trb is ~supposed to~ function, and this is sufficient to qualify it.
asciilifeform: do what you will to trb, it is still written in idiot language that does not check bounds, on idiot iron that does not check bounds.