Read every line. Adjust anything you want.

Migrating from JavaScript

If you're filtering with JavaScript and want to migrate to Go for faster filtering, use the "Migrate to a Go filter" option. AI converts your current logic to Go automatically.

Review the generated code, confirm the logic and return values match your JavaScript filter, then publish.

शुरू करना

1. Open the Streams filter editor and select Go as the filter language.

2. Describe the filter you want, or migrate an existing one.

3. Review the output and publish.

The docs at quicknode.com/docs/streams/filters now carry tabbed Go and JavaScript examples.

Streams already running in production

pay3 replaced wallet addresses with a single shareable link for stablecoin payments. Streams watches 7,000+ registered addresses across Ethereum, BNB Smart Chain, Solana, and Tron, and fires a webhook roughly two seconds after a payment confirms onchain. One pipeline, four chains, no separate tooling per chain.
Read the pay3 case study

Defimon monitors EVM chains for exploits and alerts protocol teams the moment one lands. Filtering by address, contract, and event type before data reaches their pipeline, with watchlists in Key-Value Store lists instead of in memory, took block-to-detection latency from 2 seconds on their previous polling setup to under 0.5 seconds. They went from 3 chains to 8, from 3-4 engineers to 1, and cut infrastructure costs by $48,000 a year.

Read the Defimon case study

Both are address and event-list workloads, the same shape as the 'wallets' example above. The AI Filter Agent writes that first draft for you now, and Go runs it 30% faster.