| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
User
Users enters FIO Address as their Send to address for any crypto.
User does not need to register a FIO Address inside the wallet for this integration.
Wallet
Fetch public address using /get_pub_address.
Rest of flow unchanged.
...
Map Public Addresses to their FIO Address
Request any token using FIO Request
Respond to a FIO Requests
DECISION 1
A. Wallet controls the FIO Address Registration UX
User
Picks a FIO Address
DECISION 2
A. Address registration part of on-boarding OR
DECISION 3
A. A FIO Address can automatically be assigned when a user creates a wallet account ORB. You may use a value already being collectedan exchange account, e.g. user_name@wallet, or name@greatexchange OR
B. User picks a FIO Address themselves
B.Address registration as an option
Any user may choose to register a FIO Address when they want to access the FIO features.
Wallet
Foundation-paid FIO Addresses
Register FIO Address on chain using /register_fio_address
DECISION 4
A. You want to keep the domain private. Only the wallet can register FIO Addresses on that domain.
Wallet will have to transfer domain ownership to Foundation
B. The domain can be public
Custom permission set-up will be required.
Wallet-paid FO Addresses
Register FIO Address on chain using /register_fio_address
Register FIO Address on chain using /register_fio_address
B. Exchange links user off to registration site
FIO Addresses registered to a FIO Public Key can be obtained for display using /get_fio_addresses
...
In order to receive crypto sent to a FIO Address, it has to be mapped to public addresses in the wallet.
User
DECISION 5
A. User explicitly decided which crypto currencies are mapped to their FIO Address
B. The wallet automatically maps all supported crypto currencies to the FIO Address
Wallet
Maps public addresses using /add_pub_address and FIP-15 Standard
...