Transaction

d8b0cf699b47e1ec3814b4c4ec8a5c4e3f68273adb3e38ae4bab85a633229b7b
2024-03-22 21:24:02
0.00000017 BSV
(
0.00101323 BSV
-
0.00101306 BSV
)
10.3 sat/KB
1
71,211
1,649 B

2 Outputs

Total Output:
0.00101306 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMt<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=195.msg1611#msg1611">Quote from: satoshi on June 17, 2010, 06:46:08 PM</a></div><div class="quote">I don't believe a second, compatible implementation of Bitcoin will ever be a good idea.&nbsp; So much of the design depends on all nodes getting exactly identical results in lockstep that a second implementation would be a menace to the network.&nbsp; The MIT license is compatible with all other licenses and commercial uses, so there is no need to rewrite it from a licensing standpoint.<br/></div>Good idea or not, SOMEBODY will try to mess up the network (or co-opt it for their own use) sooner or later.&nbsp; They'll either hack the existing code or write their own version, and will be a menace to the network.<br/><br/>I admire the flexibility of the scripts-in-a-transaction scheme, but my evil little mind immediately starts to think of ways I might abuse it.&nbsp; I could encode all sorts of interesting information in the TxOut script, and if non-hacked clients validated-and-then-ignored those transactions it would be a useful covert broadcast communication channel.<br/><br/>That's a cool feature until it gets popular and somebody decides it would be fun to flood the payment network with millions of transactions to transfer the latest Lady Gaga video to all their friends...<br/></div> text/html
    https://whatsonchain.com/tx/d8b0cf699b47e1ec3814b4c4ec8a5c4e3f68273adb3e38ae4bab85a633229b7b