MultiChain Developer Q&A - Recent questions tagged open-assets

What is the different between Open Asset and Multichain Asset ?

Tue, 25 Sep 2018 02:10:28 +0000

Add units in the asset from different node

Thu, 28 Jun 2018 08:24:00 +0000

Hello Friends,

I have created an asset from Node_1 using createrawsendfrom . I have tried to add more units in the same node. Then I am able to do it.

But when I am trying to add more units from different node. It's says 'from-address is not found in this wallet'.[Note: from-address is the issuer of assets]

How can I add from-address in all nodes connected.

Asset With Multi Issuance Listing Pattern Error/Bug

Tue, 09 Aug 2016 11:44:41 +0000

This is related to the multiple issuance of an asset in Multichain. I have faced the issue multiple times where in the nodes wallets failed to respond after a particular state of the system. It took me some time to pin point the issue. Once the issue is reached, the multichain nodes fails to respond and goes to hang state which doesn't get solved using reindex=1 as well.

If an asset is issued with open as true. If the asset is issued 6 -7 times further and the command listassets assetname is executed, wallet hangs. The pattern remain same if the address balances is fetched. I have multiple chains with the issue. If required I can share the data.

The issue is not related to the number of assets in the chain but the number of times any asset is reissued. I have tested creation of 600-700 assets and listing them successfully. The issue can be reproduced by the following process:

Create a new chain
Issue an asset to the origin address
Wait for the asset to get confirmed by checking for the asset reference name in listassets assetname
Execute listasset assetname true
Reissue the asset
Execute listassets assetname true/false or listassets or listassets '' true
Repeat 5 and 6 till the commands fails to respond.

One the system hangs. We can kill the process and restart multichain. The getinfo commands work, the moment commands like gettotalbalances or listassets is executed, it will go to hang state. I think the issue is related to fixed memory size allocation in the code programme.

Let me know if you require more info.

"Insufficient funds" when calling `issuemore` for an open asset

Tue, 29 Mar 2016 11:26:16 +0000

Hello,

I have an open asset that I have made multiple issuances of, but I have started getting an "Insufficient funds" error. I've included the example command and some more info below, and would appreciate any help on the matter.

multichain-cli GBP issuemore "1YXEDBc8M6PkX5saU1TNVa5655u6cBd3SdVsRf" "dGBP" 456.78 0 '{"reference":"large2"}'

{"method":"issuemore","params":["1YXEDBc8M6PkX5saU1TNVa5655u6cBd3SdVsRf","dGBP",456.78000000,0,{"reference":"large2"}],"id":1,"chain_name":"GBP"}

"error: {"code":-4,"message":"Insufficient funds"}

Nodes are all running Alpha 18, and the node has connect, send, issue permissions, and the receiving node has connect, receive permissions.

multichain-cli GBP listassets dGBP true
{"method":"listassets","params":["dGBP",true],"id":1,"chain_name":"GBP"}

[
{
"name" : "dGBP",
"issuetxid" : "4ebe4b45cbb0ae8d026619965682298826c20c28fe820d1606914d1d4e37348f",
"assetref" : "6615-266-48718",
"multiple" : 100,
"units" : 0.01000000,
"open" : true,
"details" : {
"reference" : "first"
},
"issueqty" : 220.50000000,
"issueraw" : 22050,
"issues" : [
{
"txid" : "4ebe4b45cbb0ae8d026619965682298826c20c28fe820d1606914d1d4e37348f",
"qty" : 100.00000000,
"raw" : 10000,
"details" : {
"reference" : "first"
},
"issuers" : [
"1MuehZgn2wt3mnjuoD57kst3qB3bSQHXrGrU4c"
]
},
{
"txid" : "f7f3dcfa42a7a0e0e142f8d4a02e43c767bb2c72976dd55ff33777df827a7e40",
"qty" : 10.50000000,
"raw" : 1050,
"details" : {
"issuanceReference" : "second issuance"
},
"issuers" : [
"1MuehZgn2wt3mnjuoD57kst3qB3bSQHXrGrU4c"
]
},
{
"txid" : "e2e4f68617e7eb7fd8eca15333ee94c5679e6a7809d0c222c211785fb3d5a0b7",
"qty" : 10.00000000,
"raw" : 1000,
"details" : {
"issuanceReference" : "diff block"
},
"issuers" : [
"1MuehZgn2wt3mnjuoD57kst3qB3bSQHXrGrU4c"
]
},
{
"txid" : "1004ec38dad1f80ba23f533b497196e10f7212614e91267e3e088a57d69c7c7c",
"qty" : 50.00000000,
"raw" : 5000,
"details" : {
"reference" : "double check"
},
"issuers" : [
"1MuehZgn2wt3mnjuoD57kst3qB3bSQHXrGrU4c"
]
},
{
"txid" : "09cb4fdb6397449f79d449ef5f8e8d2803694d73efbaed8c351045ac502b155c",
"qty" : 50.00000000,
"raw" : 5000,
"details" : {
"reference" : "amount-check-1"
},
"issuers" : [
"1MuehZgn2wt3mnjuoD57kst3qB3bSQHXrGrU4c"
]
}
]
}
]

Kind regards,
Knowncolor

Second Update

I was able to get this to work again by first issuing more of the open asset to the node with the issue permissions and then transferring it on. After doing this once I was again able to issue directly to other nodes.

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

Thu, 17 Mar 2016 19:39:25 +0000

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" : ""
}

Open Assets over MultiChain

Wed, 24 Jun 2015 11:23:23 +0000

Can I run the Open Assets colored coin protocol over a MultiChain blockchain?