Realtime Pub/Sub Events

Transaction confirmations are published to NSQ and streamed to clients over WebSocket. No polling architecture required on your end.

Move downstream systems from polling to event-driven operations.

Pub/Sub and webhook delivery give the platform an operational nervous system. Teams can react to uploads, confirmations, and lifecycle changes as they happen.

Value

Shorten time from storage event to business action

Event-driven workflows remove the lag and waste of periodic polling across multiple services.

Make integrations observable

Signed delivery, retries, and operational status give teams a controlled way to trust outbound events.

Create a stronger platform story

Customers are buying a workflow surface, not only a permanent file endpoint.

Use cases

Progress UIs

Show users a real-time confirmation progress bar (1/15 → 15/15) without polling. WebSocket stream drives the UI directly.

Pipeline Triggers

Subscribe backend services to confirmation events. Trigger downstream processing (indexing, notification, billing) only after on-chain confirmation.

Audit Logging

Stream every state transition to an immutable event log. Every NSQ event is time-stamped and correlated to the originating TX ID.

For operators

• Emit core runtime events around uploads, downloads, confirmations, and administrative changes.
• Route the same event envelope to webhooks, connectors, or internal consumers depending on the integration style.
• Use metrics and billing to see which event-driven flows are actually carrying operational weight.

For buyers

• Useful for customers that need ERP sync, customer notifications, or compliance alerts.
• Helps platform teams show how Evercore fits into existing process automation instead of sitting beside it.
• Supports enterprise discussions around operational readiness and integration maturity.

Do I have to use WebSocket? Can I use polling instead?

You can use either. WebSocket is recommended for low-latency UIs. For backend workflows, webhook delivery is available — Evercore will POST confirmation events to your endpoint when the transaction status changes.

What is NSQ?

NSQ is a distributed, decentralised real-time messaging platform. Evercore uses NSQ as the internal message bus to decouple transaction state changes from the API response cycle.

What events does the WebSocket stream?

The stream emits: pending (transaction submitted), bundled (included in Bundlr bundle), confirmed (N/15+ Arweave confirmations), and failed (submission error with retry metadata).