Untitled - public proposal #25

## Background
https://acala.discourse.group/t/acala-risk-parameter-change-proposal-may-2023/2096

## Proposal
The following suggestion is proposed to optimize for risk management for Acala.

+ Decrease Debt Ceiling of DOT from 50M to 20M
+ Decrease Debt Ceiling of LDOT from 5M to 2M
+ Decrease Debt Ceiling of LCDOT from 6M to 2M
+ Decrease Debt Ceiling of ACA from 6M to 1.5M

Risk parameters are best adjusted according to market conditions to balance insolvencies, liquidations, and capital efficiency. A lower debt ceiling helps mitigate the risk associated with excessive debt exposure and enable the protocol to remain solvent and resilient in volatile market conditions.



Acala Risk Parameter Change Proposal - May 2023

https://acala.discourse.group/t/proposals-to-fix-problems-caused-by-a-special-case-handling-issue-in-taiga-stable-asset-pallet-on-acala/2080/10?u=xlc

Resume full functionality of Taiga stable asset pallet on Acala

This is a runtime upgrade for Acala that fixes issue for Taiga stable asset pallet.

Release note: https://github.com/AcalaNetwork/Acala/releases/tag/2.17.0 

Runtime upgrade to fix Taipa stable asset pallet

https://acala.discourse.group/t/proposal-1-to-fix-problems-caused-by-a-special-case-handling-issue-in-taiga-stable-asset-pallet-on-acala/2080

Proposal 1 to fix problems caused by a special case handling issue in Taiga stable asset pallet on Acala

### Description
Risk parameters are best adjusted according to market conditions to balance insolvencies, liquidations, and capital efficiency. Setting minimum collateral ratios at appropriate levels can provide adequate guardrails for users without restricting them too heavily. Raising the minimum collateral ratio can prevent users from taking on additional risk in complicated market conditions and token price volatility. Liquidation is an important tool for managing systemic risk and encouraging responsible borrowing. Higher liquidation fees can reduce insolvency risk by encouraging borrowers to be more cautious and responsible when taking on debt, to maintain adequate levels of collateral and avoid taking on excessive risk.

### Proposal
The following suggestion is proposed to optimize for risk and capital efficiency for Acala.
+ Increase Minimal Collateral Ratio of ACA from 2.1 to 2.15
+ Increase Liquidation Fee from 15% to 18%

Risk Parameter Change

**TL;DR**

Proposal to list UNQ (Unique Network) native token on Acala Swap as the initial step to Advanced Economic Models implementation.

**Motivation**

As an old player of Polkadot ecosystem, we would like to integrate with multiple solutions in it. Listing UNQ on Acala swap is the first step towards integrating the projects we are going to host into the ecosystem.

**Description**

Unique Network applications can create their own cryptocurrencies as Substrate tokens or as an ERC-20 compatible fungible token. The first ambitious goal for Unique Network is to enable paying UNQ network fees in application currency to help their users avoid the necessity to deal with both UNQ and application tokens, and finally to enable application developers to sponsor user transactions to completely shield the end users from dealing with cryptocurrencies and creating the perfect frictionless user experience.
Nonetheless, for the safety of Unique tokenomics, we need to be able to exchange application tokens back for Unique. In order to complete the circle For the seamless exchange between application tokens and UNQ, we need to list UNQ on the Acala swap as the first step.

**Proposal 1**

- Enable Bootstrap for UNQ/DOT pool at block #3432175
- 168 hours of bootstrapping period ends at block #3482575 
- Bootstrap Start Time: April 24, 2023 11:00 AM (UTC)
- Minimum liquidity target is 1,400,000 UNQ OR 2,000 DOT 
- Minimum contribution requirement is 700 UNQ OR 1 DOT 

No trading is allowed during Bootstrap, and trading can only be enabled once the following criteria are met:

- Not Before the ending block has passed AND
- Either the pool has 1,400,000 UNQ OR 2,000 DOT in liquidity
- Both UNQ & DOT has >0 liquidity

If this referendum passes, and Bootstrap kicks off:

- You can contribute liquidity for UNQ, or DOT, or UNQ & DOT at the same time. The actual exchange rate of UNQ/DOT can only be known once the Bootstrap is completed.
- At the time of your contribution, you are allocated a number of LP tokens, and indicative LP shares of the pool, which are subject to change as more liquidity is added.
- You should only participate if you want to become a liquidity provider for the pool. Please be aware of various risks associated with being a liquidity provider.

**Incentives**

Incentives Parameter(#3482575)
Incentives for LP: 1m UNQ + 1k DOT
Incentives for Bootstrap: 300k UNQ (The Bootstrap rewards will airdrop to the participants directly after the Bootstrap end).
Incentives Period: 3 months
Loyalty Bonus Percentage: 50% (Claim rewards before loyalty program ends will void loyalty bonus, which is 50% of the rewards).
Loyalty Program Period: 3 months (Claim rewards after loyalty program ends (Block number #4144975) will be eligible for the loyalty bonus).

List UNQ-DOT Pair on Acala Swap

Hello everyone!

I'm an active Acala network and Polkadot ecosystem user who believes in its future.
I am pleased that the system provides the ability to return funds that were mistakenly transferred.

2022-05-11 17:28:30 I accidentally [sent](https://polkadot.subscan.io/extrinsic/0xbbc0738087df6875137fd8aed2e533b243dc660a1b428b97e79174d37226fed6) 254.1591507553 DOT from Polkadot to Acala to the null(0x0000000000000000000000000000000000000000000000000000000000000000) address. In fact, from the extrinsic details, I observed that these DOT were [crossed out](https://polkadot.subscan.io/xcm_message/polkadot-89bc9819c0d0315bbc0889808e05fa0529e61dfd) to the Acala network to address [zsbavR2qukGZb3e4KoEn1fFTrRwYqJCtQYK9qS1dYwspQF3](https://acala.subscan.io/account/zsbavR2qukGZb3e4KoEn1fFTrRwYqJCtQYK9qS1dYwspQF3).

This happened during the migration of the bridge from 1-way to XCM 3.0. I did it through my js code, where the mistake took place(related to the migration). Also, I tried to reproduce (not fill in the address) from Polkadot-js extension and it's still working [the same way](https://acala.subscan.io/xcm_message/polkadot-15276192a0d3800ecdbbb80adefffac4960862e0).

**I fully admit that this was my mistake, but I'm hoping that the community will understand my pain and take my side.**

I'm asking the community to support me with resolving this case, because:
1) The account [zsbavR2qukGZb3e4KoEn1fFTrRwYqJCtQYK9qS1dYwspQF3](https://acala.subscan.io/account/zsbavR2qukGZb3e4KoEn1fFTrRwYqJCtQYK9qS1dYwspQF3 ) has only one my extrinsic (except 1 sudo), so I assume that no one has access or is using it and these ~254 DOT is still on this account after more than half of year
2) The amount is quite big (as for me)
3) From my perspective, it is obvious that the transaction was made mistakenly and its rollback will not make anyone worse. But for one happy person in the world, there will be more. 

A few days ago I saw that in the Bifrost network, the user [returned back](https://bifrost.subsquare.io/democracy/referendum/162) accidentally sent KSM through the governance. That's why I decided that my case is similar and in theory, my tokens might be returned.

I created a [discussion](https://acala.discourse.group/t/return-back-dot-mistakenly-xcm-transferred-to-null-address/2048) regarding my issue and the community [advised](https://acala.discourse.group/t/return-back-dot-mistakenly-xcm-transferred-to-null-address/2048/5) me to create this proposal.

Please support my proposal. Much appreciated!

Return back DOT mistakenly XCM transferred to null address - public proposal #22

Context
We distribute stable asset rewards manually through our multisig account in the current setup. Due to the manual operations from multisig wallet, we distribute rewards on a weekly basis which we want to shorten to a daily basis. To make the above happen, we deployed a smart contract on EVM+ that disperse funds automatically when we trigger a reward distribution. The EVM contract has been deployed on Karura and it’s been tested extensively.
Proposal
To use the new EVM+ address deployed in the stable asset pallet, we need to change the fee recipient and yield recipient addresses to the EVM+ address: 23AdbsfTWCWtRFweQF4f3iZLcLBPwSHci9CXuMhqFirZmUZj in polkadot format and 0x081Efb42231FCa2Cfa81cdEDb6B68433ce61c486 in EVM format.
The above call is in the proposal #21: https://acala.subsquare.io/democracy/proposal/21
Preimage hash: 0xaadfddc63259f517a7c182ba5f178f8e6e6834cff9f60f4a8327d25270a4fd0d
Once the above call is completed, we can distribute the stable asset rewards automatically.

Proposal to change fee/yield address for the stable asset pallet

This is the on-chain proposal to open HRMP channel between acala and crust parachain network. Please check https://acala.discourse.group/t/open-hrmp-channel-between-acala-and-crust-parachain-network/2042 for more details.

Open HRMP Channel Between Acala and Crust Parachain Network

1. Register the Unique Network foreign asset:
     - name: Unique Network
     - symbol: UNQ
     - decimals: 18
     - minimal balance: 1,250,000,000,000,000,000 
2. Open an HRMP channel from Acala to Unique Network -- parachain #2037



Register the Unique Network foreign asset and open HRMP channel towards Unique Network

[Referenda #58](https://acala.subsquare.io/democracy/referendum/58) failed to dispatch due to missing EVM origin in governance triggered call issue. This one attempt to resubmit the proposal but using `authority.authorizeCall` to wrap the original proposal to avoid the missing EVM origin issue.

Proposal to refund stuck DAI due to EVM via XCM issue (2nd attmpt)

https://acala.discourse.group/t/proposal-to-refund-stuck-dai-due-to-evm-via-xcm-issue/2018

Proposal to refund stuck DAI due to EVM via XCM issue

## Summary
This is a full release for Acala & Karura that upgrades Substrate/Polkadot/Cumulus version to v0.9.33 and fix an issue about XCM transfer ERC20.

Release Note: https://github.com/AcalaNetwork/Acala/releases/tag/2.12.0

# Referendum
https://acala.subscan.io/referenda/57
https://acala.subsquare.io/democracy/referendum/57

#57 Runtime Upgrade - Upgrade Substrate/Polkadot/Cumulus to v0.9.33 and bug fixes

Accept HRMP channel request from Unique - **parachain #2037**


Accept HRMP channel request from Unique

Untitled - public proposal #16

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-12-20-2022/1975

Gauntlet Risk Parameter Recommendation (12/20/2022)

Register WETH, WBTC & APE to asset registry. All three assets are wrapped ERC20s and originate from Wormhole bridge (Portal).

Register WETH, WBTC & APE

# Summary
This is a full release for Acala & Karura that upgrades Substrate/Polkadot/Cumulus version to v0.9.31 and implemented sanity checks for some parameter updates.

Release Note: https://github.com/AcalaNetwork/Acala/releases/tag/2.11.0
# Referendum
https://acala.subscan.io/referenda/52
https://acala.subsquare.io/democracy/referendum/52

#52 Runtime Upgrade - Upgrade Substrate/Polkadot/Cumulus version v0.9.31

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-12-13-2022/1970

Gauntlet Risk Parameter Recommendation (12/13/2022)

Accept HRMP channel request from HydraDX - Parachain 2034

Accept HRMP channel request from HydraDX

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-12-5-2022/1967

Gauntlet Risk Parameter Recommendation (12/5/2022)

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-11-29-2022/1964

Gauntlet Risk Parameter Recommendation (11/29/2022) 

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-11-21-2022/1961/1

Gauntlet Risk Parameter Recommendation (11/21/2022)

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-11-14-2022/1953