Satellite Contracts

Architecture pattern

proof producer (Storage Proof/HDP) -> Satellite state -> consumer contracts -> app policy

Satellite is trust layer; application logic remains your responsibility.

Integration workflow

1. Select chain and environment.
2. Resolve Satellite address from deployment manifests.
3. Import ISatellite.
4. Implement minimum required read surface.
5. Gate business actions on verified reads.

Safety requirements

• Prefer safe read variants where availability is uncertain.
• Keep chain/environment/address config externalized.
• Separate read adapter logic from business policy logic.
• Fail closed if verified data is absent or inconsistent.

Anti-hallucination guardrails

• Do not invent addresses or module availability.
• Do not assume all module surfaces exist on every chain.
• Do not infer undocumented messaging paths.
• If docs and repo differ, prefer repo interfaces/manifests for integration details.

Self-contained reference example

function isEligible(
    address satellite,
    uint256 chainId,
    uint256 blockNumber,
    address account,
    uint256 minBalance
) external view returns (bool) {
    (bool ok, bytes32 v) = ISatellite(satellite).accountFieldSafe(
        chainId,
        blockNumber,
        account,
        IEvmFactRegistryModule.AccountField.BALANCE
    );
    if (!ok) return false;
    return uint256(v) >= minBalance;
}

Output checklist

• Address resolution path documented
• ABI/interface version pinned
• Safe-read fallback behavior defined
• Business rules gated on verified data only