Skip to main content

​
Requesting an Appchain

This guide explains the key parameters and tradeoffs to consider when requesting an appchain. When setting up a new Pylon appchain, three primary parameters define its identity and operational behavior:
  1. Chain Name: Human-readable identifier used in wallets and explorers
  2. Block Period: Frequency of block production, affecting latency and throughput
  3. Settlement Layer: The chain your appchain settles to, determining security and ecosystem access
Pylon appchains are available by request through the Spire contact form. In your request please include your desired parameters.

​
1. Chain Name

A human-readable name for the appchain. Use clear, descriptive names like “MyApp-Chain” or “GameFi-L3”. Guidelines:
  • Keep names under 32 characters for compatibility
  • No special characters or spaces
  • The name must be unique within the sync zone
  • Once set, the name cannot be changed without redeploying
The chain name is used in wallets, explorers, and user interfaces, so choose something memorable and unique.

​
2. Block Period

Block period determines how frequently new blocks are produced on the appchain. Default: 1 second This setting directly impacts how long users wait for transaction confirmation: Pylon supports block periods of 500 milliseconds or greater. Values from 500ms to 2 seconds have been tested for stability with Pylon’s Reth-based infrastructure.

​
3. Settlement Layer

Choose which settlement layer the appchain settles to. This impacts fees, security, and ecosystem access. Available Settlement Layers:
Settlement LayerUse CaseBenefitsLearn More
Base SepoliaTestnet developmentLow fees, easy testingBase Chain Docs
Base MainnetProduction applicationsMainnet liquidity, full securityL2Beat: Base
Optimism SepoliaCross-settlement testingTest different architecturesOptimism Docs
Celo MainnetAlternative ecosystemsAccess Celo’s DeFi ecosystemL2Beat: Celo
Once deployed, the appchain receives an RPC endpoint: 
https://pylon.{settlement-layer}.spire.dev/v1/chain/{chain-id}/rpc
Add this endpoint to wallets and foundry.toml for development.

​
4. Pre-Deployed Utility Contracts

You can request utility contracts to be pre-deployed at deterministic addresses on your appchain. These contracts enable common development patterns without requiring deployment. Available contracts:
  • SettlementForwardingProxyFactory - Deploy proxies for cross-chain reads
  • CREATE2Factory - Deterministic contract deployments
  • Multicall - Batch multiple calls in a single transaction
  • MinimalProxyFactory - Deploy minimal proxies (EIP-1167) for cheap cloning
Specify which contracts you want pre-deployed and whether to use default addresses or custom addresses when requesting your appchain. If there are others you’d be interested let us know! See Pre-Deployed Utility Contracts for details on each contract and their default addresses.

​
Next Steps