MultiChain Developer Q&A - Recent questions tagged target-block-time

Does difficulty adjustment work when anyone-can-mine=false and target-adjust-freq > 0 ?

Mon, 21 Sep 2020 08:47:15 +0000

if I set anyone-can-mine=false and target-adjust-freq > 0 ; does difficulty adjustment work to keep target block time ?

target-block-time parameter not working as intended

Wed, 07 Mar 2018 06:24:45 +0000

If I set the target-block-time to say 10 seconds, and publish just one key ("key123", "AB); from my understanding this transaction should be confirmed when the block is formed after 10 seconds. But in my case, its confirmed much earlier (varies between 3-8 seconds). If I keep publishing 3-4 keys at a time, it decreases even further :- 1-3 seconds.

Or is there any other parameter which affects this? Cant be maximum-block-size because my publish pair is very small. Or does this parameter work differently?

Setting target-adjust-freq, increases the block mining rate

Tue, 13 Feb 2018 12:14:27 +0000

Hi,

I have created the chain, and I was checking with different parameters to adjust the mining difficulty. When I set the target-adjust-freq as >0, then the blocks are being mined very fast and if I set it to -1 than the speed of mining is as per the average block time parameter. I have also set min-empty-rounds as -1 and anyone-can-mine as true.

I am not sure how to control this behavior, could you help me with this?

I have a question about target-block-time.

Tue, 21 Nov 2017 16:01:40 +0000

Below is some of the parameters.

target-block-time = 180

pow-minimum-bits = 22

target-adjust-freq = 86400

I am mining with one node and Below is the average time per 480 blocks.

No. Block	Average time
1~480	0min 45sec
481~960	2min 24sec
961~1440	3min 4sec
1441~1920	3min 3sec
1921~2400	2min 55sec
2401~2880	0min 48sec
2881~3360	2min 48sec
3361~3840	0min 52sec

As you can see, the average time to 2400 is normal,

but the average time between 2401 ~ 2880 and 3361 ~ 3840 is too fast.

I did not add nodes and did not other tasks.

Why does this happen?

How multichain sync all the nodes to keep in the same pace?

Wed, 14 Sep 2016 03:23:00 +0000

For Bitcoin, the block time is 10 minutes. Thus, Bitcoin has a scheme to change the difficulty of the cryptographic puzzle to keep the block time at 10 minutes. Others can easily check whether the puzzle has been solved or not.

For multichain, I am not sure whether it can achieve like this since multichain works in a round-robin approach. For example, if I set block time to 15 seconds, one block should be generated every 15 seconds. How can you ensure every node will follow this 15 seconds interval? What if a node is controlled by a malicious user and it broadcasts its block before 15 seconds if it is eligible to propose the next block. Thanks a lot.

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.