Transfers

Once the core wallet module is in place, we've taken a Web 2 friendly approach to the Wallaby platform. We've unified transaction construction, signing, and broadcasting into a single cross chain, standardized API call. With seed phrase decryption and transport flows setup, it is as easy to execute blockchain transfers as any other Web 2 flow.

Use Case Examples

Our transfer function/API calls can be used across a variety of use cases. You can allow the parameters to be user inputs to offer a standard peer to peer transfer capability to wallet holders. Depending on your required encryption factors, this could be as simple as a button click if you have a valid session, but most commonly will require a password/pin.

{image of a standard transfer flow}

You can also use this same transfer capability in a variety of custom flows such as payments or trading.

{wires of these flows}

How to transfer funds to another wallet

SDK

With our SDK, you can simply use the transfer function as described in Transfers with the SDK to execute a transfer. Before doing so you should confirm that the encrypted seed is available in the expected storage location. If the keys are as expected, then the SDK will take care of auth, decryption, encryption/transport, and calling the transfer API for you.

APIs

Although the SDK, wraps up the complexity described below into streamlined functions, the SDK may not be the right fit depending on your use case. If that's the case, you can still utilize the APIs to transfer funds from one wallet to the other.

Flow of Operations

1. Preliminary Actions

Before you attempt to execute a transfer, we recommend that you avoid error scenarios by checking...

1. that the encrypted seed is in the expected storage location

2. that the wallet holder has enough balance to send the desired amount (using our balance API)

3. that the wallet holder has enough balance to pay fees (using our balance API)

4. that wallet holder is informed about the fee (using our fee API)

2. Wallaby Authentication

Wallaby requires both an API key and an access token in order to utilize our APIs. With both those requirements, we are able to authenticate your system to utilize the Wallaby APIs. However, we still need to authenticate the user themselves. Wallaby's authentication system for end users utilizes SRP protocol. Read more about it in . For more implementation information, go to .

3. Seed Phrase Decryption

When authentication is complete, you will need to fetch the encrypted seed phrase from the designated storage location. In order to display the seed phrase to the wallet holder for storage, you will need to decrypt it using the client auth private key. Read more about this in

4. Seed Phrase Encryption/Transport

To keep the the user's seed phrase secure, you will need to encrypt it first. In order to do this, you should utilize the Wallaby auth public key you retrieved in the authentication process. Read more about this in . After the seed phrase is encrypted, you can send it to wallaby as part of the transfer.

5. Transfer

To transfer funds from one wallet to the other, you will simply need to call the transfer API assuming all preliminary criteria are met and the seed phrase is ready for transport. All information about transfer related APIs including the balance and fee checks can be found in Transfer API.