asciilifeform: not any dumber than mitming my trb node.
asciilifeform: the same sense the behaviour of my trb node's upstream makes.
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
tb0t: Project: trb, ID: 12, Type: F, Subject: Makefiles for building full orchastra, Antecedents: , Notes:
mod6: %p trb 12
mod6: %e trb 12 F "Makefiles for building full orchastra" "http://btcbase.org/log/2016-07-14#1502667"
tb0t: Project: trb, ID: 12, Type: F, Subject: Makefiles for building full orchastra, Antecedents: , Notes:
mod6: %p trb 12
asciilifeform: and in many cases, in particular the one now contemplated, is wholly unnecessary: fetching the trb deps is a once-per-machine thing
mod6: I tend to agree, overall though. It should belong with trb.
asciilifeform: http://btcbase.org/log/2016-07-14#1502685 << what has mircea_popescu been smoking?? there is no qt in trb
mod6: The thing is, they /are/ really a part of trb itself.
mod6: The one staring me in the face is this: If we place them in trb's tree, we'll be adding vpatch after vpatch to the source base to update the makefiles as they require to be updated. Having them in their own tree could elimiate cruft in trb.
mircea_popescu: it seems to me they should be in trb tree. which tradeoffs do you see ?
mod6: this really leaves one last question that has to be thought through before we move on; Do we place the makefiles into trb's tree, or do we place them in their own tree? I've thought about this quite a bit. And there are tradeoffs to both.
mod6: trb
shinohai wants to run a cock.li trb node
asciilifeform: ;;later tell mod6 http://thebitcoin.foundation/trusted-nodes.html << is missing dulap, the single most robust trb node i know of
a111: Logged on 2016-07-06 23:18 mod6: <+trinque> mod6: hey maybe the mircea_popescutronic wordpress is a better way to post TRB tutorials/updates than wiki << perhaps. i was hoping that with wiki (which, I admin, is not ideal) people could help out a bit more easily - as opposed to a blog or wp thing.
a111: Logged on 2016-07-06 23:17 shinohai: My trb node drops connections one by one every few hours and needs restart to connect. I'm way behind.
mod6: <+trinque> mod6: hey maybe the mircea_popescutronic wordpress is a better way to post TRB tutorials/updates than wiki << perhaps. i was hoping that with wiki (which, I admin, is not ideal) people could help out a bit more easily - as opposed to a blog or wp thing.
shinohai: My trb node drops connections one by one every few hours and needs restart to connect. I'm way behind.
mod6: <+trinque> I am wedged at 419554 too << did your trb continue on then too?
asciilifeform: i'ma install it trb-style
a111: Logged on 2016-07-06 00:26 trinque: mod6: hey maybe the mircea_popescutronic wordpress is a better way to post TRB tutorials/updates than wiki
asciilifeform: trb? trinque made one
trinque: mod6: hey maybe the mircea_popescutronic wordpress is a better way to post TRB tutorials/updates than wiki
mod6: trinque: is that the deedbot trb ip then?
asciilifeform: mod6: i was damn sure there was a draft cookbook but i slept through it, and it was not yet posted to trb www.
mod6: <+asciilifeform> ;;later tell mod6 the link in trb.foundation STILL POINTS TO BITCOIN-ASSETS WIKI << Is this necessary?
asciilifeform: soooo it appears that we do not have ~any~ recipe posted for building vtronic trb ?
asciilifeform: ;;later tell mod6 the link in trb.foundation STILL POINTS TO BITCOIN-ASSETS WIKI
mats: er, for building trb.
asciilifeform: http://btcbase.org/log/2016-07-04#1497206 << my original recipe still worx and will always work. use a recent trb tho.
a111: Logged on 2016-07-04 22:12 mats: is there an up to date guide to rolling trb on pogo's little-endian armv5?
mats: is there an up to date guide to rolling trb on pogo's little-endian armv5?
asciilifeform: we dun even have 3 reliable trb nodez.
shinohai: thestringpuller: I don't have a job other than trb/Qntra
adlai: reading SoTRB, lemme get this straight: it's impossible to download openssl without... openssl?
a111: Logged on 2016-06-29 22:54 pete_dushenski: $rate funkenstein_ 2 trb privkey patch guy
deedbot: pete_dushenski rated funkenstein_ 2 << trb privkey patch guy
pete_dushenski: $rate funkenstein_ 2 trb privkey patch guy
deedbot: pete_dushenski updated rating of shinohai from 1 to 2 << trb tester+navigator
pete_dushenski: $rate shinohai 2 trb tester+navigator
thestringpuller: I don't see a good scenario where TRB could deploy a fork i.e. "the prequisite".
a111: Logged on 2016-03-05 15:15 mircea_popescu: i suppose IF the july many-fork time comes and trb has nothing to offer then it might as well close.
asciilifeform: anything other than unconditional capitulation to trb, == prb.
thestringpuller: if it's possible to mine and validate against TRB...
phf: (trb instance)
shinohai: No, shiva the trb addition. >.>
mats: hanbot was gonna look at it but got caught up in some trb thing
mircea_popescu: trb acted correctly.
asciilifeform: i disagree that the enemy ought to have any say in how trb works.
mircea_popescu: trb has no notion of "coin history". nor should it. because taint is not a thing.
thestringpuller: cause there is no way TRB will ever enforce segwit, so there is no way it can ever truly verify a segwit output was spent "legitimately"
thestringpuller: okay. so lets say Segwitz address starts with 'P00'. you send 1 BTC from a standard address as inputs into the segitz address. the segwitz address now spends back to a standard address. but the way it spends is with non-standard opcodes, so called "bastard unspent outputs". so it spends to a real btc address "1something". When TRB validates it's the chain of tx's it'll encounter the segwit part as NO_OP. Should we just bury these coi
mircea_popescu: i don't see trb should do anything. i also don't see why any sane person would continue dealing with any entity using it.
thestringpuller: ah. but with segwit coins TRB should treat coins as if they are burned?
asciilifeform: and pieces of shit, e.g., https://wiki.openwrt.org/_media/media/tplink/tl-mr3020/tl-mr3020_top-pcb-gpio-pins.jpg?w=400&tok=e00072 << as i once experimented with for trbification << have dram.
mircea_popescu: so really, either iB or outright TRB will have to have an auth layer for nodes.
ascii_deadfiber: the transparent ploy behind the 'soft forks' and related crapolade is to try to siphon btc into corners from which it can no longer be removed with a trb node.
mod6: thestringpuller: so, one thing i can tell for sure from your dpaste is that you're not running the latest trb tree.
asciilifeform: trinque: it was how we genesis'd trb, recall.
asciilifeform: i am NOT and will NOT be willing to sign off on, e.g., tinyscheme, or even trb, with same level of assurance as for code that i and i alone had written.
trinque: my actual possible code paths in say trb should be reflected in the code
mircea_popescu: i personally never got the idea it's part of trb or anything. seemed to me more like a "alf's other project", sort of like the ffz thing.
phf: asciilifeform: i understand that but you're missing what i'm saying. you yourself said that you're not particularly trusting tinyscheme. it has overflow bugs, it has all kinds of issues, and keeping its apartness insulates ~you~ from a certain amount of responsibility. it's no longer serving a purpose as part of a bigger trb patch, now it's this third party "pedigree" thing, that we can sort of rely on, but nobody's responsible for etc.
asciilifeform: 1) trb-genesis
asciilifeform: as would be the case in a mircea_popescuated shiva trb.
mircea_popescu: mod6 : if you're building trb, you start from a trb genesis. if you're building V (via V), you start from a V genesis. and so on.
mod6: so what would your implementation look like here? a patch to a current leaf of the trb patches that inflates say t/t.pl from 'false' on the end of the trb 'light-code' ?
mod6: so we are agreed then that things outside of the trb light-cone, get its own light-cone - a multiverse of things, yeah?
asciilifeform: trb-genesis, and shiva-genesis.
mod6: one inflates the trb universe into bitcoin, the other into v. i guess it doesn't have to be that way.. v-genesis could be added later on down the line as a leaf node. but then it probably shouldn't be named "genesis" as that seems to break the convention.
mod6: mircea_popescu: i mean, if i have genesis.vpatch (trb) and v-genesis.vpatch in http://thebitcoin.foundation/v/
asciilifeform: http://btcbase.org/log/2016-06-13#1481822 << mircea_popescu made a very convincing argument in favour of ~not~ having a central repo of any kind, but rather - if anything - a streamlined mechanism for each lord (including mod6 & ben_vulpes under the banner of trb foundation) to put ~his own trb~ in usable format on ~his own~ www
asciilifeform: ;;later tell mod6 if i want trb i don't need to ask for '/trb/whateverthefuck-fixes-retardation.vpatch', asking for whateverthefuck-fixes-retardation.vpatch must suffice !
a111: Logged on 2016-06-13 23:39 mod6: and since now we have; trb, t, v, ... and many others probably forthcoming, one should need to specify what they want to pull down locally.
mircea_popescu: so you cd trb and it takes you to it.
mircea_popescu: none of this "trb". just make a dir like /7ad78d387187350 or w/e
mod6: so it would be something like: /v/, /trb/, /t/, /gossipd/ or whatever.
mod6: and since now we have; trb, t, v, ... and many others probably forthcoming, one should need to specify what they want to pull down locally.
tb0t: Project: trb, ID: 30, Type: I, Subject: Investigate a new design for the Wallet, Antecedents: , Notes: An investigation must be conducted to create a specification for a reimplemented wallet. The outcome of this will drive ticket 29.
mod6: %p trb 30
mod6: Cool jurov, when they are distrbuted (month end?), just hit me up.
tb0t: Project: trb, ID: 3, Type: I, Subject: Further investigate a solution for mem leak/fragmentation, Antecedents: , Notes: An OOM error occurs from mempool tx's that are never deallocated. A well defined and researched plan need to emerge from this investigation.
mod6: %p trb 3
mod6: %e trb 3 I "Further investigate a solution for mem leak/fragmentation" "An OOM error occurs from mempool tx's that are never deallocated. A well defined and researched plan need to emerge from this investigation."
asciilifeform: ;;later tell mod6 'It has been well established that OOM error occurs from bastards not being freed from memory.' << not accurate. bastard tx don't enter the mempool in trb. it is mempool tx that never deallocate...
mod6: ok. so what I was thinking, at least for the quick/dirty method was that lord of a project would update tickets with peoples' submitted vpatches linked either from the ML or if/when accepted. doesn't only relate to TRB obv.
a111: Logged on 2016-06-09 22:25 mod6: http://thebitcoin.foundation/tickets/trb_ticket_graph.html
a111: Logged on 2016-06-09 22:25 mod6: http://thebitcoin.foundation/tickets/trb_ticket_graph.html
tb0t: Project: trb, ID: 28, Type: S, Subject: Ideal bitcoin, Antecedents: 3,4,5,12,14,15,18,19,20,21,25,26, Notes:
mod6: %p trb 28
mod6: I'm sick of "epic" tickets, so came up with a "saga". For trb, a saga is something like ``ideal bitcoin''.
mod6: <+mircea_popescu> mod6 http://thebitcoin.foundation/tickets/trb_ascii_graph.txt << ideally numbers should be hooverable, ie show ticket content if you put mouse on it. title="$ticket" iirc. << sure. the ascii ticket graph is just ascii. not sure of any way to "mark up" the text without turning into something that's not text.
mircea_popescu: mod6 http://thebitcoin.foundation/tickets/trb_ascii_graph.txt << ideally numbers should be hooverable, ie show ticket content if you put mouse on it. title="$ticket" iirc.
tb0t: Projects: trb
tb0t: Project: trb, ID: 32, Type: T, Subject: Test funk's import/dump priv key vpatch, Antecedents: 2, Notes: Use mod6's rebased vpatch, apply to latest vpatches in thebitcoin.foundation mirror. Test import/export of private keys. Should use both valid and invalid keys here. Also test send/recieve; leave no stone unturned. http://www.mod6.net/btcf/test/mod6_funken_prikey_tools.vpatch
mod6: %p trb 32
mod6: As soon as we get through the testing, will deploy here and hopefully can turn attention to trb stuffs.
a111: Logged on 2016-06-04 18:44 asciilifeform: ;;later tell mod6 the openssl people hosed your stator script by moving their turdball without a redirect. can we plz stop linking to derps in trb autoloaders ?
mod6: <+pete_dushenski> mod6: any timeline on the 99994k release ? looking forward to testing trb with import/export, etc. << not at the moment.
pete_dushenski: mod6: any timeline on the 99994k release ? looking forward to testing trb with import/export, etc.
asciilifeform: do you recall my attempt at forcing trb to flush its mempool?
asciilifeform: http://btcbase.org/log/2016-06-04#1476897 << mod6 i was talking about the stator.sh in the tarball distributed on therealbitcoin.org. but more generally speaking we should NOT be linking to openssl.org or other heathens! the tarballs are not so big, they ought to be on trb site.
a111: Logged on 2016-06-04 18:44 asciilifeform: ;;later tell mod6 the openssl people hosed your stator script by moving their turdball without a redirect. can we plz stop linking to derps in trb autoloaders ?
asciilifeform: ;;later tell mod6 the openssl people hosed your stator script by moving their turdball without a redirect. can we plz stop linking to derps in trb autoloaders ?
pete_dushenski: obviously, it doesn't create a proper tx, but trb doesn't know this and so effectively locks the coins from being spent.
pete_dushenski: speaking of which, anyone ever tried to send full 'account balance' from trb node when it was clearly a bullshit number ?
mod6: <+trinque> monday night I'm gonna migrate deedbot off my trb node box; will be much more responsive << cool
trinque: monday night I'm gonna migrate deedbot off my trb node box; will be much more responsive
mod6: <+asciilifeform> (recall, block index is RETARDEDLY kept resident in ram, being first leak) << yeah, getting these into `t' for the trb project will be a big main priority once i get tbot deployed.
asciilifeform: the memory leak will still have to be killed though, before these can trb.
ben_vulpes: trb node!
asciilifeform: or whether the trb on the box is worth using any moar
asciilifeform: phuctor, trb
shinohai: I want to run a trb node on one of vc 's boxes if he gets moar power
asciilifeform: farewell 136+ day trb uptime
mircea_popescu: basically some usg assholes tried to hijack the bitcoin. trb aka the real bitcoin is the... well, the real bitcoin.
vc: I do not know what a trb node is
mircea_popescu: tell you what : i'll buy that, and pay it in advance for a year, provided you install and manage a trb node there.
asciilifeform: it was the trb source callgraph
mircea_popescu: ah yeah. i think we'll need to make a "min 4gb ram for new boxes" tmsr standard ; so people can run general purpose + trb on them
trinque: nah, that box is getting pushed into swap by trb
asciilifeform: i've wondered often who precisely they paid, and how much, to set up even a basic 'first 6mo of trb'-level framework for them of understanding how the shitsoup even worx
asciilifeform: i'd be curious, though, to meet a usg fauxtoshi who is willing to endure 5 minutes of my questions re trb src.
mircea_popescu: asciilifeform but in a discussion of indian tribes, the smaller trbie with guns that wipes the larger tribe with tomahawks HAS, in fact, deployed the technology.
shinohai: Will bve downloading trb blockchain with packet radio xD
asciilifeform: http://trilema.com/2013/the-future-in-the-past << great vintage mircea_popescutronic lul re trb...
asciilifeform: trb on dulap up for 127 d, 17h, 30m, contiguous; current footprint == ~8G.
asciilifeform: dulap (nosuchlabs.com, but recall we have no dns, it is 46.166.165.30 for trb purposes)
asciilifeform: (in practice, trb node on a decent box like dulap can run for a very long time - years - without reset)
mircea_popescu: asciilifeform lol trb nodes still oom. darn.
asciilifeform: http://btcbase.org/log/2016-05-16#1467378 << i must point out that, at least on same nazi site, the count of trb nodez is also record low - 5
mod6: what i also want to build is a CI thingy for trb
asciilifeform: what can i do, even my trb hasn't restarted since december
asciilifeform: my vtron was very much a battlefield wunderwaffen, adequate strictly for pressing a well-gardened trb tree that consisted 95% of asciilifeform
mod6 builds trb with key tools
mod6: or btcbase.org/trb
mod6: is there a base link to this page? should be something like trb.btcbase.org or something
mod6: <+a111> Logged on 2016-05-02 20:05 asciilifeform: ;;later tell jurov observed any spike in trb site traffic ? (it is linked from nosuchlabs.com) << cat /var/log/thebitcoin.foundation-* | grep "nosuchlabs" | wc -l 69
asciilifeform: e.g. trb and dns.
a111: Logged on 2016-05-02 20:05 asciilifeform: ;;later tell jurov observed any spike in trb site traffic ? (it is linked from nosuchlabs.com)
jurov: asciilifeform: toplevel trb is just redirected to thebitcoin.foundation, that is ran by mod6
ascii_butugychag: it is, perhaps, why i'm still alive - if 'accidented', then, e.g., trb, suddenly becomes more interesting to a buncha folk
ascii_deadfiber: witness that ~nobody walks in asking after trb, for instance.
asciilifeform: ;;later tell jurov observed any spike in trb site traffic ? (it is linked from nosuchlabs.com)
asciilifeform: but this includes, e.g., trb.
mircea_popescu: yeah but trb really doesn't load worth the mention. especially if caught up.
asciilifeform: recall it is also trb.
asciilifeform: where, i suspect, the only folks able to connect to the trb node on same box are also us.
mod6: <+adlai> mod6: and i say this with greatest regard for alf, but i will probably get more "12step" mileage out of your T-shirt (of the hair variety, sadly, but trimmer than orgmode!) than trb and phuctor, combined << wut? you lost me there amigo.
adlai: unless trb manages to compile itself next time i kick it.
adlai: mod6: and i say this with greatest regard for alf, but i will probably get more "12step" mileage out of your T-shirt (of the hair variety, sadly, but trimmer than orgmode!) than trb and phuctor, combined
asciilifeform: (does anyone still recall how trb was originally something i asked nubs to make!)
asciilifeform: after departure of nubs, who will print trb!1?111
ben_vulpes: pete_dushenski: i don't think anyone's using kelvin versioning on trb
asciilifeform: unrelatedly, trb has been up for 100+ consecutive dayz there.
pete_dushenski: http://dpaste.com/0WEJ6BF.txt << this is a new flavour of blackholing trb for me. "added time data" ??!
shinohai: Any new updates on trb?
asciilifeform: trinque: same place as the lag on my trb nodez
mircea_popescu: i think for some reason you got the idea that if mp gets phuctor server it's ok to come in, redefine it as "trb node" and move on.
asciilifeform: <mircea_popescu> including five straight months of 1/4 gb ram box at close to a btc/month pulling our dicks. << that thing incidentally has been the ONLY public trb node that has never fallen down. not once.
ben_vulpes: i have a pgbomination wired into trb somewhere in my working tree.
ben_vulpes: asciilifeform: trb is also a millstone, not a mill.
asciilifeform: and yes, i ported trb to arm. as wartime wunderwaffen (which went nowhere.)
shinohai would love to put trb on a gameboy one day
shinohai: The only reason I used it was for trb private key issues, and the last time I tried to add a key it borked the entire wallet.dat.
adlai unlike trb donators has much more creative paranoiae
asciilifeform: (or from trb at any rate, iirc mod6 had this in his original diagrammator)
pete_dushenski: i have some more fiddling to do with trb it seems.
pete_dushenski: then a 'listunspent' would seem a useful call function to bring to trb (it was in 0.7). unless there are other call functions that already do the same thing ?
pete_dushenski: trb related : has anyone else had bizarre 'balance' behaviour ? i'm seeing double over here.
mircea_popescu: asciilifeform the relationship between sane bitcoin source as available on trb www and "bitcoin" is THE SAME as the relation between a sane implementation of tetris and "running tetris"
asciilifeform: mircea_popescu: trb's www
phf: but first we port symbolics ada to scheme-81, so we can compile trb with symbolics ada
asciilifeform: ;;later tell mircea_popescu i had a notion: if we're no longer holding the 'father's pistols' line, is there any good reason not to replace openssl in trb with, e.g., ada bignum ?
asciilifeform: mircea_popescu, ben_vulpes, mod6, et al : did jurov stop working as trb treasurer , coinbr operator ? i must have missed this ? 'cause i dun see him in the mircea_popescutronic list
asciilifeform: next we calculate how many sheets of toiler paper trb fits on, etc.
asciilifeform: in other nyooz, the immunocompromise thing was accurate, already folks who oughta know better, on old planet, asked me if i'd host a powerranger idiot repo 'for trb'
mod6: speaking of which, i literally did jack fuck all this past month on trb
pete_dushenski: well there are trb nodes and there are nodes displaying version string 99999
shinohai: I wanted something a little nicer to look at that listed solely trb nodes. I know it is on wiki but ...
shinohai: hey pete_dushenski i havent done much to it unfortunately, just still running my vanilla trb node
punkman: the lords are shit, the logs are shit, bitcoin is shit, trb is shit
asciilifeform: there are reasons why my first act re trb was to exterminate all compatibility with microshit
jurov: i consider whole trb thing as something that demands my full attention, and there's always something more urgent to do...
asciilifeform: and this is a patch without which trb is ~dead in the water~
asciilifeform: it was EMINENTLY possible to build trb pre-v.
asciilifeform: (rotor invokes boost's jam thing but trb, recall, builds with ordinary gnumake)
asciilifeform: http://log.bitcoin-assets.com/?date=19-03-2016#1436543 << there is no provision for anything of the kind in trb, beyond the barbaric expedient of a tx which throws exception during processing simply not being stored
thestringpuller: fuck. i guess I'll just add watchdog and if logs don't have `ProcessBlock: ACCEPTED` in the last 60 minutes `kill -9 <pid>; ./startrb.sh`
asciilifeform: thestringpuller: nope, the only genuine solution would be multithreaded trb
asciilifeform: in related nyooz, i discovered that one of my test trb boxen has been wedged, without any meaningful log noise whatsoever, for ~2wks
assbot: Logged on 19-03-2016 17:19:23; mod6: Does anyone else see these error messages running the latest trb (minus shiva)? Looks to be in main.cpp:ProcessMessage around lines 1855:1913. It doesn't look to me to be related to the malleus patch, but I could be wrong there. Thoughts? Seen the same in your logs? Plz let us know. http://dpaste.com/21PJMY4.txt
mod6: Does anyone else see these error messages running the latest trb (minus shiva)? Looks to be in main.cpp:ProcessMessage around lines 1855:1913. It doesn't look to me to be related to the malleus patch, but I could be wrong there. Thoughts? Seen the same in your logs? Plz let us know. http://dpaste.com/21PJMY4.txt
trinque: alrighty! trb wallet deedbug fixed.
asciilifeform: and contemplating trbtronics, rather than praying to vishnu ?
trinque: jumped onto trb intending to cause myself severe pain such that gears of progress and whatnot
mircea_popescu: even historical order would acvtually beat trb on this.
asciilifeform: which is what we have in trb
asciilifeform: wallet (incl. trb) ~much~ dislikes doublespends
mircea_popescu: so your idea is, that we of course continue to maintain trb as is, but also develop a keccak pow variant, for use in case of forks ? or vice-versa, in case of forks develop it ?
asciilifeform: keccak-clean and keccak-trbchain.
adlai: asciilifeform: "port" in the loose sense of the word. let's rephrase that as "some poor code monkey should write a keccak vpatch for trb, but nobody should ever have to use it"
mircea_popescu: at no point was it proposed that trb does.
adlai: but i don't think trb should initiate a fork.
adlai: mircea_popescu: hmmm. ok, this is a valid question, my answer to which is: port Luke-Jr's keccak reset from "classic" to trb, and be ready to activate it, should a fork occur.
mircea_popescu: adlai wouldja think for a moment ? if miners fork tomorrow, pre-miner-fork trb will not be defensible. because bitfury (you know, kakobrekla's friends) have access to vc capital, and will bridge the gap between us printing press and chinese mining.
asciilifeform: or introduction of material from either into a future trb
assbot: Logged on 17-02-2016 12:54:09; asciilifeform: http://log.bitcoin-assets.com/?date=17-02-2016#1408030 << it had own genesis to establish pedigree with the historic tinyscheme. but shiva is a patch that bridges it into the trb tree. and yes i rebased it, it works with the current trb.
solrodar: I did the trb call graphing work last year
polarbeard: sup trb, any development going on since my patches got fired? B)
shinohai: ;;later tell mod6 gentoo trb v99995 was a success
mod6: shinohai: cool! what do you wanna test? probably should get all the pre-req's installed and then build trb with the latest build script: http://deedot.org/build-bitcoind-V99995.sh
trinque: I have trb dev time today. it does not address the point made about education and its function in a culture
mircea_popescu: so basically you propose - wait and see on trb, meanwhile i'll also develop a fork variant which i won't either share or have ready in time ?
asciilifeform: i will maintain trb, while 1,001 things incl. writing mine.
asciilifeform: if trb gets chainclobbered - it is 2009 again for us.
mircea_popescu: so in this sense, "trb as is only" opens us up to being forced, later on, to pick among the idiots.
mircea_popescu: there is a very specific danger which you perhaps are not seeing. if indeed we continu with trb as is, and if indeed 3) happens, as these two share pow and we don't control .7 or so exahash we become extremelty vulnerable. recall the fate of altcoin ?
mircea_popescu: but you should note, that there is no good reason to consider current trb so much different from cases 1-3.
mircea_popescu: in any case trb isn't going anywhere, nor need it go anywhere.
mircea_popescu: at this juncture, tmsr must make the decision if it will continue strictly with trb, or ALSO offer a tmsr fork of trb.
asciilifeform: and where did trb go ?
jurov: i was thinking about it as potential learning practice for trb... but such things would make alf shit girder beams
assbot: Logged on 10-03-2016 12:41:33; asciilifeform: i was willing to deal with the cpp miseryu of trb because 1) it pre-dates bitcoin being valuable 2) it was - and remains - the schelling point, 'father's pistols'
assbot: Logged on 10-03-2016 10:43:06; mircea_popescu: in other news - it still remains likely that this summer will see a bevy of various hardforks on offer. practically speaking, trb can offer either its own candidate, which takes a lot of work, or else sit tight and we'll follow the more intelligent of the avaialble offerings, which takes less work but also implies a lot of risk - experience to date shows that there's precious little intelligence avai
asciilifeform: jurov: it is for working on trb !
shinohai: I will use trb as long as it works on the overall network, failing that I will have to find something else to occupy my time.
asciilifeform: i was willing to deal with the cpp miseryu of trb because 1) it pre-dates bitcoin being valuable 2) it was - and remains - the schelling point, 'father's pistols'
assbot: Logged on 10-03-2016 10:43:06; mircea_popescu: in other news - it still remains likely that this summer will see a bevy of various hardforks on offer. practically speaking, trb can offer either its own candidate, which takes a lot of work, or else sit tight and we'll follow the more intelligent of the avaialble offerings, which takes less work but also implies a lot of risk - experience to date shows that there's precious little intelligence avai
mircea_popescu: in other news - it still remains likely that this summer will see a bevy of various hardforks on offer. practically speaking, trb can offer either its own candidate, which takes a lot of work, or else sit tight and we'll follow the more intelligent of the avaialble offerings, which takes less work but also implies a lot of risk - experience to date shows that there's precious little intelligence available outside the w
mircea_popescu: trinque> rather than dissect it, I wish to stop using the wallet entirely (as I did before with btcd) and just write a sendrawtxn for shiva <<< a raw tx manipulator for trb is prolly a very useful item, really.
asciilifeform: so i go and send on another box and guess what, it had previous trb, and tx is high-s.
asciilifeform: that trb chokes on, during rescan, and quits.
PeterL: so, as I have been watching my trb node sync the past three months (am I the only person who thinks this takes way too long?) it seems like it spends alot of time trying to connect to nodes and timing out?