tmsr - Search: trb

1800+ entries in 0.144s

mod6: now, `cd /var/trb/trb54/bitcoin ; make clean`

mod6: copy /var/trb/trb54/bitcoin/deps/*.asc to some other holding tank and let me know when ready.

mod6: so now, let's back up your /var/trb/trb54/bitcoin/deps directory.

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 ?

mike_c: this exists: /var/trb/trb54/bitcoin/build/toolchain/usr/x86_64-therealbitcoin-linux-musl

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.

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 ?)

shinohai: Heh I missed this lulzy anonymint trb writeup http://archive.is/BZ2ka

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

mod6: http://thebitcoin.foundation/trb-howto-new.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'

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