OpCo Product Team - July 2023 Update

A summary of development activity and KPIs for the OpCo product team in July 2023.


In July, our primary focus was on reducing the ‘fatal’ errors in transaction flows. This effort can be summarized as a series of bug fixes and the suppression of errors that either do not affect the flow or are beyond our control. We discovered that we were over-recording errors by up to three times, necessitating some reconfiguration of our exception-handling integration.

New features introduced include:

  • Cross-chain veBAL syncing (#3377)
  • Re-enabling of native asset joins for deep pools (#3624)
  • Saving of sort column state (#3646)
  • Support for approvals for tokens that require unapproval first (#3697)
  • Addition of CLP tag to relevant pools (#3781)
  • Support for Sepolia network (#3638)

We also made several optimizations:

  • Bundle optimization (#3659)
  • Improvement of font loading (#3658)
  • Optimization of pool page queries (#3634)

Work initiated in July and still ongoing includes portfolio page action improvements and the transition of the veBAL list into the API.

The content above covers the work completed in July at a high level. For a more detailed breakdown of all our work, you can browse the frontend repo releases page.


Transaction flow error free rate (30d): 84.6%
= 1 - (‘fatal’ errors / total successful txs)

Where ‘fatal’ is a label applied to errors recorded in a transaction flow, and total successful txs are recorded via analytics events.


  • We were overrecording ‘fatal’ errors 3x within the past 30d.
  • Ad blockers prevent error recording and analytics.
  • Some % errors are user-controlled errors we weren’t excluding, like cancelled txs.
  • Total successful txs: 98,400
  • Total fatal errors: 15,151

A concentrated effort was made in July, utilizing all our resources, to minimize fatal errors. This can be observed in the chart above. Although there is still more work to be done, it is evident that around July 20th, we managed to stabilize the number of reported errors. This was achieved through a combination of bug fixes and the suppression of errors that do not affect the flow or are beyond our control.

In August, we will maintain our focus on reducing ‘fatal’ errors, with a particular emphasis on issues related to mobile devices.

Lighthouse benchmark:

Note, as mentioned in our quarterly community update, it’s not easy for us to make significant improvements on performance without a change in stack, e.g. some server rendering with Next or Nuxt.

User satisfaction score: TBD
Avg. time on site (30d): 2:21 (-0:52 on previous 30d)

The decrease in average time spent on the site could be attributed to our focus on reducing transaction flow errors. As users encounter fewer issues, they can accomplish their tasks more efficiently. This metric can also be influenced by market conditions. For instance, we observe an increase in time spent on the site when the market is on the rise.

When we have a user satisfaction score to consider alongside the time spent on the site, we might gain a clearer understanding of this phenomenon.

Work is currently underway to implement a system for capturing user satisfaction scores.

Frontend v2 repo activity for July: