SDA Creation Rate Limits — What You Need to Know

Default Rate Limits

Total SDA Limits by Plan

In addition to the hourly creation rate limit, each pricing plan includes a total SDA allowance:

The total limit counts SDAs created across all chains. Keep in mind that a single user can consume multiple SDAs from your allowance if you generate addresses on several chains for them — for example, generating on 7 chains for one user consumes 7 SDAs.

If your expected usage exceeds your plan's allowance, speak to your Rhino.fi account manager about the right plan for your volume.

Multi-Chain Rate Limit Consumption

When you create an SDA on multiple chains in a single request (e.g., 7 EVM chains), each chain counts as a separate creation against the hourly rate limit. A single request for 7 chains consumes 7 of the 3,000 hourly allowance.

Note: Using reusePolicy: 'reuse-existing' to extend an existing SDA to additional chains does not count against the rate limit.

Generate SDAs Efficiently

Every SDA you create is actively monitored by Rhino.fi's infrastructure for incoming deposits — including SDAs that are never used. Efficient generation keeps you well within your limits and ensures the fastest deposit detection.

Best practices:

• Generate on demand, not by default. Create an SDA only when a user actively requests a deposit address (e.g., when they open the deposit screen) — not automatically for every new sign-up. Pre-generating SDAs for users who never deposit consumes your allowance without any benefit.

• Only generate on the chains you need. If a user is depositing from one chain, there's no need to generate their SDA across all supported chains up front. You can extend an existing SDA to additional chains later using reusePolicy: 'reuse-existing' without consuming additional rate limit.

• Avoid bulk pre-generation. Generating a large number of SDAs in a very short window causes a delay in Rhino.fi's monitoring setup for newly created addresses, meaning deposit detection on those addresses may be temporarily slower.

See also: What are best practices when operating SDAs?

Solana-Specific Constraints

Solana has more restrictive SDA creation limitations compared to EVM chains. If you are planning to launch with Solana support from day one, inform your Rhino.fi account manager in advance so the appropriate limits can be pre-configured.

Requesting Limit Changes

Both the hourly creation rate limit and your plan's total SDA allowance are adjustable based on your commercial agreement and expected volume. To request a change, contact your Rhino.fi account manager with:

• Your expected peak SDA generation volume

• Your expected total number of active users requiring deposit addresses

• Whether you plan to include Solana

• Your planned go-live timeline

Testing Environment

There is no public testnet for SDA flows. The recommended approach for integration testing is to:

1. Create a dedicated project in the developer portal (https://developers.rhino.fi)

2. Use small live amounts for end-to-end testing

3. Switch to production API keys when ready for launch

This gives the most representative integration experience, as testnet conditions (higher latency, custom tokens) are not equivalent to production.