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 <code>unroutable</code>, 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 <a href="https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fsys.ibp.network%2Fbridgehub-kusama#/explorer/query/0xbe5d33b166c6e839eba295c04c646c512bd715622ad8faf2287f1ea9d9f098ee">events</a> that the tokens don't get deposited anywhere. This is new information to us.
This is the call-data I have used: <code>0x1f0903000109030300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000</code>
This would have been the correct call-data: <code>0x1f090301000300010100666963fc8192623504df2da473a1db2c69e1660463e2fd5071bcc68a96c3970d0304000100000b00203d88792d0000000000</code>
Our request is to recover the 50 KSM from openGov to the account that made call.
<ul>
<li>The call was our mistake, we should have double checked.</li>
<li>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.</li>
<li>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 <code>1,001,000</code></li>
</ul>

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](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fsys.ibp.network%2Fbridgehub-kusama#/explorer/query/0xbe5d33b166c6e839eba295c04c646c512bd715622ad8faf2287f1ea9d9f098ee) 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`

- **Problem Statement:** Lost 50 KSM during a teleport call due to an error in call-data copying.
- **Significance:** Tokens lost in the system with no trace, impacting the bidding for a system-collator slot.
- **Proposed Solution:** Requesting the recovery of the 50 KSM from openGov to the account that made the call.
- **Expected Outcomes:** Potential recovery of the lost 50 KSM and ongoing efforts by core developers to address claimable errors in the future.

#401 Recover KSM from a erroneous teleport/XCM call