rich1.0npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8https://nostr.ae/npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8njumphttps://nostr.ae📅 Original date posted:2015-10-05 📝 Original message:On Mon, Oct 5, 2015 at 2:29 PM, Clément Elbaz <clem.ds at gmail.com> wrote: > The problem is that some transactions that are meaningless to you are > actually meaningful to people using an upgraded Bitcoin software. > > Therefore during a softfork, while you can not miss the existence of a > transaction, you can miss its meaning. Why would you care about payments to other people? The scriptPubKey's that you give to your payers certainly have meaning to you. > But as soon as you try to actually use Bitcoin (that is, calculate the > accurate balance of a wallet in a very broad sense), you can be led a wrong > result if you did not upgrade, which is a critical problem for financial > software. What is it important that you are able to calculate balances of wallets that aren't yours? > And because nothing prevent people to send you transactions of a new type, > you have no way to "opt out" of this problem. Why would anyone "pay you" to a scriptPubKey you don't understand? I can "pay" the bill of my internet services by burying cash in a park nearby my house for my provider to pick up later. But if I don't tell my provider, it will never know. If I inform it, I will get an answer: "no, sorry, we won't accept this new 'form of payment' of yours as payment".