missing inbound transactions for some addresses

[rob-absolute]

Hey everyone, can anyone help me investigate a weird balance / lack of transaction on polygonscan? My team is working on investigate a few weird matic balances in our data and we came across Hop Protocol which allows in the examples here to bridge matic from the Ethereum network to Polygon.
We isolated a few examples of addresses clearly sending matic to polygon, but polygonscan and oklink don't show any incoming transaction for the matic itself on ploygon.

This address: https://polygonscan.com/address/0xfdf6c6096e70799e53d6172d32c6c3b6f3d1f38f
Has only one transaction where it sends about 17.3K matic to anyswap to bridge to Boba. But, nothing shows where the Matic came from in the first place.
I found this transaction on ETH https://etherscan.io/tx/0x81ccb965f059f53a6edd005a3f3645840c24f24440eb26a04e2b0ebee757dd95 - "send to L2", of the same amount, happening before.

So that's where the Matic is coming from. However, I need a way to see the inbound matic on the Polygon chain. Is there a missing transaction here, how does the matic actually ended up in that address?

Also look at this address : https://polygonscan.com/address/0x718c0c212db4fc57f8fe14e92229a604df666ee8

it also has outbound transactions higher that inbound for matic.

[ramicaza]

A similar issue we're facing is detecting plasma bridge deposits on polygon. They don't seem to show up in the transactions or traces table but in the case of deposits they DO show up on the polygon scan. This doesn't help much though since we need to be able to access it from the polygon-etl. So it seems there are possibly 2? MATIC sources that are unhandled by this repo. Since plasma bridge deposits are quite common, many of the addresses we analyze end up having negative balance. This is causing great problems for our team as well :(