bitsko
Active Member
- Aug 31, 2015
- 730
- 1,532
'then you would realize that removing BCH support also removes BSV support because BSV never had a BUIP to officially support it'
what is this fuckery
what is this fuckery
As a general rule potential "expert witnesses" who have a personal relationship or history with the defendant or plaintiff will be barred from testimony unless there are extenuating circumstances.I don't think the court would accept @Peter R as an "expert witness" if he has had a beef with one of the parties in the case.
A thread in r/btc said Wright's lawyers made a motion to withdraw it (not sure of the correct legal terminology) so it was apparently them who submitted it. I'll guess it depends on whether there's "no backsies" legal principle or not as to whether anyone gets reamed over it.someone made a good point yesterday about the Kleiman vs CSW docs we're seeing on scribd.com. we can't be sure of their veracity nor that they match what the courts are seeing. for sure, whoever submitted that email doc from Dave to Uyen yesterday is committing perjury (assuming it even made it to the official courts) .
I dont think any storage strategy will be absolute. several entities will always be likely to insist on storing everything.It was pointed out earlier that pruning for full nodes is available. This allows a node that has already caught up to the head of the network to operate from a UTXO set that it has verified and is keeping track of.
However, if a new node is trying to join the network, is it able to catchup to the current block and function if the only blocks available were pruned? My understanding is today that answer is, no.
Note, this isn't just for transaction data. It's possible with really large blocks that most miner and full nodes will drop large OP_RETURN data for cost purposes, or simply because they don't want to pay the network traffic.
In that case new nodes need to be able to join a network using some form of merkel blocks with a mix of available transactions and merkel tree hashes where transactions are not available.
Until the ability for client software to handle this, it does seem risky to enable very large datasets. 2GB blocks is 1PB a year, I know large scale systems, there is a non trival cost to not just storing, but processing and serving that volume of data. It will be pruned by online nodes, which means new nodes need to be able to handle a pruned history.