Features
Last updated
Last updated
A based appchain combines the advantages of running an appchain (such as customizability, scalability, and sovereignty) with the benefits of deploying a smart contract on its base layer (such as composability and simplicity).
More specifically:
Scalability - Dynamically adjust gas limits to support high throughput and user demand.
Stability - Avoid “noisy neighbor” issues with tx fee isolation and dedicated execution.
Accessibility - Seamlessly tap into parent chain's existing liquidity and users.
Profitability - Capture more value with customizable fee structures and token models.
Sovereignty - Full control over infrastructure, fees, and brand identity.
Simplicity - Minimal infra to setup and manage—e.g. no duplicative oracle deployments.
As a result, your app logic can be written as if it were on the same chain as the contracts you are attempting to call into:
Pylon enables us to have seamlessly composable transactions across chains within a . These seamlessly composable transactions enable us to provide a developer experience unlike any other. Your application contracts can literally be written as if they were on the same chain you are deployed under.
In order to provide this experience 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 . Pylon then detects whenever there is a transaction calling into another chain through a . It forwards the call to the other chain and then injects the results back into the originating with a that "frontruns" the original application call to ensure the data is available to complete the call.
are used to take app calls and re-direct them to the that will have the call results available for retrieval (since the is pre-populated with the necessary data as indicated above).
See to see how Pylon makes this work!
