How to fix a broken chain?

Question

I've been playing around with MultiChain Web Demo and got 'Error: HTTP 200' when I uploaded a file within the Issue Assets section. I took a look at it in the multichain-cli with the 'listwallettransaction' command and it looks like the @file value contains a open double quote (") which improperly quits the JSON.

Is there a way to fix this? Did I break the chain? Could someone shed light on why this happening even though I'm still able to issue assets within the CLI.

Answer 1

You certainly didn't break the blockchain. At most this is triggering some bug in the API or command-line tool.

Could you please post the output of the listwallettransactions command with this open double quote, so we can take a look?

Comments

In terminal I ran 'listwallettransactions' which printed out the following:

{"method":"listwallettransactions","params":[],"id":1,"chain_name":"chain1"}
[
    {
        "balance" : {
            "amount" : 0.00000000,
            "assets" : [
                {
                    "name" : "Rage, the Flower Thrower",
                    "assetref" : "618-266-44482",
                    "qty" : 1.00000000
                }
            ]
        },
        "myaddresses" : [
            "1Q4umSZXKKFdySVeWa5jYcuVjpUZw26reobTcv"
        ],
        "addresses" : [
        ],
        "permissions" : [
        ],
        "issue" : {
            "name" : "Rage, the Flower Thrower",
            "assetref" : "618-266-44482",
            "multiple" : 1,
            "units" : 1.00000000,
            "open" : true,
            "details" : {
                "Artist Name" : "Banksy",
                "Year" : "2015",
                "@file" : "
chain1:
chain1:
chain1:



As you can see the JSON is not properly closed. Also on the front-end the web demo is displaying the following:

Error: HTTP 200
{"result":
[{"name":"Rage, the Flower Thrower","issuetxid":"c2ad740075eb01d9ef01bb9bdb72d5dd96ddf8ac3e21019e4a39f6eb5ab1aae2","assetref":"618-266-44482","multiple":1,"units":1.00000000,"open":true,"details":{"Artist Name":"Banksy","Year":"2015","@file":"2Banksy-Bethlehem-22.jpgimage/jpeg171618"},"issueqty":1.00000000,"issueraw":1,"subscribed":false,"issues":[{"txid":"c2ad740075eb01d9ef01bb9bdb72d5dd96ddf8ac3e21019e4a39f6eb5ab1aae2","qty":1.00000000,"raw":1,"details":{"Artist Name":"Banksy","Year":"2015","@file":"2Banksy-Bethlehem-22.jpgimage/jpeg171618"},"issuers":["1Q4umSZXKKFdySVeWa5jYcuVjpUZw26reobTcv"]}]}
http://127.0.0.1:7732/

---

OK. This just looks like a bug that was introduced in MultiChain 1.0.5 and fixed in 1.0.6 – please download and use the latest version. If you're on MultiChain 2.0 alphas, the bug has also been fixed there in the latest alpha.

---

That was it, thank you!