Generate a new smart deposit address
Please use the identical endpoint under https://api.rhino.fi/sda. The sda endpoints here exist only for backwards compatibility and will be removed in the future. If you use the SDK, please upgrade to the latest version which uses the correct endpoint.
Authorizations
JWT token for authentication
Body
An array of blockchain names where deposit addresses should be created, e.g. ["ETHEREUM", "AVALANCHE"].
1a non empty string
1The blockchain that the tokenOut will be bridged to, e.g. "AVALANCHE".
1The address where tokenOut will be bridged to, e.g. "0x123...ABC".
1The ability to add a note or label for the deposit address as a reference, e.g. "clientID12345678".
80Whether the Smart Deposit Address generated should be a re-use of an existing one which matches the given parameters or a new Smart Deposit Address. "create-new" will generate a new Smart Deposit Address and "reuse-existing" will provide an already generated Smart Deposit Address. If omitted, an existing matching Smart Deposit Address is reused where one is available, otherwise a new one is created.
create-new, reuse-existing A URL that success or failure events related to this bridging transaction should be sent to, e.g. "https://client.com/rhino-webhook". If a webhook address has been set via the Rhino.fi Console then an entry here will override that.
1An address that funds should be returned to in the event that the transaction is unsuccessfully executed. However we recommend that this is not set and is managed on a case by case basis with your Rhino.fi Account Manager, to avoid situations whereby funds are returned to pooled addresses on an exchange or into an address that the user no longer has control over.
1Custom Routing Rules as configured by Rhino.fi for specific clients, e.g. to move funds after the initial bridge into a yield bearing vault. To understand more about how Routing Rules can help automate onchain actions and ensure that your funds land in an active state, please contact your Rhino.fi Customer Success Manager or speak to a member of the Rhino.fi sales team.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
The token that is to be received on the destinationChain, e.g. "USDT".
1If true, deposited tokens that cannot be swapped to the tokenOut will be bridged instead of causing a failed transaction. If false, any deposited tokens that cannot be swapped to the tokenOut will cause the transaction to fail. Must be used in conjunction with the tokenOut parameter, e.g. "true".
Response
Success
The blockchain that the Smart Deposit Address is on and that deposits should be sent to, e.g. "ETHEREUM".
1The Rhino.fi Smart Deposit Address that the deposit has been sent to.
1The blockchain that the received tokens will be bridged to.
1The assets that can be deposited to the depositAddress for this depositChain.
Whether the Smart Deposit Address is being actively monitored for incoming deposits of supportedTokens (true), in which case it will take the necessary bridge / bridge and swap actions, or is not currently being monitored or actioned by Rhino.fi (false). All Smart Deposit Addresses are set to isActive = true when generated and will be monitored and actioned for 10 years, however Smart Deposit Addresses can be disabled via request.
Whether this deposit address is currently paused. Paused addresses reject incoming deposits until they are unpaused.
The blockchain address that the received tokens will be bridged / bridged and swapped to.
1A note or label for the deposit address as a reference.
80Custom Routing Rules as configured by Rhino.fi for specific clients, e.g. to move funds after the initial bridge into a yield bearing vault. To understand more about how Routing Rules can help automate onchain actions and ensure that your funds land in an active state, please contact your Rhino.fi Customer Success Manager or speak to a member of the Rhino.fi sales team.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
The token that will be received on the destinationChain.
The address that any funds would be returned to in the case that a transaction to this Smart Deposit Address is unsuccessful.
1If true, deposited tokens that cannot be swapped to the tokenOut will be bridged instead of causing a failed transaction. If false, any deposited tokens that cannot be swapped to the tokenOut will cause the transaction to fail. Must be used in conjunction with the tokenOut parameter.
Optional chain-specific metadata. Currently only populated for Stellar SDAs, where it exposes the base address and memo id that the muxed deposit address resolves to.