How does SDA deposit monitoring and detection speed work?

Last updated: May 19, 2026

Overview

Rhino.fi continuously monitors all active Smart Deposit Addresses for incoming deposits. Detection speed depends on the chain and how recently the SDA was created or last used.

Detection Speed by Chain

Most EVM Chains

On most EVM chains, SDAs are monitored continuously with no speed penalty based on usage patterns. Once a deposit is detected, the bridge process begins within seconds. There is no change in monitoring speed after periods of inactivity.

Tron (Special Case)

Tron SDAs are monitored at a higher frequency during the first 14 days after creation or after the last deposit:

  • Within 14 days of creation or last use: Near-real-time monitoring (sub-second to a few seconds detection).

  • After 14 days of no activity: Monitoring frequency drops to approximately every 10 minutes, meaning the average detection delay is ~5 minutes.

Important: This is a tradeoff Rhino.fi makes between processing speed and resource efficiency. The 10-minute interval is the current default and is unlikely to become slower in future. Rhino.fi may improve this speed over time.

Once a deposit is detected on a Tron SDA in reduced-frequency mode, the monitoring reverts to live frequency for the following two weeks.

After Detection

On all chains, once a deposit is detected:

  • The address is immediately placed back into live monitoring.

  • The bridge processing begins — withdrawal on the destination chain typically completes within seconds for standard-speed transactions.

Total End-to-End Time

For a complete picture of the end-to-end bridge duration:

Detection time + Bridge processing time = Total time

  • Detection time: near-instant (most chains) or up to ~10 min (Tron, inactive SDA)

  • Bridge processing: < 10 seconds for most transactions with sufficient liquidity

  • The estimatedDuration field in the quote response (in milliseconds) covers the bridge processing step only — add the detection time on top for Tron.

Best Practice: Generate SDAs at the Point of Use

Because Tron monitoring speed depends on recency of creation or last use, do not pre-generate SDAs in bulk or during user onboarding. Generate SDAs only when the user actually wants to initiate a deposit. This ensures the SDA is in its fastest monitoring state for the first use.

No API-Based Reactivation (Tron)

There is no API endpoint to reset or restore the fast monitoring frequency for a Tron SDA that has gone into reduced-frequency mode. The only way to return to fast monitoring is for a new deposit to be received. The deprecated "Reactivate deposit address" endpoint has been discontinued as SDAs now remain active for 10 years by default.