j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMi<div class="post">I thought about the BitX block format more today, and (with the help of ByteCoin on irc) decided that block rejection is an important part of the system. So, the format would work more or less like the following:<br/><br/><previous block hash><br/><timestamp><br/><br/><hash of app name> <hash of app data> <previous app block offset><br/><hash of app name> ....<br/><br/><nonce><br/><br/>Basically, there is the BitX block chain which is maintained in the first field. But there are also "subchains" for each app. The "previous app block offset" is the number of blocks to travel backwards in the chain to find the last previous block for this app.<br/><br/>Omitting some details, a Bitcoin fork would appear as follows, inside a non-forked BitX chain:<br/><br/>block 0:<br/><empty, this is the genesis block><br/>(bitcoin) datahash... 0<br/><br/>A previous app block offset of zero indicates that this is a genesis block for that app. Each BitX block is only allowed to specify a genesis block for one app.<br/><br/>block 1:<br/><hash of block 0><br/>(bitcoin) datahash... 1<br/><br/>This is a continuation of the last BitX block and it also claims to be a successor of the previous block's bitcoin chain.<br/><br/>block 2:<br/><hash of block 1><br/><empty><br/><br/>It's perfectly legit for any given application to not appear in a block.<br/><br/>block 3:<br/><hash of block 2><br/>(bitcoin) datahash... 3<br/><br/>This is a continuation of the BitX chain, but it has rejected the previous bitcoin block. Clients will now have to accept one bitcoin app block and reject the other, but there is no reason to reject the BitX block. The rejected bitcoin app block will stay in the BitX block chain, but it will not be part of the longest valid bitcoin block chain.</div> text/html
https://whatsonchain.com/tx/23c4c2ffeda882e289cc39bc08d74a52297fb4a80fbbdb766d96e5ffa3ad5dec