RemovedBlackList (USDT) event signature and topic0
The topic0 of the RemovedBlackList (USDT) event is 0xd7e9ec6e6ecd65492dce6bf513cd6867560d49544421d0783ddf06e76c24470c, the keccak-256 hash of RemovedBlackList(address); none of its arguments are indexed. Address unfrozen by the token issuer (Tether).
Topics
- topic00xd7e9ec6e6ecd65492dce6bf513cd6867560d49544421d0783ddf06e76c24470ckeccak256("RemovedBlackList(address)")
Data
- data_user (address)ABI-encoded, decoded with the ABI
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 |
|---|---|---|
| _user | address | data |
Solidity declaration
event RemovedBlackList(address _user);
Canonical signature
RemovedBlackList(address)
topic0
0xd7e9ec6e6ecd65492dce6bf513cd6867560d49544421d0783ddf06e76c24470c
Get an alert on RemovedBlackList
Each rule opens with the contract and the conditions filled in. Sign in, pick your chat and click Create.
Contracts we list that emit RemovedBlackList
Any other contract with the same signature emits a log with the same topic0.
Read RemovedBlackList logs in code
The same filter in viem, ethers and plain JSON-RPC, and the Solidity that emits it. The address is Tether (USDT), a contract we list that emits it.
import { createPublicClient, http, parseAbiItem } from "viem"
import { mainnet } from "viem/chains"
const client = createPublicClient({ chain: mainnet, transport: http() })
const logs = await client.getLogs({
address: "0xdac17f958d2ee523a2206206994597c13d831ec7",
event: parseAbiItem("event RemovedBlackList(address _user)"),
fromBlock: "latest",
})
for (const log of logs) console.log(log.args) // { _user }import { Interface, JsonRpcProvider } from "ethers"
const provider = new JsonRpcProvider(process.env.RPC_URL)
const iface = new Interface(["event RemovedBlackList(address _user)"])
const logs = await provider.getLogs({
address: "0xdac17f958d2ee523a2206206994597c13d831ec7",
topics: [iface.getEvent("RemovedBlackList")!.topicHash],
})
for (const log of logs) console.log(iface.parseLog(log)?.args){
"jsonrpc": "2.0",
"id": 1,
"method": "eth_getLogs",
"params": [
{
"address": "0xdac17f958d2ee523a2206206994597c13d831ec7",
"topics": [
"0xd7e9ec6e6ecd65492dce6bf513cd6867560d49544421d0783ddf06e76c24470c"
],
"fromBlock": "latest"
}
]
}event RemovedBlackList(address _user);
// inside a function:
emit RemovedBlackList(_user);An example RemovedBlackList 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.
- topic0keccak256("RemovedBlackList(address)")0xd7e9ec6e6ecd65492dce6bf513cd6867560d49544421d0783ddf06e76c24470c
- data0x0000000000000000000000001111111111111111111111111111111111111111
- _useraddress0x1111111111111111111111111111111111111111
Frequently asked questions
What is the topic0 of the RemovedBlackList (USDT) event?
0xd7e9ec6e6ecd65492dce6bf513cd6867560d49544421d0783ddf06e76c24470c: the keccak-256 hash of RemovedBlackList(address).
Which RemovedBlackList (USDT) arguments are indexed?
None: _user is ABI-encoded in the log's data, so a log can only be filtered by address and topic0.
How do I get an alert when a contract emits RemovedBlackList (USDT)?
Open one of the ready-made rules on this page, or add any contract and pick RemovedBlackList (USDT) from the event list. Conditions can be set on its arguments, and each alert names the contract and links to the transaction.
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.