[RFC] - Deploy Uniswap V3 on Redbelly Network

Requests for Comment
1

Overview:

  • The purpose of this post is to apply for canonical Uniswap V3 deployment on Redbelly Network
  • All of the Uniswap V3 contracts have already been deployed. (details below)
  • No further actions need to be taken by the DAO.

About Redbelly:

Redbelly Network is the world’s first formally verified layer 1 blockchain, developed at the University of Sydney in collaboration with CSIRO, the Australian National Science Agency, and holds Patent #12093247 granted in the United States.

Redbelly Network enables Real World Asset (RWA) issuers to tokenize and trade compliant on-chain structured products. With over US$1 billion in tokenized assets already deployed on-chain and a network of 750,000 KYC verified wallets, our ecosystem is growing fast.

  • Focused on compliant on-chain RWAs and structured products
  • 97,500 Transactions per Second, as seen on chainspect
  • Sub-Second Finality
  • Formally Verified Consensus
  • Predictable and Constant Gas Fee
  • 100% EVM Compatible
  • Solidity Support

Key Benefits of Redbelly Network and synergy with Uniswap:

  1. A network of clean liquidity (Every wallet is linked to a KYC/KYB), combined with network-wide verifiable credentials enables structured products with composable eligibility criteria.

  2. Enables asset managers to establish digital registries as a shared source of truth, and create structured financial products using tokenised assets.

  3. Scalability and Speed: Redbelly Network boasts the ability to process 97,500 transactions per second (TPS) with sub-second transaction finality, ensuring fast and irreversible transactions. This makes it highly efficient for applications requiring high throughput and low latency.

  4. Predictable and Constant Gas Fee: With Redbelly Network, gas fees are predictable and constant (calculated in USD and not in native tokens), meaning that users, developers and businesses never need to worry about paying more when the network is in demand. This assures users, developers and businesses that their transaction costs will remain constant and predictable, making it easier to budget when planning for blockchain projects.

  5. EVM Compatibility: Redbelly Network is fully compatible with the Ethereum Virtual Machine (EVM), allowing developers to deploy existing smart contracts without modifications. This ensures seamless migration from other chains and expands the potential for onboarding new applications.

  6. With its focus on RWA, Redbelly will open a new area of exploration to the Uniswap and ETH ecosystem, paving the way with standardising the process of tokenisation.

    6.1. All users need to go through a KYC/KYB process to get transaction capabilities on Redbelly Mainnet and without that they can’t swap on OKU frontend or add liquidity to pools.

    6.2. Redbelly enables verifiable credentials on-chain. which can be used with uniswap smart contracts to bring complex logic based on jurisdictions, compliance or any other condition as part of the system, enabling RWA.

Proposal Stakeholders

Deployment Details

As with all canonical v3 deployments, this deployment will be subject to Ethereum Layer 1 Uniswap Protocol governance and control. The text record of the uniswap.eth ENS subdomain titled v3-deployments.uniswap.eth will be amended by the Accountability Committee to include references to the stated v3 contracts.

Deployed Addresses:

Timeline

  • Uniswap V3 has already been deployed on Redbelly Network
2

Thank you for the update. Could you provide additional information regarding the structure of the business arrangement related to the deployment of Uniswap V3 on Redbelly.

  1. What are the terms of compensation for GFX Labs/Oku in relation to their role as the deployer and provider of the frontend interface?

  2. Could you provide data on current user activity—specifically, the number of unique daily active users on the Redbelly chain and the number of users who have interacted with the Uniswap V3 contracts?

  3. Was the canonical nature of the deployment a determining factor in the selection of GFX Labs as the deployer, as opposed to other potential providers, or self deployment?