Arana Digital Delegate Platform

PIP-71: VeloraDAO Sponsorship of Governance Day 2025 – Buenos Aires

Vote: Sponsor Gold Tier

Rationale:

We opted in for the middle-ground Gold tier option. It’s not a very large expense and could have positive ROI by helping out with Velora brand recognition. Since the event will have a handful of governance participants, it can also attract decent candidates for future delegation. Regardless, now is a good time to begin getting the Velora name out there in a more prominent manner.

PIP-72 - Liquidity Funding for Futarchy Experimentation in Velora Governance

Vote: For

Rationale:

This proposal introduces a valuable governance experiment. We’re interested to learn how it plays out. The downside, like with IL, seems quite tame. Futarchy offers Velora a way to test whether conditional markets can effectively signal which policies the DAO should pursue by aligning incentives with measurable outcomes like token performance or protocol revenue. Allocating $50k in liquidity for market-making is a modest but meaningful step to test the viability of futarchy in practice, with limited downside and high informational value. If successful, Velora could build on a governance system that fuses economic forecasting with decentralized coordination, creating a more data-driven, feedback-rich mechanism for collective decision-making, following the likes of Gnosis, for example. We have seen more DAOs begin aligning behind futarchy-based models. The implementations are in their infancy but are exciting to see develop, especially from the vantage point of investors.

Rewards distribution for Epoch 35 & Gas Refunds distribution for Epoch 35

Vote: For Both

Rationale:

We voted in favor of both the rewards distribution and gas refund for Epoch 35, in line with our support for the distributions/refunds for previous epochs.

PIP-73 : VeloraDAO x Octav Partnership for Clear Treasury Reporting

Vote: For

Rationale:

Transparency and clarity regarding multisig funds is something that we are in favor of. Tracking them without a standardized and systematic fashion can be cumbersome. The SEED team has already put effort into these initiatives, but formalization through Octav is a welcome step. We’ll monitor the value-add of this partnership over the coming 12 months and reassess afterwards. Since Avantgarde also brought this forward as a proposal, we trust their judgement.

Rewards distribution for Epoch 36 & Gas Refunds distribution for Epoch 36

Vote: For Both

Rationale:

We voted in favor of both the rewards distribution and gas refund for Epoch 36, in line with our support for the distributions/refunds for previous epochs.

PIP-74: Discontinuing the Gas Refund Program

Vote: For

Rationale:

The low % of users who actually claimed their refund is substantially lower than we were expecting, at ~13%. If this was much higher, we’d reconsider, however, this refund program just seems to be an overhead burden at the moment. It’s fine to consider reviewing this later in the event more users are inclined to participate if/when ETH gas may be consistently higher. However, there seems to be some sort of disconnect with users. It would be prudent to investigate why the participation rate is presently so low. Do people just consider the gas component to be negligible and not worth the effort?

1 Like

Rewards distribution for Epoch 37 & Gas Refunds distribution for Epoch 37

Vote: For Both

Rationale:

We voted in favor of both the rewards distribution and gas refund for Epoch 37, in line with our support for the distributions/refunds for previous epochs.

PIP-75 - Fund request from a user claiming losses due to the March 2024 AugustusV6 vulnerability

Vote: Against

Rationale:

The reported exploit and issues pertaining to the AugustusV6 smart contracts is of course unfortunate. We went back and forth internally in regards to the legitimacy of this request. After observing the discussion on the forum and verifying with alternative sources, we believe that voting in favor of this proposal would bring more harm than good in the long term, opening Velora up to subjective liabilities and put delegates in a precarious decision-making position. Since it seemed like Velora/ParaSwap took the proper steps to advise users regarding the issue in a prompt manner, we believe the response from the team was apt. In order to quell future headaches, we voted against this proposal.