Event signature · Lending

SupplyCollateral (Compound V3) event signature and topic0

The topic0 of the SupplyCollateral (Compound V3) event is 0xfa56f7b24f17183d81894d3ac2ee654e3c26388d17a28dbd9549b8114304e1f4, the keccak-256 hash of SupplyCollateral(address,address,address,uint256); 3 of its 4 arguments are indexed. Collateral supplied to a Compound V3 (Comet) market.

Anatomy of a SupplyCollateral (Compound V3) log

Topics

  • topic00xfa56f7b24f17183d81894d3ac2ee654e3c26388d17a28dbd9549b8114304e1f4keccak256("SupplyCollateral(address,address,address,uint256)")
  • topic1from (address)indexed: filterable
  • topic2dst (address)indexed: filterable
  • topic3asset (address)indexed: filterable

Data

  • dataamount (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
fromaddresstopic1
dstaddresstopic2
assetaddresstopic3
amountuint256data

Solidity declaration

event SupplyCollateral(address indexed from, address indexed dst, address indexed asset, uint256 amount);

Canonical signature

SupplyCollateral(address,address,address,uint256)

topic0

0xfa56f7b24f17183d81894d3ac2ee654e3c26388d17a28dbd9549b8114304e1f4

Ready-made alerts

Get an alert on SupplyCollateral

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 SupplyCollateral

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

Code

Read SupplyCollateral 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 SupplyCollateral(address indexed from, address indexed dst, address indexed asset, uint256 amount)"),
  fromBlock: "latest",
})

for (const log of logs) console.log(log.args) // { from, dst, asset, amount }
ethers v6
import { Interface, JsonRpcProvider } from "ethers"

const provider = new JsonRpcProvider(process.env.RPC_URL)
const iface = new Interface(["event SupplyCollateral(address indexed from, address indexed dst, address indexed asset, uint256 amount)"])

const logs = await provider.getLogs({
  address: "0xc3d688b66703497daa19211eedff47f25384cdc3",
  topics: [iface.getEvent("SupplyCollateral")!.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": [
        "0xfa56f7b24f17183d81894d3ac2ee654e3c26388d17a28dbd9549b8114304e1f4"
      ],
      "fromBlock": "latest"
    }
  ]
}
Solidity
event SupplyCollateral(address indexed from, address indexed dst, address indexed asset, uint256 amount);

// inside a function:
emit SupplyCollateral(from, dst, asset, amount);
Example

An example SupplyCollateral 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("SupplyCollateral(address,address,address,uint256)")0xfa56f7b24f17183d81894d3ac2ee654e3c26388d17a28dbd9549b8114304e1f4
  • topic1from0x0000000000000000000000001111111111111111111111111111111111111111
  • topic2dst0x0000000000000000000000002222222222222222222222222222222222222222
  • topic3asset0x0000000000000000000000003333333333333333333333333333333333333333
  • data0x0000000000000000000000000000000000000000000000000000000000000fa0
Decoded with the ABI
  • fromaddress · indexed0x1111111111111111111111111111111111111111
  • dstaddress · indexed0x2222222222222222222222222222222222222222
  • assetaddress · indexed0x3333333333333333333333333333333333333333
  • amountuint2564000
FAQ

Frequently asked questions

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

0xfa56f7b24f17183d81894d3ac2ee654e3c26388d17a28dbd9549b8114304e1f4: the keccak-256 hash of SupplyCollateral(address,address,address,uint256).

Which SupplyCollateral (Compound V3) arguments are indexed?

from, dst, asset are indexed and sit in the log's topics; amount is in the data.

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

Open one of the ready-made rules on this page, or add any contract and pick SupplyCollateral (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.