FAQs

How do synchronously composable transactions work?

Pylon runs a node for the settlement chain you are deployed to as well as the sequencing node for your appchain and any other appchains in your Sync Zone. Pylon then detects whenever there is a transaction calling into another chain through a Port Contract. It forwards the call to the other chain and then injects the results back into the originating Port contract with a Priming Transaction that frontruns the original application call to ensure the data is available to complete the call. See Synchronously Composable Transactions for details.

How can I trust the data being injected into the port contract?

We are working on a TEE based proof process that will ensure data moving across chains is verifiably correct with the speed to ensure a seamless experience. We will be releasing more about this soon!

What are the trust assumptions for the chain itself?

We currently run a reth stack based system. So the trust assumptions for the chain are fraud proof based and of course impacted by the parent chain you deploy on. Due to the requirement for coordinated sequencing within a Sync Zone and the current architecture all appchain sequencers within a Sync Zone run on a single node. Standard nodes for a given appchain (such as for submitting fraud proofs) can be operated by anyone.

What stacks/settlement chains are supported?

Currently we support any op-stack settlement chains but are working on adding support for additional chains. Even if your targeted settlement chain is not already supported we'd love to speak with you about getting your use-case supported. Please reach out through this form.

What fees are there?

Please reach out to discuss through this form!