MultiChain Developer Q&A - Recent questions tagged multiple-nodes

Docker issue connecting to genesis node

Wed, 05 Mar 2025 23:08:00 +0000

I have "rpcallowip=0.0.0.0/0" in my multichain.conf

docker images are able to ping and netcat displays the necessary port on genesis image as open..

Any idea on why they wont talk?

https://imgur.com/a/kdDiDPG

AWS Cloud9: Multichain Error: Couldn't connect to the seed node (Please help)

Mon, 25 Apr 2022 15:37:27 +0000

I am using AWS - cloud9 virtual machines for creation a multichain blockchain instance.

Unable to connect two virtual machine.
Error: Couldn't connect to the seed node 172.31.77.199 on port 4351 - please check multichaind is running at that address and that your firewall settings allow incoming connections.

From address not found

Mon, 25 Jan 2021 18:05:19 +0000

I have created a blockchain and did some asset transactions between the addresses, and added a node to the blockchain. Then tried to do the transaction on the new node ( The connected one), I got the following response.

Did I miss anything on the permission side or have to pass any command to import the address to the new node?

The response is as below

code: -709
message: "from-address is not found in this wallet"
success: false

Doubts about Node Clustering

Fri, 15 May 2020 15:46:20 +0000

Hi, I have several questions about node grouping at Multichain.

Reading the documentation on this topic, I understand that we must manually add the address that is generated in the main node, that also applies to transactions of the addresses? We need to import manually the transactions on the replica node?

For example; the cluster has two nodes, one main and another replica for backup if the first fails, in the event that the first node fails and the second is used as a backup, if the addresses are imported in the replica node the transactions will also be?

Another question, if I have a cluster of nodes and the main node goes down, then I must manually connect the replica node from my custom API created in PHP?

First of all, Thanks

multichain connecting seed node issue.

Mon, 17 Feb 2020 09:09:04 +0000

Hii there

I am new to multichain as I am able to connect second node through the same system but when i am trying to connect it through another system I get an error

"Couldn't connect to the seed node id: on port *** -please check multichain is running at the same address and that your firewall settings allow the incoming connection."

I have opened the port in both the systems. closed the firewall too.but then also I am getting the same issue.

please if anyone can help on this.

cant connect nodes

Fri, 22 Nov 2019 03:35:26 +0000

Ran through the MultiChain getting started guide and got stuck connecting my nodes in Google Cloud; what am I doing wrong?

node: gravid1

Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.15.0-1049-gcp x86_64)
* Documentation: https://help.ubuntu.com
* Management:     https://landscape.canonical.com
* Support:        https://ubuntu.com/advantage
0 packages can be updated.
0 updates are security updates.
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
hectortorres5123@instance-3:~$
hectortorres5123@instance-3:~$ sudo -i
root@instance-3:~# passwd
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
root@instance-3:~# cd /tmp
root@instance-3:/tmp# wget https://www.multichain.com/download/multichain-2.0.3.tar.gz
--2019-11-16 14:01:13-- https://www.multichain.com/download/multichain-2.0.3.tar.gz
Resolving www.multichain.com (www.multichain.com)... 162.243.214.85
Connecting to www.multichain.com (www.multichain.com)|162.243.214.85|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 24227320 (23M) [application/x-gzip]
Saving to: ‘multichain-2.0.3.tar.gz’
multichain-2.0.3.tar.g 100%[============================>] 23.10M 10.6MB/s    in 2.2s
2019-11-16 14:01:16 (10.6 MB/s) - ‘multichain-2.0.3.tar.gz’ saved [24227320/24227320]
root@instance-3:/tmp# tar -xvzf nultichain-2.0.3.tar.gz
tar (child): nultichain-2.0.3.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
root@instance-3:/tmp# tar -xvzf multichain-2.0.3.tar.gz
multichain-2.0.3/
multichain-2.0.3/multichain-util
multichain-2.0.3/multichain-cli
multichain-2.0.3/README.txt
multichain-2.0.3/multichaind
multichain-2.0.3/multichaind-cold
root@instance-3:/tmp# cd multichain-2.0.3
root@instance-3:/tmp/multichain-2.0.3# mv multichaind multichain-cli multichain-util /usr/local/bin
root@instance-3:/tmp/multichain-2.0.3# exit
logout
hectortorres5123@instance-3:~$
hectortorres5123@instance-3:~$ multichain-util create gravid1
MultiChain 2.0.3 Utilities (latest protocol 20011)
Blockchain parameter set was successfully generated.
You can edit it in /home/hectortorres5123/.multichain/gravid1/params.dat before running multichaind for the first time.

To generate blockchain please run "multichaind gravid1 -daemon".
hectortorres5123@instance-3:~$ multichaind gravid1 -daemon

MultiChain 2.0.3 Daemon (Community Edition, latest protocol 20011)

Starting up node...

Looking for genesis block...
Genesis block found

Other nodes can connect to this node using:
multichaind gravid1@10.128.0.4:8369

Listening for API requests on port 8368 (local only - see rpcallowip setting)

Node ready.

hectortorres5123@instance-3:~$
hectortorres5123@instance-3:~$ multichaind multichaind gravid2@10.128.0.3:6461

MultiChain 2.0.3 Daemon (Community Edition, latest protocol 20011)

ERROR: Parameter set for blockchain multichaind is not complete.

If you want to create new blockchain please run one of the following:

  multichain-util create multichaind
  multichain-util clone <old-blockchain-name> multichaind

And rerun multichaind multichaind

If you want to connect to existing blockchain please specify seed node:

  multichaind multichaind@<seed-node-ip>
  multichaind multichaind@<seed-node-ip>:<seed-node-port>

node: gravid2

Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.15.0-1049-gcp x86_64)

* Documentation: https://help.ubuntu.com
* Management:     https://landscape.canonical.com
* Support:        https://ubuntu.com/advantage

* Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
   Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

     https://ubuntu.com/kubernetes/docs/release-notes

0 packages can be updated.
0 updates are security updates.

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

hectortorres5123@instance-2:~$ multichaind multichaind gravid1@10.128.0.4:8369
multichaind: command not found
hectortorres5123@instance-2:~$ multichaind multichaind gravid1@10.128.0.4:8369
multichaind: command not found
hectortorres5123@instance-2:~$ multichaind gravid1@10.128.0.4:8369
multichaind: command not found
hectortorres5123@instance-2:~$ multichaind multichaind gravid1@10.128.0.4:8369
multichaind: command not found
hectortorres5123@instance-2:~$ sudo -i
root@instance-2:~# password
No command 'password' found, did you mean:
Command 'assword' from package 'assword' (universe)
password: command not found
root@instance-2:~# passwd
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
root@instance-2:~# su
root@instance-2:~#
root@instance-2:~# cd /tmp
root@instance-2:/tmp# wget https://www.multichain.com/download/multichain-2.0.3.tar.gz
--2019-11-16 14:07:49-- https://www.multichain.com/download/multichain-2.0.3.tar.gz
Resolving www.multichain.com (www.multichain.com)... 162.243.214.85
Connecting to www.multichain.com (www.multichain.com)|162.243.214.85|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 24227320 (23M) [application/x-gzip]
Saving to: ‘multichain-2.0.3.tar.gz’

multichain-2.0.3.tar.gz                           100%[==========================================================================================================>] 23.10M 10.8MB/s    in 2.1s

2019-11-16 14:07:51 (10.8 MB/s) - ‘multichain-2.0.3.tar.gz’ saved [24227320/24227320]

root@instance-2:/tmp# tar -xvzf multichain-2.0.3.tar.gz
multichain-2.0.3/
multichain-2.0.3/multichain-util
multichain-2.0.3/multichain-cli
multichain-2.0.3/README.txt
multichain-2.0.3/multichaind
multichain-2.0.3/multichaind-cold
root@instance-2:/tmp# cd multichain-2.0.3
root@instance-2:/tmp/multichain-2.0.3# mv multichaind multichain-cli multichain-util /usr/local/bin
root@instance-2:/tmp/multichain-2.0.3# multichain-util create gravid2

MultiChain 2.0.3 Utilities (latest protocol 20011)

Blockchain parameter set was successfully generated.
You can edit it in /root/.multichain/gravid2/params.dat before running multichaind for the first time.

To generate blockchain please run "multichaind gravid2 -daemon".
root@instance-2:/tmp/multichain-2.0.3# multichaind gravid2 -daemon

MultiChain 2.0.3 Daemon (Community Edition, latest protocol 20011)

Starting up node...

Looking for genesis block...
Genesis block found

Other nodes can connect to this node using:
multichaind gravid2@10.128.0.3:6461

Listening for API requests on port 6460 (local only - see rpcallowip setting)

Node ready.

root@instance-2:/tmp/multichain-2.0.3# multichaind multichaind gravid1@10.128.0.4:8369

MultiChain 2.0.3 Daemon (Community Edition, latest protocol 20011)

ERROR: Parameter set for blockchain multichaind is not complete.

If you want to create new blockchain please run one of the following:

  multichain-util create multichaind
  multichain-util clone <old-blockchain-name> multichaind

And rerun multichaind multichaind

If you want to connect to existing blockchain please specify seed node:

  multichaind multichaind@<seed-node-ip>
  multichaind multichaind@<seed-node-ip>:<seed-node-port>

root@instance-2:/tmp/multichain-2.0.3#

Two nodes on one host

Wed, 19 Jun 2019 03:30:54 +0000

Is there any way to run two nodes on one host just like bitcoin?

Is it required to have more than one node?

Mon, 29 Apr 2019 21:00:28 +0000

Hi, in doc example is required to have 2 nodes. Can I have a blockchain with only one node? What is the difference one node or multiply nodes?

Blockchain stops working with 3 nodes using a stream with 2M transactions

Thu, 07 Mar 2019 16:26:18 +0000

I have the following scenario:

1 node that created the blockchain and a stream, which I used to create a stream and add 2M items into it, with random off-chain content (images).
2 nodes that join the blockchain after all the data has been imported through the master node, so on startup they begin to catch up with the master node at their own pace.

At the very beginning when the 2 new joined nodes are initially catching up, I can issue commands to any of the 3 nodes using the multichain-cli tool. For instance, I send this command to the master node and I get the reply back immediately:

multichain-cli ipregister -rpcuser=multichainrpc -rpcpassword=m4lt1ch41nRpC! getaddresses
{"method":"getaddresses","params":[],"id":"85616894-1551974478","chain_name":"ipregister"}
[
"1WTvECnAdMgvXDqMDQeiwXExCfvvMuHwq1HR7S"
]

However, at some point in time, when the volume of data being already synced up grows, the multichain-cli tool stops responding for all the nodes, and as the volume of synced data still grows, the nodes start to degrade dramatically until they just do not respond to commands.

Both 2 nodes join the blockchain through the DNS name of the master and they just subscribe to the stream to be able to find data by key, that's all.

Then I stop everything (without deleting the data) and restart first the master node. It starts to respond again to multichain-cli commands. But when I start again the first of the 2 additional nodes, I start getting this from it:

Node started
mchn: Sending minimal parameter set to 174.16.60.237:8099
receive version message: /MultiChain:0.2.0.6/: version 70002, blocks=28632, us=174.16.138.178:50952, peer=1
Added time data, samples 2, offset +0 (+0 minutes)
mchn: Parameter set from peer=1 verified
Loading addresses from DNS seeds (could take a while)
0 addresses found from DNS seeds
dnsseed thread exit
socket sending timeout: 61s

And then in the master:

Sending minimal parameter set to 174.16.138.178:50952
receive version message: /MultiChain:0.2.0.6/: version 70002, blocks=28627, us=174.16.60.237:8099, peer=7
Added time data, samples 3, offset +0 (+0 minutes)
mchn: Parameter set from peer=7 verified
ResendWalletTransactions()
Sending minimal parameter set to 174.16.138.178:8099
receive version message: /MultiChain:0.2.0.6/: version 70002, blocks=28627, us=174.16.60.237:58276, peer=12
mchn: Parameter set from peer=12 verified

Clearly, the 2nd node degrades just after joining again the blockchain. If I join the 3rd node it gets even worse.

how to create a node which can connect to an existing node .

Tue, 05 Feb 2019 17:51:26 +0000

how to create a node which can connect to an existing node . I want all the nodes to sync at the same time and all transactions should be present on all the nodes. In order to create a cluster of nodes for better reliability.

Can you tell me how to clone a node and how two nodes will communicate to each other.?

Timeout downloading block from peer, disconnecting

Wed, 30 Jan 2019 09:24:29 +0000

Hi,

I have a master node with 900+ blocks. Now I try to connect a new node, but when it starts syncing up with the master, it disconnects after some blocks complaining about a timeout:

receive version message: /MultiChain:0.2.0.6/: version 70002, blocks=959, us=174.16.213.31:53738, peer=2
Added time data, samples 2, offset +0 (+0 minutes)
mchn: Parameter set from peer=2 verified
Pre-allocating up to position 0x100000 in rev00000.dat
UpdateTip: new best=00f4c23c213136008518e74414f17605c024ad3cf34d81cb53f8130266ee815b height=1 log2_work=9 tx=2 date=2019-01-28 08:48:07 progress=1.000000 cache=0
UpdateTip: new best=0000b25e3031363046cc69e138f209868484bbd15f6fee3f0dc42b5f51be3565 height=2 log2_work=9.5849625 tx=3 date=2019-01-28 08:48:08 progress=1.000000 cache=0
...
...
UpdateTip: new best=00113d9451141fc321bc88e5bc2f2388580f683fa3c9af4705a754485c3fbdac height=126 log2_work=14.988685 tx=1284 date=2019-01-28 14:10:10 progress=1.000000 cache=0
UpdateTip: new best=005f0110f6d32bf8e68a9598dd7533852a30cff92ec65341e25e55149f976eff height=127 log2_work=15 tx=1540 date=2019-01-28 14:10:14 progress=1.000000 cache=0
UpdateTip: new best=00f59a8a840365aa1c3bac5fe717753c07f4cf27f6e95926423531ab33488af8 height=128 log2_work=15.011227 tx=1760 date=2019-01-28 14:10:16 progress=1.000000 cache=0
ResendWalletTransactions()
UpdateTip: new best=008a866cb66d2f98894fd98ebe2b7eb78f5d9ff5460d6e723ef0db38ba6757f2 height=129 log2_work=15.022368 tx=1908 date=2019-01-28 14:10:18 progress=1.000000 cache=0
UpdateTip: new best=00e7442c16a2008681791394d95966db86e5155cee8668ff25566c332953d6f0 height=130 log2_work=15.033423 tx=2015 date=2019-01-28 14:10:20 progress=1.000000 cache=0
UpdateTip: new best=0012883f0df88e470804ec4f5aefe78fbbfd0ced34b02737a321bb496b0f63d2 height=131 log2_work=15.044394 tx=2112 date=2019-01-28 14:10:23 progress=1.000000 cache=0
UpdateTip: new best=00d26a69b99e592f5687a8704a217b87be3516f4f72dfdb80d734d939aa52663 height=132 log2_work=15.055282 tx=2273 date=2019-01-28 14:10:25 progress=1.000000 cache=0
UpdateTip: new best=00a163113a22b08250698cd44280b44e4a7f952ddf9dbb9aa33f88a8c57741d9 height=133 log2_work=15.066089 tx=2410 date=2019-01-28 14:10:27 progress=1.000000 cache=0
UpdateTip: new best=006862bab537d132727e6abc9f1adef8e2520c9d26d5d1f5f727d7ab24f4e8b4 height=134 log2_work=15.076816 tx=2521 date=2019-01-28 14:10:28 progress=1.000000 cache=0
UpdateTip: new best=00c77418d1248a4118363b5df2c620023d2e3fd28ed6b83f3366eeed99a04118 height=135 log2_work=15.087463 tx=2613 date=2019-01-28 14:10:30 progress=1.000000 cache=0
ResendWalletTransactions()
UpdateTip: new best=0081d6e61d0b716b1b318ddd48260d1c620be5b100fdad271e2732311fe7b049 height=136 log2_work=15.098032 tx=2789 date=2019-01-28 14:10:33 progress=1.000000 cache=0
Timeout downloading block 00e9dfcfc91067a07d32a80e241d944089d33a5aeea12335422970dd270dcbe1 from peer=2, disconnecting

What is this timeout about? Why does it happen? Is there any parameter that allows me to increase such timeout?

Thanks!

Can't connect two nodes on different networks

Fri, 14 Sep 2018 14:46:38 +0000

I'm creating a chain using multichain-util, setting a username and password in multichain.conf, and then starting the daemon using multichaind chainname -rpcallowip=0.0.0.0/0 -daemon.

I receive the following output:

Starting up node...

Other nodes can connect to this node using:

multichaind chainname@172.20.10.0:7217

Node ready.

When trying to use multichaind chainname@172.20.10.0:7217 -rpcport=7216 -rpcuser=multichainrpc -multichainpass=pass from another computer I receive:

Error: Couldn't connect to the seed node 172.20.10.0 on port 7217 - please check multichaind is running at that address and that your firewall settings allow incoming connections.

I have tried turning firewalls off to no success. I can create two nodes and connect them successfully when they are using the same internet connection, but can't find what the problem is here.

Cannot connect to Multichain ran inside Docker

Thu, 13 Sep 2018 14:07:04 +0000

I have created a Dockerfile to run a blockchain within a Docker container. The chain is created successfully, and multichaind ran, which gives an output of:

Other nodes can connect to this node using:

multichaind dockChain2@172.17.0.2:5001

Listening for API requests on port 5002 (local only - see rpcallowip setting)

When trying to connect from another node the error received is -

Error: Couldn't connect to the seed node 172.17.0.2 on port 5001 - please check multichaind is running at that address and that your firewall settings allow incoming connections.

I have tried exposing port 5001 in docker, and using docker ps -a shows 0.0.0.0:5001->5001/tcp under PORTS.

Seeder for the network

Wed, 25 Apr 2018 18:58:41 +0000

I want to set up a DNS seed for my multichain network, since I don't want to specify the IP to which a new node should connect every time I spin up a new node.

Do I have to use a seeder like https://github.com/sipa/bitcoin-seeder to be running on my DNS server or?
I know it's not a Multichain-related question, but I could use any help/tutorial link/hint that you could provide!

P.S. I'm doing my thesis using Multichain, so you will be helping a student in need! :)

Stopping A Node

Sun, 01 Apr 2018 12:34:28 +0000

This might seem like a dumb question but I just want to be sure. So I have two nodes connected to each other on the same server. The first node is the one that created the blockchain. If I stop it using the command:

>sudo multichain-cli [chain-name] stop

Will that automatically kill all the other nodes created afterwards that are connected to the blockchain as well? Also is it possible to stop one node without stopping the entire blockchain and the other nodes connected to it?

Can't connect cli from other connected node

Wed, 21 Mar 2018 11:13:21 +0000

Hi,

I'm trying to connect CLI from connected node, am getting the following error.

https://ibb.co/n3nMuc

(Please check the above link, attached the screen shot)

Is there any parameter should pass along with the command. (multichain-cli chain1 )

Thanks

Shiva,P

Sending signed transaction in to several nodes at once

Thu, 30 Nov 2017 14:02:42 +0000

And what will happen, if I sign a transaction outside of Multichain, and then send it simultaneously in to several nodes. It will makes a double spending as well or not ?

I'm asking because interested to make a scenario, when several Multichain nodes working across the globe, and users connects to the less loaded node. On a round-robin scenario basis.

But what will happens, in case if a "bad-guy" send same signed transactions to all of this nodes. It will lead to a double-spend as well, or Multichain will take the first transaction only and cancel all others ?

Thank you!

Transferring partially signed transactions

Tue, 17 Oct 2017 11:09:00 +0000

Hi guys,

I'm interesting in multisig and have a question about it.

Is there any built in way for transferring partially signed transactions between participants? Or what is the recommended approach for doing this?

retrieve a list of pending rawtransactions to be signed

Fri, 08 Sep 2017 10:04:04 +0000

I'm trying to wrap my head around multisignature addresses. In the terminal it's very easy, but the thing I don't understand yet is how, for example, an app running on a second server is supposed to retrieve the pending transactions that needs to be signed.

Is there a way to retrieve these transactions?

Couldn't connect to the seed node error on Ubuntu AWS EC2

Sat, 26 Aug 2017 19:06:00 +0000

I have our chain running for a few weeks now with 4 nodes. I can fire up new nodes on my AWS account and be connected and running in a few minutes. I can do this repeatedly with zero issues. I've launched, connected and mined with hundreds of testing nodes by now.

However, when ANY other server outside my AWS account tries to connect to our chain they get the same problem here:

https://www.multichain.com/qa/3381/couldnt-connect-to-the-seed-node-error-on-ubuntu-aws-ec2

I ran multichaind -debug=mchn -debug=mchnminor -debug=net on our chain but I don't see anything in the debug.log file at the timestamp when I try to connect.

Here's all I see around that time stamp on the debug.log

2017-08-26 19:03:42 (8 bytes) peer=1
2017-08-26 19:03:42 mchn: RECV: pong, peer=1
2017-08-26 19:03:42 received: pong (8 bytes) peer=1
2017-08-26 19:03:43 mchn: RECV: ping, peer=2
2017-08-26 19:03:43 received: ping (8 bytes) peer=2
2017-08-26 19:03:43 sending: pong mchn: SEND: pong
2017-08-26 19:03:43 (8 bytes) peer=2
2017-08-26 19:03:43 sending: ping mchn: SEND: ping
2017-08-26 19:03:43 (8 bytes) peer=2
2017-08-26 19:03:43 mchn: RECV: pong, peer=2
2017-08-26 19:03:43 received: pong (8 bytes) peer=2
2017-08-26 19:03:44 mchn: RECV: ping, peer=3
2017-08-26 19:03:44 received: ping (8 bytes) peer=3
2017-08-26 19:03:44 sending: pong mchn: SEND: pong
2017-08-26 19:03:44 (8 bytes) peer=3
2017-08-26 19:03:44 sending: ping mchn: SEND: ping
2017-08-26 19:03:44 (8 bytes) peer=3
2017-08-26 19:03:44 mchn: RECV: pong, peer=3
2017-08-26 19:03:44 received: pong (8 bytes) peer=3
2017-08-26 19:03:52 mchn: RECV: ping, peer=1
2017-08-26 19:03:52 received: ping (8 bytes) peer=1
2017-08-26 19:03:52 sending: pong mchn: SEND: pong
2017-08-26 19:03:52 (8 bytes) peer=1
2017-08-26 19:03:52 sending: ping mchn: SEND: ping
2017-08-26 19:03:52 (8 bytes) peer=1
2017-08-26 19:03:52 mchn: RECV: pong, peer=1
2017-08-26 19:03:52 received: pong (8 bytes) peer=1
2017-08-26 19:03:53 mchn: RECV: ping, peer=2
2017-08-26 19:03:53 received: ping (8 bytes) peer=2
2017-08-26 19:03:53 sending: pong mchn: SEND: pong
2017-08-26 19:03:53 (8 bytes) peer=2
2017-08-26 19:03:53 sending: ping mchn: SEND: ping
2017-08-26 19:03:53 (8 bytes) peer=2

Could this be something simple I'm using in security settings on AWS? I can connect nodes from inside my own AWS account but no one else can connect. All get the same error. The ports are wide open too.

Ideas?

Can transactions still be signed by addresses on a down server?

Wed, 24 May 2017 01:28:09 +0000

Hi, I'm wondering that, in case of a server downtime, can transactions still be signed/sent from addresses that are generated on the down server?

Thanks!

Transact on another node

Wed, 03 May 2017 04:58:18 +0000

Hi,

Can I make a transaction on a different node from which the transacting address exists? For instance, two nodes A and B each with addresses having some assets. Can i transfer an address's assets from node B if the address was generated in node A.

I know the answer is No and one reason why is because the private key for the addresses are stored on their node. I am looking for additional reasons if there is as well as how to go around this for instance if I have the address, public key and private key copied to a file, and the node goes down, can i transfer the assets owned by that address from a different node?

Thanks.

R

Maximum (recommended) nodes on a server

Thu, 27 Apr 2017 16:58:56 +0000

I know that if you use the datadir option and a different JSON-RPC port and peer-to-peer port for each node you can run multiple nodes on a single machine. Is there a recommended limit to the number of nodes one can or should run on a single machine before the performance starts to degrade? I can appreciate that this may be subjective because it is likely based on the specs of the machine and various other factors, but I'm wondering if you guys have tested this at all. Thanks!