Five Chains. One Integration. Under 3 Seconds.
How KOSH covers five chains on one Webhook integration instead of adding a second provider for Solana.
- 110K+ wallet addresses monitored
- < 5 days from decision to production
- Under 3 seconds from onchain confirmation to available balance
KOSH is a mobile-first financial account for freelancers, professionals, and businesses in Asia: USD accounts, a global Visa card, and cross-border payouts settled in USDC and USDT. Users receive USD and EUR payments from clients in 90+ countries. Every account gets a smart contract wallet at creation. Safe on EVM chains, Squads on Solana. KOSH registers each one with Quicknode Webhooks automatically, one address per user per chain. That comes to 110K+ addresses across five chains, carrying about 4K onchain events a month.
挑戰
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.
"One provider, five chains, one integration. That's what let us stop treating chain coverage as an operational problem."Tarun Mangukiya, Founder,KOSH