Transaction

bb2da5afdab2a169b00e849db56d7e6ebebc76a6fbb00061ff6a8a4f6097d1dd
Timestamp (utc)
2024-03-23 20:07:44
Fee Paid
0.00000032 BSV
(
0.02455561 BSV
-
0.02455529 BSV
)
Fee Rate
10.04 sat/KB
Version
1
Confirmations
102,157
Size Stats
3,187 B

2 Outputs

Total Output:
0.02455529 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMw <div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=721.msg7918#msg7918">Quote from: knightmb on August 06, 2010, 05:46:56 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=721.msg7907#msg7907">Quote from: kiba on August 06, 2010, 05:30:41 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=721.msg7904#msg7904">Quote from: knightmb on August 06, 2010, 05:24:10 PM</a></div><div class="quote">Currently the rules are why they are because the entire network is designed with "trust no one" but instead "trust everyone collectively".<br/><br/></div>You mean it is designed&nbsp; to "trust no one", not of "trust everyone collectively"?<br/></div>Trust no one node, but if enough nodes are saying the same thing, then trust that.&nbsp; <img alt="Grin" border="0" src="/static/img/emoticons/grin.gif"/><br/></div><br/>This exchange is fascinating! At some sense it's just a matter of semantics, but it is very insightful semantics.<br/><br/>Logically I can support knightmb's statement "trust everyone collectively".<br/>However kiba's statement "trust no one" is disprovable,<br/>as is knightmb's statement "Trust no one node, but if enough nodes are saying the same thing, then trust that."<br/><br/>The way the system works is every node attempts to receive every transaction, they each try to put every received transaction into a block at the same time. And while they are doing that, they each play the hashing game individually looking for fate to bless them with a match before it does anyone else.<br/><br/>So at any given point in time the system is really *trust (but validate) someone arbitrarily*. This happens when someone declares a block &amp; hash "solved". All the other nodes check the block for self consistency, but they DON'T check the block's transactions for consistency with the transactions they themselves were working on. Nor do they check against the transactions other nodes received. So I see no support for the "if enough nodes are saying the same thing, then trust that."<br/><br/>All nodes simply declare, "I will trust this node's work as the next increment of bitcoin truth, because fate has blessed it." So it doesn't qualify as a "trust no one" system. Node's never say, "Hey you fuck head! I have 5 known transactions you didn't bother to put in your block! You are a lying bastard." Everyone just presumes the missing transactions will be resubmitted and they'll end up in a subsequent block. This is heuristically plausible, but not absolutely deterministic. Everyone has to keep checking to make sure their transactions actually cleared the process.<br/><br/>So if knight's "trust everyone collectively" meant, "trust in the process" I find that insightful and a good motto. I'd probably add "...but keep doing your own validation!"<br/><br/></div> text/html
    https://whatsonchain.com/tx/bb2da5afdab2a169b00e849db56d7e6ebebc76a6fbb00061ff6a8a4f6097d1dd