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

Gauntlet Risk Parameter Recommendation (11/14/2022)

Untitled - public proposal #13

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-11-07-2022/1933

Gauntlet Risk Parameter Recommendation (11/07/2022)

# Summary

This is a runtime release for Acala that improves security and correct incentive related onchain state.

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

# Referendum

* https://acala.subscan.io/referenda/42
* https://acala.subsquare.io/democracy/referendum/42

#42 Runtime upgrade - fixes and improvements

This proposal will update auction collateral size limit as
10,000 ACA
1,000 DOT
1,200 LcDOT
5,000 LDOT
to reduce liquidation impact in response to current volatile market conditions.

Update auction collateral size limit.

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

Gauntlet Risk Parameter Recommendation (11/01/2022)

https://acala.discourse.group/t/gauntlet-risk-parameter-recommendation-10-14-2022/1919

Gauntlet Risk Parameter Recommendation (10/14/2022)

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmYP8SQYgKgnJxBgUbxWGcNSAEXv4rDCnnfHTtana3Vqj9) of the general direction for resume services was passed. 
Let’s vote for the [staged executions](https://acala.discourse.group/t/proposal-to-resume-services/1805#proposal-1). 
This is the stage 3 vote.


Stage 3 for Resume Services


A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmYP8SQYgKgnJxBgUbxWGcNSAEXv4rDCnnfHTtana3Vqj9) of the general direction for resume services was passed. 
Let’s vote for the [staged executions](https://acala.discourse.group/t/proposal-to-resume-services/1805#proposal-1). 

This is the stage 2.2 vote.


Stage 2.2 for Resume Services

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmYP8SQYgKgnJxBgUbxWGcNSAEXv4rDCnnfHTtana3Vqj9) of the general direction for resume services was passed. 
Let’s vote for the [staged executions](https://acala.discourse.group/t/proposal-to-resume-services/1805#proposal-1). 
This is the stage 2 vote.


Stage 2 for Resume Services

This proposes a reset of the schedulers affected by previous [runtime upgrade](https://acala.subsquare.io/democracy/referendum/32) that removed dex saving code. 


Reset schedulers after dex saving removed

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmYP8SQYgKgnJxBgUbxWGcNSAEXv4rDCnnfHTtana3Vqj9) of the general direction for resume services was passed. 
Let‘s vote for the [staged executions](https://acala.discourse.group/t/proposal-to-resume-services/1805#proposal-1). 
This is the stage 1 vote.

Stage 1 for Resume Services

This proposes an upgrade of the Acala Runtime to fix a critical security vulnerability that was reported to Parity.

Proposal hash: 0x71860be879125b742eec6cde2802c08f655e1ce64c58276a8c58afff7a631e90
Ecoded: 0x1e02947955583e688e616a8dbd1b8471a9b83ae546ce4471e83a8cb0f9a7fe0b4226

Release:
https://github.com/AcalaNetwork/Acala/releases/tag/2.9.5-acala

This needs to be expedited for its criticality.


Acala Runtime Upgrade 

https://acala.discourse.group/t/proposal-to-fix-dex-saving-code/1872

Proposal to fix dex saving code

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmZrpoQfRiHkaejsxsefKLub1VJVhCnGyuk7wMXXAiYTMD) of general direction for aUSD recovery has passed. Here are the [execution steps](https://acala.discourse.group/t/proposal-for-ausd-recovery-based-on-full-trace-results/1580#execution-updated-6). This is step 4.2 vote.

Step 4.2 for aUSD Recovery

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmZrpoQfRiHkaejsxsefKLub1VJVhCnGyuk7wMXXAiYTMD) of general direction for aUSD recovery has passed. Here are the [execution steps](https://acala.discourse.group/t/proposal-for-ausd-recovery-based-on-full-trace-results/1580#execution-updated-6). This is step 4.1 vote.

Step 4.1 for aUSD Recovery

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmZrpoQfRiHkaejsxsefKLub1VJVhCnGyuk7wMXXAiYTMD) of general direction for aUSD recovery has passed. Here are the [execution steps](https://acala.discourse.group/t/proposal-for-ausd-recovery-based-on-full-trace-results/1580#execution-updated-6). This is the third step/referendum vote.

Step #3 for aUSD Recovery

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmZrpoQfRiHkaejsxsefKLub1VJVhCnGyuk7wMXXAiYTMD) of general direction for aUSD recovery has passed. Here are the [execution steps](https://acala.discourse.group/t/proposal-for-ausd-recovery-based-on-full-trace-results/1580#execution-updated-6). This is the second step/referendum vote.

Step #2 for aUSD Recovery

A [sentiment vote](https://voting.opensquare.io/space/acala/proposal/QmZrpoQfRiHkaejsxsefKLub1VJVhCnGyuk7wMXXAiYTMD) of general direction for aUSD recovery has passed. Here are the [execution steps.](https://acala.discourse.group/t/proposal-for-ausd-recovery-based-on-full-trace-results/1580#execution-updated-6) This is the first step/referendum vote to pause homa and stableswap, and turn on the freeze feature.

Step #1 for aUSD Recovery

https://acala.discourse.group/t/proposal-1-for-trace-result-4-aug-19-2022/1387

Proposal #1 for Trace Result #4 Aug-19-2022

https://acala.discourse.group/t/proposal-1-for-trace-result-4-aug-19-2022/1387/30

Emergency vote requested by community

Untitled - public proposal #0

https://acala.discourse.group/t/proposal-for-trace-result-2-08-17-2022/1285

Proposal for Trace Result #2: 08-17-2022

https://acala.discourse.group/t/proposal-for-expedited-referenda/1228

Runtime upgrade to expedite referenda

https://acala.discourse.group/t/proposal-for-trace-result-1-08-15-2022/1137

 Proposal for Trace Result #1: 08-15-2022 

# Summary

This is a runtime release for Acala and Karura that upgrades Substrate/Cumulus/Polkadot to v0.9.26 and reduced the publication fee for Acala EVM+.

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

# Referendum

* https://acala.subscan.io/referenda/20
* https://acala.subsquare.io/democracy/referendum/20

#20 Runtime Upgrade - Upgrade Substrate/Polkadot/Cumulus version and enable EVM+ for Acala

## Summary
Read more [here](https://acala.discourse.group/t/honzon-fungibility-pallet-to-make-ausd-fungible-between-acala-karura/1091/2)

## Proposal Call
Configuration of `Quota to Acala`
1. Generate aUSD@Acala quota (not in circulation) = 1.1M 
2. Deposits to the Wormhole bridge to mint 1:1 waUSD
3. Deposit the waUSD to the Honzon Fungibility pallet on Karura

## Referendum
https://acala.subscan.io/referenda/19

Execute Honzon Fungibility Pallet to make aUSD fungible between Acala & Karura

# Summary
This is a runtime release for Acala that supports XCM transfer to Statemint

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

#18 Runtime Upgrade - Enable Statemint XCM transfer

# Summary
This is a runtime release for Acala that fix evm bug.

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

# Referendum
https://acala.subscan.io/referenda/17


Runtime Upgrade - Fix EVM bug

# Summary
This is a runtime release for Acala that enable aggregated-dex and honzon-bridge, and fix calculation overflow bug for stable-asset.

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

# Referendum
https://acala.subscan.io/referenda/16


#16 Runtime Upgrade - Enable Aggregated DEX and Enable Honzon Bridge

# Summary

This is a runtime release for Acala and Karura that upgrades Substrate/Polkadot/Cumulus version to v0.9.24, add new Homa ProxyType, improves fee handling, and add TAP token.

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

# Referendum

* https://acala.subscan.io/referenda/15
* https://acala.subsquare.io/democracy/referendum/15

#15 Runtime Upgrade - Upgrade Substrate/Polkadot/Cumulus to v0.9.24

# Summary

This is a full release for Acala and Karura that upgrades Substrate/Polkadot/Cumulus version to v0.9.22, enables XCM transfer for ERC20 tokens and fixes dex aggregator pallet.

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

# Referendum

* https://acala.subscan.io/referenda/14
* https://acala.subsquare.io/democracy/referendum/14