Ir al contenido principal
Volver a las aplicaciones de ejemplo

Wallet Tracking

Monitor a list of wallet addresses on Solana and Ethereum easily with Quicknode Streams. Update the wallet list through a simple UI.

Marco de trabajo o biblioteca de front-end:
React
Idioma:
TypeScript
Herramienta de compilación/servidor de desarrollo:
Next.js
Vista previa de la aplicación de ejemplo

Resumen

This sample app ships a live user activity feed that wires Quicknode Streams + Key-Value Store (KV Store) to monitor addresses, verify webhooks, store events in SQLite via Prisma, and push updates over SSE in real time (EVM + Solana).

Arquitectura

Blockchain (EVM + Solana)
-> Quicknode Streams + KV
-> POST /api/webhook/streams (signature verified)
-> DB insert + SSE emit
-> UI live feed

Características


  • Quicknode Streams setup scripts (create + activate)
  • EVM filter for native transfers and ERC-20 Transfer logs
  • Solana filter for native transfers and SPL token transfers
  • Quicknode KV list backed user monitoring, enabling dynamic user monitoring without redeploying the stream
  • Labeling monitored addresses
  • Bulk add monitored addresses
  • Webhook signature verification and timestamp checks
  • SSE live updates
  • ENS resolution for EVM addresses
  • Prisma + SQLite local storage

Requisitos previos


  • Node.js 20+ and a package manager (pnpm, yarn, npm).
  • Cuenta de Quicknode and API key: Create an account, and get your Admin API key para QN_API_KEY.
  • EVM endpoint for ENS/ERC-20 metadata: Create an Ethereum endpoint and copy the HTTPS URL for QN_EVM_ENDPOINT.
  • Solana RPC endpoint for SPL token metadata: Create a Solana endpoint and copy the HTTPS URL for QN_SOLANA_ENDPOINT.
  • Public webhook URL: Use a tunnel like ngrok or deploy the app so APP_URL is reachable by Quicknode.

Estructura del proyecto

filters/
evm-filter.js # Quicknode Streams filter (EVM)
solana-filter.js # Quicknode Streams filter (Solana)
scripts/
setup-streams.ts # Creates KV lists + stream (paused)
activate-streams.ts # Activates stream by id
src/
app/api/ # API routes (webhooks, users, SSE)
lib/ # Quicknode, webhook, SSE helpers
types/ # Stream payload types
prisma/
schema.prisma # SQLite schema

Environment Variables

Copiar .env.example a .env and fill in:

QN_API_KEY=""                  # Quicknode API key
QN_STREAM_SECURITY_TOKEN_EVM="" # EVM stream security token (from setup)
QN_STREAM_SECURITY_TOKEN_SOL="" # Solana stream security token (from setup)
QN_EVM_ENDPOINT="" # Quicknode EVM endpoint URL
QN_SOLANA_ENDPOINT="" # Solana RPC endpoint URL
DATABASE_URL="file:./dev.db" # SQLite DB
APP_URL="http://localhost:3000" # Public app URL (ngrok for local webhooks)

Notes:

  • QN_STREAM_SECURITY_TOKEN_EVM y QN_STREAM_SECURITY_TOKEN_SOL are returned by setup:streams per chain.
  • APP_URL must be reachable by Quicknode (use ngrok or a deployed URL).

Primeros pasos

1. Install dependencies

npm install
# pnpm install
# yarn install

2. Create your env file

cp .env.example .env

3. Add required variables

Fill in .env (see Requisitos previos). For local webhooks, expose your app with ngrok and copy the HTTPS URL into APP_URL:

ngrok http 3000

4. Create Quicknode Streams + KV lists

npm run setup:streams
# pnpm run setup:streams
# yarn setup:streams

Copy the printed security token into .env (QN_STREAM_SECURITY_TOKEN_EVM o QN_STREAM_SECURITY_TOKEN_SOL). If you want Solana, run the command again with chain=solana-mainnet (see Quicknode Streams Setup for options).

5. Set up the database and start the app

npx prisma migrate dev --name init
# pnpm prisma migrate dev --name init
# yarn prisma migrate dev --name init
npm run dev
# pnpm dev
# yarn dev

6. Activate the stream

npm run activate:streams
# pnpm run activate:streams
# yarn activate:streams

Open http://localhost:3000, add wallet addresses, and you should see live events as streams deliver webhooks.

Base de datos

SQLite is used by default. Prisma schema is in prisma/schema.prisma.

Comandos habituales:

pnpm prisma migrate dev --name init
pnpm prisma studio

Quicknode Streams Setup

Following the Getting Started section is enough. However, if you want to manage Streams settings or KV lists manually, follow these steps.

1. Check the filter

The EVM filter lives in filters/evm-filter.js. It emits:

  • nativeTransfer events (ETH transfers with non-zero value)
  • erc20Transfer events (ERC-20 Transfer logs)

The filter checks addresses against the userstream_monitored_users_evm KV list.

The Solana filter lives in filters/solana-filter.js. It emits:

  • solTransfer events (native SOL transfers)
  • splTransfer events (SPL token transfers)

The filter checks addresses against the userstream_monitored_users_sol KV list.

Adding addresses through UI will update the KV list automatically. However, if you need to manage KV lists manually, you can do so through the Quicknode REST API. Check the Key-Value Store documentation page to learn more.

2. Create stream + KV lists

pnpm run setup:streams

This will:

  • Create the KV list for the selected chain (userstream_monitored_users_evm o userstream_monitored_users_sol)
  • Base64 encode the filter for the chosen chain
  • Test the filter with a test block number (as KV list will be empty at first, no events will be emitted.)
  • Create a stream with:
    • status=paused
    • dataset=block_with_receipts (EVM) or dataset=block (Solana)
    • required webhook attributes (compression, retries, timeouts)
  • Save the stream id to .quicknode/streams.json
  • Print the security_token para .env (QN_STREAM_SECURITY_TOKEN_EVM o QN_STREAM_SECURITY_TOKEN_SOL)
  • Creates a single stream per run (run again with chain=solana-mainnet o chain=ethereum-mainnet to create both).

You can override options using key=value args, for example:

pnpm run setup:streams chain=ethereum-mainnet name="UserStream EVM Monitor" test_block_number=24223192
pnpm run setup:streams chain=solana-mainnet name="UserStream Solana Monitor" test_block_number=393612994

Common options:

  • chain=ethereum-mainnet (alias: network=ethereum-mainnet)
  • dataset=block_with_receipts
  • dataset_batch_size=1
  • status=paused
  • elastic_batch_enabled=true
  • filter_path=filters/evm-filter.js
  • test_block_number=24223192
  • destination_compression=none
  • destination_headers='{"Content-Type":"application/json"}'
  • destination_max_retry=3
  • destination_retry_interval_sec=1
  • destination_post_timeout_sec=10

Webhook Security and Payload


  • Endpoint: POST /api/webhook/streams
  • Headers required: x-qn-nonce, x-qn-timestamp, x-qn-signature
  • Payload can be gzip compressed; the handler auto-detects content-encoding: gzip
  • Signature verification uses QN_STREAM_SECURITY_TOKEN_EVM o QN_STREAM_SECURITY_TOKEN_SOL

Puntos de conexión de la API


  • GET /api/health - health check
  • GET /api/users - list monitored users
  • POST /api/users - add a single user (walletAddress, optional nombre)
  • PATCH /api/users?id=... - update user name/displayName
  • DELETE /api/users?id=... - delete a user
  • POST /api/users/bulk - bulk add users (newline separated)
  • POST /api/webhook/streams - Quicknode Streams webhook
  • POST /api/webhook/test - local-only webhook test
  • GET /api/sse - SSE stream of activity events

Vista previa

Vista previa

Aportaciones y comentarios
¡Nos encantaría conocer tu opinión y agradecemos cualquier aportación a esta aplicación de ejemplo!
Para informar de problemas o enviar comentarios, abre una incidencia en GitHub en el qn-guide-ejemplos repositorio.
Para colaborar, sigue estos pasos:
  1. Hacer un fork del repositorio
  2. Crear una rama de características:
    git checkout -b feature/amazing-feature
  3. Guarda los cambios:
    git commit -m "Añadir una función increíble"
  4. Envía tu rama:
    git push origin feature/amazing-feature
  5. Abre una solicitud de incorporación de cambios.