rich1.0npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4chttps://nostr.now/npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4cnjumphttps://nostr.nowThis also illustrates that if we had made this change earlier, they would not have designed the system to create unspendable public keys in the first place. They have no financial incentive to deviate from the original design. And once such a system goes live, assuming it has any uptake, their engineers will be busy with all sorts of more urgent things. Any typical corporate CTO would look at this situation and say: hey look, there's a bunch of drama here, let's assume the brigaders win and the OP_RETURN limit stays in place. So let's just stick to the original design. We're not price sensitive, so it's the safest option. It also saves us a bunch of engineering hours. Also, it protects our engineers from being harassed. Finally, this also goes to show that we really need to make progress on Utreexo, because UTXO set growth is a sitting duck. All we can do is ask people nicely to not grow it needlessly.