Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Make the SCA a user-defined actor #231

Open
adlrocha opened this issue Jul 28, 2022 · 0 comments
Open

Make the SCA a user-defined actor #231

adlrocha opened this issue Jul 28, 2022 · 0 comments

Comments

@adlrocha
Copy link
Collaborator

The SCA is currently implemented as a builtin actor that is loaded in the builtin bundle. As discussed here we would reduce the friction of introducing HC in Filecoin mainnet (and improve the maintainability and upgradability of the actor) if we make the SCA a builtin actor. This may involve several major changes in the current implementation:

  • We need to take hierarchial_sca from https://github.com/adlrocha/builtin-actors to its own repo (we'll need to figure out how to benefit from all the runtime and testing tools provided for builtin-actors in that repo).
  • Instead of deploying the SCA in genesis, part of spawning the subnet is also deploying the SCA in the subnet and publishing the address for everyone to know how to interact with it.
  • In subnets we may be able to fix (or predict) the address of the SCA (as it is deployed along with the subnet deployment).
  • We may need to change the way in which we call ApplyMsg to execute cross-net messages. If we remove the implicit execution of these messages, we can't force ApplyMsg to be executed by the SYSTEM_ACTOR and will have to figure out a way to prevent this function from being externally callable.

(Further updates coming soon)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant