Closed jsoares closed 10 months ago
async
async
ref-fvm
and its underlying mechanism.tcid
consensus-shipyard
.MockedRuntime
with fvm-*
crate integration solution.runtime
crate to ensure example
code runs in wasm testnet also in unit tests. The previous runtime
crate cannot build to wasm target due to missing c lib. Need to downgrade getrandom
and rand
temporarily to make it work.example
crate compiles and runs.cicd
for checking cargo fmt/build/test/clippy
master
ready.master
(experimental/fvm-m2
will soon be deprecated).sync
hierarchical-sca
repo to ipc-gateway
with the following changes
fvm_util
runtime for the implementationHCAddress
to fvm_shared
address v3+. In this case we are using delegated address typeitests
.mircat
event inspector and debugger.async
ipc-atomic-execution
into separate repoipc-gateway
through feature and cratesipc-subnet-actor
consensus-shipyard/lotus
and I would say that they are up to date, but let me know if you need some additional input regarding pllannin g and next steps, or if you want to do a quick sync to catch-up on this. ipc-subnet-actor
completelyasync
ipc-subnet-actor
constructor and join method with test casesipc-subnet-actor
leave and kill methodsipc-subnet-actor
completelyipc-gateway
add more unit testsleave
and kill
..ipc-subnet-actor
completely, migrated submit-checkpoint
and all its related code. Updated testcases to use MockedRuntime. Also added a few more test cases in submit-checkpoint
.https://github.com/consensus-shipyard/ipc-subnet-actor/issues/10
for some simple code refactoring ipc-gateway
unit testsipc-gateway
and ipc-subnet-actor
on local fvm.
@jsoares commented on Wed Nov 24 2021
Description
Once we have a production-level implementation of hierarchical consensus (#6) and efficient subnet consensus protocols (#9), the next step is to combine them into a production system, deployable on the Filecoin mainnet.
Scope
Interplanetary Consensus (IPC) is a framework to enable on-demand horizontal scalability of Filecoin through the deployment of subnets (self-governing chains) that spawn their own state, validate messages in parallel, and seamlessly interact with any network in the hierarchy, as well as the Filecoin mainnet. Subnets can run different consensus algorithms, adjusting to the needs of the application. IPC is complementary to the programmability introduced by FVM, in that it provides a framework to further program the Filecoin network, accommodating a wide variety of use cases while overcoming potential consensus bottlenecks.
This project combines the outputs of #6 and #9 into a production implementation of IPC. It ends with actual real-world deployment but, as a first step towards that, it will launch Spacenet.
Dependencies
6
9
Roadmap
eta: 2023-12-31 children:
180
185
186
194
Talks
2022-10-27, Interplanetary Consensus: Scaling Blockchains with Subnets in an Easy-to-Trust Model
2022-10-27, Interplanetary Consensus: Now Playing in Eudico Near You
2022-10-27, Applications of IPC
2022-10-27, Building Modular and Scalable BFT Consensus Using the Mir Framework
Demos
2022-10-14, uptimeChecker β an FVM actor & service for cluster management
2022-12-05, Spacenet
2022-12-05, IPC FVM Actors Implementation
2023-03-21, Running an IPC Subnet
Resources