It’s completely doable, operating parallel networks can be even added as a GUI possibility within the subsequent RaspiBlitz launch (FOSS bitcoin – lightning node bundle) which will even make C-lightning obtainable.
See the difficulty in regards to the parallel networks:
https://github.com/rootzoll/raspiblitz/points/2290
Here’s a screenshot demonstrating operating 5 LN nodes (3 C-lightning, 2 LND) on the three Bitcoin networks (mainnet, testnet and signet) on the identical machine:
https://twitter.com/openoms/standing/1397187128136802326
For LND have to rigorously specify the ZMQ ports to not combine the block hashes of the networks through:
important.zmqpubrawblock=tcp://127.0.0.1:28332
important.zmqpubrawtx=tcp://127.0.0.1:28333
and for instance:
check.zmqpubrawblock=tcp://127.0.0.1:21332
check.zmqpubrawtx=tcp://127.0.0.1:21333
within the bitcoin.conf.
The Bitcoin Core, Lightningd and LND binaries will be the identical, however – if utilizing systemd – totally different providers are the most effective for use for the particular community situations.
I discovered utilizing one bitcoin.conf file is enough (as ports will be set with the community prefixes), however the LN implementations ought to have their devoted config recordsdata per occasion.
Because it was talked about C-lightning makes this straightforward by having totally different directories for every community by default.