Proposal Name: Launch of Status Layer 2 Rollup Chain
Author(s): Status Core Contributors
Date of Submission: Tuesday, November 7th, 2023
External Discussions: N/A
With the introduction of Status Communities and its token-based interactions, it’s essential to ensure that there is always a low gas fee environment available for users of Status Communities and other Status blockchain-based functionality, so that users are not priced out due to congestion on popular chains.
This proposal primarily targets Status users engaging with Status Communities and other blockchain-based functionality which requires a low-cost onchain transaction environment to facilitate growth and adoption of the platform.
Status is on a transformative journey to become the web3 super app that brings online self-sovereignty to individuals and communities worldwide. The key part of this evolution lies in the Status Communities product, which features tokenised interactions, channel monetisation, token gating, airdrops, token-based admin permissions, NFT minting, and more. Blockchain-based interactions are at the core of this product, which means that high gas prices will hinder or prevent growth and adoption.
In the future, Status aims to build its Community dApp plugin API and its dApp chat plugin SDK to enable dApps to be directly accessed and utilised in Status Communities and Status Messaging contexts. Unlocking highly affordable transaction fees for this functionality is needed to foster a vibrant open ecosystem of 3rd-party Status Communities dApps. This proposal aligns with the broader vision as depicted on the Communities page (Status - Make the jump to web3) on our new website.
- The solution must be EVM equivalent or compatible to ensure seamless portability for apps to run on it with minimal to no code changes necessary
- The transaction fees should target around 1 cent per transaction, enabling a wide range of onchain user interactions.
- The framework needs to be open-source (MIT licensed or equivalent) and align with the Status super apps’ objectives (reflected in our new website https://status.app/) and with Status’ core principles of open development, open-source, and decentralisation.
- The team leading the solution should be able to work collaboratively with the Nimbus team at Status.
- The solution should use Ethereum for data availability.
- Undertake rigorous technical due diligence to select the most appropriate L2 rollup tech stack partner that meets the outlined requirements and launch this L2 chain for use by Status users and the wider Status ecosystem.
- Adapt Nimbus to the rollup tech stack so that the Status chain can be powered by Status’ existing Nimbus Ethereum client software.
- The Status chain will act as a default chain for Status Communities interactions, but the Status apps will support multiple values-aligned EVM chains like Ethereum, Optimism, Arbitrum, and more (including of course Status’ L2 tech stack partner) in the future.
- If a decision is made to proceed with the SNT staking proposal (https://discuss.status.im/t/nip-1-introduction-of-snt-staking-mechanism/4141), the SNT staking contract could live on Status Chain.
Users will transition from experiencing high gas fees and potential exclusion from onchain activities to engaging in tokenised interactions within Status Communities at minimal costs. The proposed Status L2 chain will provide a default setting for these interactions, with the Status app continuing to support other EVM chains. Thanks to integrated bridging, users will be able to move their funds seamlessly between the L1 and all the L2s, including the Status chain.
- Substantially reduced transaction fees for Status users.
- Increased accessibility of onchain social interactions.
- Expanded user adoption due to lower costs.
- Enhanced growth potential for Status Communities.
- Engagement from external developers to start building on the Status chain.
- Not being able to find the right infra partners for this chain, resulting in a delayed or cancelled launch.
- Potential technical challenges in adapting Nimbus to the new rollup tech stack.
- Risk of not aligning with user expectations and core Status principles.
- Possibility of low engagement from external developers in the initial phase.
- Communities page detailing the broader vision: Status - Make the jump to web3