Transaction

7e8d5e0bfeea02499472c1ffda0e4993e35ffa8cef07b17229e2c0b8c8d2f5d1
2024-03-24 22:19:56
0.00000020 BSV
(
0.00651322 BSV
-
0.00651302 BSV
)
10.35 sat/KB
1
76,132
1,932 B

2 Outputs

Total Output:
0.00651302 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1790.msg28696#msg28696">Quote from: satoshi on December 09, 2010, 09:02:42 PM</a></div><div class="quote">I think it would be possible for BitDNS to be a completely separate network and separate block chain, yet share CPU power with Bitcoin.&nbsp; The only overlap is to make it so miners can search for proof-of-work for both networks simultaneously.<br/><br/>The networks wouldn't need any coordination.&nbsp; Miners would subscribe to both networks in parallel.&nbsp; They would scan SHA such that if they get a hit, they potentially solve both at once.&nbsp; A solution may be for just one of the networks if one network has a lower difficulty.<br/></div><br/>This sounds very very interesting, something to explore.<br/><br/>Can you elaborate on how would it work in practice?&nbsp; Separate networks and block chains implies hashing one block header for each network, with different resulting hashes, does it not?<br/><br/>The only thing I can come up with is the completely naive and slightly cache-unfriendly implementation...<br/><br/>while (nonce &lt; 0xffffff)<br/>&nbsp; &nbsp; nonce++<br/>&nbsp; &nbsp; for each network<br/>&nbsp; &nbsp; &nbsp; &nbsp; data_block[nonce_offset] = nonce&nbsp; &nbsp; &nbsp; &nbsp; // ie. our nonce<br/>&nbsp; &nbsp; &nbsp; &nbsp; scanhash(data_block)<br/><br/>or<br/><br/>for each network<br/>&nbsp; &nbsp; while (nonce &lt; 0xffff)<br/>&nbsp; &nbsp; &nbsp; &nbsp; data_block[nonce_offset]++<br/>&nbsp; &nbsp; &nbsp; &nbsp; scanhash(data_block)<br/><br/>I could easily update cpuminer to poll multiple RPC endpoints for 'getwork'...<br/></div> text/html
    https://whatsonchain.com/tx/7e8d5e0bfeea02499472c1ffda0e4993e35ffa8cef07b17229e2c0b8c8d2f5d1