3 ms·
Bitcoin is permissionless. Whether you, or Gavin, or Nick Szabo, thinks it should be used for a particular application is not relevant, if it in fact works for
by zekevermillion 11y ago
Bitcoin is permissionless. Whether you, or Gavin, or Nick Szabo, thinks it should be used for a particular application is not relevant, if it in fact works for that application. Maybe your use of bitcoin as a value transfer protocol is burdening me by driving up the costs of storing objects for multiplayer games! Altcoins are often not suitable because there is not a well-maintained software implementation of the protocol for a particular alt, or because there is insufficient mining on that chain to foster adequate security. As it becomes more expensive to send tx on bitcoin, of course, there are opportunities for alts to fill certain niches. Just as there are opportunities for people to find ways like sidechains, or other hacks, to get more out of bitcoin itself.
- ryanlol 11y agoUntil all of your data gets pruned from the blockchain in an update...
- zekevermillion 11y agoWell, that is also fair game...
- adrianmacneil 11y agoPruning is/will be a client feature, so your data would never be pruned out of existence, it's simply up to clients whether or not they want to keep it around.
- ryanlol 11y agoWhat's not a client feature? It'll be pretty annoying when you've only got a couple of custom clients hosting your version of the 10TB blockchain.
- adrianmacneil 11y agoWell, you can't prune the blockchain until you have fully downloaded and verified it anyway. So if no clients are hosting the full, complete blockchain then you won't be able to sync at all, which will be bad for everyone. You could theoretically get around this by starting sync from a known (hard coded) recent block + UXTO set, but at that point you are losing _all_ transaction history, not just your OP_RETURNs. So, I don't think OP_RETURN data added to the blockchain today will be going anywhere fast.