How textileio/ipc works
Main Components
a) Core Layer Components:
• IPC CLI (ipc/cli) - User interface component
• IPC Provider (ipc/provider) - Core interaction library
• Fendermint - Subnet implementation using Tendermint
• Smart Contracts (contracts/) - IPC protocol actors
• IPLD Resolver (ipld/resolver) - Content addressing system
b) Runtime Components:
• Subnet Management System
• Cross-chain Communication Layer
• Wallet Management System
• Consensus Layer (Tendermint Core)
Architectural Patterns to Highlight
a) Hierarchical Structure:
• Root Network (e.g., Filecoin Calibration)
• Subnet Hierarchy
• Cross-subnet Communication Channels
b) Actor Model:
• Gateway Actor
• Subnet Actor
• Registry Actor
[IPC CLI] ←→ [Configuration Management]
[IPC Provider] ←→ [Wallet Management] ←→ [IPLD Resolver]
[Fendermint Node] ←→ [Consensus Engine] ←→ [State Machine]
[Gateway Contracts] ←→ [Subnet Contracts] ←→ [Registry Contracts]
Key Interactions
• Cross-chain message flow
• Checkpoint synchronization
• Validator set management
• Subnet creation and management
• IPLD content resolution
Additional Elements
Specific annotations for:
• Security boundaries
• Cross-chain message paths
• Consensus participation flows
• State synchronization mechanisms
• External network interfaces
Technical Details
• WebAssembly runtime integration
• EVM compatibility layer
• Tendermint consensus integration
• IPLD-based content addressing
• Cross-chain messaging protocols
Implementation Notes
• Modular architecture allowing different consensus algorithms
• Recursive scalability through subnet hierarchy
• Integration with existing blockchain networks
• Security and validation boundaries
• State management and synchronization