Testing Your SDA Integration Without a Public Testnet

Last updated: May 19, 2026

Why There Is No Public SDA Testnet

Rhino.fi uses testnets internally during development, but does not expose them to clients for the following reasons:

  • Higher latency: Testnet conditions do not reflect production performance and would give misleading benchmarks.

  • Custom tokens: Many testnet tokens are not publicly acquirable without coordination with Rhino.fi.

  • Non-representative environment: Testnet results are not indicative of what clients or their users will experience in production.

Recommended Approach: Developer Accounts with Live Amounts

The recommended approach is to create one or more dedicated developer projects in the Rhino.fi developer console (https://developers.rhino.fi) and conduct integration testing using small live amounts.

Steps:

  1. Create a developer account with your company email.

  2. Create a project and share the Project ID with your Rhino.fi account manager.

  3. Rhino.fi will configure your project for testing (e.g., 500 SDA creation allowance, test-appropriate limits).

  4. Use a separate project for your beta/development environment and another for production.

  5. When you go live, switch your integration to use the production project's API keys.

This approach gives you the most accurate and representative test results.

What to Test

During integration testing, validate:

  • ✅ SDA creation on all target chains

  • ✅ Webhook delivery for BRIDGE_ACCEPTED and BRIDGE_EXECUTED

  • ✅ Deposit detection timing (send a small amount and measure time to webhook)

  • ✅ DEPOSIT_ADDRESS_BRIDGE_REJECTED behaviour (test with amount below minimum)

  • ✅ Reconciliation using /history-cursor/user with _tag: "depositAddressBridge"

  • ✅ Quote endpoint (/quote/bridge-swap/user?isSda=true) response parsing

  • ✅ Webhook IP allowlisting (if your dev environment is behind a firewall — allowlist 34.78.119.255)

Identifying SDA Records in Transaction History

When querying /history-cursor/user, SDA bridge records are identified by _tag: "depositAddressBridge". Standard bridge and bridgeSwap records use different tag values and should be handled separately in your reconciliation logic.

Multiple Developer Projects

You can create multiple developer projects (e.g., one for development, one for staging, one for production). Each project has its own API key and Project ID. Rhino.fi can configure each project independently with appropriate limits.