Event signature · Lending

Supply (Morpho Blue) event signature and topic0

The topic0 of the Supply (Morpho Blue) event is 0xedf8870433c83823eb071d3df1caa8d008f12f6440918c20d75a3602cda30fe0, the keccak-256 hash of Supply(bytes32,address,address,uint256,uint256); 3 of its 5 arguments are indexed. Loan asset supplied to a Morpho Blue market.

Anatomy of a Supply (Morpho Blue) log

Topics

topic00xedf8870433c83823eb071d3df1caa8d008f12f6440918c20d75a3602cda30fe0keccak256("Supply(bytes32,address,address,uint256,uint256)")
topic1id (bytes32)indexed: filterable
topic2caller (address)indexed: filterable
topic3onBehalf (address)indexed: filterable

Data

dataassets (uint256), shares (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.

Name	Type	In the log
id	bytes32	topic1
caller	address	topic2
onBehalf	address	topic3
assets	uint256	data
shares	uint256	data

Solidity declaration

event Supply(bytes32 indexed id, address indexed caller, address indexed onBehalf, uint256 assets, uint256 shares);

Canonical signature

Supply(bytes32,address,address,uint256,uint256)

topic0

0xedf8870433c83823eb071d3df1caa8d008f12f6440918c20d75a3602cda30fe0

Ready-made alerts

Get an alert on Supply

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

Ready-made rule · Morpho BlueAlert on every Supply

Ready-made rule · Any contractAlert on Supply from a contract you pick

Who emits it

Contracts we list that emit Supply

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

Morpho Blue

0xbbbbbbbbbb9cc5e90e3b3af64bdaf62c37eeffcb

Tracker: Morpho Blue alerts

Code

Read Supply logs in code

The same filter in viem, ethers and plain JSON-RPC, and the Solidity that emits it. The address is Morpho Blue, 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: "0xbbbbbbbbbb9cc5e90e3b3af64bdaf62c37eeffcb",
  event: parseAbiItem("event Supply(bytes32 indexed id, address indexed caller, address indexed onBehalf, uint256 assets, uint256 shares)"),
  fromBlock: "latest",
})

for (const log of logs) console.log(log.args) // { id, caller, onBehalf, assets, shares }

ethers v6

import { Interface, JsonRpcProvider } from "ethers"

const provider = new JsonRpcProvider(process.env.RPC_URL)
const iface = new Interface(["event Supply(bytes32 indexed id, address indexed caller, address indexed onBehalf, uint256 assets, uint256 shares)"])

const logs = await provider.getLogs({
  address: "0xbbbbbbbbbb9cc5e90e3b3af64bdaf62c37eeffcb",
  topics: [iface.getEvent("Supply")!.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": "0xbbbbbbbbbb9cc5e90e3b3af64bdaf62c37eeffcb",
      "topics": [
        "0xedf8870433c83823eb071d3df1caa8d008f12f6440918c20d75a3602cda30fe0"
      ],
      "fromBlock": "latest"
    }
  ]
}

Solidity

event Supply(bytes32 indexed id, address indexed caller, address indexed onBehalf, uint256 assets, uint256 shares);

// inside a function:
emit Supply(id, caller, onBehalf, assets, shares);

Example

An example Supply 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("Supply(bytes32,address,address,uint256,uint256)")0xedf8870433c83823eb071d3df1caa8d008f12f6440918c20d75a3602cda30fe0
topic1id0xabababababababababababababababababababababababababababababababab
topic2caller0x0000000000000000000000002222222222222222222222222222222222222222
topic3onBehalf0x0000000000000000000000003333333333333333333333333333333333333333
data0x0000000000000000000000000000000000000000000000000000000000000fa00000000000000000000000000000000000000000000000000000000000001388

Decoded with the ABI

idbytes32 · indexed0xabababababababababababababababababababababababababababababababab
calleraddress · indexed0x2222222222222222222222222222222222222222
onBehalfaddress · indexed0x3333333333333333333333333333333333333333
assetsuint2564000
sharesuint2565000

FAQ

Frequently asked questions

What is the topic0 of the Supply (Morpho Blue) event?

0xedf8870433c83823eb071d3df1caa8d008f12f6440918c20d75a3602cda30fe0: the keccak-256 hash of Supply(bytes32,address,address,uint256,uint256).

Which Supply (Morpho Blue) arguments are indexed?

id, caller, onBehalf are indexed and sit in the log's topics; assets, shares are in the data.

How do I get an alert when a contract emits Supply (Morpho Blue)?

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