Rena Dev Report #27 — V2 Announcing Public Beta in July

5 min readJun 30, 2023

This past development sprint primarily focused on internal development activities, particularly refactoring, and resolving essential critical debt. A critical blocker incident restricted other updates planned for the front end. This was a 3rd party issue with the Uniwap V2 Subgraph. The team focused efforts on resolving critical technical debt in lieu of limitations caused by the subgraph indexing issue, which now seems to be resolved. Key usability, scalability, and performance improvements have been accomplished during this sprint.

The team is focused on getting the protocol ready for OPEN BETA Testing set to be launched in July 2023 on Rena’s private testnet.

Summary of Tasks Completed

Technical Debt: Refactor Transaction Flow & Enable Live Updates:

rStaking: Transaction Flow Refactor & Live Updates — Completion: 100%
rGov: Transaction Flow Refactor & Live Updates — Completion: 100%
rBonds: Transaction Flow Refactor & Live Updates — Completion: 70%

Critical Blocker / Uniswap v2 Subgraph Indexing Issue:

Critical Blocker Issue Encountered Related to Uniswap V2 Subgraph
Third-Party Issue Resolved

Technical Debt: Messages / Notification System:

Message / Notification System Successfully Implemented
rStaking, rGov, and rBonds: 100% Completion Achieved
Ready for QA of Message / Notification Syntax

Preparations for PUBLIC BETA Testing in July:

Infrastructure Improvements to Enhance System Performance
Testnet Node Migrated to AWS and Virtual Machine Upgraded
Testnet Token-Faucet Repair — Impacted by Subgraph

Notable Pull-Requests:

Ticket #186 — RenaV2 Core Repo
Ticket #92 — RenaV2 Frontend Repo

What was Achieved?

Transaction Flow Refactoring & State Live-Updates:

rStaking: Transaction Flow Refactor & Live Updates — Completion: 100%
rGov: Transaction Flow Refactor & Live Updates — Completion: 100%
rBonds: Transaction Flow Refactor & Live Updates — Completion: 70%

The team successfully refactored the transaction flow and implemented state live-updates, which significantly improved the system’s performance and user experience. This effort involved one of the largest Pull Requests thus far, closing four tickets and addressing a major technical debt issue.

The completion of transaction flow refactoring and state live-updates for the rBonds module reached 70%, progress was impacted by the Uniswap sub-graph issue up until June 27th. Nonetheless, significant advancements were still made in improving this module and can now be completed.

Critical Blocker / Uniswap V2 Subgraph Indexing Issue:

Critical Blocker Issue Encountered related to Uniswap V2 Subgraph

A critical issue arose with the GraphQL Uniswap subgraph, specifically the subgraph for Uniswap V2 not syncing. This indexing issue had a significant impact on the project’s front end functionality and limited some ability to implement front end updates for a portion of the development cycle, namely as new rBonds could not be bound to liquidity pairs during the incident. Work on technical debt was prioritised to fill the development throughput while the 3rd party error remained unresolved.

Third-Party Issue Resolved

On June 27th the issue was resolved. We need to investigate why this happened, what alternatives exist, and implement proper guards for failing subgraph queries in the future.

New Ticket: Subgraph Incident Investigation & Future Management

Github Discussion: (https://github.com/Uniswap/v2-subgraph/issues/128).

Messages / Notification System:

Message / Notification System Successfully Implemented

Successful implementation of notifications across all transaction processes, including handling potential error states. These notifications were integrated into the rStaking, rGov, and rBonds modules, achieving 100% completion across all three components.

rStaking, rGov, and rBonds: 100% Completion Achieved

The notifications serve to provide users with informative and actionable messages, improving the overall user experience. For example, users will now receive notifications if they attempt to unstake before the designated unstaking period has ended. This implementation enhances user awareness and helps prevent unintentional errors or actions.

Ready for QA of Message / Notification Syntax

Next steps are to QA and do final updates on message content now that the technical capacity has been implemented on the platform.

New Ticket: QA: Final Check Number Formatting & Editorial Check Messages Across App

Preparations for PUBLIC BETA Testing in July:

Infrastructure Improvements to Enhance System Performance

In preparation for the upcoming Public Beta Testing phase, substantial efforts have been made to ensure a smooth user experience. These preparations aim to provide a seamless testing experience and increase the effectiveness of user feedback during the Public Beta Test.

Testnet Node Migrated to AWS and Virtual Machine Upgraded

The project’s node infrastructure has been upgraded by migrating to AWS and using a larger machine for improved scalability and performance.

Testnet Token-Faucet Repair — Impacted by Subgraph

The team is actively resolving the temporary disruption of the Token-Faucet functionality caused by the Uniswap subgraph incident.

Notable Pull-Request:

Ticket #186 — RenaV2 Core Repo

This pull request involved changes to the tests and web3 library in the RenaV2 Core Repo needed to make the implementation of RenaV2 Frontend Repo Ticket #92 possible.