Deposit Crypto using FIO Addresses & FIO Requests

FIO Addresses are human-readable wallet identifiers (such as [email protected] or [email protected]) which eliminate the need to see, or even know of, blockchain public addresses. Enabling deposits using FIO Addresses gives exchange users friendly interwallet operability, making deposits easy and near error-free, dramatically reducing support tickets.

As a first step, Exchanges should register a custom FIO Domain (e.g., @myexchange). Exchange users will then be able to register FIO Addresses on that custom domain (e.g., [email protected]).


Using a unique FIO Address for each user

To accept crypto deposits using FIO Addresses, an exchange may register a unique FIO Address for each user of the exchange, and display it in their deposit area, e.g. [email protected]

To deposit tokens of any supported cryptocurrency to their account the user would simply send tokens from a FIO-enabled wallet to their FIO Address (e.g. [email protected]) and would not have to deal with Public Keys, memo fields, or even having to log into the exchange.

Each FIO Address may be mapped using the addaddress action to either the same crypto public address for all users, or a unique crypto public address for each user.


Using the same FIO Address for all users

An exchange may register a single deposit FIO Address for all users of the exchange, and display it their deposit area (e.g. [email protected]).

To deposit any supported token to their account the user would simply send tokens from a FIO-enabled wallet to the Deposit FIO Address, e.g. [email protected] To properly identify the inbound transaction, the user would have to either include a FIO Data memo which includes their exchange account, or provide the exchange, ahead of time, with a list of FIO Addresses which the user owns.

The Deposit FIO Address would be mapped using addaddress to a single FIO Public Key.

The inbound transaction can be identified by reading the OBT Data using /get_obt_data. The data is encrypted. Once decrypted, the memo or FIO Address of Payee can be used to uniquely identify the user, and the obt_id will contain native chain transaction ID of the corresponding deposit.

Transaction memo for FIO token transfer

The trnsfiopubky action does not accept a memo field. To attach a FIO Data memo to a FIO token transfer, a recordobt transaction should be sent after the tokens are transferred and include the token transfer transaction id. recordobt requires that both payer and payee have a FIO Address. If either party does not have a FIO Address then transfer of memo is not supported.


Using a FIO Request

If users of the exchange were assigned unique FIO Addresses, they could send a FIO Request from the exchange to a FIO Address of a FIO-integrated wallet or exchange. (e.g., [email protected]). The user would then login to the wallet and approve the FIO Request. Once approved, the wallet would execute the transfer on the native chain.