Event signature · NFT sales, names and staking

Submitted (Lido) event signature and topic0

The topic0 of the Submitted (Lido) event is 0x96a25c8ce0baabc1fdefd93e9ed25d8e092a3332f3aa9a41722b5697231d1d1a, the keccak-256 hash of Submitted(address,uint256,address); 1 of its 3 arguments is indexed. ETH staked with Lido for stETH.

Anatomy of a Submitted (Lido) log

Topics

topic00x96a25c8ce0baabc1fdefd93e9ed25d8e092a3332f3aa9a41722b5697231d1d1akeccak256("Submitted(address,uint256,address)")
topic1sender (address)indexed: filterable

Data

dataamount (uint256), referral (address)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
sender	address	topic1
amount	uint256	data
referral	address	data

Solidity declaration

event Submitted(address indexed sender, uint256 amount, address referral);

Canonical signature

Submitted(address,uint256,address)

topic0

0x96a25c8ce0baabc1fdefd93e9ed25d8e092a3332f3aa9a41722b5697231d1d1a

Ready-made alerts

Get an alert on Submitted

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

Ready-made rule · Lido Staked Ether (stETH)Lido large stakes

Ready-made rule · Lido Staked Ether (stETH)Alert on every Submitted

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

Who emits it

Contracts we list that emit Submitted

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

Lido Staked Ether (stETH)

0xae7ab96520de3a18e5e111b5eaab095312d7fe84

Tracker: Lido stETH alerts

Code

Read Submitted logs in code

The same filter in viem, ethers and plain JSON-RPC, and the Solidity that emits it. The address is Lido Staked Ether (stETH), 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: "0xae7ab96520de3a18e5e111b5eaab095312d7fe84",
  event: parseAbiItem("event Submitted(address indexed sender, uint256 amount, address referral)"),
  fromBlock: "latest",
})

for (const log of logs) console.log(log.args) // { sender, amount, referral }

ethers v6

import { Interface, JsonRpcProvider } from "ethers"

const provider = new JsonRpcProvider(process.env.RPC_URL)
const iface = new Interface(["event Submitted(address indexed sender, uint256 amount, address referral)"])

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

Solidity

event Submitted(address indexed sender, uint256 amount, address referral);

// inside a function:
emit Submitted(sender, amount, referral);

Example

An example Submitted 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("Submitted(address,uint256,address)")0x96a25c8ce0baabc1fdefd93e9ed25d8e092a3332f3aa9a41722b5697231d1d1a
topic1sender0x0000000000000000000000001111111111111111111111111111111111111111
data0x00000000000000000000000000000000000000000000000000000000000007d00000000000000000000000003333333333333333333333333333333333333333

Decoded with the ABI

senderaddress · indexed0x1111111111111111111111111111111111111111
amountuint2562000
referraladdress0x3333333333333333333333333333333333333333

FAQ

Frequently asked questions

What is the topic0 of the Submitted (Lido) event?

0x96a25c8ce0baabc1fdefd93e9ed25d8e092a3332f3aa9a41722b5697231d1d1a: the keccak-256 hash of Submitted(address,uint256,address).

Which Submitted (Lido) arguments are indexed?

sender is indexed and sit in the log's topics; amount, referral are in the data.

How do I get an alert when a contract emits Submitted (Lido)?

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