Map NFTs

post https://test.fio.eosusa.io/v1/chain/add_nft

This call maps the supplied NFTs to the supplied FIO Handle, so that it can be returned using /get_nfts_fio_address.It will allow anyone to see which FIO Handle has mapped ("signed") a particular NFT.

You may pass up to 3 public addresses in a single call. A maximum of 200 public addresses may be mapped to a FIO Handle.

The actor must own the supplied FIO Handle.

See NFT Signatures 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.address
name: addnft

SDK Sandbox Example

Body Params

fio_address

string

required

length between 3 and 64

FIO Handle. It used to be called FIO Address, so you will still see it referred to as such.

nfts

array of objects

required

length between 1 and 3

Maximum of 3 NFTs can be mapped to single FIO Handle at any one time.

nfts*

chain_code

string

required

length between 1 and 10

See Chain and token code standard

contract_address

string

required

length between 1 and 128

NFT contract address.

token_id

string

required

length between 1 and 64

NFT token ID.

url

string

required

length between 0 and 128

URL of NFT asset. For example, the media URL.

hash

string

required

length between 0 and 64

SHA-256 hash of NFT asset.

metadata

string

required

length between 0 and 128

JSON formatted metadata. For example, creator URL.

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

Language

URL

Request


xxxxxxxxxx
59
1
// Map NFT Action
2
var action = 'addnft'
3
var contract = 'fio.address'
4
5
const {FIOSDK} = require('@fioprotocol/fiosdk')
6
var fetch = require('node-fetch')
7
const fetchJson = async (uri, opts = {}) => {
8
  return fetch(uri, opts)
9
}
10
11
// EDIT this section then type node addnft.js in Terminal to run
12
// API endpoint, see https://github.com/fioprotocol/fio.mainnet for complete list
13
const apiNode = 'https://fiotestnet.blockpane.com/v1/' 
14
// FIO Chain Testnet private key. Get one from http://monitor.testnet.fioprotocol.io:3000/#createKey
15
// and then add tokens via faucet: http://monitor.testnet.fioprotocol.io:3000/#faucet
16
const privateKey = '5K9du1JcEVNyBZKU6Uc9bSihgUzmMvGUxPDRwyxVmo9Xuh2NNW3'
17
const publicKey = FIOSDK.derivedPublicKey(privateKey).publicKey
18
const account = FIOSDK.accountHash(publicKey).accountnm
19
// Action parameters
20
var actionData = 
21
{
22
  fio_address: 'user10006@regtest',
23
  nfts: [
24
    {
25
      chain_code: 'ETH',
26
      contract_address: '0x63c0691d05f441f42915ca6ca0a6f60d8ce148cd',
27
      token_id: '100010001',
28
      url: 'ipfs://ipfs/QmZ15eQX8FPjfrtdX3QYbrhZxJpbLpvDpsgb2p3VEH8Bqq',
29
      hash: 'f83b5702557b1ee76d966c6bf92ae0d038cd176aaf36f86a18e2ab59e6aefa4b',

Choose an example:

application/json