MultiChain Developer Q&A - Recent questions tagged nft

Send NFT

Sun, 02 Nov 2025 18:08:48 +0000

how to send NFT?
sendassetfrom "from-address" "to-address" "asset-identifier" asset-qty ( native-amount "comment" "comment-to" )

sendassetfrom doesn't have any way to send a specific token

NFTs revisited

Mon, 16 Jun 2025 23:56:01 +0000

Hello MultiChain Team,

I've read an article about how a luxory watch manufacturer uses the blockchain to fight against counterfeit products. They make use of NFTs as well. I loved the idea and tried to reproduce the use case.

So issue an NFT:

multichain-cli chain1 issue 1UBXNq177rgPi8yperyAZgBhMNtr66hBAHxGCD 
'{"name": "12345klp111", "open": false, "fungible": false, 
"canopen": true}' 0 1 0 '{"Manufacturer" : "Swiss watch", 
"model" : "super time", "serial no" : "12345klp111"}'

e80aca96c38e7c239b5f186b461623c23e6bf70d1a0b0491208874912f2efd74

so far, so good. But actually, what are the parameters "open" and "canopen"? I understand that it allows some sort of later manipulation, like issuing a token that depends on the NFT? What use case would that be?

multichain-cli chain1 listassets "12345klp111"
{"method":"listassets","params":["12345klp111"],"id":"70189557-1750117422","chain_name":"chain1"}

[
    {
        "name" : "12345klp111",
        "issuetxid" : "e80aca96c38e7c239b5f186b461623c23e6bf70d1a0b0491208874912f2efd74",
        "assetref" : null,
        "multiple" : 1,
        "units" : 1,
        "open" : false,
        "restrict" : {
            "send" : false,
            "receive" : false,
            "issue" : true
        },
        "fungible" : false,
        "canopen" : true,
        "canclose" : false,
        "totallimit" : null,
        "issuelimit" : null,
        "details" : {
            "Manufacturer" : "Swiss watch",
            "model" : "super time",
            "serial no" : "12345klp111"
        },
        "issuecount" : 1,
        "issueqty" : 0,
        "issueraw" : 0,
        "subscribed" : true,
        "synchronized" : true,
        "transactions" : 1,
        "confirmed" : 0
    }
]

it looks good to me, NFT is created.

When I try to transfer it to another address (aka the watch is sold and the buyer shall get the digital representation of the watch into his wallet), I get an error:

multichain-cli chain1 sendasset 
1HrnzpVLvSu6Ecs26Q3ZRakTWd2NskzbgGCq64 "12345klp111" 1
{"method":"sendasset","params":
["1HrnzpVLvSu6Ecs26Q3ZRakTWd2NskzbgGCq64",
"12345klp111",1],"id":"22511383-1750117567",
"chain_name":"chain1"}

error code: -702
error message:
This API is not supported for nun-fungible assets

whats wrong here? Here is my getinfo:

multichain-cli chain1 getinfo
{"method":"getinfo","params":[],"id":"
49769585-1750117609","chain_name":"chain1"}

{
    "version" : "2.3.3",
    "nodeversion" : 20303901,
    "edition" : "Community",
    "protocolversion" : 20013,
    "chainname" : "chain1",
    "description" : "MultiChain chain1",
    "protocol" : "multichain",
    "port" : 5759,
    "setupblocks" : 60,
    "nodeaddress" : "chain1@192.168.10.114:5759",
    "burnaddress" : "1XXXXXXWpvXXXXXXZXXXXXXXk7XXXXXXV1FN3N",
    "incomingpaused" : false,
    "miningpaused" : false,
    "offchainpaused" : false,
    "walletversion" : 60000,
    "balance" : 0,
    "walletdbversion" : 3,
    "reindex" : false,
    "blocks" : 297171,
    "chainrewards" : 0,
    "assets" : 13,
    "streams" : 3,
    "addresses" : 12,
    "transactions" : 698134,
    "peers" : 0,
    "timeoffset" : 0,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 5.96046447753906e-8,
    "testnet" : false,
    "keypoololdest" : 1744062673,
    "keypoolsize" : 2,
    "paytxfee" : 0,
    "relayfee" : 0,
    "errors" : ""
}

ok, lets say sending works. Lets also assume, the watch was destroyed in a fire, so its time to destroy the belonging NFT as well. So I though I'll send it to the burn address:

multichain-cli chain1 sendasset 
1XXXXXXWpvXXXXXXZXXXXXXXk7XXXXXXV1FN3N  "12345klp111" 1
{"method":"sendasset","params":["1XXXXXXWpvXXXXXXZXXXXXXXk7XXXXXXV1FN3N",
"12345klp111",1],"id":"61043256-1750117758","chain_name":"chain1"}

error code: -704
error message:
Destination address doesn't have receive permission

This is also unexpected to me: I thought the burn address can receive every kind of tokens at all times.

I'd be very happy to get this straight - I also think this would help other interested folks get a deeper understanding for use cases for a blockchain.

Thanks for the great work anyway.

Issuing assets is limited? Problem with new NFT in UI

Sun, 16 Mar 2025 16:39:51 +0000

Hi,

I was exploring the possibilities with assets and created a coin and an NFT. At least, I was hoping for doing it right, but I might have made an error. For the NFT I decleared the quantity to 3 and the units to 1:

Afterwards I've read in the API docs that the quantity for an NFT should be 0 and units should be 1. So I have a quantity of 3 at the moment, I was sending them back and forth between 2 nodes, now node 1 holds qty of 1 and node 2 holds also qty of 1. Where did the 3rd piece go?

I also issued a coin, transfers between nodes work fine. But now I am not able to issue anything new from the Web-UI. On the command line I can successfully run this command:

bbking@bc-debian:~$ multichain-cli chain1 issue 1UBXNq177rgPi8yperyAZgBhMNtr66hBAHxGCD '{"name": "realNFT", "open": true, "fungible": false, "canopen": true}' 0 1
{"method":"issue","params":["1UBXNq177rgPi8yperyAZgBhMNtr66hBAHxGCD",{"name":"realNFT","open":true,"fungible":false,"canopen":true},0,1],"id":"41253787-1742139590","chain_name":"chain1"}


c53c7736f22b05a3f4a12d5b6b7d4afe79887cc5cb8ebe8224e5cfd773c7f9e8

and I can see the NFT on the chain:

bbking@bc-debian:~$ multichain-cli chain1 listassets realNFT
{"method":"listassets","params":["realNFT"],"id":"11745015-1742142513","chain_name":"chain1"}

[
    {
        "name" : "realNFT",
        "issuetxid" : "c53c7736f22b05a3f4a12d5b6b7d4afe79887cc5cb8ebe8224e5cfd773c7f9e8",
        "assetref" : "197025-267-15557",
        "multiple" : 1,
        "units" : 1,
        "open" : true,
        "restrict" : {
            "send" : false,
            "receive" : false,
            "issue" : true
        },
        "fungible" : false,
        "canopen" : true,
        "canclose" : false,
        "totallimit" : null,
        "issuelimit" : null,
        "details" : {
        },
        "issuecount" : 1,
        "issueqty" : 0,
        "issueraw" : 0,
        "subscribed" : true,
        "synchronized" : true,
        "transactions" : 1,
        "confirmed" : 1
    }
]

When I go to the Web-UI "Issue Asset/Update" or "Send" menus, I don't see realNFT showing up there.

What do I do wrong?

Temporary Aggregation of Different Assets in Supply Chain

Wed, 05 May 2021 15:40:41 +0000

Let's say I have two different real world items (e.g. a racket and a ball) and I issue each of them as a new asset type with quantity 1 to make them NFTs (https://www.multichain.com/qa/12997/non-fungible-tokens?show=12999#a12999).

Now I want to ship them together in a box from A -> B -> C. When C receives the box they should be able to open it and get the items back. How can I make sure the items cannot be separated while in transit? Does it make sense to issue a new asset for the box? I can't send the racket and ball assets to a burn address as is recommended here: https://www.multichain.com/qa/1913/asset-tracking-in-supply-chain-management, because I need to get the assets back in the end.