Constants§
- FM_
BITCOIND_ PASSWORD_ ENV - FM_
BITCOIND_ URL_ ENV - FM_
BITCOIND_ USERNAME_ ENV - FM_
DB_ BACKEND_ ENV - Environment variable to select database backend (rocksdb or cursed-redb)
- FM_
DEBUG_ GATEWAY_ ENV - Environment variable that instructs the gateway to run in “debug mode”, which allows errors to return to clients without redacting private information.
- FM_
ESPLORA_ URL_ ENV - FM_
GATEWAY_ API_ ADDR_ ENV - Environment variable that specifies the URL that clients can use to make requests to the gateway.
- FM_
GATEWAY_ BCRYPT_ PASSWORD_ HASH_ ENV - Environment variable that specifies the bcrypt password hash.
- FM_
GATEWAY_ DATA_ DIR_ ENV - Environment variable that specifies the directory of the gateway’s database.
- FM_
GATEWAY_ LIGHTNING_ MODULE_ MODE_ ENV - Environment variable that specifies the “module mode” the gateway should run in. Options are “LNv1”, “LNv2”, or “All”. It is not recommended to run “All” in production so that clients are not able to use the same gateway to create LNv1 and LNv2 invoices.
- FM_
GATEWAY_ LISTEN_ ADDR_ ENV - Environment variable that specifies the address the gateway’s HTTP server should listen on.
- FM_
GATEWAY_ MNEMONIC_ ENV - Environment variable that specifies the mnemonic that the gateway should use for ecash and the LDK Node should use for onchain funds. If not set, a mnemonic will be generated. This environment variable can be used for recovering from an existing mnemonic.
- FM_
GATEWAY_ NETWORK_ ENV - Environment variable that specifies that Bitcoin network that the gateway should use. Must match the network of the Lightning node.
- FM_
GATEWAY_ OVERRIDE_ LN_ MODULE_ CHECK_ ENV - Environment variable that instructs the gateway to skip checking if the
Bitcoin network is set to mainnet and the lightning module mode is set to
All
- FM_
GATEWAY_ SKIP_ WAIT_ FOR_ SYNC_ ENV - Environment variable that instructs the gateway to skip waiting for the bitcoin node to sync to the chain.
- FM_
NUMBER_ OF_ ROUTE_ HINTS_ ENV - Environment variable that instructs the gateway how many route hints to include in LNv1 invoices.