a111: Logged on 2017-10-06 13:55 diana_coman: hi mod6, I've set up a public node running vanilla trb, at 103.36.92.112; it's still getting up to date so probably not of much use yet but it's meant to stay as it is anyway (it's at ~260k atm)
diana_coman: hi mod6, I've set up a public node running vanilla trb, at 103.36.92.112; it's still getting up to date so probably not of much use yet but it's meant to stay as it is anyway (it's at ~260k atm)
mod6: This will be quite awesome. "Here lies mod6. emerge trb" it will say.
mod6: yeah, i think emerge a trb would be the ticket, no?
mod6: diana_coman, asciilifeform, mircea_popescu, ben_vulpes, et. al. ok TRB HowTo updated with 'bzip2 tools [including bzcat]'/
mod6: <+diana_coman> mod6, the online build (at least that one) of trb seems to require also bzip2 -> to add to deps at http://thebitcoin.foundation/trb-howto.html ? <+diana_coman> asciilifeform, barf: http://p.bvulpes.com/pastes/wJ9yF/?raw=true << noted, will add, thanks!
asciilifeform: ( btw is it clear that buildroot is only part of the trb universe because we dun have a musltronic linux to do ordinary stator builds in ? )
diana_coman: mod6, the online build (at least that one) of trb seems to require also bzip2 -> to add to deps at http://thebitcoin.foundation/trb-howto.html ?
asciilifeform: and iirc we also had thread re how crapple is not in business because asciilifeform reads trb coad and 1970s 'химия и жизнь' on a crappad
asciilifeform: ( remember, an unsynced trb node rejects ~ALL tx )
ag3nt_zer0: yeah hmmm as i went through the required stuff listed on trb node setup page, all of them said "______ is already the newest version"... all except the sha512sum
ag3nt_zer0: following the guide for trb node creation, in making sure i have correct packages and binaries, seems everything is fine but "sha512sum" read package lists, built dep. tree, read state info, and then says: E: Unable to locate package sha512sum - is this going to create problems and if so how might i fix?
asciilifeform: ^ asciilifeform's very painstaking 'trbfication' of koch
diana_coman: asciilifeform, heh, thanks; ofc I have the keys otherwise - I was just getting trb on a new box and getting the keys for it via deedbot seemed most straightforward
asciilifeform: diana_coman: and in your trb wot dir likewise.
BingoBoingo: <mircea_popescu> teh network is disrupted to all hell fwiw. << On the plus side, most of the public facing trb identified nodes are back caught up to sync
trinque: anyhow got payments bot to ship, which while running long is forcing me to develop sane processes around airgapped trb use
trinque: been cranking on being able to cut transactions on an airgap machine with only trb+deps
asciilifeform: http://btcbase.org/log/2017-09-14#1714258 << funkenstein was an odd d00d: shat on trb, but lifted it wholesale for use in his altwhatever; today hangs in kakolandia and misses no chance to hurrdurrmpisafraud etc
a111: Logged on 2017-09-14 06:03 trinque: http://p.bvulpes.com/pastes/GCYtI/?raw=true << example, simple trb-addr proggie
trinque been spelunking in the trb innards a while, close to wrapped up on a few little tools to go hexstring->privkey->pubkey->addr relying solely on existing trb innards.
asciilifeform: and so long all trb nodes ?
mod6: <+shinohai> Just sitting here with my Baroness hoping you haz good news re: trb or ada experiments? << ah, just trying to catch up on this 2nd megal0g
shinohai: Just sitting here with my Baroness hoping you haz good news re: trb or ada experiments?
mircea_popescu: rothbart if you have it in a portable data format, can just feed it into trb
asciilifeform: 1) move the btc using trb, to new addr 2) import (now empty on btc chain) privkey into shitcoin node 3) empty the shitcoins into a gox 4) sell
asciilifeform: move the btc using a trb node
fromloper: (I will be running trb soon, though!)
mircea_popescu: it'd help if we first had a trb wallet model.
asciilifeform: http://btcbase.org/log/2017-09-10#1711819 << prb wasn't involved here, was operating on trb .dat's
mod6: <+mircea_popescu> http://btcbase.org/log/2017-09-10#1711763 << yes, to fish out CHANGE addresses in trb you must FOLLOW txns trees to the unspent leaf. true pain in butt. << ah, good point. i'll make a note of these requests.
mircea_popescu: http://btcbase.org/log/2017-09-10#1711763 << yes, to fish out CHANGE addresses in trb you must FOLLOW txns trees to the unspent leaf. true pain in butt.
lobbes: Just ordered my 480gb ssd for my soon-to-be trb node. Hopefully big enough, but after review of the logs it sounds like the things die long before they fill
trinque: shinohai: 4.9.2's in deedbot for trb deps btw
ag3nt_zer0: Hello TMSR... trying to implement trb here. What is the proper way to "save the PGP public keys" before placing them in .wot? Do I simply copy the entirety of the text (including -----BEGIN PGP PUBLIC KEY BLOCK-----) revealed at the link provided by deedbot, place that into a text editor, and then save as .asc?
BingoBoingo: http://btcbase.org/log/2017-09-01#1708137 << Until they try to run a node... Syncing TRB far less painful that keeping up with Ethereum...
mircea_popescu: shinohai: "connections" : 5, << i think that's how many of the trb list are actually up atm
asciilifeform: a trb node that's perpetually months (or yearz) behind topheight, mainly sits around rejecting tx all day long
asciilifeform: because even in whole 1G i never saw trb live for >week
asciilifeform: how long your longest run of trb on pogo, danielpbarron ?
shinohai: cashmoney: Since you list `linux` as a hobby, have you tried http://thebitcoin.foundation/trb-howto.html yet?
asciilifeform: it is why i work on, e.g., trb, despite having scarcely any coin personally.
asciilifeform: probably never yet seen trb, either...
hanbot: following fun-filled central american day of rando power outages, mid-sync trb aborts at startup with http://wotpaste.cascadianhacker.com/pastes/Kub6l/?raw=true
mircea_popescu: ah. no i meant, is jhvh1 sitting atop a trb node feeding !~blocks
a111: Logged on 2017-08-24 14:59 runsegshet: TRB how to isn't truly noob proof. I have never even used Linux. I'm not qualified to run a TRB node it seems. I'm just a user who wants my BTC to remain mine
mircea_popescu: um. how would trb see the tx anyway ? it dun interpret segwit
asciilifeform: stock trb dun help much
runsegshet: What about hardware wallets like Ledger nano? Are those secure enough to hold TRB safe?
runsegshet: TRB how to isn't truly noob proof. I have never even used Linux. I'm not qualified to run a TRB node it seems. I'm just a user who wants my BTC to remain mine
mircea_popescu: anyway, i'm not sure what's easier, eulora install or trb install. they're very similar processes for some reason (har har)
a111: Logged on 2017-08-24 13:12 runsegshet: Also is core hard forked from TRB? How would one be able to mine TRB instead?
mircea_popescu: http://btcbase.org/log/2017-08-24#1702779 << core hasn't yet hardforked from trb. their "segwit" thing is a "soft fork". basically they intend to make everyone's transactions be blockchain messages instead of actual transactions.
mircea_popescu: http://btcbase.org/log/2017-08-24#1702761 << run trb. follow mod6 's instructions, it's a relatively painless half hour install on most any sane linux.
diana_coman: runsegshet, so learn; run your own node keeping your bitcoin; start perhaps from http://thebitcoin.foundation/trb-howto.html
asciilifeform: the reason why mike_c's node appears 'stalled' is that it stopped fetching blocks. trb's block sync behaviour is unspeakably moronic, it will attempt 'long sync' ONCE, on warmup
asciilifeform: if trb node is not fetching blocks, but is not showing symptoms of 'black hole'
asciilifeform: !~later tell mike_c http://btcbase.org/log/2017-08-23#1702508 << this is NORMAL behaviour for a trb node. and see below re 'stalls' :
ben_vulpes: bringing a trb node up on whatever gentoo image scaleway has; 'pthread: command not found', log notes indicate patch necessary to cmake CheckIncludeFiles.cmake, investigation of which shows...no cmake on this box
mike_c: doh. trb node stalled out.
pete_dushenski: mircea_popescu: it predates trb by a bit at least, ya.
asciilifeform: mircea_popescu: hilariously wrong description of trb
a111: Logged on 2017-08-22 23:56 mod6: <+mircea_popescu> and speaking of nodes and things, https://coin.dance/nodes << never saw this one before, pretty cool blurb there on trb.
BingoBoingo: <mircea_popescu> i mean, a trb capable machine is somewhere in the 50-100 bux / month range, certainly an expense but not the end of the world. << Negrodamus, i.e. 192.187.99.74 rents for less
a111: Logged on 2017-08-22 23:56 mod6: <+mircea_popescu> and speaking of nodes and things, https://coin.dance/nodes << never saw this one before, pretty cool blurb there on trb.
mod6: To all L1 who do not have a TRB node yet, please start this process now-ish, and let me know if you need a hand standing one up when ready.
mircea_popescu: i mean, a trb capable machine is somewhere in the 50-100 bux / month range, certainly an expense but not the end of the world.
mod6: I guess I'd like to see all of L1 at least have a trb node at least sync'ing by years end. That's a good goal.
mod6: <+mircea_popescu> and speaking of nodes and things, https://coin.dance/nodes << never saw this one before, pretty cool blurb there on trb.
mod6: Also all, I have updated the howto page to link the trusted-nodes page as well: http://thebitcoin.foundation/trb-howto.html
asciilifeform: http://btcbase.org/log/2017-08-22#1702394 << it is zoolag, it is resyncing, and ( i assume everybody knows ) it is ~impossible to usefully connect to a trb node that is syncing
asciilifeform: spyked: trb is very long way from 'sane object' but otherwise yes.
spyked: valentinbuza, my issue is that "framework" approach (as used in today's terminology) is utterly anti-engineering. one can (on the condition that they know what they're doing! and there really is no alternative to that) write own software from first principles without requiring 3rd party. or, use 3rd party only to strip of shit and output sane object (e.g. http://btcbase.org/log-search?q=trb ), which is distinct from "framework".
a111: Logged on 2017-08-21 22:31 asciilifeform: i don't much like the phrase 'trusted nodes', when you connect to trb node, you get plaintext tcp, and 0 guarantees re who or what you're actually talking to.
asciilifeform: i use it in workstations. but the cost is imho misplaced in a trb node, which are supposed to be a redundancy layer p2pfully in themselves !
a111: Logged on 2017-08-22 01:42 pete_dushenski: in other nodes, my latest 0-fullheight trb sync experiment was completed in a hair under two weeks. nb i say!
a111: Logged on 2017-08-21 22:22 hanbot: say, where's the current list of trb nodes? http://thebitcoin.foundation/trusted-nodes.html << accurate?
asciilifeform: pete_dushenski: as i understand it's a couplea line patch to trb
pete_dushenski: mod6: ya, it was ~half the time of the last 0-fullheight trb sync i tried maybe 18 months ago, but that was on hdd and this was on ssd :)
pete_dushenski: in other nodes, my latest 0-fullheight trb sync experiment was completed in a hair under two weeks. nb i say!
mod6: <+hanbot> say, where's the current list of trb nodes? http://thebitcoin.foundation/trusted-nodes.html << accurate? << I do update it as people tell me.
asciilifeform: !~later tell ben_vulpes was it you who had a trb patch abolishing the idiotic truncation of block and tx hashes in debug.log ? where did it go ?
asciilifeform: i don't much like the phrase 'trusted nodes', when you connect to trb node, you get plaintext tcp, and 0 guarantees re who or what you're actually talking to.
hanbot: say, where's the current list of trb nodes? http://thebitcoin.foundation/trusted-nodes.html << accurate?
spyked: anyway, I'm interested in getting a Lisp machine up. also, getting a trb node up once I get some hardware for it
asciilifeform: !~later tell mike_c http://btcbase.org/log/2017-08-19#1700623 << why was it necessary to use closed turd client ? ( what's the actual diff in the lolfork anyway ? the 2mb thing ? could exist as a lulzpatch for trb, even, in principle )
asciilifeform: ACHTUNG panzers!! trb node 'zoolag' is back in business, this time as ordinary linux box -- syncing from 0 . same ip as prev.
asciilifeform: mike_c: congrats on building trb, incidentally
mike_c: it is using /var/trb/trb54/bitcoin/build/toolchain/usr/bin/x86_64-therealbitcoin-linux-musl-g++, so I guess it exists..
mod6: can you also do me a favor; `ls -al /var/trb/trb54/bitcoin/build/toolchain/usr/bin/` then paste.
mod6: ok, next: `cd /var/trb/trb54/bitcoin/deps ; cp ~/*.asc .` -- hopefully, in your ~ you only have .asc deeds, and not, say, other stuff...
mike_c: ./toolchain/usr/include/ncurses -O2 -I/var/trb/trb54/bitcoin/build/buildroot-2015.05/output/../../toolchain/usr/include --param max-inline-insns-single=1200 -fPIC -c ../ncurses/lib_gen.c -o ../obj_s/lib_gen.o
mod6: phf: <+mike_c> this exists: /var/trb/trb54/bitcoin/build/toolchain/usr/x86_64-therealbitcoin-linux-musl
phf: mike_c: does this exist /var/trb/trb54/bitcoin/build/toolchain/usr/bin/x86_64-therealbitcoin-linux-musl-gcc ?
phf: actually i've no idea what you're talking about, but considering "seals" i assumed it's trb
asciilifeform: other idea is to demonstrate that trb can work without riding on top of existing telecom structure.
asciilifeform: also interesting to mike_c will be the 'trbi' threads..
mod6: <+mike_c> mod6 - you mentioned I might need some hand holding. anything I need to know that's not in http://thebitcoin.foundation/trb-howto.html ? << that /should/ be all you need to know. less steps in the on-line version, but use which ever you need.
mike_c: mod6 - you mentioned I might need some hand holding. anything I need to know that's not in http://thebitcoin.foundation/trb-howto.html ?
mod6: <+mircea_popescu> mike_c but look at the new v-based trb build << yah, if you're interested in standing up a node, we'll talk ya through it.
mircea_popescu: mike_c but look at the new v-based trb build
a111: Logged on 2016-02-17 21:08 asciilifeform: (the folks who laughed when i said 'no curl on trb build box' - still laughing ?)
asciilifeform: the index won't read by trb.
trinque: 4.5gb for trb build, not blockchain
a111: Logged on 2017-08-10 21:46 edivad: in the case of segwit, this means that trb won't care about segwit blocks and as long as they will complies with the "hard rules" (I really don't know how to explain myself better) they will be accepted?
a111: Logged on 2017-08-10 21:38 edivad: in my case i've recycled a previous bitcoin core blockchain and fired up TRB
mod6: ok updated, take another look: http://thebitcoin.foundation/trb-howto.html
edivad: in the case of segwit, this means that trb won't care about segwit blocks and as long as they will complies with the "hard rules" (I really don't know how to explain myself better) they will be accepted?
edivad: i've understood that TRB = purity
trinque: looks like my trb dir weighs 4.5gb over here; something like that should be fine
edivad: 2nd) the second time that i've started TRB, it was complaining that wallet.dat was corrupted (this wallet.dat was generated from latest core, so i suppose is deterministic, is this the reason for being rejected?)
edivad: the 1st) when i started for the first time TRB, he was bitching that myip=something wasn't present on my .conf. Is this a TRB specific requirement?
edivad: in my case i've recycled a previous bitcoin core blockchain and fired up TRB
edivad: i think that is important to add to the guide that the average joe will need at least 6 gb of space in his hard disk to be able to compile from scratch TRB
shinohai: I did: shinohai@trb locate CheckIncludeFiles.cmake
mod6: <+shinohai> mircea_popescu: The cmake in Debian/Ubuntu repositories used to have that pthread bug, first time I built a trb with `V` that happened. << i don't remember ever having this issue fwiw
shinohai: mircea_popescu: The cmake in Debian/Ubuntu repositories used to have that pthread bug, first time I built a trb with `V` that happened.
hanbot: http://btcbase.org/log/2017-08-10#1696608 << looks crisp, though imho "To build TRB, you are going to need some basic requirements on your system environment." is spurious unless said requirements are specified...the next line about packages and list of same seem sufficient.
edivad: i promise that this will be the last emergency troubleshooting about TRB
mod6: alright, I have published those changes to : http://thebitcoin.foundation/trb-howto.html
edivad: yes, following these instructions since the beginning: http://thebitcoin.foundation/trb-howto.html
edivad: i'm a junior sysadmin trying to install trb on my VPS without success
asciilifeform: also i thought mention of mp/trb/et al were a hangin' offense at tardstalk
a111: Logged on 2017-08-06 20:05 mod6: http://btcbase.org/log/2017-08-06#1694494 << did you use your vtron here? My vtron does not support bsd at this time, when we have a working trb on bsd, then will support bsd.
mod6: http://btcbase.org/log/2017-08-06#1694494 << did you use your vtron here? My vtron does not support bsd at this time, when we have a working trb on bsd, then will support bsd.
asciilifeform: and there's a history of trb nodes of various types perma-wedging there
asciilifeform: this thing behaves precisely like trb sans locks patch, i think
asciilifeform: i dun think it is anything to do with that tx per se -- it is the drop that overflowed the barrel in pre-dblockspatch trb
asciilifeform: until this 'not' remains, trb ain't a program, it's a voodoo incantation.
asciilifeform: naively thought 'i'll start with the smallest trb node!'
phf: well, if i were approaching this, i'd replay to 167998 or so, setup a script to ensure that every time i start trb it starts from that state. i would then see if on forward play it would wedge. i would then investigate what is the nature of wedging, and slowly instrument the code along the various paths to tell me where exactly it decides to stop doing the right thing, etc.
BingoBoingo: last sync test WAS trb on linux
asciilifeform: trb on linux : does
mod6: <+phf> that's because you didn't try to simply use the patch to makefile that i posted on the list << i've had a trb openbsd since you posted this yes.
asciilifeform attempts a build of traditional stator trb inside netbsd ( as rotor is unnecessary there, there is no drepper glibc )
asciilifeform: ( no trb yet, but enough to re-pour the cement... )
asciilifeform: well i have. currently, by expecting 1 fewer trb testbed..
mircea_popescu: and ~possibly~ easier than to sanely rewrite trb
mircea_popescu: there';s no fundamental reason trb needs more than about 5mb or so of ram ; but this aside : gotta find a way to put your own ram in the damned arm boxes.
asciilifeform: trb in 256M ain't happening.
asciilifeform: extra infuriating detail -- i dun specifically need x86 for this , trb runs ok on arm. BUT all extant arms have soldered down (and insufficient) ram.
asciilifeform: btw in case this wasn't clear, this was zoolag , which did 2+ yrs of 24/7 trb.
asciilifeform: and this is true of pretty much any box that makes decent trb node (i.e. has sata3 + ssd )
asciilifeform: ( and in fact it ran on my pogo. but that doesn't produce a usable trb node. )
mod6: <+ben_vulpes> edivad: what kind of system are you building trb on that shipped without `patch`? << this is the same thing I said.
ben_vulpes: edivad: what kind of system are you building trb on that shipped without `patch`?
trinque: not that I've looked into wtf "bitcoin crash" transactions look like, distinct from trb transactions, but that'd perhaps explain it.
asciilifeform: not sure how that goes directly with trb
trinque: will have a few things to chew on re: trb once this walletbot sits down.
a111: Logged on 2017-08-03 14:53 asciilifeform: also lol re the attempted theft of the name 'trb'/'the real bitcoin'
a111: Logged on 2017-08-03 14:53 asciilifeform: also lol re the attempted theft of the name 'trb'/'the real bitcoin'
asciilifeform: also lol re the attempted theft of the name 'trb'/'the real bitcoin'
asciilifeform: for clarity : asciilifeform ain't inluvv with superH. but he ~does~ search for a cpu where 1) respectable (say, even trb-capable) horse 2) no internal flash rom 3) not ARM
asciilifeform: in other noose!, a samsung ssd lasts about 2y in a high-traffic trb node.
BingoBoingo: <asciilifeform> ... though i can see what mircea_popescu means. prb would not, iirc, eat a highS block. and several other types that trb happily eats. << PRB will eat high S when in block. Will fail to propagate high S until mined.
asciilifeform: ... though i can see what mircea_popescu means. prb would not, iirc, eat a highS block. and several other types that trb happily eats.
BingoBoingo: Holy fuck we are about as close to TMSR Wagon as we were to TRB in 2013 given all this engine talk
asciilifeform: interestingly asciilifeform recently learned that the 'mutate high to low S and broadcast malleated tx but ONLY if a 'doublespend attempt' ( you retransmitting, say, with patched trb ) is detected ' thing is STILL running
ag3nt_zer0: mricea_popescu I know your response to my question is run my own node... but if I currently do not have one set up and wanted to be safe with my coins during this nonsense (i.e. take them off of coinbase & store safely), would following pete_dushenski's guide to creating an offline brainwallet utilizing 13 words arrived at through the dice method using only english dictionary be sufficient until I get an up and running trb node? B
mircea_popescu: trb has problems resulting from being written by monkeys.
asciilifeform: it is a problem in the same way as it is for trb.
mircea_popescu: a solution to the problem would actually help trb too
lobbes: BingoBoingo: <lobbes> damn. looks like my plans for my old craptop being a trb node will have to wait until I secure better iron. << Why can old craptop not eat SSD? << wtf I didn't even consider this. And yeah, this'll be a great opportunity to clean out the physical crap that's probably choking out the airflow in the thing.
BingoBoingo: <lobbes> damn. looks like my plans for my old craptop being a trb node will have to wait until I secure better iron. << Why can old craptop not eat SSD?
lobbes: damn. looks like my plans for my old craptop being a trb node will have to wait until I secure better iron.
lobbes: in other questions: Prompted by up-stack threads and after much log reading I've concluded that a SSD is a must for trb-ing. Would an external usb SSD be adequate, versus, say a SATA connection?
a111: Logged on 2017-07-18 20:11 user705: is there a way to do a trb node not on Linux?
shinohai: Sure, the foundation has trb.exe available on website
user705: is there a way to do a trb node not on Linux?
mircea_popescu: or stand up a log bot, or whatever. run a trb node. run the ada implementation passed around recently of a big number calculator and produce 655356! to compare with the given values.
shinohai: Generating keypairs, etc on trb node has worked reliably for me 100% of time since inception
BingoBoingo: badD00d: TRB now WILL accept segwit blocks, but it will not parse the segwit'd portion as anything other than "anyone can spend"
badD00d: I am wondering if you have an estimation as to when this will be and as a second questions (if TRB nodes will be the ONLY non-shit accepting nodes, or if you think there are other groups of people running nodes that will side with your nodes and continue rejecting shit
BingoBoingo: TRB will continue accepting valid blocks
badD00d: will TRB nodes start rejecting blocks whenever BIP91 or other bologna segwit proposals gain the majority hashing power?
badD00d: question for the TRB node running gentlemen
asciilifeform: nothing observable to ~people~ -- i.e. folx using trb -- yes. to redditus running gavincoin etc - thermonukokalypse
a111: Logged on 2015-12-28 18:09 mircea_popescu: http://log.bitcoin-assets.com/?date=28-12-2015#1355361 << quite. all this verbiage about how "oh lalala, if miners stop enforcing X fork they will be excluded" fails to account for the fact that unlike the various PRBs, TRB does NOT actually implement any of the soft forks. so no, they won't be "excluded". nobody will notice they stopped.
mod6: this box does nothing else other than just test builds/dev for trb, and is currently idle. should be a decent test. albiet much slower than the metrics collected with alf's i7 box.
mod6: Perhaps people can donate hardware for whatever purpose trb, uci/gossip via deedbot; then could be accounted for by some process while under our control; maybe even listed as "asset"?
mod6: Perhaps, something could be devised, but it'd be a bit complex. As such, someone could "donate a node" in lieu or some credit to their yearly taxation obligations, and to receive such credit we would need to have some basic requirements met. 1) The node is running trb. 2) It is "caught up". 3) Is available and connected for >95% of the time. 4) Can be independently checked/verified that it is up by some sor
trinque: as it stands I'm already the host for the trb deps.
mod6: and as far as pete_dushenski or whomevers quest to write a log digest or whatever, it never happened. the foundation briefly considered a role for gathering up trb related parts, but that was set aside in exchange for tb0t
asciilifeform: phf: imho sampling profilers are a wholly useless thing, 'horse with pedals', unless you're working a honeywagon (e.g. virginal trb) and have deeply nfi what the hell the program is doing
a111: Logged on 2017-06-30 15:18 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.
deedbot: shinohai rated TomServo 1 << #trilema Working on trb node
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.
deedbot: pete_dushenski updated rating of mod6 from 3 to 4 << co-chair of trbf. gentleman and patient preceptor.
deedbot: pete_dushenski rated mod6 3 at 2015/12/31 17:23:00 << co-chair of trbf. gentleman.
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.
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
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.