(1) When using the Graph, the amount of data on the chain is very large, and it is difficult to find the required fields. We read a large number of protocol documents, and source codes, and then found many calculation methods and storage of corresponding variables such as APY to obtain data which we use to help users find better DiFi products.
(2) When trying to integrate the Chain Signature feature of NEAR into our Dapp, we find that the example is completely based on @ethereumjs. It interacts with smart contracts by directly sending a transaction. We have to modify the simple transfer transaction into a much more complex transaction which allows the NEAR wallet to generate the signature and directly interact with the Ethereum DeFi smart contract.
(3) When creating a new subgraph for the burrow protocol on the Near chain, we can't get the ABI directly. To make matters worse, the source code on github is outdated. We tried to solve the problem with the tech staff from the Graph, Near and Burrow protocol together, but still couldn't debug it. So we built another new subgraph of AAVE on the Sepolia network instead. Since AAVE v3 adopts the EIP-1967, we create that subgraph from a proxy contract.