Replace and Recover Failed Treasury Spend
Beneficiary:This proposal is to replace and recover a failed treasury spend that Snowbridge submitted earlier this year. The spend was for a past proposal that failed because at the time when it was claimed, there was not enough USDC in the Asset Hub treasury.
The claim extrinsic was successfully submitted to Polkadot, but then when the XCM was sent to AssetHub to transfer the funds, the transfer failed due to insufficient USDC.
Unfortunately, we cannot retry the claim since Polkadot marked it as successful, even though the XCM failed.
The original approved treasury spend is here: https://polkadot.subscan.io/treasury_spend/29
The treasury.spend extrinsic that succeeded on Polkadot: https://polkadot.subscan.io/extrinsic/25613045-2?tab=event
The corresponding XCM message that was processed (and failed) on AssetHub due to insufficient USDC: https://assethub-polkadot.subscan.io/block/8652209?tab=event&event=8652209-7 - the XCM message queue was processed correctly, but within the event one can see that the message itself was not successful.
This proposal creates a new spend, the same as the original one, ie, 312,500 USDC
Comments (1)
Voting has Started
2
of 3Decision Period
6 / 28 days
Confirmation Period
0 / 4 days
Summary
0%
Aye
0%
Nay
Aye (21)0.0 DOT
Support0.0 DOT
Nay (6)0.0 DOT
Comments (1)
Dear Proposer,
Thank you for your proposal. Our first vote on this proposal is AYE.
The Medium Spender track requires 50% quorum (at least 5 aye votes) and simple majority of non-abstain votes according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received five aye and zero nay votes from ten available members. Below is a summary of our members' comments:
The voters expressed unanimous support by affirming that the proposal justified fulfilling the previously approved treasury payment despite technical setbacks. They argued that rectifying the failed asset transfer was necessary to honor commitments made in earlier proposals. The comments highlighted that even though administrative errors led to an unsuccessful payment execution, addressing the issue was fair and essential to uphold past approvals. The decision was driven by a shared belief in the importance of meeting contractual obligations and recovering funds, ensuring that the work previously endorsed was appropriately compensated despite the encountered challenges.
The full discussion can be found in our internal voting.
Please feel free to contact us through the links below for further discussion.
Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate
📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate
Dear Proposer,
Thank you for your proposal. Our first vote on this proposal is AYE.
The Medium Spender track requires 50% quorum (at least 5 aye votes) and simple majority of non-abstain votes according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received five aye and zero nay votes from ten available members. Below is a summary of our members' comments:
The full discussion can be found in our internal voting.
Please feel free to contact us through the links below for further discussion.
Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate
📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate