Why we built SwyDex

Most of us have built the same things at least twice: HD wallet generation, chain-specific deposit address rotation, sweep workers, gas top-ups, webhook signing, idempotent withdrawal jobs. Each one is a week of work, and a year later you find subtle bugs you didn't have time to fix the first time.

SwyDex is a bet that this set of primitives is finally a commodity. We want a platform team to add custodial wallets to their product the same way they add Stripe — clone an SDK, paste an API key, and ship.

What that means concretely on day one:

• One API for wallets across 12 chains, with the EVM family sharing a master so we don't spam-create derivation paths.
• Sweep + gas-station built in. We refill from a tenant gas vault automatically when a chain goes below threshold.
• Webhooks signed with a per-webhook HMAC and retried with exponential backoff. Auto-disabled after sustained failure with an email to the account owner.
• KMS-wrapped per-tenant DEKs. The runtime can decrypt; nobody can encrypt new keys without going through us.

What it doesn't mean: SwyDex is the bank. We're the infrastructure under your bank. Treat balances accordingly.

We'll write here every week or so as we ship. The first few posts will be architecture deep-dives; we'll mix in operational stuff and post-mortems as they happen.