Skip to main content

Public preview: What to expect

Orbit chains are currently a public preview offering. This concept document explains what "public preview" means, what to expect from Orbit's public preview capabilities, and how to engage with our team as you tinker.

Arbitrum Orbit is Mainnet ready, but deploy to Testnet first

Arbitrum Orbit's core technology has undergone a comprehensive audit and is now able to support deployments to Mainnet.

It's important to note that Orbit is a new technology and as such, there are risks involved.

To mitigate these risks, you're strongly encouraged to deploy your Orbit chain on Testnet first. If you don't launch on Testnet first, you significantly increase risk.

Refer to the Orbit quickstart for instructions that walk you through the process of deploying your Orbit chain to Testnet.

How products like Orbit are developed at Offchain Labs

Offchain Labs builds products in a way that aligns loosely with the spirit of "building in public". We like to release things early and often so that we can capture feedback and iterate in service of your needs, as empirically as possible.

To do this, some of our product offerings are documented with public preview disclaimers that look like this:


Orbit chains are now Mainnet ready! Note that Orbit is still a public preview capability - the Orbit product and its supporting documentation may change significantly as we capture feedback from readers like you.

To provide feedback, click the Request an update button at the top of this document, join the Arbitrum Discord, or reach out to our team directly by completing this form.

This banner's purpose is to set expectations while inviting readers like you to express your needs so that we can incorporate them into the way that we iterate on product.

What to expect when using public preview offerings

As you tinker and provide feedback, we'll be listening. Sometimes, we'll learn something non-obvious that will result in a significant change. More commonly, you'll experience incremental improvements to the developer experience as the offering grows out of its public preview status, towards stable status.

Public preview offerings are evolving rapidly, so don't expect the degree of release notes discipline that you'd expect from a stable offering. Keep your eyes open for notifications regarding patch, minor, and major changes, along with corresponding relnotes that highlight breaking changes and new capabilities.

How to provide feedback

Our product team primarily uses three feedback channels while iterating on public preview capabilities:

  1. Docs: Click on the Request an update button located in the top-right corner of any document to provide feedback on the docs and/or developer experience. This will lead you to a prefilled Github issue that members of our product team periodically review.
  2. Discord: Join the Arbitrum Discord to engage with members of the Arbitrum community and product team.
  3. Google form: Complete this form to ask for support.

What to expect when providing feedback

Our ability to respond to feedback is determined by our ever-evolving capacity and priorities. We can't guarantee responses to all feedback submissions, but our small-but-mighty team is listening, and we'll try our best to acknowledge and respond to your feedback. No guarantees though!

PS, our small-but-mighty team is hiring.

Thank you!

Thanks for helping us build things that meet your needs! We're excited to engage with OGs and newcomers alike; please don't hesitate to reach out.