BUG in Version 18

Question

Version 18 : first address that was created together with a node has account name "" (default account - it does not chain name!)

$multichain-cli chain1 getaddresses true
{"method":"getaddresses","params":[true],"id":1,"chain_name":"chain1"}

[
    {
        "address" : "12dtzRxJ18jqQ3dkzc....aoJ",
        "ismine" : true,
        "iswatchonly" : false,
        "isscript" : false,
        "pubkey" : "03904cc5157af5f0e779509214acafccf9c7bcc....e21ce48b07a0aa9eb",
        "iscompressed" : true,
        "account" : "chain1"
    },
    {
        "address" : "19rokDHy7F8RCKA6kc....o1wTuBoKy",
        "ismine" : true,
        "iswatchonly" : false,
        "isscript" : false,
        "pubkey" : "022b76561644fb740774e5e1211c30d7148c....e00df073e7a3c0954a324",
        "iscompressed" : true,
        "account" : "chain1"
    },
    {
        "address" : "16qF2cwRiHFBGxpinc....5KJyhpEmZg",
        "ismine" : true,
        "iswatchonly" : false,
        "isscript" : false,
        "pubkey" : "03a229edf1a0d2bdb57b2df9a16c46cbf993fb7f5c....cd3cc1582c030bf84b",
        "iscompressed" : true,
        "account" : ""
    },
    {
        "address" : "1G6Ckg8vBszJf1zc....mSCtWLMkjiNmm",
        "ismine" : true,
        "iswatchonly" : false,
        "isscript" : false,
        "pubkey" : "030f4cf1874f767f8bdfd0741c30e112c6b348d9c....c9c9aa5eb1b2c2df08d3",
        "iscompressed" : true,
        "account" : "chain1"
    }
]

Comments

I send asset into primary account of the node but I cannot spend it!

Answer 1

The account field is present for backwards compatibility with Bitcoin Core API adapters, but does not have much meaning in MultiChain. See this note:

http://www.multichain.com/developers/json-rpc-api/#accounts

Comments

I cannot spend assets sent to such accounts on other nodes!!!
It was not happened under older versions!

---

If you send an asset to another node, it should not be spendable, independent of the "account" field. Unless that it, you have imported a private key across. If this does not match the behavior you see please let us know and we'll need to get some debug information.