Closed adlrocha closed 1 year ago
@cryptoAtwill, @sergefdrv, I would love your thoughts. I would try to take this one ASAP if possible. Thanks!
I like this idea! Though I would first wait until all open pull requests in other repos get merged before moving the code.
Closed by #23 and #33
Background
The code for IPC actors is scattered in several different repos, mainly:
This has been a consequence of the different stages of development of these actors. We first started with the gateway as part of the builtin-actor and the subnet actor as a user-defined actor; to then having both as user-defined actors; to having to decouple the atomic execution logic from the gateway, etc. As the code (and our plans) are starting to stabilize, I think we would benefit from having all the IPC actors code, primitives and sdk in the same repo. The protocol will evolve as a whole, and it will ease the deployment and reduce the maintenance burden in the future. Dependency updates and new releases will be easier to handle. This may also ease the transition for the case that we end up going "full system actors" for IPC (see https://github.com/consensus-shipyard/ipc-gateway/issues/19).
Goal
The goal would be to have all IPC actor-related code in the same repo with (at least initially) the following crates:
ipc-gateway
with all the IPC gatway actor code.ipc-subnet-actor
with the subnet actor code.ipc-atomic-exec
with all atomic exec-related code.ipc-sdk
with IPC actor SDK and IPC types and methods. Everything that other actors may need to interact with IPC.Tasks