New answers tagged

0

You can run a C-lightning instance on top of a pruned bitcoind. You can also opt in to a different Bitcoin backend than bitcoind by using a plugin. For instance the Sauron plugin connects to an Esplora instance, this is a more lightweight way to get started albeit you are trusting whoever operates the API. A lightweight solution seems appropriate for testnet ...


1

I am thinking of running my own lightning node in testnet. Going through the tutorials it seems the lightning node needs to be connected to bitcoin node inorder to get connected to bitcoin network. But running a full bitcoin node like bitcoind seems out of my scope as I don't want invest and maintain it. A Bitcoin testnet node block chain occupies less than ...


4

Regtest was added in version 0.9.0 which was released in March 2014 Add '-regtest' mode, similar to testnet but private with instant block generation with 'setgenerate' RPC. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.9.0.md Testnet's history: Has the TestNet ever been reset? There is one more chain which is used for ...


1

There is currently no realm byte defined for testnet and signet. At least lseed.bitcoinstats.com and lseed.darosior.ninja don't support testnet nor signet.


2

It is absolutely possible, running parallel networks will be even added as a GUI option in the next RaspiBlitz release (FOSS bitcoin - lightning node package) which will also make C-lightning available. See the issue about the parallel networks: https://github.com/rootzoll/raspiblitz/issues/2290 Here is a screenshot demonstrating running 5 LN nodes (3 C-...


3

This was answered by individuals on IRC. It is perfectly fine to run any number of c-lightning nodes for any combination of networks as long as you keep home directories (--lightning-dir) and (--bind-addr, --addr) bindings distinct. For different networks (i.e. mainnet, testnet, signet etc) c-lightning already has subdirectories so there is no need to ...


Top 50 recent answers are included