Stellaswap Liquidity Program - Vote passed, XCM msg failed, re-execution downvoted

Dear Interlay community,

We've got a slightly awkward situation in our governance with respect to proposals #46 and #47.

TLDR

• Stellaswap made a treasury proposal to help build up the liquidity of iBTC and INTR in their new, more efficient Pulsar AMM (Uniswap v3-style). https://interlay.subsquare.io/democracy/referendum/46
• That proposal passed with 88% "aye" votes and a comparably high turnout.
• Unfortunately, an XCM bug caused the transfer to fail*
• The TC committee decided to re-execute and fast-track the proposal, considering it had clearly passed the vote.
  https://interlay.subsquare.io/democracy/referendum/47
• Fast-track only gives 3h to vote. Parties opposing the original proposal (a minority of the original vote) voted "No" again - but this time the proposal failed.

What now?
It is important to understand why the re-execution of the proposal was blocked.

• Did the community change its mind with respect to the Stellaswap proposal?
• Or was there simply insufficient time for everyone to vote on the re-execution?

We have 3 options on how to proceed:

1. Re-vote on the same proposal with a full 7-day vote.
2. Re-execute via fast-track (if majority of the community is clearly in favor)
3. Change the proposal and put to 7-day vote

Either way, we need to come to an agreement.
FYI: the Pular pool was set to launch next week, considering the original proposal had passed.

---

• The runtime upgrade in referendum #45 updated the Interlay XCM weight types. This change was not accounted for when the StellaSwap referendum #46 was made. The referendum passed but due to the change in the XCM weight types, #46 cannot be decoded by the chain and thus not executed. No XCM transfer happened.