a111: Logged on 2016-11-26 19:46 trinque: phf: is there a way to link to the list of trb patches signed by a given key?
trinque: actually not just trb, all seals would be nice.
trinque: phf: is there a way to link to the list of trb patches signed by a given key?
shinohai: More in the worx, juggling those, trb, and eulora mods.
mod6: anyway, trb takes my top efforts, but i'll fit this new t stuff in when I can for sure.
tb0t: Project: trb, ID: 1, Type: D, Subject: Wallet counts change amounts in total balance, Antecedents: , Notes: It has been wildly reported that version 0.5.4 (99999) of the Reference Implementation adds change from a given transaction to the wallet balance.
mod6: !%p trb 1
mod6: %p trb 1
mod6: Framedragger: are you trying to view a ticket for trb?
tb0t: Projects: UCI | t | trb | v
asciilifeform: using what patch ? standard trb dun have import..
shinohai: !~later tell mod6 so after roughly 10 minutes, trb will accept a 8192 char string as label :D
deedbot: shinohai updated rating of trinque from 2 to 3 << deedbot.org, trb
shinohai: !!rate trinque 3 deedbot.org, trb
asciilifeform: mircea_popescu: cheap vps will fall down just as readily when flooded (as will the trb node, mine or anybody's)
asciilifeform: trb, ssh, www, all.
asciilifeform: (and , for folks with poor reading comprehension, i will repeat - entire box is ~unreachable, trb node, ssh, 80, etc )
mod6: Framedragger: point taken about 'owner' on tickets. I considered adding a 'assignee' or 'owner' for a given ticket(s), but with the narrow view of the first project (trb), i didn't want to discourage people from thinking about solutions for a given problem just because it had my name on it or something.
asciilifeform: the trb node just as dead.
Framedragger: trinque's invoice thing may come useful. but then, there's more space to bridge, such as the vast gap between person who wants to buy useful item and person spending coins from trb so can pay invoice....
asciilifeform: Framedragger: that 1 file is almost longer than ALL OF TRB
asciilifeform: earlier this year, i wanted to fit symmetric cipher into trb, and get rid of 'blackholing' etc. but mircea_popescu correctly pointed out that it is the Wrong Thing to cement a pseudoscientific abortion like AES (or ANY OTHER known symmetric cipher!) into place
pete_dushenski: anyways, phf's line is but one example. the corpse that was my 'trb history' should serve as the only proof required that i have deeply nfi which way is up in the cs field and that is has ~zero to do with maths.
a111: Logged on 2016-11-08 18:31 asciilifeform: incidentally, anybody else's trb node under 'askfor tx somecrapolade' ddos ?
asciilifeform: mempool really belongs chopped cleanly out of trb.
asciilifeform: incidentally, anybody else's trb node under 'askfor tx somecrapolade' ddos ?
mircea_popescu: anyway. if we were to bother with this we'd best fix all the other problems too, so the current miners wouldn't be able to mine trb anyway.
mircea_popescu: just as long as i pay 700 bux to the trb, it's not going anywhere.
mircea_popescu: this is connected. simmer down and stop confusing yourself. you said : <asciilifeform> going briefly upstack, my understanding is that this particular batch of forkolade is effectively 'hard', in that no trb-generated tx is likely to be mined. and i said <mircea_popescu> if it is, whatever, we'll release a proper trb and they can all go hang. im pegging it.
asciilifeform: to have separate market, as in 'x prb == y trb coin', they gotta be circulatable separately
mircea_popescu: asciilifeform to peg as in a currency, 1 trb = 1 prb to start. may devalue as time goes by of course.
mircea_popescu: if it is, whatever, we'll release a proper trb and they can all go hang. im pegging it.
asciilifeform: going briefly upstack, my understanding is that this particular batch of forkolade is effectively 'hard', in that no trb-generated tx is likely to be mined.
asciilifeform: ( the other prong of the front is the attempt to make trb difficult to use reliably by preventing effective quarantine of derp nodes and their tx)
mircea_popescu: anyway. it significantly weakens trb, which they're more than welcome to.
asciilifeform: (summary: usg's most recent attempt to pound in the cock 'halfway', 'segwit', consists of prb churning out txen that result in 'anyone can spend' from trb pov, but miners are to 'agree never to process counter-softforkian tx', a la 'timelock' etc)
tb0t: Project: trb, ID: 29, Type: F, Subject: Redesign Wallet, Antecedents: 30, Notes: The original Reference Implementation wallet needs a redesign. http://trilema.com/2016/the-ideal-bitcoin-wallet/ http://trilema.com/2016/how-to-cut-the-wallet/
mod6: !%p trb 29
mod6: !%e trb 29 F "Redesign Wallet" "The original Reference Implementation wallet needs a redesign. http://trilema.com/2016/the-ideal-bitcoin-wallet/ http://trilema.com/2016/how-to-cut-the-wallet/" 30
mircea_popescu: would you want someone working on trb on the basis of having read the book or on the basis of having watched "the videos" ?
a111: Logged on 2016-11-02 17:21 PeterL: so we need a sort of "frozen" archive of "how to make X, which you need to make Y", sort of like how trb has frozen deps
PeterL: so we need a sort of "frozen" archive of "how to make X, which you need to make Y", sort of like how trb has frozen deps
thestringpuller: trb the bsd of bitcoin
asciilifeform: trb absolutely gives no fuck if it cannot find the network.
asciilifeform: incidentally you can make this out of CURRENT trb simply by putting it on a box without a nic
asciilifeform: thestringpuller: how do you propose to 'check against multiple trb nodes' on an airgapped signing box ?
thestringpuller: asciilifeform: unless tx you craft is gargantuan, I don't see how you couldn't do a partial audit of the non-signed tx that is spit out. in this context it would be best to check against multiple known TRB nodes the tx hashes are valid
thestringpuller: as of current you have to dump block on TRB in order to manually grep for a tx-hash to use as an Input to construct a raw transaction
mircea_popescu: anyway. to not get entirely sidetracked : the exact sense in which wallet should be separated from rest of trb needs a lot more thinking.
asciilifeform: and pretty much everyone who has attempted to fire a tx using trb prior to mod6's 'S' patch, now has a supply of such 'evil' coin with which to test this hypothesis, if he wants.
asciilifeform: trb wallet is every bit as broken as prb wallet in this respect
phf: but i think asciilifeform also had an imperative of keeping trb canonical sourth of all btc knowledge, so that wallet stays in (so that you can read and know what wallet even is), but you solve the separation by starting the daemon with different flags indicating intended usecase
tb0t: Project: trb, ID: 33, Type: F, Subject: Possible DB Replacement with UNIX Filesystem, Antecedents: , Notes: http://btcbase.org/log/2016-11-01#1561093
mod6: !%p trb 33
tb0t: Project: trb, ID: 8, Type: C, Subject: Remove BDB and integrate BitcoinFS, Antecedents: 6,7,33, Notes: Change ticket to integrate the BitcoinFS, once implemented.
mod6: !%p trb 8
mod6: !%e trb 8 C "Remove BDB and integrate BitcoinFS" "Change ticket to integrate the BitcoinFS, once implemented." 6,7,33
mod6: !%a trb F "Possible DB Replacement with UNIX Filesystem" "http://btcbase.org/log/2016-11-01#1561093"
BingoBoingo: In other news TRB leads the way! "Alert" system in PRB being retired via... ALERTS!!! https://archive.is/5OoKT
asciilifeform: and the glomming of otherwise separate concerns is one of the things that makes reading trb a reliable headache.
mircea_popescu: sadly. the main thing that holds back sanevelopment on trb is the fact that whatever you want to discuss everyone starts muttering curses and mashing kbd about the 10bn other things connected.
mircea_popescu: definitely trb fork will have a sane tx-to-block coding scheme
mod6: i think putting effort into: http://thebitcoin.foundation/tickets/trb_tickets.html#6 is the right idea.
mod6: Anyway, overall, I'm super excited for the future of TRB.
mod6: Another long term goal is to possibly get some more unit tests written for trb. Might not even need to be something in the perm source base, but something as an overlay to give us confidence when we make critical changes down the road.
trinque: the same was contemplated for trb; it doesn't rule out use of V
asciilifeform: might be lulzy to cross-check with phuctor, ben_vulpes's trb nodes' banhammer lists, etc.
asciilifeform: https://stashnode.com << in other lulz, 'why build a trb node, buy a prb box from stranger today!'
a111: Logged on 2016-10-23 17:58 ben_vulpes: my trb node just breached 4950 megs in virt and 3470 megs in res
ben_vulpes: my trb node just breached 4950 megs in virt and 3470 megs in res
asciilifeform: and, eh, 'v', or trb, or various other items contemplated here, fall much closer to the jet than to the tv set.
mircea_popescu: besides, at some point we'll get rid of sha2 in trb, and then we'll know.
deedbot: shinohai updated rating of ben_vulpes from 1 to 2 << http://cascadianhacker.com/ #trilema trb
thestringpuller: oh no, i think my trb hit its first blackhole :(
asciilifeform: mats: you oughta port trb to it!111
asciilifeform: http://btcbase.org/log/2016-10-09#1554091 << you would have to begin by putting shiva back in... it isn't in the mainline trb (on account of questionable usefulness)
a111: Logged on 2016-10-09 00:41 thestringpuller: asciilifeform: how would i use shiva to hook into the trb wallet functions?
thestringpuller: asciilifeform: how would i use shiva to hook into the trb wallet functions?
mod6: mircea_popescu: in the context of an ideological history, I have nothing further to add. I'll denote that the recent progress of freezing trb's 3rd party deps, starting in the end of July, is signifigant, however covered by item #10 imho.
tb0t: Projects: UCI | t | trb | v
thestringpuller: File: trb54/bitcoin/.gitignore
thestringpuller: i'm testing trb54 and I get this from V:
a111: Logged on 2016-10-05 01:48 mircea_popescu: currently some miners process, eg, 3-leading bitcoin addresses. while that lasts, trb can send money to you. once it goes away - can send no longer, resulting in some lost bitcoin (practically, sent to unspendable address)
a111: Logged on 2016-10-05 02:26 asciilifeform: the thing i do not understand is, how does the thing not fork? say i fire up a prbtron and prbsend to A. then fire up trbtron and send same coin to B.
asciilifeform: possibly answer is, trb thinks i sent it to neverneverland ?
asciilifeform: the thing i do not understand is, how does the thing not fork? say i fire up a prbtron and prbsend to A. then fire up trbtron and send same coin to B.
mircea_popescu: currently some miners process, eg, 3-leading bitcoin addresses. while that lasts, trb can send money to you. once it goes away - can send no longer, resulting in some lost bitcoin (practically, sent to unspendable address)
mircea_popescu: asciilifeform your trb node is not capable to send money from derpy addresses ; which is ok because it's also not able to send to them. other people are more than free to do whatever the fuck they like.
asciilifeform: does it thereby follow that prb and trb have differing notions of how much coin is contained in A ?
trinque: other times, vintage gpg, complete deps for trb, all sorts of things
adlai: dude i'm http://thebitcoin.foundation/trb-howto.html - ing
adlai: but i still can't build the silly offline trb doodad!
mod6: here's the list, that corresponds to the trb-howto.html corresponds to: http://thebitcoin.foundation/v/patches/
adlai wonders why the _v_ in http://thebitcoin.foundation/trb-howto.html when invoking v.pl
asciilifeform: you could use trb-rotor almost as-is, if you went to this.
a111: Logged on 2016-10-03 18:26 mircea_popescu: if anyone is inclined to maintain forks of any linux distro (much in the manner of trb - to clean, not to "support"/utf/systemd/etc) we can prolly work something out.
trinque: henceforth working on trb was known throughout the land as "doughfucking"
adlai: even if you want to atomic-swap trb against etc, you're stuck shelling out, so you're at best "sbcl/ccl programmer"
mircea_popescu: if anyone is inclined to maintain forks of any linux distro (much in the manner of trb - to clean, not to "support"/utf/systemd/etc) we can prolly work something out.
asciilifeform: otherwise one day you discover 'surprise', gcc6 or whatever won't build trb, or worse, builds-with-boojum
asciilifeform: for so long as you are still using traditional trb, you are stuck with some variant of this.
asciilifeform: and, incidentally, recall that we reground the trb genesis once.
asciilifeform: it made marginally more sense re the trb patch, but even there mircea_popescu insisted on the regrind.
asciilifeform: ( i could even see an argument that, e.g., rawtx eater doesn't belong in trb , and that tx ought to be injected via the ordinary tcp method. but i dun recall having this argument )
mircea_popescu: there's no specific problem known at that height ; trb does tend to want to use about 4gb or so if it can get to it.
whaack: asciilifeform: I built following the steps of http://thebitcoin.foundation/trb-howto.html the online build section on a ubuntu 12.04 and by "where" do you mean my general lat/lng?
whaack: Greetings I'm trying to get a trb node running and I've gotten stuck during sync at block height 212033 any help would be appreciated here is the last 1k lines of my debug.log dpaste.com/03P772C
asciilifeform: there is fragging. which is why current trb runs indefinitely in a footprint of ~4GB.
shinohai: Probably not practical idea until mem leak is plugged in trb
asciilifeform: shinohai: trb memory pighoggery prevents the practical trbification of any of these. but it is ~impossible to fix without rewriting good chunk of it.
asciilifeform: shinohai: don't expect to do much trb on the g1 board that comes with the sage - it has soldered-down 1GB of ram
shinohai: Well it isn't really weight I guess, I do rsync trb blockchain to it. So it has uses.
mod6: The following have been updated: The Foundation's repository of vpatches & seals, the trb-howto.html, and the vpatch graph. You now are able to build the entire orchastra via integrated makefiles; offline (default) or online, operators choice. All through the use of vtroncis, of course.
a111: Logged on 2016-09-23 14:20 mircea_popescu: actually since you brought it up it reminded me of vague discussion, so let's make it explicit. mod6 asciilifeform i dunno how practical it is yet, but eventually trb block mechanics will have to be expanded to memory datastore, so that it holds the current blk000n it's working on in ram and dumps it to disk only when full. MUCH easier to cache a disk with no writes on it.
tb0t: Project: trb, ID: 26, Type: C, Subject: Mempool changes implemented, Antecedents: 25, Notes:
mod6: !%p trb 26
a111: Logged on 2016-09-23 14:20 mircea_popescu: actually since you brought it up it reminded me of vague discussion, so let's make it explicit. mod6 asciilifeform i dunno how practical it is yet, but eventually trb block mechanics will have to be expanded to memory datastore, so that it holds the current blk000n it's working on in ram and dumps it to disk only when full. MUCH easier to cache a disk with no writes on it.
a111: Logged on 2016-09-23 14:20 mircea_popescu: actually since you brought it up it reminded me of vague discussion, so let's make it explicit. mod6 asciilifeform i dunno how practical it is yet, but eventually trb block mechanics will have to be expanded to memory datastore, so that it holds the current blk000n it's working on in ram and dumps it to disk only when full. MUCH easier to cache a disk with no writes on it.
asciilifeform: the unparallelized-yet-wholly-parallelizable block verification is the biggest embarrassment in trb
asciilifeform: of trb?
mircea_popescu: actually since you brought it up it reminded me of vague discussion, so let's make it explicit. mod6 asciilifeform i dunno how practical it is yet, but eventually trb block mechanics will have to be expanded to memory datastore, so that it holds the current blk000n it's working on in ram and dumps it to disk only when full. MUCH easier to cache a disk with no writes on it.
mircea_popescu: well massive overkill. trb wants what, 4g ? i was thinking more in terms of tb.
shinohai: mircea_popescu is suitable for trb ?
mircea_popescu: asciilifeform it does link ? http://thebitcoin.foundation/trb-howto.html
asciilifeform: !~later tell mircea_popescu your new page's section IV oughta link to trb
ben_vulpes: i don't even think you can have max compact size anything in trb.
asciilifeform: (and trb does in fact store orphaned blocks eternally)
asciilifeform: esp. if coupled with actual working wireshark + trb node.
phf: i think one could take either of those and turn them into real systems, the way we did with trb, but it's the same class of work
mircea_popescu: same thing as trb, but with lisplisp instead of cc
asciilifeform: ben_vulpes: if you read the code, you will notice that trb is, at most times of 'very very busy bee', quite unready to react to rpc command because one of the global locks is engaged.
asciilifeform: the trb method.
ben_vulpes: in other strange, my trb node is currently sitting on 9756 VIRT, and has an entire core completely pegged.
asciilifeform: which is why any item that is of interest here, ought to be picked up and nailed to the floor, as i nailed trb's deps.
mod6: so here's my using 'init' to sync trb, and trinque's ircbot, then using both. trb with the default 'patches' and '.seals' and ircbot with the non-default: http://dpaste.com/2EFW6G4.txt
mod6: is this not what you're trying to do? one parent dir, two child 'patches' dirs ('trb' and 'ircbot'), each with respective seal dirs ('.trb-seals' and '.ircbot-seals') both being able to be used ~fine~ with v.pl (v99995)
mod6: and im stuck between trying to making getting trb up and going for people, in a "one-trigger-pull", and an organic vtron garden.
phf: i think mod6's v is trying to solve bootstrapping problem, by pretending like it's not one. you have to have v tools, and you also have to have your ~/wot. those are created organically, at which point picking up a tar.gz of vpatches or picking them manually is a nobrainer. but if you're a trb newb, you want all three at the same time, which seems like a subversion of v design. why not just have a v starter kit? you unpack it, you have
tb0t: Projects: UCI | t | trb | v
tb0t: Project: trb, ID: 12, Type: F, Subject: Makefiles for building full orchastra, Antecedents: , Notes: http://btcbase.org/log/2016-07-14#1502667
mod6: !%p trb 12
mod6: %!p trb 12
a111: Logged on 2016-09-07 16:29 asciilifeform: in other noose, 70.33.211.11 (yes, 1 box) has been ddosing trb nodes, in particular zoolag.
a111: Logged on 2016-09-13 03:11 ben_vulpes: asciilifeform: does your trb node's memory usage grow unboundedly?
asciilifeform: a specification can exist as a real object (which is very painful, consider the standard kilogram block, or trb) or an ideal object.
asciilifeform: and i have reason to suspect that mpb is catastrophically defective and fails to pass tx to trb (which, recall, is a reference, one does not get to say that it is broken in vs the unpublished mpb) under certain circumstances.
asciilifeform: half the time i do not even know if he is speaking of a trb -- or mpb! node.
asciilifeform: incidentally, i still have nfi what mircea_popescu's patchset is. understandably he can stay mum about it if he likes, but it makes his debugging reports ~useless from a trb pov.
asciilifeform: (trb is 100% static, i hope this is not news to anyone)
a111: Logged on 2016-09-13 08:14 mircea_popescu: http://log.mkj.lt/trilema/20160913/#28 < no trb node of mine ever allocated 4gb ram. there's something weird there.
mircea_popescu: http://log.mkj.lt/trilema/20160913/#28 < no trb node of mine ever allocated 4gb ram. there's something weird there.
a111: Logged on 2016-09-13 03:11 ben_vulpes: asciilifeform: does your trb node's memory usage grow unboundedly?
BingoBoingo: ben_vulpes: Restart every few weeks to back up blockchain. Is not trb, but other on Openbsd with trb shit bolted onto sides
ben_vulpes: asciilifeform: does your trb node's memory usage grow unboundedly?
asciilifeform: mircea_popescu: if either of my trbtrons aren't answering, now or whenever, gimme a ping
mircea_popescu: incidentally, what's the current list of public trb nodes ? i have -connect=108.31.170.49 54.187.227.228 46.166.165.30 91.218.246.31 172.86.178.46 50.168.67.12 of which a coupla be answering.
mircea_popescu: this said, i see absolutely no problem whatsoever implementing trb nodes on sign-hello.
asciilifeform: i even built trb for it.
shinohai: Imma try and have it up by first of week, I got sidetracked with this trb makefile thing
trinque: that said shinohai pls do not hook a cruddy anything to your trb for your own sake.
shinohai: What were specs for a bot wallet anyway? There was a cruddy one written by gribble's author I started to hook to trb one time but never finished
ascii_zimbabwe: i dun have this now only because it doesn't play well with trb.
trinque: because trb demons not fully enumerated
asciilifeform: conventional in the 'trb as we now have it' sense.
asciilifeform: at one time i considered adding, e.g., rate limiter, to trb, but decided that it is not the Right Thing.
asciilifeform: in other noose, 70.33.211.11 (yes, 1 box) has been ddosing trb nodes, in particular zoolag.
shinohai: All jhvh1 wants is to be sure you have a working copy of trb when X-Day comes
mod6: <+asciilifeform> we burned it out of trb with hot irons, first thing, for a reason. << werd. thx.
asciilifeform: we burned it out of trb with hot irons, first thing, for a reason.
thestringpuller: asciilifeform: nah i'm sourcing it in my own docs. i'm doing a big write up of trb for n00bs.
asciilifeform: thestringpuller: not satisfied with the cookbooks on trb mailinglist ?
Framedragger: asciilifeform: trb and mpex don't make themselves easy to be used by everyone. which YES is a great thing. but it's not because an angelic light shines upon them, repelling all evil.
davout: yeah sure, but that's kind of different from saying 'sucks because roger ver'. ver probably used the bitcoin client before it was set in stone for trb
asciilifeform: they aren't flocking to trb, or mpex, etc.
gribble: trinque was last seen in #trilema 2 hours, 18 minutes, and 23 seconds ago: <trinque> mircea_popescu: aha, will keep running the latest trb
asciilifeform: i've contemplated attempting an openwatcom build of trb.
trinque: mircea_popescu: aha, will keep running the latest trb
asciilifeform: as happens many times every day on our trb nodes.
thestringpuller: wow did trb blackhole the entire box this time
asciilifeform: mircea_popescu: the 'segwit' thing is, as i understand, intended as a protocol hardfork - to isolate trb users.
asciilifeform: there will (and perhaps already are) a multitude of chumpers who believe they have X btc, while really they have some quantity Q, possible 0, of actual btc, and X-Q of gavinola, which consists of tx, somehow elaborately processed, that trb rejects as noise, and display as wtf 'shot into the sun' crapolade in any civilized block viewer
mircea_popescu: trb is however distinguished by being the most acceptant. so...
PeterL: but will trb accept block with chain of transactions in it?
asciilifeform: this piece was put in as attempt to disincentivize connection to trb nodes.
mircea_popescu: miner runnign trb-esque thing only would not, right. the first gets cut off because fees, the second because unknown inputs.
PeterL: so miner running trb-esque thing would not have second transaction
asciilifeform: mircea_popescu: as i understand, PeterL was pointing out that trb does not relay the ingredients desired in this kitchen.
asciilifeform: phf: the 'grabs a broom and a bucket and cleans it' incidentally is more or less the story of my 1st year of trb.
asciilifeform: shinohai: even trb will run for no more than 2-3 weeks on 2G.
asciilifeform: jurov: aha, and those are the 5 people who have any business patching trb.
mircea_popescu: anyway ; it's evident that in the future republican code will have one of the two possible profiles (trb-like ; eulora-like), not necessarily one, and certainly not necessarily the former.
phf: fwiw trb and eulora have opposite goals as far as exposure
phf: trb's build system is not sane
asciilifeform: as trb does.
asciilifeform: as trb does.
phf: trb builds on three systems altogether, and it's still a pita
asciilifeform: mod6's trb-builder.
phf: asciilifeform: do you have a gnupg1 version, that can be used as a trb-like base? i want to go through an execise of reading a diff between some version that can be relied on with all the disclaimers and whatever's in the trunk
a111: Logged on 2016-08-20 21:17 mod6: the goal is and remains this: get the trb build infrastructure completed, once and for all. close out this portion of development with the completion of that (Makefiles) and a subsequent tying vpatch to mark the milestone.
shinohai: +mircea_popescu why not try playing it lol. you just wanna compile thangs ? lol, this is why I stick more on trb side of things xD
a111: Logged on 2016-08-20 21:17 mod6: the goal is and remains this: get the trb build infrastructure completed, once and for all. close out this portion of development with the completion of that (Makefiles) and a subsequent tying vpatch to mark the milestone.
mod6: the goal is and remains this: get the trb build infrastructure completed, once and for all. close out this portion of development with the completion of that (Makefiles) and a subsequent tying vpatch to mark the milestone.
mod6: pposed to replace it <+phf> instead. obviously this doesn't make for pretty graphs, so i don't upload it << yup. there's a planned vpatch for this. bunch of discussions. just been focusing my attention on trb build stuff lately.
asciilifeform: and trb - its own. etc.
asciilifeform: e.g., mod6's vtron does not depend on trb in any way shape or form
asciilifeform: not only trb.
asciilifeform: it is still the authoritative history of trb.
asciilifeform: this would be a handy (optional) item to have in trb.
mod6: <+mircea_popescu> heh. aaand a trb node is at height 419220 for absolutely no reason ; 50+ connections, stable etc. << did this get fixed? or is it stuck at that same block still?
a111: Logged on 2016-08-16 01:35 mod6: <+pete_dushenski> mod6: pleased to report that 99994k spins up on deb7 without fuss. only comment would be on 'trb-howto' to suggest '-lows' command when booting bitcoind for the first time. << hey! Thanks for testing that!
mircea_popescu: heh. aaand a trb node is at height 419220 for absolutely no reason ; 50+ connections, stable etc.
mod6: <+pete_dushenski> mod6: pleased to report that 99994k spins up on deb7 without fuss. only comment would be on 'trb-howto' to suggest '-lows' command when booting bitcoind for the first time. << hey! Thanks for testing that!
pete_dushenski: mod6: pleased to report that 99994k spins up on deb7 without fuss. only comment would be on 'trb-howto' to suggest '-lows' command when booting bitcoind for the first time.
mod6: essentially, i've taken all the buildroot deps (typically collected from the wan), along with the trb deeds, placed them in a local dir with the build script (modified to suit this process) and launched.
mod6: So in test-land news; I've created a working totally off-line build for trb.
mod6: asciilifeform: is nsa's trb down?
asciilifeform: he trb'd it.
asciilifeform: he solved it the trb way.
asciilifeform: sorta like we did with trb.
asciilifeform: iirc it was the db descriptors thing in trb.
mod6: basically, one can follow the instrutions here: http://thebitcoin.foundation/trb-howto.html
a111: Logged on 2016-07-31 21:31 mod6: %p trb 29
tb0t: Project: trb, ID: 29, Type: F, Subject: Redesign Wallet, Antecedents: 30, Notes: The original Reference Implementation wallet needs a redesign. http://trilema.com/2016/the-ideal-bitcoin-wallet/
mod6: %p trb 29
mod6: %e trb 29 F "Redesign Wallet" "The original Reference Implementation wallet needs a redesign. http://trilema.com/2016/the-ideal-bitcoin-wallet/" 30
tb0t: Project: trb, ID: 29, Type: F, Subject: Redesign Wallet, Antecedents: 30, Notes: The original Reference Implementation wallet needs a redesign.
mod6: %p trb 29
asciilifeform: nor could ever, with trb.
asciilifeform: it is about miners spitting on a perfectly valid, per trb rules, tx
asciilifeform: ~0 hashrate behind 100%-everything-trb-will-happily-eat protocol breadth
asciilifeform: so long as trb node accepts a hypothetical block as valid, it is mineable.
asciilifeform: (if this, they will eventually be candidates for anal reeducation, just as we would have been sans trb)
asciilifeform: so... has an 'eth trb' yet appeared ?
shinohai: $down trbbot
deedbot: shinohai may not $down trbbot.
shinohai: trbbot: bash 3
deedbot: trbbot voiced for 30 minutes.
shinohai: $up trbbot
shinohai: trbbot: bash 5
shinohai: trb users unaffected
asciilifeform: trbbot?
trinque: tbot here is perl, trb builder is either sh or Makefile
trinque: only reliable trb node eh?
asciilifeform: box also hosts the only (afaik) 'five nines'-reliable trb node.