This new version of the proposal better reflects a stable way forward for the community, which is good to see.
However the proposal actually serves no practical purpose at this point, as it seeks to compel Orb to proceed exactly the same way it already does, with some minor adjustments that we would voluntarily make if just asked.
Whether this goes to a vote or not doesn’t change the outcome, but we should be considerate of the community’s time, with the heavy load of proposals there are to review each week.
These are already the terms of BIP-20 which was ratified by the community; it’s redundant to ask the community to approve something they’ve already approved.
As @Danko8383 has pointed out, governance-based monthly approvals might not make operational sense.
Since there are only 2.5 mo left, it is logical to make our financial updates monthly instead of quarterly- happy to do it. Our accounting books are normally finalized 2 weeks after the end of each month (standard accounting practice).
So in the 2nd- 3rd week of each month, we can provide a retrospective update on the previous month regarding actual spend (vs forecasted spend) include the addition/reduction of the difference in our forecast for the next month. In August, we’ll provide our update on July spend and reconcile the difference.
This would happen whether the community votes on it or not; it’s simple to just ask us to share monthly instead of quarterly updates. We were never compelled by governance to provide quarterly financial updates either- they’ve been voluntary.
We’re open to other suggestions the community may have for ensuring transparency regarding our monthly spend if this is a concern.
I’ve already stated our intention to return unused BAL and we “return” unused USDC every month by deducting it from our next monthly invoice to the OpCo. The only difference going forward is that after July we won’t be requesting any further funds, so we’d reconcile any difference by sending back or requesting funds.