#bug; Missing Transactions in Spark Subgraph Due to New Proxy Contract

[benjamindamm]

Describe the bug

It seems that transactions related to a new contract address in Spark Lend are not being picked up by the current subgraph. This is likely due to the fact that a new proxy contract was deployed approximately 148 days ago, while the original implementation contract was deployed about 700 days ago. If the subgraph is still tracking the old contract or implementation logic, it may be missing events from the new proxy.

Reproduction

Where can we see this bug in action?

This issue is difficult to reproduce directly, as it depends on the indexing behavior of the subgraph. However, we can observe that the last indexed deposit event is associated with the timestamp 1710549599, which corresponds to Saturday, 16 March 2024 00:39:59 (UTC). This suggests that more recent transactions, particularly those from the new proxy contract, may not be captured correctly.

Steps to reproduce:

• Verify the old contract address (original implementation):
  Old contract address: 0x03cfa0c4622ff84e50e75062683f44c9587e6cc1
  Etherscan
• Verify the new proxy contract address:
  New proxy contract address: 0xd0A61F2963622e992e6534bde4D52fd0a89F39E0
  Etherscan
• Check if transactions passing through the new proxy contract are missing in the subgraph.

Expected behavior

Transactions routed through the new proxy contract should be picked up by the subgraph, similar to how they were handled by the original implementation contract. The subgraph should correctly index events related to lending, borrowing, and token transfers from the new proxy contract.

Screenshots

Additional context

• Old contract deployment: ~700 days ago
• New proxy contract deployment: ~148 days ago
• The Spark subgraph currently tracks the address 0x03cfa0c4622ff84e50e75062683f44c9587e6cc1 on Mainnet, which might be outdated. The new proxy may not be included in the event handlers.
• Suggest verifying the event signatures from both contracts to ensure compatibility. If necessary, update the subgraph mappings or handler configuration.

[ishraq8]

@harsh9200 Whenever you can, mind taking a look at this?