hsm VS ehsm

Finally you can make a more complete Hierarchical (or Nested) State Machine, which allows you to have states within states. This is what we've done in several games I've worked on. This can allow reusing states in multiple contexts, such as being in an Idle state that pushes a Targeting state, or in a Running state that also pushes the Targeting state. You are then considered in all of the states on your state stack. This is tricky to implement right though and needs careful design, but used correctly can be extremely powerful. I'm aware of a C++ HSM library that I can recommend ( https://github.com/amaiorano/hsm ), but there's probably other good ones out there.

* dynamic HSM (https://github.com/intel/ehsm)

* machine learning in tandem with GPUs https://azure.microsoft.com/en-us/blog/azure-confidential-co...

* autonomous key management (https://docs.oasis.dev/general/oasis-network/overview#privac...)

* signal contact discovery (https://signal.org/blog/private-contact-discovery/)

Many of these will also work with next-gen enclave tech (mainly in the direction of total VM encryption), but those aren’t as secure as SGX yet, so SGX has continued utility to applications beyond DRM.