# The Problem:

#### <mark style="color:green;">**Now that we have identified the problem:**</mark>&#x20;

The interoperability (or lack thereof) \&incompatibility between separate blockchains & platforms like centralized exachanges (think about trying to use a Microsoft product on an Apple computer, or trying to use an Android application on an iPhone – it doesn’t work, there is no compatibility), this begs the question:

* What happens if a crypto participant accidentally sends tokens to a mismatched receiving wallet address (ie: Sends USDC from a Polygon Network \[MATIC] wallet to an Avalanche Network \[AVAX] wallet – Two chains that do not communicate or credit each other’s assets in most cases).
* Another critical example would be sending Ethereum (ETH) tokens to a public key (cryptocurrency wallet) generated for receiving Bitcoin (BTC).&#x20;

#### <mark style="color:green;">So, what happens to these tokens/coins?</mark>

* The tokens are unfortunately lost in transit, neither arriving at the receiver’s wallet address nor returning to the sender.
* In most cases, these funds have an inability to be recovered and are off in the proverbial “crypto oblivion” forever. Never to be seen, nor heard from, ever again. Of course, the easiest way to avoid such an incident is by double-checking the details of any, and all, given transaction(s) to ensure that everything is coming from and being credited to the proper chain and wallet address.&#x20;
* This can become a tedious, time consuming, endeavor the more transactions you send. However, as humans, we are not infallible. Our imperfections leave our actions susceptible to error, but the consequences of such an error in the cryptocurrency ecosystem can be detrimental to crypto participants’ portfolios.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.presend.io/the-problem.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.