The Cardano Treasury withdrawal process for DRep-approved budget proposals is a significant task for DReps and the community to actively participate in. Several withdrawal options should be reviewed and considered by the community to support the best interests of the ecosystem. The amount of information can be overwhelming, so we’d like to provide some insights based on each option. In follow-up to the voting results of our recent “Asking for a friend” polls, we stated that conducting 39 separate withdrawals (one for each approved budget proposal) would prove to be very burdensome and costly, requiring 3.9 million ADA in deposits, thereby slowing funding for vendors. Each withdrawal method has some pros and cons. We also understand that there were DReps who were unable to previously participate and vote to approve proposals, so each one should be carefully considered. Here’s a quick breakdown of each option. Option A: Single Withdrawal We are aware that the community largely opposes this option. While it is the most expedient and efficient, it lacks the level of oversight many expect. Option B: Two Support brackets with one withdrawal each Option C: Two Support brackets with two withdrawals each Option D: Five Support brackets (50-59%, 60-69%...) For options B,C and D, we believe the three middle-ground options strike a good balance. They offer administrative efficiency while still ensuring reasonable oversight from DReps. Option E: 39 Individual Treasury Withdrawals We understand the community may favor this option. However, it is admin-heavy and places a significant burden on operations, and costly, requiring 3.9 million ADA in deposits, thereby slowing funding for vendors potentially putting many proposals and events at risk. There is a real world implication to projects and the people that have committed to building on Cardano - ie salaries, hiring plans, fixed cost commitments, deadlines to secure venues. Ultimately, whichever withdrawal method is chosen by the community, we strongly advocate that withdrawals be batched or grouped together to prioritize efficiency while balancing the need for fair DRep oversight, as our ecosystem is already 6 months behind with regards to the current funding cycle. This is the first year of the Treasury withdrawal process, and we’ve all learned valuable lessons along the way. Moving forward, we feel that these experiences will help us refine the process and continue to strengthen Cardano’s community-run governance model. We continue to deliberate on our final voting stance and will communicate our decision once finalized. How would you like to see Intersect submit Treasury Withdrawals against the Budget Info Action? Place your vote on Ekklesia before Tuesday, June 10 at 23:59 UTC https://intersect.ekklesia.vote/ballots/6842059aee76bef65d558e68/proposals/6842059bee76bef65d558e6b And review the voting pack here https://docs.intersectmbo.org/cardano/cardano-budget-submission/treasury-withdrawal-poll-voting-pack