Foreign context: ingest, query or deliver

Foreign context: ingest, query or deliver A data-flow diagram generated by Archify. 01 / Start 02 / Verify 03 / Context 04 / Act HILSA feed · configured foreign facts · 01 / Start · heads · deposits · withdrawals HILSA feed configured foreign facts heads · deposits · withdrawals Verify + commit · ordered Singularity input · 02 / Verify Verify + commit ordered Singularity input Shared snapshot · committed local context · 03 / Context · arbitrary subtrees reserved Shared snapshot committed local context arbitrary subtrees reserved Local VM app · verification + finality minima · 04 / Act Local VM app verification + finality minima Query request · requested block / time · 01 / Start · lzRead · Wormhole Queries Query request requested block / time lzRead · Wormhole Queries Query verification · read source-chain state · 02 / Verify Query verification read source-chain state Verified response · returned or submitted · 03 / Context Verified response returned or submitted Existing application · validate response + act · 04 / Act Existing application validate response + act Origin app · emit cross-chain message · 01 / Start · LayerZero · Wormhole · Axelar Origin app emit cross-chain message LayerZero · Wormhole · Axelar Destination check · route-specific verification · 02 / Verify · Hyperlane · CCIP · IBC Destination check route-specific verification Hyperlane · CCIP · IBC Destination app · execute intended action · 04 / Act Destination app execute intended action Separate RPC proof verification · Caller MPT proof + admitted head → hilsa_proveRead → checked account / storage · 03 / Context · Arbitrum / Base / Optimism direct roots · BNB header-bound roots Separate RPC proof verification Caller MPT proof + admitted head → hilsa_proveRead → checked account / storage Arbitrum / Base / Optimism direct roots · BNB header-bound roots artifact accepted local read request evidence response message asynchronous delivery

HILSA: reusable covered facts

  • • Committed reads cover configured facts; arbitrary consensus subtrees remain reserved. The separate supplied-proof RPC performs no foreign HTTP fetch and does not mutate that snapshot.

On-demand: two distinct mechanisms

  • • LayerZero lzRead and Wormhole Queries use distinct request and verification paths. This row compares timing and data ownership, not identical trust.

Messaging: complete the destination action

  • • LayerZero, Wormhole, Axelar, Hyperlane, CCIP and IBC have different security configurations. Delivery can fail; independent chains do not commit atomically.