Event signature · Lending

AbsorbCollateral (Compound V3) event signature and topic0

The topic0 of the AbsorbCollateral (Compound V3) event is 0x9850ab1af75177e4a9201c65a2cf7976d5d28e40ef63494b44366f86b2f9412e, the keccak-256 hash of AbsorbCollateral(address,address,address,uint256,uint256); 3 of its 5 arguments are indexed. Liquidated account's collateral seized on a Compound V3 market.

Anatomy of a AbsorbCollateral (Compound V3) log

Topics

  • topic00x9850ab1af75177e4a9201c65a2cf7976d5d28e40ef63494b44366f86b2f9412ekeccak256("AbsorbCollateral(address,address,address,uint256,uint256)")
  • topic1absorber (address)indexed: filterable
  • topic2borrower (address)indexed: filterable
  • topic3asset (address)indexed: filterable

Data

  • datacollateralAbsorbed (uint256), usdValue (uint256)ABI-encoded, decoded with the ABI
Parameters

Arguments and where they sit in the log

Indexed arguments travel as topics and can be filtered cheaply; the others are ABI-encoded together in the data.

NameTypeIn the log
absorberaddresstopic1
borroweraddresstopic2
assetaddresstopic3
collateralAbsorbeduint256data
usdValueuint256data

Solidity declaration

event AbsorbCollateral(address indexed absorber, address indexed borrower, address indexed asset, uint256 collateralAbsorbed, uint256 usdValue);

Canonical signature

AbsorbCollateral(address,address,address,uint256,uint256)

topic0

0x9850ab1af75177e4a9201c65a2cf7976d5d28e40ef63494b44366f86b2f9412e

Ready-made alerts

Get an alert on AbsorbCollateral

Each rule opens with the contract and the conditions filled in. Sign in, pick your chat and click Create.

Who emits it

Contracts we list that emit AbsorbCollateral

Any other contract with the same signature emits a log with the same topic0.

Code

Read AbsorbCollateral logs in code

The same filter in viem, ethers and plain JSON-RPC, and the Solidity that emits it. The address is Compound V3 USDC (cUSDCv3), a contract we list that emits it.

viem
import { createPublicClient, http, parseAbiItem } from "viem"
import { mainnet } from "viem/chains"

const client = createPublicClient({ chain: mainnet, transport: http() })

const logs = await client.getLogs({
  address: "0xc3d688b66703497daa19211eedff47f25384cdc3",
  event: parseAbiItem("event AbsorbCollateral(address indexed absorber, address indexed borrower, address indexed asset, uint256 collateralAbsorbed, uint256 usdValue)"),
  fromBlock: "latest",
})

for (const log of logs) console.log(log.args) // { absorber, borrower, asset, collateralAbsorbed, usdValue }
ethers v6
import { Interface, JsonRpcProvider } from "ethers"

const provider = new JsonRpcProvider(process.env.RPC_URL)
const iface = new Interface(["event AbsorbCollateral(address indexed absorber, address indexed borrower, address indexed asset, uint256 collateralAbsorbed, uint256 usdValue)"])

const logs = await provider.getLogs({
  address: "0xc3d688b66703497daa19211eedff47f25384cdc3",
  topics: [iface.getEvent("AbsorbCollateral")!.topicHash],
})

for (const log of logs) console.log(iface.parseLog(log)?.args)
JSON-RPC (eth_getLogs)
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getLogs",
  "params": [
    {
      "address": "0xc3d688b66703497daa19211eedff47f25384cdc3",
      "topics": [
        "0x9850ab1af75177e4a9201c65a2cf7976d5d28e40ef63494b44366f86b2f9412e"
      ],
      "fromBlock": "latest"
    }
  ]
}
Solidity
event AbsorbCollateral(address indexed absorber, address indexed borrower, address indexed asset, uint256 collateralAbsorbed, uint256 usdValue);

// inside a function:
emit AbsorbCollateral(absorber, borrower, asset, collateralAbsorbed, usdValue);
Example

An example AbsorbCollateral log, encoded and decoded

Placeholder values, not a real transaction: how each argument is stored in the topics and the data, and what decoding gives back.

Encoded (as the node returns it)
  • topic0keccak256("AbsorbCollateral(address,address,address,uint256,uint256)")0x9850ab1af75177e4a9201c65a2cf7976d5d28e40ef63494b44366f86b2f9412e
  • topic1absorber0x0000000000000000000000001111111111111111111111111111111111111111
  • topic2borrower0x0000000000000000000000002222222222222222222222222222222222222222
  • topic3asset0x0000000000000000000000003333333333333333333333333333333333333333
  • data0x0000000000000000000000000000000000000000000000000000000000000fa00000000000000000000000000000000000000000000000000000000000001388
Decoded with the ABI
  • absorberaddress · indexed0x1111111111111111111111111111111111111111
  • borroweraddress · indexed0x2222222222222222222222222222222222222222
  • assetaddress · indexed0x3333333333333333333333333333333333333333
  • collateralAbsorbeduint2564000
  • usdValueuint2565000
FAQ

Frequently asked questions

What is the topic0 of the AbsorbCollateral (Compound V3) event?

0x9850ab1af75177e4a9201c65a2cf7976d5d28e40ef63494b44366f86b2f9412e: the keccak-256 hash of AbsorbCollateral(address,address,address,uint256,uint256).

Which AbsorbCollateral (Compound V3) arguments are indexed?

absorber, borrower, asset are indexed and sit in the log's topics; collateralAbsorbed, usdValue are in the data.

How do I get an alert when a contract emits AbsorbCollateral (Compound V3)?

Open one of the ready-made rules on this page, or add any contract and pick AbsorbCollateral (Compound V3) from the event list. Conditions can be set on indexed and non-indexed arguments, and each alert names the contract and links to the transaction.

Keep exploring

More event signatures and tools

Know the moment a contract emits it

The Beta plan is free: one wallet and one contract, no credit card.