FAQs

Are you a RaaS (Rollup-as-a-Service)?

No, we are not a RaaS, but we partner with RaaS providers. We offer the ability to easily spin up a chain with fewer dependencies by:

• Replacing centralized sequencers with decentralized, onchain sequencers
• Replacing centralized backups with onchain data storage

While we do host some services ourselves that do not require RaaS (like sequencers, RPC nodes, and block explorers), these are intended for developer usage only. We strongly recommend a RaaS provider when your app is getting ready to go live. Onchain sequencing will simplify the process and make it easy to move onto or between RaaS providers with a simpler, more reliable stack.

Are you a rollup framework?

No, we are not a rollup framework. We integrate with existing rollup frameworks to provide them with programmable sequencing and long-term data storage. See why we start with Arbitrum Orbit in our Execution Framework page.

Are you a DA (Data Availability) layer?

No, we’re not a data availability layer. We use data availability layers under the hood (like EigenDA). By using onchain sequencing on top of Syndicate Chain, your data is stored there, so you don’t need a separate data availability layer. Essentially, we use one under the hood so you don’t have to.

Are you a shared sequencer? How are you different from shared sequencing or based sequencing?

See our Sequencing Architectures comparison for a detailed explanation.

What frameworks does your appchain support?

Currently, we support Arbitrum Orbit for EVM blockchains. Learn more in the Syndicate Stack. More stacks may be added soon, including non-EVM chains.

What gas token can I use?

You can use either ETH or custom ERC-20 gas tokens. We recommend custom gas tokens since they’re much cheaper to set up.

What settlement layer can I use?

Any settlement layer can be used. The most common ones are Ethereum Mainnet and Base.

Is there anything special I have to do to use your service?

No. All your existing tooling and wallets should work without any modifications.

Do you fork any code for your rollup framework?

Not functionally. We run Arbitrum Nitro via the Arbitrum Orbit stack with a minimal, additive fork that only exposes a few extra read-only functions; we do not change execution logic or consensus. In the Arbitrum smart contracts, we make only small modifications (e.g., minor performance tweaks and additional onchain logging for Orbit). These changes are a few lines and remain upstream-compatible, so they should not affect your ability to receive upstream updates.