After a little bit of a rebuilding period SFRX development is back on. Some of the concepts in using crypto are advanced to even me as a developer and take some time to work though. One of the things I had issues with in the previous almost release was I tried to make my own Patricia Merkle Trie type structure without studying why it was used that way in ETH. I also couldn't figure out how to use it before in my code on two different peers and ended up giving up and creating my own blend of the concept, a KV db, and a peer hash based on checkpoints that kind of worked but not so well as I thought it would. Let's just say there is room for error in calculating hashes on patterns and especially if you use a reduced data set on that pattern in every peer evaluating the hash on the same set of transaction each block and the blocks are empty. I could have figured that part out but the filesize for this tree substitute was getting kind of heavy also. Now, ETH is a heavy ass chain (large file size) so maybe this isn't the besst evaluator. I think most of ETH heaviness, though, is more related to a 15 second or less block time average and I mean look at all you can do on the block. I love using an ethereum clone as a base for sapphire. It makes it so easy to use the address and signature capabilities of legacy chains and merge them into a product. I mean, by definition, that means cross chain functionality. If the functionality on the legacy chain will also work on your chain then it works "cross chain" in some regard once you figure out the link between the chains. Embed the "link" into your own chain and you create the link. Embed the functionality from multiple other currencies and you extend that relationship to all those chains. Since at least one of them (Eth) and now even other's like BCH, give you the ability to release your own currencies in the form of tokens you have a powerhouse concept. So, this is where my brain goes on Sapphire. I don't care how long it takes me to make it, it's fun to work on.