Five Chains. One Integration. Under 3 Seconds.

KOSH needed webhook coverage on five chains: Solana, Ethereum, Base, Arbitrum One, and OP Mainnet. Solana at the same tier as the EVM chains, not in beta.

Their existing setup could not do it on one integration. Either pay for a second provider just to cover Solana, or ship without the chain.

Quicknode Webhooks monitors every KOSH wallet across all five chains, listening for USDC and USDT transfers plus the native asset on each chain.

A payment confirms onchain. Quicknode fires the webhook. KOSH verifies the signature, credits the balance, and pushes a notification. KOSH writes event identifiers to Quicknode Key-Value Store and checks them first, so a redelivered event never credits a balance twice.

For a user receiving USDC on Solana, the clock starts at onchain confirmation. Under 3 seconds later the phone buzzes and the balance is already in the app.

Migration took under 5 days from decision to production. The API surface was close to what the team already had, so most of the work was moving addresses across and running both providers in parallel long enough to compare. The Quicknode team answered every question as it came in. Nothing tripped the migration up.

Quicknode covers all five chains at the same tier. Solana included, on the same integration as the EVM chains rather than alongside it.

110K+ addresses run through that one integration. One point of contact, one dashboard, one bill, and no second provider to keep in sync when something changes.

Webhook spend moved from pay-as-you-go to a fixed monthly fee, so KOSH sets the number before the month starts instead of reconciling it after. Adding a sixth chain is a config change on the same integration, not a second procurement cycle.

Five chains, one integration, and a fixed number on the invoice.

"Every one of those depends on webhook infrastructure we don't have to think about." Tarun Mangukiya, Founder, KOSH