How to delete an asset from multichain

+1 vote
I have created an asset by mistake. I want to delete the asset using burn address.

I have used the below command to get the burn address and send to burn address.

{
 "method":"getinfo",
  "params":[],"id":null,
  "name":"SPS1005"
}

output

---------

{
    "result": {
        "version": "1.0.6",
        "nodeversion": 10006901,
        "protocolversion": 10011,
        "chainname": "mc-3661669235695858080",
        "description": "MultiChain mc-3661669235695858080",
        "protocol": "multichain",
        "port": 7000,
        "setupblocks": 60,
        "nodeaddress": "mc-3661669235695858080@172.31.21.182:7000",
        "burnaddress": "1XXXXXXXKyXXXXXY2DXXXXXXYGXXXXXXX5EwRc",
        "incomingpaused": false,
        "miningpaused": false,
        "walletversion": 60000,
        "balance": 0,
        "walletdbversion": 2,
        "reindex": false,
        "blocks": 612,
        "timeoffset": 0,
        "connections": 0,
        "proxy": "",
        "difficulty": 6e-8,
        "testnet": false,
        "keypoololdest": 1534167746,
        "keypoolsize": 2,
        "paytxfee": 0,
        "relayfee": 0,
        "errors": ""
    },
    "error": null,
    "id": null
}

After that I am sending my asset SPS1005 to burn address using below command

{"method":"sendassettoaddress",
 "params":["1XXXXXXXKyXXXXXY2DXXXXXXYGXXXXXXX5EwRc","SPS1005",100]
}

Now I am trying to issue the same asset using below command

{

"method": "issue",

"asset": "SPS1005",

"params": ["1PeM6q5ZSbne5SuLPFLD3zcPWcKke9MBiKT1Ln"],

"qty" :100,

"units":1,

"custom-fields":{

"Inventory No": "SPS1005",

"Order No": "ORD0001",

"Value": 154,

"Currency": "USD",

"LOT No": 3456,

"Status": "In transit",

"Partner": "Distributor"

}

}

But it gives error ,

 

 

{
    "result": null,
    "error": {
        "code": -1,
        "message": "issue \"address\" \"asset-name\"|asset-params quantity ( smallest-unit native-amount custom-fields )\n\nIssue new asset\n\nArguments:\n1. \"address\"                        (string, required) The address to send newly created asset to.\n2. \"asset-name\"                     (string, required) Asset name, if not \"\" should be unique.\n or\n2. asset-params                     (object, required) A json object of with asset params\n    {\n      \"name\" : \"asset-name\"         (string, optional) Asset name\n      \"open\" : true|false           (boolean, optional, default false) True if follow-on issues are allowed\n      ,...\n    }\n3. quantity                         (numeric, required) The asset total amount in display units. eg. 1234.56\n4. smallest-unit                    (numeric, optional, default=1) Number of raw units in one displayed unit, eg 0.01 for cents\n5. native-amount                    (numeric, optional) native currency amount to send. eg 0.1, Default: minimum-per-output.\n6  custom-fields                    (object, optional)  a json object with custom fields\n    {\n      \"param-name\": \"param-value\"   (strings, required) The key is the parameter name, the value is parameter value\n      ,...\n    }\n\nResult:\n\"transactionid\"                     (string) The transaction id.\n\nExamples:\n> multichain-cli mc-3661669235695858080 issue \"1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd\" \"Dollar\" 1000000\n> multichain-cli mc-3661669235695858080 issue \"1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd\" Dollar 1000000 0.01 0.01 \n> curl --user myusername --data-binary '{\"jsonrpc\": \"1.0\", \"id\":\"curltest\", \"method\": \"issue\", \"params\": [\"1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd\", \"Dollar\", 1000000, 0.01, 0.01 \"description=1 Million dollars\"] }' -H 'content-type: text/plain;' http://127.0.0.1:8000\n"
    },
    "id": null
}
asked Oct 23, 2018 by anonymous

1 Answer

+1 vote
When you burn an asset, what you are doing is just sending the tokens that you have sent to the burn address. Burnt tokens become unusable.

However, the asset still exists. So you can't issue a new asset with the same name. You can re-issue the asset if the asset allows for re-issue.
answered Oct 23, 2018 by StevenChan
...