tmsr - Search: prb

jfw: mod6: do we have any picture of what software the larger miners are running these days? Because that's the possibly-prb-afflicted network I'd rather not be isolated from.

mod6: Your notion is correct on the former, 'more exposed to potentially misbehaving or sybil peers'. As to the latter, I suspect you will be connected simply more prb nodes. It is possible that you'll also find, in a 'subgraph', nodes that are playing nicely, but seems less likely.

asciilifeform: some subset of chinese are almost certainly tuned into prb net specifically to collect that delish candy of eventually-unwindable 'pay-anyone' segshit tx.

asciilifeform: iirc past coupla yrs of prb won't even give peers table. but i'm not interested so much in what prb nodes have to say to begin with.

BingoBoingo: I'm suspecting a lot of nodes on the intermediate PRB version numbers 0.8, 0.9, etc before peer-to-peer pki-ism are falling enough that we may have few bridges allowing communication between prb and trb

a111: Logged on 2017-08-14 18:53 asciilifeform: meanwhile, usg.prb folx claiming they will soon 'broadcast blocks from satellite', 'use prb without internet!111' -- leveraging the orbit monopoly to diddle 'these blox, mined by us, legal, other, terrorist blox -- orphans nao'

asciilifeform: prb had 'orphanage' mechanism where it accepted antecedent-less inputs 'on faith'. this opens node both to memory exhaustion and algorithmic complexity attack (i.e. crafted input can prompt machine into wasting arbitrary amt of memory, + arbitrary amt of cpu cycle walking it)

girlattorney: asciilifeform i'm aware of the fast sync part. Just saying that when i sync a node i actually get data from other prb nodes. I'm not getting garbage or errors, and I think (not being technically able unfortunately) that you could modify prb to verify all the blocks, and eventually discard the excess if I reecived them in sprayed order

a111: Logged on 2019-07-16 12:52 asciilifeform: trb, unlike prb, does not accept blocks 'on credit' (i.e. ones for whom the antecedent block is not yet on the disk)

asciilifeform: girlattorney: 'core' (aka prb) when bootstrapping, asks randomly selected peer for 'headers' and eats'em on faith. afterwards does same with blocks (none of which it bothers to actually verify, in the traditional sense)

asciilifeform: BingoBoingo: fwiw none of the nodes i've operated were ever set to masquerade as prb (other than in the 0.9999... aspect)

girlattorney: but let's say the following: you get a core (prb) node, you set a minrelaytxfee very high, so you don't propagate at all, just include what new blocks have because you have to (to stay up to date)

a111: Logged on 2019-07-16 12:52 asciilifeform: trb, unlike prb, does not accept blocks 'on credit' (i.e. ones for whom the antecedent block is not yet on the disk)

asciilifeform: trb, unlike prb, does not accept blocks 'on credit' (i.e. ones for whom the antecedent block is not yet on the disk) ☟︎☟︎

asciilifeform: http://btcbase.org/log/2019-07-16#1922523 << trb doesn't ignore, the (prb-powered) 'blockchain sites' ignore. ☝︎

mp_en_viaje: (prb is the name given to the one remaining group of scammers masquerading as bitcoin developers, in memory of their "power rangers" heritage. numerous others have meanwhile discontinued, too many to merit enumeration.)

asciilifeform hasn't looked at prb in years, wouldn't at this point be surprised by anything at all

asciilifeform: granted , it is impossible to say what exactly the 9000 garbage 'nodes' are running, it could be a published prb , or just about anyffin else entirely.

asciilifeform: that being said, none of the prb's asciilifeform dissected to date, appeared to contain any mechanism that would preferentially propagate a tx in an n-spend set vs 'ordinary'

asciilifeform: BingoBoingo: prb ~does~ iirc have a lulzy notion that it can somehow prefer 1 tx in an n-spend tuple ~in mempool~ as 'the real tx' (the protocol offers no such mechanism, of course, tx dun contain anyffin to tie it to e.g. leading block when-issued , only a promisetronic timestamp that can equal whatever the issuer wants)

asciilifeform: BingoBoingo: unless , i suppose, you know of some prb variant that in fact preferentially relays 'double spends'

a111: Logged on 2019-04-02 19:37 asciilifeform: http://btcbase.org/log/2019-04-02#1906563 << the 1 gotcha, is that if you (or peers) are wedged (genuinely wedged, on db grind; or peers wedged; or stuck on island in sea of prb; or... buncha documented , in log, cases ) then will get exactly 'where the fuck is my tx' errytime

asciilifeform: http://btcbase.org/log/2019-04-02#1906563 << the 1 gotcha, is that if you (or peers) are wedged (genuinely wedged, on db grind; or peers wedged; or stuck on island in sea of prb; or... buncha documented , in log, cases ) then will get exactly 'where the fuck is my tx' errytime ☝︎☟︎☟︎

a111: Logged on 2019-02-17 16:10 mircea_popescu: asciilifeform i very much don't expect you want the prb 12 that is emacs. rewrite yes ? :D

mircea_popescu: asciilifeform i very much don't expect you want the prb 12 that is emacs. rewrite yes ? :D ☟︎

asciilifeform: re 'e', i can't picture what'd move anyone with two neurons to rub together to maintain a glibc, that'd be rather like starting a trb from prb 12 (or what is current one)

asciilifeform: for that matter, somebody's still perpetrating (i hesitate to describe as 'maintain') prb

mircea_popescu: mats you can check by connecting independently to a prb node and checking if it reports it in its mempool.

asciilifeform: 'cyber threats' is, a la prb, smoke grenade to obscure the actual ur-'cyberthreat' to reich, i.e. comp stack sans usg

mircea_popescu: in other dubious news, i see some old versions of prb stuck on block 551110

a111: Logged on 2018-12-01 18:37 asciilifeform: http://btcbase.org/log/2018-12-01#1877254 << pretty lulzy, and apparently not a joak -- indeed some folx, somewhere, habitually move 20-30k coin in 1 shot, and doing it with prb and onto segshitaddrs

asciilifeform: http://btcbase.org/log/2018-12-01#1877254 << pretty lulzy, and apparently not a joak -- indeed some folx, somewhere, habitually move 20-30k coin in 1 shot, and doing it with prb and onto segshitaddrs ☝︎☟︎

asciilifeform: they junkyardwars'd together a working ottoman-style org system ought of sumthing like '80s su -- sorta like we trb from prb etc

asciilifeform: mod6: afaik 'current' prb is more or less separate net, for all practical purpose

mod6: yeah, exactly. prb is fake-cheese, for losers. can't hack it with the republic, the false choice is thinking that they have an alternative - a loser one at at that. but there really is no alternative. no matter how much you wish it to be REAL cheese, it is not, and never will be.

asciilifeform: mircea_popescu: aha, but still gotta wonder. rly, srsly, prb ??

asciilifeform: i do sometimes wonder what goes on in the heads, 'hey i hate them nao, mebbe prb is where it's at', wtf

asciilifeform: iirc shinohai also started prb approx 6mo after his 'what am i doing here' monologue

asciilifeform: the only practical defense against this is checkpointing, afaik. ( the prb folx tried to defend with 'orphanage', but with finite ram this does not actually solve the problem in the general case, simply ensures that different noades will wedge at different times )

asciilifeform: mod6: i think there's also an ordinary (as they go) prb noad mixed into that pcap

asciilifeform: suggests that the typical shitcoin-of-the-day nowadays is a bch-style phork, rather than 2013-style 'prb with genesis swapped'

asciilifeform: i gotta wonder nao, if prb's tx checker is porous enuff that it actually relays these !

asciilifeform: if receiving end were prb ( which last i knew, still had the 'orphanage' thing ) -- would balloon to fill ram

mircea_popescu: certainly. in general speaking, trbi will prolly not use any of the current trb/prb legacy common code

asciilifeform: it doesn't actually speed up sync ( alert long-time readers will know why : sig verification, contrary to the spew of the prb people, is NOT bottleneck for acceptblock() , rather tx indexing is )

asciilifeform: in not wholly-unrelated lulz, the # of prb 'nodes' that break the protocol in all kinds of ways, is astonishing even to asciilifeform ; it's a wonder they manage to relay anyffing at all

asciilifeform: phf: context : i was baking a noad walker / torturer, orig in python, little thing, thought it would be doable in a day or 2; then found that mass of prb etc all break protocol in 9000 interesting ways, an extra byte here an' there, and realized that it aint doable without adult condition handling/restarts, which means cl.

asciilifeform: mircea_popescu: funnily enuff, kako was actually trying to bake one of these, and i was almost disappointed when it flamed out and left the current cinders, largely consisting of spamola and occasional prb 'news'

asciilifeform: meanwhile in upstack lulz: asciilifeform discovered that a good % of prb returns NOTHING to getaddr command. how the fuck do these people connect to peers ? ( i'ma guess some gavintronic-over-https curated nonsense )

asciilifeform: btw trb could in principle be made entirely distinguishable, if we were to permit asking for a ~tx~ in 'inv' command ( currently prohibited , because prb nuked indexing , but could be brought into trb with no ill effect aside from some cpu cost )

asciilifeform: mircea_popescu: btw i think you'll like this, by default thing does opposite of the heathen one, doesn't display prb nodes individually, but simply as a collective 'sad people' stat # .

a111: Logged on 2018-10-10 01:24 asciilifeform: qatar >> https://archive.is/uy5I6 << nuffing but prb... perhaps Mocky will fix..

asciilifeform: qatar >> https://archive.is/uy5I6 << nuffing but prb... perhaps Mocky will fix.. ☟︎

mod6: http://btcbase.org/log/2018-10-03#1857624 << I did hear about this bug, of course. I had considered perhaps sending out something about this, but before I even dared to speak, I wanted to investigate the problem in prb-shithub, as well as the CVE. I haven't even had a spare moment yet. ☝︎

asciilifeform: http://btcbase.org/log/2018-10-01#1856296 << i gotta admit that i dun see point in 'growth for growth's sake'. there was already prb 'foundation' for ~that~. tbf is for maintaining & improving (constructively! there's plenty of actual ills to cure, that dun reduce to 'not enuff heathen notoriety' ) trb. ☝︎

a111: Logged on 2018-09-30 02:10 asciilifeform: whereas when somebody throws coin into a prb wallet, for any reason whatsoever, whether because he is idjit or because we made it harder to avoid, that's coin into usg coffers.

a111: Logged on 2018-09-30 02:08 asciilifeform: if idjit breaks it, he can do no harm thereby that prb does not already do; if he runs a valid node, it contributes to strength of the net.

asciilifeform: whereas when somebody throws coin into a prb wallet, for any reason whatsoever, whether because he is idjit or because we made it harder to avoid, that's coin into usg coffers. ☟︎

asciilifeform: if idjit breaks it, he can do no harm thereby that prb does not already do; if he runs a valid node, it contributes to strength of the net. ☟︎

asciilifeform: there appeared out of the usg depths, this squid, 'linux foundation', sponsored at various times erry possible scamola, prb, later gavinisms, tor, etc

a111: Logged on 2018-07-24 01:56 mod6: <+asciilifeform> in other lulz, http://btcinfo.sdf.org/blog/bitcoin-knots-restored-as-the-default-upstream-ebuild.html << shinohai endorses prb... << yeah, wtf is this all about. srsly now.

mod6: <+asciilifeform> in other lulz, http://btcinfo.sdf.org/blog/bitcoin-knots-restored-as-the-default-upstream-ebuild.html << shinohai endorses prb... << yeah, wtf is this all about. srsly now. ☟︎

asciilifeform: then again forkologists are generally harmless idjits ( in effect give away btc for phree ) , while prb purveyors actively aid & comfort the enemy

asciilifeform: ( a surprising % of the moar outrageous prb & quasi-forkolade derps, are stingy, parked on aws )

mod6: In other tales from the TRB: I spent a solid chunk of time this weekend trying to backport all of the rpc rawtx functions from upstream prb. Just to see if it was workable, and an educational endevour. This is not going to be a thing. They change tons of baseclasses and introduce a variety of new ones. Going forward, I think these will just be reimplmented in a trb-fashion.

asciilifeform: for that matter, why does douchebag settle for small change of www ? a remote ex for trb or even prb will easily bring in enuff loot to buy a battleship. without having to convince anybody, i'll note, of anything.

BingoBoingo: <mircea_popescu> BingoBoingo in other lulz, other than trying to push bitcoin crash as an implicit alternative, bitpay finally dropped bitcoin payments in favour of some nonsense "payment protocol" they developed in-house. << AHA, yeah the PRB v 0.9 thing

a111: Logged on 2017-03-02 21:10 asciilifeform: oooh hey hey hey lbj. i finally found out why prb folx like schnorr.

a111: Logged on 2018-02-02 22:30 asciilifeform: fwiw i'm still quite convinced that errything other than GET and PUT is ~= prb orphanage.

asciilifeform: fwiw i'm still quite convinced that errything other than GET and PUT is ~= prb orphanage. ☟︎

asciilifeform: it's one thing where prb refuses to serve trb node blox, or puts out some oddball liquishit that gets it malleus'd, etc

asciilifeform: trinque: indeed i marked it as experimental. did not know if, e.g., prb would shun the patched nodes, say

a111: Logged on 2018-01-08 20:30 shinohai: Any students of prb here know what this Lightning shit is? http://archive.is/pLqJN

shinohai: Any students of prb here know what this Lightning shit is? http://archive.is/pLqJN ☟︎

a111: Logged on 2018-01-07 05:12 shinohai: In other prb: http://archive.is/hgoit

asciilifeform: ( though will point out, consequences of this type of leak, is early death of the proggy, rather than 'ballons into red dwarf' a la prb or firefox )

asciilifeform: and a not-insignificant chunk of the work one sees in http://btcbase.org/patches?patchset=stable , had to happen on account of 'and we still have to talk to prb somehow...'

asciilifeform: the intrinsic difficulty of a trbtron's job is more or less 100% in dealing-with-prb.

asciilifeform: ^ if anybody knows what kind of prb generates these, and for what, plox to write in.