Wrap FIO Tokens

post

https://test.fio.eosusa.io/v1/chain/wrap_fio_tokens

This action wraps FIO Tokens to another chain.

Currently, only Ethereum chain is supported (chain_code: ETH). When FIO Tokens are wrapped, they are first sent to an escrow contract on the FIO Chain. Next, a set of oracles run by FIO Block Producers detect the wrapped tokens and mint the equivalent amount of WFIO to the supplied Ethereum public_address.

See Wrapped FIO Token Guide for more information.

This action has to be serialized and signed!

Please note that this action has to be be serialized and signed before it's sent to the blockchain. The request object below only represents the action specific parameters and action specific response. See Write Transactions Guide for more information.

Actions parameters

account: fio.oracle
name: wraptokens

SDK Sandbox Example

Body Params

amount

integer

required

Amount of FIO Tokens to wrap in SUFs.

chain_code

string

required

length between 1 and 10

See Chain and token code standard

public_address

string

required

length between 1 and 128

Public address for chain/token code.

Integrated Address

If the blockchain supports it, an integrated address may be passed in just like standard public address. The FIO protocol does not perform validation on the passed string.

URI Scheme

FIO Protocol will support formatting of public addresses using URI where certain attributes are appended to the public address following a '?' and delimited with '&'. To allow inter-wallet operability, the following standardized parameters will be supported in official FIO Protocol SDKs.

Parameters

dt - Ripple
memo - Any - use as generic memo field
memo_id - Stellar
memo_text - Stellar
memo_hash - Stellar
memo_return - Stellar
payment_id - Monero

See FIO Handle Mapping Guide for more information.

max_oracle_fee

integer

required

Maximum amount of SUFs the user is willing to pay as Oracle fee. Current fee can be found using /get_oracle_fees.

max_fee

integer

required

Defaults to 10000000000000

Maximum amount of SUFs the user is willing to pay for on-chain fee. Should be preceded by /get_fee for correct value.

Alternatively, you can set this number to a very high value, e.g. 10000000000000, since the user will only be charged the actual amount of the fee.

See

tpid

string

required

length between 3 and 64

Defaults to vitalik@safu

FIO Handle of the wallet which generated this transaction. This FIO Handle will be paid 10% of the fee collected. Set to empty if not known.

See Transaction Provider ID (TPID) Guide for more information.

actor

string

required

Represents FIO Account which will execute the action. In most cases this is the hashed FIO Public Key.

Response

200