2000+ entries in 0.139s
mircea_popescu: it is trying to fix the
trb, which is a component of the c machine, defined as "runs
trb"
mircea_popescu: in any proper statement, all the eg
trb foundation's work goes towards one fold of "fixing c machine" in this sense.
mircea_popescu: phf yeah, but still, we have some experience with the neat
trb building process. it can be done.
ben_vulpes: anyways, hey asciilifeform have you ever built the
trb test target?
nacci: perhaps the republic will need to maintain its own os in which to run
trb ben_vulpes:
trb just looks through the script for pubkey or pubkey hash opcodes
scriba: Logged on 2017-03-28: [23:57:45] <asciilifeform> ( possibly -- if some hero devotes several years to it,
trb-style -- but even then )
phf: in fact, i static linked a copy of
trb on a recent machine (5.6 say), and then moved it to a libretto (that was running 5.3 or whatever) and the binary booted and worked, but then silently failed on some system calls.
mod6: i realized when trying to diagram out, for instance, the notated split of
trb.node with
trb.wallet (posted in logs a little while back) that I didn't have enough paper on 8.5"x11"
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
a111: Logged on 2017-03-26 16:10 asciilifeform: 'Hello asciilifeform I see on coin.dance/nodes , The Real Bitcoin is listed with the 'Emergent Consensus' feature tag. Could you tell me if that's accurate - will you follow a HF to > 1MB , and could you tell me anything about how it's implemented in
TRB ? Thx!'
mp_en_viaje: asciilifeform, mmm, on contemplation the issue might just be mp logotron reports "failed reorg" when the purporting-to-generate-reorg block failed to actually verify. old prb/
trb don't.
mp_en_viaje: asciilifeform, this was re the "our new v 13 nodes will not accept blocks relayed by
trb"
TomServo: asciilifeform: time is okay, other than
trb logs being gmt system is cdt. disk okay. Yes, earliest.
pete_dushenski: mircea_popescu: 'Every service is in a dedicated VM container' << i'm not clear on difference between vm and vps, but i have at least one
trb box on vm it seems.
a111: Logged on 2017-03-23 04:46 pete_dushenski:
http://btcbase.org/log/2017-03-22#1631221 << define 'possible'. >x connections ? doesn't crash ? because i've been running
trb on vps since it came out and have no particular complaints other than semi-regular st9 errors.
a111: Logged on 2017-03-22 23:34 mircea_popescu: tbh i have nfi how you could run
trb in a vps. i don't think it's possible, not really. would be certainly quite the medal of merit on any software that can handle such.
mircea_popescu: tbh i have nfi how you could run
trb in a vps. i don't think it's possible, not really. would be certainly quite the medal of merit on any software that can handle such.
☟︎ trinque: mod6: I'm quite happy to host anything that supports
trb work
mod6: <+trinque> strike that, all
trb deps mod6 deeded; he is hosting the V stuff. << fwiw it's also posted to the ML which is on some other environment.
trinque: strike that, all
trb deps mod6 deeded; he is hosting the V stuff.
trinque: ftr, all
trb downloads come from a dedicated deeds box I've been happy to run as core infrastructure pro bono.
mod6: You will find that The Bitcoin Foundation website has duly been updated as well as the
TRB How-To Steps (nothing more has changed than the version number of the tarball to grab for V).
shinohai: "If you upgrade to
trb, this has been fixed for ages" <<< /me wants to comment
mod6: well, yeah, i've got a new dedicated box that is
trb w/wires and currently syncing from thin air.
phf: ben_vulpes: we're not actually discussing various relative merritts of various who calls, because we don't have any problem in mind. for
trb clion's who-calls is above and beyond anything emacs provides, for genera's clim ~genera~ is way better at who calls, etc.
lulcoinz:
trb specifically (I know what a btc node is)
lulcoinz: what is a
trb node (sorry for my ignorance)
ben_vulpes: no but seriously, why even bother hoping? run a
trb node, insulate yourself from the retardation.
a111: Logged on 2017-03-20 00:42 mod6: So I'll be getting into the thick of that very soon. Lot to do to get
trb-i going.
Framedragger: (current version records the important things including
trb work, so imho it's doing fine)
Framedragger: i guess having an easy way to add new projects (or have a 'misc' parent but maybe that's too dirty) would help in that it'd be easier to record stuff, including tasks not directly tied to
trb or V
mod6: So I'll be getting into the thick of that very soon. Lot to do to get
trb-i going.
☟︎ mod6: I do want to outline more of the
trb-i work in tickets, and do some clean-up/management of existing
trb tickets.
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
☟︎ a111: Logged on 2017-02-27 16:56 mircea_popescu: but the correct
trb-i might just as well end up this situation where block reward is 1mn bitcoin, and it dies within 1mn blocks. so all mining does is produce ~ a lease ~ on a chunk of bitcoin. and the value of old bitcoin is monotonically decreasing over their lifetime.
mircea_popescu: this is at the core of the argument in favour of a
trb-i implementation.
mircea_popescu: honestly, it should just be a patch. there's no serious reason to allow the usage of
trb on tiny boxes
davout: du -sh ~/.
trb reports 131gb
a111: Logged on 2017-03-15 06:46 davout: my
trb node is finally synced up, took approx ~2.5 months on a smallish server without an SSD
davout: my
trb node is finally synced up, took approx ~2.5 months on a smallish server without an SSD
☟︎ Framedragger: ..which means that the latter should be dropped eventually, i guess (but then cue my question 'why not just work on
trb-i if no compatibility with heathen prb network')
Framedragger: i think it makes sense, thinking of the future, to eventually move to a model where there is no 'public
trb node ip list'.
Framedragger: asciilifeform: btw regarding bitcoin, sure re. 1000 machines but if/when there's only 15 or however many
trb nodes....
Framedragger: (this is just to juxtapose topics of
trb and gossipd for a second and to maybe show why some folks really like the lighthouse idea) :)
mod6: so either user creates ~/
trb-deps and then pulls all .asc's from deedbot manually in offline mode. or makefile creates ~/
trb-deps and pulls .asc files in `make ONLINE=1` mode and dumps files in there.
trinque: makefile would make the dir, maybe ~/
trb-deps as default, or w/e
mod6: this would leave, for instance, a '
trb' output press directory along side of the above stated dirs. of which, all that would be contained in there is a bitcoin directory, and the underlying 'src' directory.