Version .10.3 of FIO Typescript SDK has been released. Action may be required if your application sends or receives FIO Requests or FIO Data.

Overview

FIO Requests and FIO Data historically required token_code to be supplied to describe the specific token. Token codes are being maintained in FIP-15 token code definition, but with the proliferation of meme coins on sites like pump.fun, it has become impractical to update the token codes fast enough.

As a result we are introducing support for contract address to be supplied instead of token code inside the token_code parameter in FIO Requests and FIO Data. Contract address must be prefixed with ca:.

Here's an example of content field for /new_funds_request requesting WFIO (Wrapped FIO Token) on Ethereum chain:

{
	"payee_public_address": "0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B",
	"amount": "1000",
	"chain_code": "ETH",
	"token_code": "ca:0xbea269038eb75bdab47a9c04d0f5c572d94b93d5"
}

Token codes as defined in FIP-15 token code definition continue to be supported in token_code as before.

Please not that this change applies only to FIO Request and FIO Data. Token addresses mapped to FIO Handles using /add_pub_address will continue to use token codes, until FIP-52 is adopted.

❗️

Action may be required

If your application sends or receives FIO Requests or FIO Data:

• You should update your logic to allow contract address to be received in FIO Request and FIO Data in addition to token codes. Failure to upgrade may cause your customers to receive FIO Request or FIO Data which your application will not be able to parse as it will contain unexpected contract address inside token_code field.
• If you use the Typescript SDK, you should upgrade to version 1.10.3 of the Typescript SDK, which allows contract addresses to be passed in token_code.
• Optionally, you may allow your customer to request specific tokens based on their contract address, in addition to token code.

New versions