build_event_topic
Generates event topic signatures for blockchain events by specifying the event name and argument types, enabling accurate data retrieval and analysis on supported networks.
Instructions
Builds an event topic signature based on event name and arguments
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| arguments | Yes | Event arguments types | |
| name | Yes | Event name (e.g., "Transfer(address,address,uint256)") | |
| network | Yes | The blockchain network (e.g., "ethereum", "base") |
Input Schema (JSON Schema)
{
"$schema": "http://json-schema.org/draft-07/schema#",
"additionalProperties": false,
"properties": {
"arguments": {
"description": "Event arguments types",
"items": {
"additionalProperties": false,
"properties": {
"components": {
"description": "optional components for tuple types",
"items": {
"$ref": "#/properties/arguments/items"
},
"type": "array"
},
"type": {
"description": "Expected output types for the method call. \n In case of a tuple, don't use type tuple, but specify the inner types (found in the source) in order. For nested structs, include the substructs types.\n \n Example: \n struct DataTypeA {\n DataTypeB b;\n //the liquidity index. Expressed in ray\n uint128 liquidityIndex;\n }\n \n struct DataTypeB {\n address token;\n }\n \n results in outputs for function with return type DataTypeA (tuple in abi): outputs: [{\"type\": \"address\"}, {\"type\": \"uint128\"}]\n ",
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
},
"type": "array"
},
"name": {
"description": "Event name (e.g., \"Transfer(address,address,uint256)\")",
"type": "string"
},
"network": {
"description": "The blockchain network (e.g., \"ethereum\", \"base\")",
"type": "string"
}
},
"required": [
"network",
"name",
"arguments"
],
"type": "object"
}