This issue will be left open to discuss, where to put the radix tree. It is not currently supported in NEO, however it can be added and hidden from other nodes.
The only actors who need to know about it are light clients. If implemented, we will also be able to rollback state a lot easier.
I will keep this open for discussions on where to put it, ideally it should be calculated at the same time as the merkle tree is calculated. However, there was a recent issue raised in the neo-project on decoupling the state changes for the vm and implementing state_height so we may have to make it a standalone also.
This issue will be left open to discuss, where to put the radix tree. It is not currently supported in NEO, however it can be added and hidden from other nodes.
The only actors who need to know about it are light clients. If implemented, we will also be able to rollback state a lot easier.
I will keep this open for discussions on where to put it, ideally it should be calculated at the same time as the merkle tree is calculated. However, there was a recent issue raised in the neo-project on decoupling the state changes for the vm and implementing
state_height
so we may have to make it a standalone also.