PR with Payload

https://github.com/BalancerMaxis/multisig-ops/pull/1111

Abstract

We propose the establishment of a financial reporting system for Balancer DAO’s assets. This system will deliver insights into the DAO’s financial status, aiding strategic decision-making.

In the initial phase, we will offer analytics and insights into the treasury. Based on the DAO’s goals and community feedback, we will refine the system to align with the needs of the community and Maxis.

Motivation

Karpatkey has been serving as Balancer DAO’s treasury manager, aiming to help the DAO achieve sustainability. Understanding the DAO’s financial landscape is crucial for making informed business decisions.

Currently, there is no comprehensive method to effectively visualize the DAO’s dynamic financial positions. Available resources include:

1. Karpatkey’s monthly reports on the Karpatkey-managed portion of the treasury.
2. Defilytica’s balances of the DAO as a whole.

However, these resources do not offer an in-depth analysis of the DAO’s overall financial position over time or the flow of funds. Due to the protocol’s multi-chain nature, Balancer is unique in holding assets across various chains, including Mainnet, Arbitrum, and other L2s.

Therefore, Karpatkey proposes building and maintaining a financial system for the DAO Treasury. This system will facilitate Balancer’s integration with GAAP (Generally Accepted Accounting Principles) and enable the DAO to better understand its finances, leading to more informed decision-making. The GAAP used shall be determined by Karpatkey based on factors such as international acceptance and understanding, as well as difficulty of implementation.

Specification

Based on GAAP, every transaction since the DAO’s inception would be reviewed and categorized with specific labels (e.g., “Fjord LBP”) and categories (e.g., “Operating revenue”). The categorized transactions would then be refined into the following information:

• Balance statement (i.e., Initial vs. Final Balances and USD conversions).
• Fund flow analysis.
• Expenses breakdown (e.g., by Service Providers, Payroll, etc.).
• Income breakdown (e.g., Swap & Yield fees, Fjord LBP, L2 fee, etc.).
• Cash flow forecasting (TBD).

The reports will eventually be available on an interactive website, where users can filter and sort based on the desired timeframe for analysis. Until a satisfactory UI is developed, the reports will be delivered in PDF format. Illustrations of the proposed outcomes can be seen in the following links:

• User Interface Demo: https://balaccounting-88030bbe433f.herokuapp.com
• Interim PDF presentation, including Financial report: https://drive.google.com/file/d/1_bmp9DvhOv5sKE9GXw0-hkNdhpweAjsa/view?usp=sharing

Other concomitant responsibilities will include:

• Integrating the bal_addresses repo for automatic indexing of all on-chain transactions in alignment with the DAO’s labels.
• Reviewing the efficiency of the DAO’s financial structure and publishing findings/recommendations to optimize expenses, operational results, and treasury management.
• Communicating with and supporting Balancer DAO to ensure the system can ultimately be used as a source of truth for potential taxes, legal, accounting, and other inquiries:
  • Conducting workshops with the Maxis to incorporate custom/technical details into the system.
  • Assisting future service providers, legal teams, and accountants in utilizing the system’s data and structure.

Budget

We propose a one-time grant of USD 20,000, fully payable in BAL, to Karpatkey for developing the financial reporting system. Additionally, we propose a quarterly fee of USD 6,000, also fully payable in BAL, for maintaining the system, providing monthly reports, and publishing findings and recommendations. For the one-time grant, the amount of BAL to be disbursed will be determined based on the 90-day moving average price of BAL on the payment date. For the quarterly fees, the amount of BAL to be disbursed will be determined based on the 90-day moving average price of BAL on the last day of the third month of each quarter.

Furthermore, Karpatkey pledges to lock each payment in the veBAL contract for at least one year from the moment it is received in Karpatkey’s wallet.

ETH Address to Receive Funds: 0x58e6c7ab55Aa9012eAccA16d1ED4c15795669E1C

Next steps

We encourage the community to review and provide feedback on this proposal. Our goal is to develop a comprehensive and useful toolkit for the DAO and its community to leverage for gaining deeper insights into the DAO’s finances.

Below are the suggested future steps and timeline:

1. Conduct a temp-check and review suggestions/feedback from the Balancer community.
2. Request access to the Foundation/OpCos bookkeeping records.
3. Collaborate with the Balancer Product team/Maxis to validate tags, labels, and other technical aspects of the system.
4. Generate financial reports in PDF format on a monthly basis.
5. Build and conduct user testing of the interactive UI.
6. Present the demo UI/product to the community for final feedback.
7. Deliver the UI and commence maintenance.

Termination

Balancer may terminate Karpatkey DAO’s engagement under this agreement for any reason through its Governance Mechanism. Karpatkey DAO may terminate this agreement upon four weeks’ notice, posted as a new discussion thread in the Balancer forum. If the termination is requested by Balancer without at least a four-week notice, Karpatkey DAO will be granted an exit fee equal to the fees collected during the last two months, which will be paid in ETH. Regular fees will be collected until the day of termination.

Technical Specification

The Balancer DAO multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with BAL 0xba100000625a3754423978a60c9317c58a424e3d by writing transfer passing the specified karpatkey safe 0x58e6c7ab55Aa9012eAccA16d1ED4c15795669E1C as recipient and amount as 5205 BAL 5205000000000000000000.