That gained support and quite quickly, but when Gavin Andresen or Jeff Garzik tried to get involved in the coding, BU’s lead dev, Andrew Stones, responded undiplomatically.
https://www.trustnodes.com/2019/03/...nt-to-get-rid-of-bu-they-did-it-to-themselves
My god, there's some kind of pathology going on there.
[doublepost=1553719759][/doublepost]
The fact that is intra-block or inter-block it's an interpretation.
Not really. "Timestamp", "Chronological", it's all time related. Given two independent transactions, A and B, there's no way to tell which is generated first. The only thing that's chronological is that you can say that block (n+1) occurred *after* block (n). It's not an interpretation,
it's the only way it can be.
(The chronology of two dependent transactions is defined by the dependence of one on the TXID of the other).
[doublepost=1553720126,1553719296][/doublepost]
to have everything remain the same for these buips all 3 would need to pass
That doesn't sound very, uh, sound. I think you would need to pass a BUIP to enable that to be the case first.
[doublepost=1553720750][/doublepost]
yes, it's actually important for BU to provide an alternate implementation on the BSV protocol as a fallback to any shenanigans that asshole CSW might pull, if he can (im doubtful that he can).
Here's an alternative view on that. BU is not just about offering alternative implementations of protocol X, it's actually about allowing users and miners choice in advancing the protocol.
https://www.bitcoinunlimited.info/resources/BUarticles.pdf
However, BSV intends to lock down the protocol, set it in stone. So as far as BU is concerned, job done. There's no more to see there.
Now, obviously, future direction is decided by BUIPs and voting but I think it's important to consider original intent in these things.
(Edit: Apologies, you already upvoted this post for the first part and the forum software has collapsed all the posts into one).