feat: add Morpho protocol events to events database #14
Description
Summary
Morpho protocol (0xbbbbbbbbbb9cc5e90e3b3af64bdaf62c37eeffcb on Ethereum mainnet) emits events via inline assembly, so they don't appear in the compiled ABI returned by Sourcify or Etherscan. This means the event decoder can't decode them despite the contract being verified.
Events to Add
| Topic0 | Event Signature |
|---|---|
0x9d9bd501d0657d7dfe415f779a620a62b78bc508ddc0891fbbd8b7ac0f8fce87 |
AccrueInterest(bytes32,uint256,uint256,uint256) |
0xedf8870433c83823eb071d3df1caa8d008f12f6440918c20d75a3602cda30fe0 |
Supply(bytes32,address,address,uint256,uint256) |
0xa56fc0ad5702ec05ce63666221f796b2d72d8c738525aae210ab01a926db588f |
Withdraw(bytes32,address,address,address,uint256,uint256) |
0x570954540bed6b1304a87dfe815a5eda4a648f7097a16240dcd85c9b5fd42a43 |
Borrow(bytes32,address,address,address,uint256,uint256) |
0x52acb05cebbd3cd39715469f22afbf5a17496295ef3bc9bb5944056c63ccaa09 |
Repay(bytes32,address,address,uint256,uint256) |
0xa3b9472a1399e17e123f3c2e6586c23e504184d504de59cdaa2b375e880c6187 |
SupplyCollateral(bytes32,address,address,uint256) |
0xe80ebd7cc9223d7382aab2e0d1d6155c65c5b3d3750e95e0c47500a7e1449e55 |
WithdrawCollateral(bytes32,address,address,address,uint256) |
0xa4946ede45d0c6f06a0f5ce92c9ad3b4751e2b26571a85dbdec969b881b2be1e |
Liquidate(bytes32,address,address,uint256,uint256,uint256,uint256) |
0x0d7d75e01ab95780d3cd1c8ec0dd6c2ce19e3a20427eec8bf53283b6fb8e95f0 |
FlashLoan(address,address,uint256) |
0x40b84e46cf529e7860e1a449f3d24ef9535e0eabd5c8f018a839b5a22b36e548 |
SetAuthorization(address,address,address,bool) |
0xac4b2400f169220b0c0afdde7a0b32e775ba727ea1cb30b35f935cdaab8683ac |
CreateMarket(bytes32) |
Context
Discovered while viewing tx 0x4807fb5e4a85cd00815725c400c0285e11c9c42feae389ceacb67fb98eef1253 — events 16, 18, and 19 from Morpho are not decoded despite the contract being verified on Sourcify. This is because Morpho emits events via Solidity inline assembly, so they are absent from the compiled ABI.