ISatellite interface.
MMR and block commitment modules
MmrCoreModule: manages MMR creation, root/size history, parent hash storage, and MMR queries.EvmOnChainGrowingModule: appends EVM header batches directly on-chain.EvmSharpMmrGrowingModule: updates MMR state from SHARP-proven job outputs.StarknetSharpMmrGrowingModule: Starknet-oriented SHARP growth module surface.
Proof and fact registry modules
EvmFactRegistryModule: verifies and stores EVM header/account/storage/timestamp facts.CairoFactRegistryModule: tracks Cairo facts (verified and mocked modes are both represented).
Parent hash fetch modules
- Native fetcher: pulls recent parent hashes from the local chain context.
- Network-specific fetchers: modules for Starknet, Arbitrum, and Optimism-specific flows.
Messaging modules
- Sender side: universal sender plus network-specific senders (for example L1->Starknet, L1->Optimism, L1->Arbitrum, L1->ZkSync, Arbitrum->ApeChain).
- Receiver side: receiver modules validate the cross-domain source and ingest incoming parent hashes/MMRs/facts.
- Registry:
SatelliteRegistryModulestores known satellites and connection metadata.
Data Processor module
DataProcessorModule: stores HDP task status/results and authenticates task completion by checking authorized program hashes and valid Cairo facts against MMR roots used by the task.
Governance and maintenance modules
- Ownership/admin controls: owner and admin management.
- Inspector module: module/function selector introspection.
- Maintenance module: add/replace/remove module selectors (diamond maintenance operations).
Practical interpretation
For most integrators, the key interaction is with proof/read surfaces (EvmFactRegistryModule + read helpers).
For protocol operators, growth/messaging/maintenance modules are what keep commitments fresh and synchronized across chains.
