fix signature handling

[iuwqyir]

TL;DR

Improved signature handling for logs and transactions by moving ABI construction into the main handler functions.

What changed?

• Consolidated log and transaction handler logic by moving signature processing into the main handler functions
• Updated signature hash calculation to use ABI-generated IDs instead of manual Keccak256 hashing
• Simplified function signatures by removing unnecessary parameter passing
• Improved error handling for ABI construction

How to test?

1. Query event logs with a valid event signature
   • GET /{chainId}/events/{contract}/{signature}
2. Query transactions with a valid function signature
   • GET /{chainId}/transactions/{to}/{signature}
3. Verify that signature hashes are correctly generated from ABIs
4. Confirm that error handling works for invalid signatures

Why make this change?

The previous implementation had redundant signature processing and used a less reliable method for generating signature hashes. This change makes the code more maintainable and uses the more accurate ABI-generated IDs for signature matching, reducing potential edge cases and improving reliability.

[iuwqyir]

• use consistent read when deleting data #171
• use contract api as a fallback for decoding if signature based fails #170
• fix signature handling #169 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.