Skip to content

EVM log trigger requires both address and event signature [TS] #3413

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
khadni merged 1 commit into from
Jan 29, 2026
Merged

EVM log trigger requires both address and event signature [TS] #3413

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions src/content/cre/llms-full-ts.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15186,7 +15186,7 @@ export async function main() {

# SDK Reference: EVM Log Trigger
Source: https://docs.chain.link/cre/reference/sdk/triggers/evm-log-trigger-ts
Last Updated: 2026-01-26
Last Updated: 2026-01-28

The EVM Log Trigger fires when a specific log (event) is emitted by an onchain smart contract.

Expand All @@ -15212,12 +15212,7 @@ const network = getNetwork({

const evmClient = new EVMClient(network.chainSelector.selector)

// Basic log trigger for a contract address
const trigger = evmClient.logTrigger({
addresses: [hexToBase64("0x123...abc")],
})

// With topics for event filtering
// Create a log trigger with address and event signature
const transferEventHash = keccak256(toBytes("Transfer(address,address,uint256)"))

const trigger = evmClient.logTrigger({
Expand All @@ -15237,7 +15232,7 @@ The `logTrigger()` method accepts a configuration object with the following fiel
| Field | Type | Description |
| ------------ | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `addresses` | `string[]` | **Required.** A list of contract addresses to monitor. **Must be base64 encoded** using `hexToBase64()`. At least one address is required. |
| `topics` | `TopicValues[]` | Optional. An array to filter event topics. The first element contains event signatures, and the next three elements contain indexed argument values. An empty array element acts as a wildcard. **All topic values must be base64 encoded** using `hexToBase64()`. |
| `topics` | `TopicValues[]` | **Required.** An array to filter event topics. The first element must contain at least one event signature. The next three elements can contain indexed argument values (optional). An empty array element acts as a wildcard for indexed arguments. **All topic values must be base64 encoded** using `hexToBase64()`. |
| `confidence` | `string` | Optional. The block confirmation level to monitor. Can be: <ul><li>**`"CONFIDENCE_LEVEL_LATEST"`**: The most recent block (fastest but least secure).</li><li>**`"CONFIDENCE_LEVEL_SAFE"` (default)**: A block unlikely to be reorged but not yet irreversible.</li><li>**`"CONFIDENCE_LEVEL_FINALIZED"`**: A block considered irreversible (safest, but requires waiting longer for finality).</li></ul> |

<Aside type="note" title="Finality details">
Expand Down
11 changes: 3 additions & 8 deletions src/content/cre/reference/sdk/triggers/evm-log-trigger-ts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ pageId: "reference-sdk-evm-log-trigger"
metadata:
description: "Reference for TypeScript EVM Log Trigger: Config interface, Payload fields, and topic filtering for event-driven workflows."
datePublished: "2025-11-04"
lastModified: "2026-01-26"
lastModified: "2026-01-28"
---

import { Aside } from "@components"
Expand Down Expand Up @@ -36,12 +36,7 @@ const network = getNetwork({

const evmClient = new EVMClient(network.chainSelector.selector)

// Basic log trigger for a contract address
const trigger = evmClient.logTrigger({
addresses: [hexToBase64("0x123...abc")],
})

// With topics for event filtering
// Create a log trigger with address and event signature
const transferEventHash = keccak256(toBytes("Transfer(address,address,uint256)"))

const trigger = evmClient.logTrigger({
Expand All @@ -61,7 +56,7 @@ The `logTrigger()` method accepts a configuration object with the following fiel
| <div style="width: 100px;">Field</div> | <div style="width: 140px;">Type</div> | Description |
| -------------------------------------- | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `addresses` | `string[]` | **Required.** A list of contract addresses to monitor. **Must be base64 encoded** using `hexToBase64()`. At least one address is required. |
| `topics` | `TopicValues[]` | Optional. An array to filter event topics. The first element contains event signatures, and the next three elements contain indexed argument values. An empty array element acts as a wildcard. **All topic values must be base64 encoded** using `hexToBase64()`. |
| `topics` | `TopicValues[]` | **Required.** An array to filter event topics. The first element must contain at least one event signature. The next three elements can contain indexed argument values (optional). An empty array element acts as a wildcard for indexed arguments. **All topic values must be base64 encoded** using `hexToBase64()`. |
| `confidence` | `string` | Optional. The block confirmation level to monitor. Can be: <ul><li>**`"CONFIDENCE_LEVEL_LATEST"`**: The most recent block (fastest but least secure).</li><li>**`"CONFIDENCE_LEVEL_SAFE"` (default)**: A block unlikely to be reorged but not yet irreversible.</li><li>**`"CONFIDENCE_LEVEL_FINALIZED"`**: A block considered irreversible (safest, but requires waiting longer for finality).</li></ul> |

<Aside type="note" title="Finality details">
Expand Down
Loading