Dear HydraDX Community,

I am Josep, the lead of the Polkadot-API Development team. Today, I reach out to request your urgent assistance in rectifying a significant oversight on our part.

**TL; DR**
In a recent transaction intended to manage our salary funds, we inadvertently sent USDT to the public address of our pure-proxy on the relay-chain ([View Transaction](https://hydradx.subscan.io/extrinsic/4768439-3)). Unfortunately, this address is under [our control on the relay-chain](https://polkadot.subscan.io/account/13dXmfrN4Prb3FmdxKDNRyUeNDuNwUTZibYAMFNKmZJut2Lq), via [our multisig](https://polkadot.subscan.io/account/12R1XCdgkHysv8Y4ntiXguo4eUYHXjQTmfRjL8FbmezsG71j), but not on HydraDX. As a result, the assets have become inaccessible to us.

**Detailed Context:**
- Funds were received from our first OpenGov proposal ([Referendum](https://polkadot.polkassembly.io/referenda/467)).
- In adherence to the proposal's guidelines, we allocated the necessary amount of DOTs for operational expenses and converted them to USDT through HydraDX's DCA pallet. Excess DOTs were [responsibly staked](https://polkadot.subscan.io/extrinsic/20055960-3) to support the network's security.
- To that end we sent the required amount of DOTs to [an account that we control](https://polkadot.subscan.io/extrinsic/20054029-3).
- We then [teleported those DOTs to HydraDX](https://polkadot.subscan.io/xcm_message/polkadot-92122869706ae71c0edd8524a36d8054d69628b7).
- We then converted those DOTs to USDT via HydraDX's a [24 hours DCA trade](https://hydradx.subscan.io/extrinsic/4761544-2).
- The critical error occurred when the resulting USDT were mistakenly [sent back to the public address of our pure-proxy on the relay chain](https://hydradx.subscan.io/extrinsic/4768439-3).

**Proof of Ownership and Control:**
We have documented proof of our control over the involved address through [a remark on the Polkadot-Relay chain](https://polkadot.statescan.io/#/extrinsics/20070452-6).

![image.png](https://subsquare.infura-ipfs.io/ipfs/Qmeqf8d2nCszuGv4cNWCEMszmv19nwchMVd9feRyBQeyVw)
Feel free to double-check yourself using the data attached on the on-chain remark.

**Proposed Solutions:**
~We've prepared a pre-image (`0x02796f6eb254c73c5347f35929f4a63fd5a10e8839b8f52bdbd08bf3f5bf1755`) aiming to transfer the assets from the inaccessible account to a [HydraDX-controlled pure-proxy, overseen by our multisig](https://hydradx.subscan.io/extrinsic/4768595-2). An alternative could be to reverse the transaction, redirecting the assets back to the sender. We are open to either solution.~

EDIT: 
We have prepared a pre-image (hash: `0x8258249202c74c8cd67ce4fab175da5641507f3ca19bc0051c6db8ae29b4bbde`, len: `76`, call-data: `0x4d037454e2120a4f7b4eddc39c681fea50a8366b39c176e7393913bbfaca5649a450a020f6f98fd6505a856348c371cb7a0eee430c366f8ecddcee8cfbdfecb37e790a000000072e4755c416`) aiming to transfer the assets back to the sender. Therefore, effectively reverting the mistaken transaction. After some discussions, we do agree that this is the cleanest action given the current state of things.

**Request for Action:**
We kindly ask the HydraDX council to present a motion to amend this mistake. We are ready to provide any additional information or clarification needed.

We sincerely apologize for this oversight and the inconvenience it may cause. We operated under a critical misunderstanding regarding XCM capabilities between the relay-chain and parachains. Our assumption was that control over an address on the relay-chain would enable us to utilize XCM to access and manage these assets directly on any parachain, including HydraDX. This misunderstanding led to our decision to transfer the USDT to what we believed was an accessible address under our control. We now recognize the gap in our understanding and are seeking assistance to correct this oversight. Your understanding and prompt support would be greatly appreciated. 

Thank you for considering our request,

Josep


#175 Amend "Polkadot-API Dev Team" Misdirected USDT Funds