potential actor entrypoints cache #639
Description
(For M2.2) Besides invoke we are adding new entrypoints to actors to support account abstraction and updatable actors. Both the FVM and clients will need to make a quick determination as to whether:
- a signature-less message is eligible for in-actor validation (through the validate/authenticate entrypoint).
- a CodeCID that an actor wants to update to supports intaking an update.
It's possible we may need to maintain an on-disk cache in the FVM, and maybe even communicate some metadata to clients (e.g. client may want to maintain its own cache of sender actors, so it doesn't have to call the FVM to validate every gossiped message).
Alternatively, we could store such metadata in the state tree. Technically it would belong in the actor code entry within the init actor, but it would be simpler if these attributes were attached as a bitfield to the actor entry in the state tree.
The reason this is not necessary for M2.1 (EVM) is that the system won't allow deployment of new native actors.