Appchain Components
Last updated
Last updated
Spire enables synchronous composability across chains that sit under the same parent chain. This is done through coordinated sequencing. Our current design leverages a single large node that acts as the coordinating sequencer across all appchains in a sync zone.
A sync zone dictates which chains can interact as if they were all on the same chain.
Which chains are within your sync zone is determined by which other chains are running under the same coordinator (ultimately limited by the settlement chain they operate within).
These are nodes that can be used for following the chain, indexing the chain, etc. but they are read only. Writes must pass through the Coordinator or through the Settlement chain in order to be properly simulated, sequenced, and/or executed.
These are where the data shipped between chains land to enable .
Cross-chain calls are dynamically detected by Pylon and their results are injected into the Port Contract to pre-populate the required data to fulfill the call. The system transaction used to pre-populate the required data is called a Priming Transaction.