Hey Dan
I really support the forking and renaming of EOSIO.
There are two very important features as part of the EOSIO 2.1 and 2.2 releases that I strongly suggest you and your team to consider adopting.
2.1 introduces Action return values https://github.com/EOSIO/eos/pull/8327
2.2 introduces Read-only contract queries https://github.com/EOSIO/eos/pull/10189
Both of these features together allow application developers to create read-only syncronous queries of contract state. This is done without using get_tables. Contract state is guaranteed to be consistent and at the same block height when the queries made, ensuring that the query returns consistent results.
In addition, by allowing query functions to be written alongside write functions, contract functionality can bundle together and more modular and understandable for application developers. Please see the following issue which was the conversation that led to these features.
