Smart contracts are mapped on the native blockchains in chain.report. This applies to standard smart contracts, such as trading NFTs. However, we cannot map all smart contracts from all platforms. Especially since there are theoretically an infinite number of smart contracts.
chain.report covers the majority of all known smart contracts, including AAVE, Curve, Liquity, Uniswap, 1nch, and many others.
However, some smart contract protocols are from niche areas and often cannot be recognized by our fallback base detection. We therefore generally advise against the use of exotic smart contracts and their products, as well as interim solutions such as DeFi Saver.
Example:
With LIDO's smart contract, the input into staking is readable, as is the withdrawal. However, the staking rewards are not.
Reading unknown smart contracts can result in faulty transactions.
Below, you will find the corresponding reasons and how you can handle them. A summary is available in this video:
Be cautious when reading smart contract platforms via the native blockchain
For example, you might try to read GrizzlyFi via the BNB chain.
However, GrizzlyFi is not officially supported. Due to the lack of smart contract interpretation, defective or misinterpreted transactions can occur.
This could be, for instance, a deposit of two assets at once. Behind this could be a pool entry or something similar from GrizzlyFi, which is not connected.
There are three options:
1) Manually adjust the transactions imported from the native blockchain individually, so they reflect the transactions that actually occurred in reality. This might also mean you need to delete and recreate transactions. A clear understanding of the operations performed is required here.
2) Use the manual template completely
3) Wait for our integration of the corresponding exchange.