Transaction

dd586bcc069dfaae4e5e6569d991187e2b2e1ce21e9094ebe2cc96c33a8495b9
Timestamp (utc)
2024-03-22 10:54:24
Fee Paid
0.00000012 BSV
(
0.00813843 BSV
-
0.00813831 BSV
)
Fee Rate
10.61 sat/KB
Version
1
Confirmations
93,995
Size Stats
1,131 B

2 Outputs

Total Output:
0.00813831 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMo<div class="post">ByteCoin, I think you can just keep a pointer to the last valid block per app in the big block chain.<br/><br/>So, when you mined, you would produce new app data for each app you cared about and stick the hash of that data as well as pointer to the previous vaild app block (per app you care about) into the big block chain.<br/><br/>In other words, the big chain has a next pointer to the last valid big block, as well as a next pointer to each last valid app block you care about.&nbsp; So, if you think there was an invalid app block, you can still add to the longest big block chain and reject the invalid app block by pointing further back in the chain to the last valid (in your view) app block.<br/><br/>You don't have to know about every app in this case.&nbsp; This plan still retains the bonus that miners can mine for as many apps as they want.</div> text/html
    https://whatsonchain.com/tx/dd586bcc069dfaae4e5e6569d991187e2b2e1ce21e9094ebe2cc96c33a8495b9