tl;dr The preimage for <a href="1346" target="_blank" rel="noopener">Ref. 1346</a> was pulled during confirmation to avoid payout of AssetHub assets to a Relay Chain Proxy. This ref intends to rectify the payout approved by Ref. 1346.
Q: What was the problem? A: A Relay Chain Proxy as beneficiary of Asset Hub assets would mean the assets were inaccessible.
Q: Proof the preimage was pulled? A: You can verify it <a href="https://polkadot.subscan.io/extrinsic/24266734-2">here</a> - pulled ~30 minutes before the end of the confirmation period.
Q: Why not wait until Pure Proxy Replication is implemented? A: <a href="https://github.com/polkadot-fellows/RFCs/pull/111">Pure Proxy Replication</a> will solve this UX issue however it is unclear when the fix will be pushed to prod which would render the assets useless until then.
Q: Why not submit root ref to replicate proxy? A: While such a ref has recently been submitted for <a href="https://polkadot.subsquare.io/referenda/1308">several other projects</a> caught in this UX snare, we decided it would be unwise to tie the root track for a single instance. It would also take months during which time the assets would be useless.
Your vote will accelerate the rectification of this payout previously approved. Thank you for the support! ❤️🤖

**tl;dr**  
The preimage for [Ref. 1346](1346) was pulled during confirmation to avoid payout of AssetHub assets to a Relay Chain Proxy. This ref intends to rectify the payout approved by Ref. 1346.

**Q: What was the problem?**  
A: A Relay Chain Proxy as beneficiary of Asset Hub assets would mean the assets were inaccessible.

**Q: Proof the preimage was pulled?**  
A: You can verify it [here](https://polkadot.subscan.io/extrinsic/24266734-2) - pulled ~30 minutes before the end of the confirmation period.

**Q: Why not wait until Pure Proxy Replication is implemented?**  
A: [Pure Proxy Replication](https://github.com/polkadot-fellows/RFCs/pull/111) will solve this UX issue however it is unclear when the fix will be pushed to prod which would render the assets useless until then.

**Q: Why not submit root ref to replicate proxy?**  
A: While such a ref has recently been submitted for [several other projects](https://polkadot.subsquare.io/referenda/1308) caught in this UX snare, we decided it would be unwise to tie the root track for a single instance. It would also take months during which time the assets would be useless.

Your vote will accelerate the rectification of this payout previously approved. Thank you for the support! ❤️🤖

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

- Problem Statement: Rectifying the payout approved by Ref. 1346 to avoid assets being inaccessible to a Relay Chain Proxy.
- Significance: Avoiding assets becoming useless due to the Relay Chain Proxy beneficiary.
- Proposed Solution: Accelerating the rectification of the payout through a new referendum.
- Expected Outcomes: Timely resolution of the issue to prevent assets from being rendered useless.

#1381 Ratify Payout APPROVED by Ref. 1346 - Token Terminal

No Active Proposals