As a user, I am bridging tokens from one blockchain to another. Bridging is defined as a portal connecting several distinct blockchains, enabling users to transfer data and assets across different blockchains. In this example, I am bridging MATIC from the Polygon network to the Ethereum network. In some cases, the bridge used may issue a token representing the quantity of an asset being bridged to the receiving blockchain. In this case, I have bridged XX MATIC from Polygon to Ethereum - in CoinTracker that appears as a single Sent transaction of XX MATIC. Users should see a Transfer transaction represent XX MATIC Sent and Received in the same transaction with the specificed Sent (MATIC) and Received (ETH) wallets. Some bridges send a token to the receiving blockchain representing the quantity of the token sent. So some users may see the single Sent transactions followed by a Trade transaction that shows an unsupported token flagged with an insufficient balance being traded for the equivalent amount of XX MATIC (Image 1).
This is not selective to bridging between the MATIC and ETH networks, this type of bridging can be represented on other blockchains. The bridge used will play a factor into how bridging is treated by CoinTracker. There are bridges that do not assign a token.
Users can workaround this by ignoring the transaction with the unsupported token and changing the single Sent transaction to a transfer transaction and designating the receive wallet. If there are two fees, users can add both fees to the single transaction.
We have escalated this behavior and will update this post once a fix is deployed.