Recover KSM from a erroneous teleport/XCM call

We lost 50 KSM in a blockhole during a teleport call. We were trying to teleport 50 KSM from our account on Bridgehub-Kusama to Kusama.

We first tried with small amounts after we had found the right working call and then we thought copied the call-data to initiate the actual transfer, but it was an old copy that lead to the error of unroutable, which is a fatal error and the tokens get lost apparently in the system. We don't know where they get lost. You can see it in the events that the tokens don't get deposited anywhere. This is new information to us.

This is the call-data I have used: 0x1f0903000109030300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000

This would have been the correct call-data: 0x1f090301000300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000

Our request is to recover the 50 KSM from openGov to the account that made call.

The call was our mistake, we should have double checked.
There is work in progress by the core developers to make sure these errors are claimable in the future, but it's not in production yet.
The 50 KSM was on that account was to bid for a system-collator slot for bridgehub, which we didn't win. The teleport was one way until runtime upgrade 1,001,000

We lost 50 KSM while trying to move it between accounts.
We used the wrong code, so the KSM disappeared.
The KSM didn’t go to any account—it’s lost in the system.
We made a mistake by not double-checking the code.
Developers are working to fix this problem in the future.
The 50 KSM was meant to bid for a special job (system-collator).
We didn’t win the bid, and now the KSM is gone.
We hope to recover the lost KSM.

Source

We lost 50 KSM in a blockhole during a teleport call. We were trying to teleport 50 KSM from our account on Bridgehub-Kusama to Kusama.

We first tried with small amounts after we had found the right working call and then we thought copied the call-data to initiate the actual transfer, but it was an old copy that lead to the error of unroutable, which is a fatal error and the tokens get lost apparently in the system. We don't know where they get lost. You can see it in the events that the tokens don't get deposited anywhere. This is new information to us.

This is the call-data I have used: 0x1f0903000109030300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000

This would have been the correct call-data: 0x1f090301000300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000

Our request is to recover the 50 KSM from openGov to the account that made call.

The call was our mistake, we should have double checked.
There is work in progress by the core developers to make sure these errors are claimable in the future, but it's not in production yet.
The 50 KSM was on that account was to bid for a system-collator slot for bridgehub, which we didn't win. The teleport was one way until runtime upgrade 1,001,000