[Feature Request] Support more signet networks #3078
Assignees
Comments
|
That sounds reasonable, and should be simple enough to do! @remyers can you add this to your backlog? |
remyers
added a commit
to remyers/eclair
that referenced
this issue
May 19, 2025
This change enables custom signets by allowing the user to specify the txid of a transaction to check or "" to skip this check for signet. See issue ACINQ#3078.
remyers
added a commit
to remyers/eclair
that referenced
this issue
May 19, 2025
remyers
added a commit
that referenced
this issue
May 20, 2025
This change enables custom signets by allowing the user to specify the txid of a transaction to check or "" to skip this check for signet. See issue #3078.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During elcair's startup a check is made against the bitcoind instance to verify it is using the expected network by looking up a hardcoded transaction that exists for the given network. This seems fine for mainnet and testnets where they are defined by bitcoin conf itself. For signets, however, this causes challenges as its more common for someone to spin up their own signet for testing and thus wont be able to run eclair against it (since the transaction wont exist on their custom signet). For example, having this network check not be configurable for signet stops anyone from running eclair against mutinynet. Goal of this feature would be to allow the node runner the ability to use any signet they choose.
eclair/eclair-core/src/main/scala/fr/acinq/eclair/Setup.scala
Line 164 in 826284c
The text was updated successfully, but these errors were encountered: