MultiChain Developer Q&A - Recent questions tagged params

Can I set "anyone-can-admin" at runtime?

Tue, 19 Jun 2018 16:57:04 +0000

I looked through the list of runtime parameters and anyone-can-activate wasn't there.
I tried to set it like: multichaind -anyone-can-activate=true but it didn't work.

I guess I can do it through some unix text-replacement commands against the params.dat file, but that's a nasty solution.
Any suggestions?

listassets is giving an error HTTP 200

Wed, 09 May 2018 12:06:03 +0000

Hello,

I am trying to list all assets in multichain web demo but I am getting an error HTTP 200 but when i am running in CMD using multichain-cli chain2 listassets * true I am getting the list of assets which i have created.

Can you help me with alternative of listassets command or how to fix that error.

Thanks.

How to pass an array of asset names to listassets API ?

Mon, 29 Jan 2018 08:18:18 +0000

Hi Team,

I have checked the doc and got to know that we can pass the more than one assets to the listassets API call?

But I don't know how to test on the CLI mode.

Can you help me on that.

Thanks in advance.

Regards,

Shiva.P

What is the minimum system requirement?

Mon, 13 Nov 2017 12:37:28 +0000

What is the minimum system requirement for using multichain? Can it be used in 32bit windows system? What are other minimum parameters required for smoothing running the multichain system?

Thank you.

How to pass optional API parameters

Fri, 10 Nov 2017 03:08:36 +0000

I would like some guidance on the proper way to specify optional API parameters. For example the listaddresses api command, where I would like to specify a value for start but not one of count. Since the count parameter must be specified before the start parameter, it appears I must specify a value for count (it can't be null) without generating errors. Is this correct?

what is 'minimum per output' in params.dat

Tue, 19 Sep 2017 08:33:30 +0000

what is 'minimum per output' in params.dat

if minimum per output value is '-1' , this will be calculated from minimum relay fee

I don't know what is this value

What runtime params setup constitutes bad outcomes?

Mon, 04 Sep 2017 11:32:24 +0000

we have the ability to change permissions and consensus rules. Sometimes its difficult to ascertain what value may affect another, and equal a bad consequence.

Are there some "bad" examples of param settings. and further could this be coded as a warning when first run? You have chosen round robin mining but set difficulty to a high value.

perhaps not the best example:

running multichaind chain -daemon
warning: difficulty value outside normal expected operation (since it would take 12 months to mine)

continue y/n

Multichain cloning

Sat, 18 Feb 2017 17:31:18 +0000

Hi,

I noticed that multichain-util clone [old-name] [chain-name] uses the old multichain name as the chain description in the new params.dat file. Is this by design?

Mining-Requires-Peers not working

Mon, 06 Feb 2017 08:15:44 +0000

When I start a single multichain node with parameters:

mining-requires-peers = true

setup-first-blocks = 5

The node should with my understanding stop mining after about 5 blocks.

But it does continue mining (at the moment at block 57)

Did I miss something?

Anyone can issue - don't seem to work

Thu, 12 Jan 2017 00:53:00 +0000

Hi,

I created a new multichain blockchain, edited the params.dat file so that all the global permissions are true. Then i started the blockchain and connected three other nodes. However, when i use listpermissions issue command on node1 (or node2), the json only contained node1 (my starting nodes) address.

I also got the "No unspent output with issue permission" when i went ahead to try issuing a new asset to node2 address. Using getblockchainparams still clearly shows "anyone-can-issue" : true.

Any idea what i am missing?

Thanks.

Is it possible to send a metadata larger than 4096B ?

Tue, 13 Sep 2016 16:56:54 +0000

Hi,

I've been trying to send larger metadata on my blockchain, but it keeps being cut at 4096B.

To send larger hex strings, I followed the Creating data streams tutorial and I changed the params.dat file right after creating the blockchain and before launching it with -daemon. I edited the following fields to maximum :
max-std-op-return-size =8388608
maximum-block-size=1000000000
max-std-tx-size=10000000
max-std-element-size=32768
max-std-op-drops-count=100

I also enabled the following fields by marking them true :
anyone-can-connect ; anyone-can-send ; anyone-can-receive ; anyone-can-issue ; anyone-can-mine ; anyone-can-activate ; anyone-can-admin

I can tell that my modifications have been taken into account since the params.dat file is updated on both my nodes after I launch them and I no longer need to grant send, receive, etc. to my addresses.

Any clue as to why my metadata always gets cut at 4096 ?

Thanks

Can we change the "target-block-time" to a new value ?

Mon, 18 Apr 2016 12:25:55 +0000

Can we change the "target-block-time" parameter in the params.dat of an existing chain? I understand that if thats possible it needs to be synced across all the nodes in the chain, which might be a challenge.
but do we have a facility if in case we want to change any of the parameter. Another possible candidate is the "max-std-op-return-size". I was testing with private chains and the requirement of modifying the op-return-size appeared later and I had to clone the chain and modify the paramater.

However , I wanted to check if the reload of configuration is supported.

I tried modifying the params.dat after shutting down the node, but multichaind threw the following error message:

ERROR: Parameter set for blockchain <chain> is invalid.