tmsr - Search: trb

1700+ entries in 0.18s

asciilifeform: http://btcbase.org/log/2017-10-06#1721644 << what is 'vanilla trb' ? ☝︎

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?

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: 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

rothbart: asciilifeform: will I need to redownload the blockchain on trb?

rothbart: asciilifeform - haven't even started syncing it yet - still processing the plan in light of your advice (ie. sweeping via trb first)

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?

Barbarossa_: but I'm in the process of getting trb/linux/FG and all that

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 ?

danielpbarron: trb

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://thebitcoin.foundation/trb-howto.html <<

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. ☝︎

runsegshet: Also is core hard forked from TRB? How would one be able to mine TRB instead? ☟︎

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. ☟︎

mike_c: LC_ALL=C /var/trb/trb54/bitcoin/bin/bitcoind getblockcount

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.

mike_c: CC =/var/trb/trb54/bitcoin/build/toolchain/usr/bin/x86_64-therealbitcoin-linux-musl-gcc

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

mod6: ok, next: `cd /var/trb/trb54/bitcoin/deps ; cp ~/*.asc .` -- hopefully, in your ~ you only have .asc deeds, and not, say, other stuff...