FAQ | Conduit Documentation

What kinds of teams use Conduit?

Any team building high-performance applications onchain. We support use cases across DeFi, TradFi, DEXs, RWAs, stablecoins, gaming, consumer apps, AI, and beyond. See some of our customers here.

My app works fine running on another chain, why do I need my own?

Applications often start strong on shared chains but inevitably hit scaling limits – high fees, latency, and congestion – as they compete for blockspace. A dedicated chain solves these challenges, enables full customization for your exact needs, and transforms gas fees from overhead into revenue.

I want my own chain. Should I build a rollup or custom L1?

It depends on your goals. Conduit supports both rollups and custom L1s, and we work closely with every team to choose the right architecture. Whether you need Ethereum alignment, full sovereignty, or a hybrid solution, we provide the infrastructure and expertise to launch the best version of your chain.

Why should I launch my chain with Conduit rather than build it myself?

Building a chain in-house comes with significant costs – months of work, millions in engineering costs, and coordination between many third parties (rollup frameworks, DA providers, interoperability, etc.). Ongoing maintenance, troubleshooting, and upgrade implementations add further strain post-launch. Conduit covers all of this seamlessly, starting at just $36K/year, freeing you to focus entirely on your business.

Do I own my chain if I launch it with Conduit?

Yes. If you need to take control of your chain or want to migrate to a different hosting platform, we’ll send the necessary keys to a wallet of your specification as soon as you ask. This is standard in our contracts. If you need our help migrating, we can do that too.

Does Conduit offer support?

Absolutely. Every Conduit customer gets a dedicated SLA, with options up to <1-hour response times and direct access to our engineering team. Beyond technical support, we partner strategically to optimize your chain, advise on integrations, fine-tune your GTM strategy, and ensure your long-term success. Learn more about our support plans.

What’s the difference between a discoverable and hidden chain?

When your chain is set as discoverable it’s displayed in the Conduit app to other users. This means that it’s published on pages such as Nodes, which anyone with a Conduit account outside of your organization can access. Also, a public URL is generated for your chain where its network information and tooling can be found.

All chains are set as hidden by default. Hidden rollups are not discoverable or visible anywhere in the Conduit app except to your own organization. However, it still remains a live, publicly viewable blockchain.

What’s a verified chain?

Since chain deployment is permissionless and their names, icons, or IDs aren’t always unique, we’ve introduced a small feature in the UI which we call verification. All that means is that we have manually verified the chain and its owner are authentic. Anyone can request us to verify their chain by submitting a request. We typically only verify popular chains in an effort to protect people from malicious chains imitating legitimate chains (we’ve yet to see this happen but verification is there as a precaution).

How do I cancel a testnet or mainnet subscription plan?

Deleting your testnet or mainnet rollup automatically cancels the subscription associated with that deployment. You can delete your rollup from Settings > General in your deployment dashboard.

Why do I see a “This is a potential scam” warning when adding my network to MetaMask?

MetaMask shows this warning when a network’s ChainID isn’t recognized or verified. MetaMask pulls ChainIDs from a community-maintained repository on GitHub: Ethereum-Lists. To resolve this, you can submit a PR to add your network’s ChainID to the list.

Why did my transaction fail with “oversized data” error?

Transactions can fail if they exceed the maximum allowed size (128KB). This limit exists because large transactions are more expensive to process and harder to propagate across the network. This commonly occurs when batch minting/purchasing multiple NFTs or making complex smart contract interactions with large calldata.

If you encounter this error, you can resolve it by breaking your transaction into smaller batches or reducing the number of items per transaction.

For reference, transactions are limited to 128KB by the txMaxSize parameter in Geth based nodes.