log☇︎
2300+ entries in 0.235s
hanbot: http://btcbase.org/log/2017-02-19#1615687 << fwiw, receiving wallet does see amt sent. meanwhile trb restarted with -rescan shows same balance as before, which we now realize *had changed* following transaction just...not by amt sent. to wit, listtransactions sees original balance, sees correct sent amt with fee, nevertheless balance via getinfo has mystery-difference. which shows as a negative, and only value, via listaccounts. ☝︎
asciilifeform: ada proggy, speaks the protocol as defined by trb; but does not attempt to verify blocks, instead uses its 'horse' (trb node it rides) as an oracle
asciilifeform has been experimenting with a proggy that 'rides' a trb node, and takes over all comms with outside world
asciilifeform: and yes, i revved up a fully mod6tronic trb to have what to patch against, my working copies are quite dated
asciilifeform: considering that this builds toolchain, gcc, linux kernel, busybox userland (currently unused), then trb deps, and then trb...
asciilifeform reports a successful replication of mod6's recipe http://thebitcoin.foundation/trb-howto.html , 'offline' variant, using his vtron etc. took exactly 40 minutes from the instance of making an empty dir to do it in, to having <5MB finished binary in my hands.
asciilifeform: http://btcbase.org/log/2017-02-19#1615717 << i gotta wonder what the folx without 1+ working trb node, think they are doing. ☝︎
asciilifeform: in other lulz, heathendom https://bitnodes.21.co/nodes/?q=/therealbitcoin.org:0.9.99.99 sees 9 trb nodez.
mircea_popescu: i am not against trb having a debugger
asciilifeform: to revisit upstack, ftr trb still does not have a tx debugger. when, e.g., mircea_popescu, asks me 'have you seen tx T', all i have is to grep the log barf
asciilifeform: mircea_popescu: consider publishing your tx debugger as a trb patch ? (the thing that lets mircea_popescu answer questions like 'where is ea58f22fe5bbb4f42edb8be90a37f98b57af12007f7620f7ab94111a06ff3ebb ?' )
mircea_popescu: i'm not entirely sure, but afaik trb still imports original satoshi assumptive boneheadedness in that it will not consider tx updating its own wallet which it didn't issue itself.
mircea_popescu: i don't think trb updates your wallet balance in this case. it updates it when it sends something, it doesn't rescan for doublespends.
hanbot: i mean the amt sent to non-trb wallet is still included in trb wallet.
hanbot: test tx via trb using sendtoaddress fails to send diddly squat, meanwhile @ blockchain.info: transaction rejected by our node. Reason:Script resulted in a non-true stack: []
thestringpuller: asciilifeform: would i have to modify how OpenSSL is initialized in order to use FUCKGOATS with TRB? >> https://wiki.openssl.org/index.php/Random_Numbers#Hardware
a111: Logged on 2017-02-16 02:49 hanbot: what's the proper name to ascribe to this super fun phenomenon wherein trb node happily catches up on blocks until 99.x% and then drops connections and stops seeing new blocks after <10mins?
a111: Logged on 2017-01-13 02:53 asciilifeform: http://btcbase.org/log/2017-01-12#1602003 << we do not, afaik, presently have a knob in trb that would enable the 'at you' part of this.
asciilifeform: what you want is a box that ~only~ talks to a handful of trb nodes. that you operate.
asciilifeform: ben_vulpes: didja try the scheme where your node only talks to trb nodes ?
ben_vulpes: so in light of the triviality with which the TRB node to which mimisbrunnr talks is taken out by even moderately determined actors, i'm considering taking the whole thing down until i have a more robust data collector system in place.
asciilifeform: different patch sets will give trb with DEEPLY differing behaviours.
asciilifeform: hanbot: (and everyone else reporting a suboptimally-behaving trb node) -- plz consider stating the vpatch-set
asciilifeform: ( recall when i suggested to distribute trb+buildroot+gcc et al. on a cdrom. )
asciilifeform: incidentally i realized that, sadly, trb will need a (simple) patch in order to link via 'g'. from simple fact that, by default, it does not like to connect to 127.0.0.1:weirdport
BingoBoingo: Coding patch to simply say "no" to compact blocks and restore TRB/PRB communion would likely be trivial, BUT setting that precedent is impossibru
hanbot: what's the proper name to ascribe to this super fun phenomenon wherein trb node happily catches up on blocks until 99.x% and then drops connections and stops seeing new blocks after <10mins? ☟︎
a111: Logged on 2017-02-08 20:46 Reuel: mircea_popescu, i am geting blocks so i guess i built TRB, what would you suggest i do next? you mentioned mimisbrunnr, looking at that now, anything practical I could do except read?
mircea_popescu: http://btcbase.org/log/2017-02-08#1612495 << if your trb node is on solid hardware might as well add it to the list of nodes ; otherwise there's an ample swath of thingd to do, depends what your inclination is. i suggested looking into mimisbrunnr in the context of http://btcbase.org/log/2017-01-29#1609460 ☝︎☝︎
Reuel: mircea_popescu, i am geting blocks so i guess i built TRB, what would you suggest i do next? you mentioned mimisbrunnr, looking at that now, anything practical I could do except read? ☟︎
shinohai: http://thebitcoin.foundation/trb-howto.html <<< is pretty self explanatory ... phf also has a nice source viewer which is helpful for reading the code.
Reuel: does trb have the bitcoin-cli rpc stuff like the other implementation?
shinohai: Reuel: I'd say Gentoo myself, though trb *has* built countless times for me on Ubuntu/Debian
Reuel: When I am looking at the TRB site seals, I see more than one for each patch, does that mean code has been reviewed?
asciilifeform: anyone other than thestringpuller has trb node that can't hear dulap ?
thestringpuller: as of current looks like there are no TRB nodes responding
shinohai: Strange wheezy won't build trb ... I did it < month ago without issue.
thestringpuller: mod6: wheezy doesn't want to build TRB anymore. ping me if you have a specific image that you recommend from the wheezy era
nicknaem: on another machine now just wanted to get the keys as described in http://thebitcoin.foundation/trb-howto.html
pete_dushenski: trb has 'help' yes ?
pete_dushenski: my own recent efforts at coding are going less productively. trying to implement polarbeard's 'getpeerinfo' patch and can't even get trb to show the option on the help menu nevermind implement the functionality
a111: Logged on 2017-02-03 15:26 asciilifeform: http://btcbase.org/log/2017-02-03#1611084 << it is approximately as useful as trb's wallet encrypter, and for the same reason
mircea_popescu: http://btcbase.org/log/2017-02-03#1611095 << this is not actually true. trb wallet encryptor is pretty strong. not ideal, but there's no actual cause of worry if you lose an encrypted bitcoi nwallet (still, doesn't encrypt metadata, has many other warts discussed in http://trilema.com/2016/the-ideal-bitcoin-wallet/ ) ; i wouldn't say same re gpg keyring. ☝︎
asciilifeform: http://btcbase.org/log/2017-02-03#1611084 << it is approximately as useful as trb's wallet encrypter, and for the same reason ☝︎☟︎
pete_dushenski , very late to the party, wishes for getpeerinfo in trb
ben_vulpes: pete_dushenski: the most i can imagine you'll learn about the differences between prb and trb without reading the source is that the latter doesn't have a gui
asciilifeform: it is not actually very enlightening to a student of trb, because various subsystems were replaced wholesale.
pete_dushenski: i have no such software in operation atm. though i may fire one up just to see what i can learn about the cuts trb ultimately made.
asciilifeform: as for mempool messages, we have , in current trb :
asciilifeform: i can trivially cause it on my box by throwing, e.g., FUCKGOATS genesis, into trb dir...
mod6: I need to get the ball rolling for something like that with TRB as well.
asciilifeform: imho it may or may not make sense to make a tool just for trb. just as raising most ww2 sunken submarines is not +ev, only the ones full of nazi gold.
asciilifeform: the only cpp in my pogo build was trb.
asciilifeform: trb is the only one i know of first-hand
asciilifeform: btw mircea_popescu's list of Open Problemz imho should include (~usable~, unlike solrodar's) trb flow-graph
mircea_popescu: use v to set up a trb node yes.
mircea_popescu: ah. well, from a simple "cs competency" perspective, doing a trb build first is very good practice. i'll familiarize you with what's here a minimal bar of qualification and anywhere else above the reach of graduate students somehow. and it'll show you the power of the tools and the quality of the engineering.
mircea_popescu: do you understand the bitcoin end of things ? are you running a client ? ever got a v-build of trb to run for instance ?
a111: Logged on 2017-01-27 19:32 ben_vulpes: davout: reference miner is still in trb bin.
asciilifeform: again, if davout breaks his trb, and signs off on a b0rk3d proggy, it does not 'pick my pocket or break my leg', mine will still work.
asciilifeform: and in fact recall, i asked for trb, because i wanted The B00k
asciilifeform: fwiw i do not hold to 'trb 4evah!'
asciilifeform: which is why the clock on replacing trb, does run.
asciilifeform: my objection is not 'davout Broke Trb oh noez!!' but to the thought process that might lead an otherwise literate d00d to contemplate a 'reference' that lacks vital organs as a valid thing
asciilifeform: ditto trb-minus-mempool.
asciilifeform: ditto trb-minus-any-miner.
asciilifeform: but to rewind: i do not object to davout mutilating his own personal trb however he likes. however i do object to calling a trb-minus-any-wallet a 'reference implementation'.
asciilifeform: btw since folx are itchy to snippety-snip, i will note, there is actual dead code in trb
asciilifeform: in point of fact if trb knew how to eat raw tx, you have the knob, neh?
asciilifeform: i asked very specific question. say davout makes a wallet-less trb. and for some reason we all embrace it and roll it into each his own personal vtree.
trinque: the wallet merely generates inputs trb will validate or not independently of it
davout: asciilifeform: trb is about keeping the core, prb is about "moar featurez"
asciilifeform: what i would like to do in this thread, is to ask folx to stop and think for half a minute about what differentiates trb from prb.
ben_vulpes: davout: reference miner is still in trb bin. ☟︎
ben_vulpes: davout: what /currently/ compiles as the single binary "trb"
davout: i'm not really sure whether transaction signature itself should stay in trb or be extracted out
ben_vulpes: i am still not sold on moving the wallet outside of what compiles as "trb"
davout: asciilifeform: if trb provides sane endpoints the wallet can be written in whatever floats anyone's boat
asciilifeform: in fact, until we nailed down the dependencies all the way down to the kernel and gcc, it was possible to argue that trb does not define bitcoin.
asciilifeform: but to lose functionality, however uncommonly needed, that does exactly 0 harm, and the loss of which reduces by no amount the labour of a trb code reader, is at best a snore.
davout: if you ~must~ verify one of those sigs you pull up a trb that can ~fin~
davout: maybe we can have trb-classic then trollface.jpg
trinque: there are goals at odds here. to fix the nightmare that is current trb, gotta start slashing til you have something that's able to be comprehended
trinque: "nothing but this particular arrangement of driftwood counts as actual reference trb"
davout: asciilifeform: the trb tree has a "continuity-preserving" mission, not "current trb official version"
asciilifeform: davout: yes, they could 'rebuild historical trb' but imho if this is a kind of thing that ever becomes necessary, trb will have failed in its continuity-preserving mission.
davout: asciilifeform: archaeologists can build a verifymessage-capable trb, couldn't they?
asciilifeform: trinque: trb already exists in multiple branches, such is the nature of vtronics.
trinque: I don't see that it'd be a terrible sin to have multiple branches descending from current trb
davout: lighter trb?
thestringpuller: s/with bitcoin/with trb*
thestringpuller: is there a way to scrape the UTXO set in TRB or do you have to do that manually as of now?
asciilifeform: snipping old wallet is a trivial patch, i suspect that any and each of trb folx could re-create it in half hour
asciilifeform: if , using your trb, i cannot transact ?
asciilifeform: mircea_popescu had a pretty good imho description of the necessary cutting-apart of trb
ben_vulpes: davout: why would you even consider releasing a patch that leaves trb unable to cook and transmit transactions? keep it on your table where it's useful to you.
davout: asciilifeform: can use same openssl as trb
ben_vulpes: davout: trb cannot exist in a state where "user must supply code for x"
asciilifeform: or is the plan to create (why???) a quite-useless castrato-trb.
davout: asciilifeform: to me trb just has to provide "return txouts spendable by arbitrary set of addresses", "add this transaction to mempool"