MultiChain Developer Q&A - Recent questions tagged protocol

protocol upgrade (20003->20012) not detected by latest binary (2.3.3)

Thu, 03 Aug 2023 14:38:53 +0000

Hello,
when upgrading a blockchain (protocol), I run into the following problem:

1) The existing chain is 20003, the binary version of multichaind is 2.1.2
2) I follow the instruction from https://www.multichain.com/developers/upgrading-nodes-chains/ to upgrade to protocol 20012.
3) Everything worked.
4) When restarting multichaind 2.1.2 it detects the new version 20012. Other nodes also detect 20012.
getinfo says:
    [version] => 2.1.2
    [nodeversion] => 20102901
    [edition] => Community
    [protocolversion] => 20012

5) BUT: Moving to multichaind-latest (2.3.3) it stops with the following error:
MultiChain 2.3.3 Daemon (Community Edition, latest protocol 20013)
Starting up node...
ERROR: The protocol version (20003) for blockchain mc2a3 has been deprecated and was last supported in MultiChain 2.2 beta 3

What can be the problem?

Thanks,
Chris

Multichain routing using testnet support

Wed, 23 Feb 2022 08:12:03 +0000

Hey wanted to know if there is a way to check out routing protocol provided by multichain through testnets. Looking at the documentation also I didnt see anywhere where support for testnets is mentioned. Any reference/ help would be highly appreciated.

Regards

Astha

MultiChain routing protocol

Mon, 13 Jul 2020 04:16:41 +0000

What kind of routing protocol is used in MultiChain to propagate blocks/transactions?

Is it just a gossip protocol or maybe something more elaborate?

Missing exactly one transaction after "merkleblock"-message

Mon, 04 May 2020 17:30:01 +0000

Hi,

I've come across an "issue" where after a "merkleblock"-message Multichain leaves out exactly one of transactions in the following "tx"-messages. I'm not sure whether this is intended behavior and I just misunderstood the Bitcoin documentation or an actual problem.

Here's the setup:
I'm using Multichain as a single full node in combination with a browser based Bitcoin SPV node (bcoin).
When the SPV node creates and announces a new unconfirmed transaction Multichain receives, validates and adds it to the next block as expected. Multichain proceeds to announce the new block ("inv"-message) and the SPV node requests it ("getdata"-message) as should be. In response, Multichain sends a "merkleblock"-message to the SPV node as well as separate "tx"-messages for all but one transaction of the newly created block.

From the Bitcoin documentation [1]:
The merkleblock message is a reply to a getdata message which requested a block using the inventory type MSG_MERKLEBLOCK. It is only part of the reply: if any matching transactions are found, they will be sent separately as tx messages.

And from [2]:
After a merkleblock, transactions matching the bloom filter are automatically sent in tx messages.

Since I didn't set a bloom filter I expected one "tx"-message for every transaction that is included in the block. However, Multichain leaves out exactly one of those transactions.
I've noticed that the missing transaction is always the one the SPV node announced earlier. My best guess here is that Multichain assumes the SPV node won't need that transaction a second time since it announced it in the first place? Is this intended behavior by Multichain or am I missing something here?

Thanks in advance and best regards

[1] https://bitcoin.org/en/developer-reference#merkleblock
[2] https://en.bitcoin.it/wiki/Protocol_documentation#filterload.2C_filteradd.2C_filterclear.2C_merkleblock

Webdemo is not connecting with multichain protocol version 20011

Sat, 21 Dec 2019 02:30:32 +0000

Hi MC Team

I have been using multichain since 2017 , I am resuming some projects and I am trying to run webdemo and a I am facing an ERROR http 0 , I have checked rpcusername , rpcpassword, and I grant access using rpcallowip=0.0.0.0/0 and the problem continues, Multichain demo just does not connect to node using rpc. Perhaps is something to do with version protocol I haven't used 20011 before.

Any valuable help for this case?

Thanks

Upgrading protocol from 10009 to10011

Sun, 10 Mar 2019 15:44:15 +0000

I am running version 1.0.7 on Windows, and I am trying to upgrade the protocol from 10009 to 10011. When I attempt the command

multichain-cli chain1 createfrom 1... upgrade protocol-upgrade false '{"protocol-version":10011}'

all I see is the error message error: Error parsing JSON:'{protocol-version:10011}'

I have copied the command directly from your web page and changed the values as appropriate, so what is wrong?

Upgrading the chain's protocol

Thu, 20 Dec 2018 12:30:25 +0000

Hello again.

After I updated the chain's software to the new beta and I ran `multichaind -version`, it showed that the new range of supported protocols are (20001-20006). So, I tried to upgrade the chain's protocol by running:

`multichain-cli chainName createfrom 1.. upgrade protocol_upgrade false '{"protocol-version":20006}'`

However, I am getting this error:

`Invalid value for protocol version. Valid range: 10004-10011, 20001-20004`

Am I missing something? Thanks for the help in advance.

What is Multichain 2.0 Alpha 4 - protocol version 20003 is ?

Mon, 22 Oct 2018 07:15:25 +0000

Can we safely assume Multichain 2.0 Alpha 4 - protocol version 20003 merely means running multichaind on port 20003 ? Or is my understanding completely different as such ? If so, where and how can I can gain insights to this ?

protocol upgrade

Mon, 11 Jun 2018 00:39:30 +0000

I have some questions regarding using the Multichain software. We have downloaded the version 1.0.4 version of Multichain and have made a new chain. We are attempting to upgrade the protocol of this chain to 20002 from 10010 using the instructions written on https://www.multichain.com/developers/upgrading-nodes-chains/. During the upgrade process (after step 3 to be exact), an error pops up like below:

error code: -8

error message:

Invalid protocol version, cannot upgrade to future version

So we downloaded the 2.0 alpha 2 version of the software, and proceeded to run the same chain using the 2.0 alpha 2 version instead of the 1.0.4 version, only to be met with another error

ERROR: Parameter set for blockchain kaitest was generated by MultiChain running newer protocol version (10010) Please upgrade MultiChain

So, to summarize, how can we upgrade the protocol of our blockchain from 10010 to 20002 without encountering such errors above?

Wallet goes up blocks but does not raise money - Error

Thu, 08 Mar 2018 17:02:44 +0000

Hello,
I have created a blockchain with the example file, I have done it as in the last version as in a previous one that uses the 10002 protocol.
In both cases I have obtained a block reading, but the cryptocurrency never reaches the wallet.
If someone has any idea what may be happening. It would help me a lot.
Thank you so much.