Unable to issue more of an 'open' asset, is it created correctly?

Question

Hello Multichain!

I am trying to issue more of a previously created asset, all my nodes are running 1.0 Alpha 18.

I created the asset originally with the command:

multichain-cli GBP issue 15J4fYch5GrMxH1LEK4rSZAesWy2t5Yj1nf9jj '{"name":"dGBP2","open":true}' 100 0.01 0 '{"reference":"first"}'

Which I can see with the listassets command, everything looks good but should I expect to see the 'open' param here?

multichain-cli GBP listassets '*' true

[
    {
        "name" : "dGBP2",
        "issuetxid" : "ef4425486cb5a78dab10752d76398a7cd20c63c9519d27141393b61eea7c94ec",
        "assetref" : "787-267-17647",
        "multiple" : 100,
        "units" : 0.01000000,
        "details" : {
            "reference" : "first"
        },
        "issueqty" : 100.00000000,
        "issueraw" : 10000
    }
]

When I try to issue more of the same asset - referenced by name (I have tried with and without quotes around dGBP2)...

multichain-cli GBP issuemore 15J4fYch5GrMxH1LEK4rSZAesWy2t5Yj1nf9jj 'dGBP2' 100 0 '{"reference":"second"}'

{"method":"issuemore","params":["15J4fYch5GrMxH1LEK4rSZAesWy2t5Yj1nf9jj","dGBP2",100,0,{"reference":"second"}],"id":1,"chain_name":"GBP"}

error: {"code":-32603,"message":"Issuing more units not allowed for this asset: dGBP2"}

Anyone able to shed some light on this mystery?

Much appreciated, knowncolor.

 

Edit: Updated

I've double checked the version on all (3) nodes are "MultiChain Core RPC client build 1.0 alpha 18 protocol 10005", this is a new Multichain that I deployed from scratch today in newly built Docker containers.

However, my peerinfo result shows it is using protocolversion: 10003 not 10005 as above. I will start another fresh deployment on new hosts in the meantime.

GBP: getinfo
{"method":"getinfo","params":[],"id":1,"chain_name":"GBP"}

{
    "version" : "1.0 alpha 18",
    "protocolversion" : 10003,
    "chainname" : "GBP",
    "description" : "Thank you for the awesome support.",
    "protocol" : "multichain",
    "port" : 6457,
    "setupblocks" : 60,
    "nodeaddress" : "GBP@172.17.xxx.xxx:6457",
    "burnaddress" : "1XXXXXXXJLXXXXXXFjXXXXXXgVXXXXXXYftEMh",
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 5392,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 0.00001526,
    "testnet" : false,
    "keypoololdest" : 1458222164,
    "keypoolsize" : 2,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00000000,
    "errors" : ""
}

 

 

Answer 1

It is odd that you don't have open fields in your output from listassets. Did you ever install an earlier version of MultiChain that might still be receiving your API requests?

Comments

Thank you for your help, I have updated my question with more information.

---

Ah yes, that would explain it - if the blockchain is running an old protocol then it's not possible that an asset was 'open'. The listassets API however should still show 'open':false rather than omitting this parameter - we will check into this and if appropriate, resolve it in the next alpha.

---

I had created the blockchain using a params.dat generated by the Alpha 16 build. Mystery solved.