Advertisement
Guest User

Untitled

a guest
Jul 1st, 2018
556
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.91 KB | None | 0 0
  1. [Application Options]
  2.  
  3. ; The directory that lnd stores all wallet, chain, and channel related data
  4. ; within The default is ~/.lnd/data on POSIX OSes, $LOCALAPPDATA/Lnd/data on
  5. ; Windows, ~/Library/Application Support/Lnd/data on Mac OS, and $home/lnd/data
  6. ; on Plan9. Environment variables are expanded so they may be used. NOTE:
  7. ; Windows environment variables are typically %VARIABLE%, but they must be
  8. ; accessed with $VARIABLE here. Also, ~ is expanded to $LOCALAPPDATA on Windows.
  9. ; datadir=~/.lnd/data
  10.  
  11. ; The directory that logs are stored in. The logs are auto-rotated by default.
  12. ; Rotated logs are compressed in place.
  13. ; logdir=~/.lnd/logs
  14.  
  15. ; Path to TLS certificate for lnd's RPC and REST services.
  16. ; tlscertpath=~/.lnd/tls.cert
  17.  
  18. ; Path to TLS private key for lnd's RPC and REST services.
  19. ; tlskeypath=~/.lnd/tls.key
  20.  
  21. ; Disable macaroon authentication. Macaroons are used are bearer credentials to
  22. ; authenticate all RPC access. If one wishes to opt out of macaroons, uncomment
  23. ; the line below.
  24. ; no-macaroons=true
  25.  
  26. ; Path to write the admin macaroon for lnd's RPC and REST services if it
  27. ; doesn't exist. This can be set if one wishes to store the admin macaroon in a
  28. ; distinct location. By default, it is stored within lnd's main home directory.
  29. ; Applications that are able to read this file, gains admin macaroon access
  30. ; adminmacaroonpath=~/.lnd/admin.macaroon
  31.  
  32. ; Path to write the read-only macaroon for lnd's RPC and REST services if it
  33. ; doesn't exist. This can be set if one wishes to store the read-only macaroon
  34. ; in a distinct location. The read only macaroon allows users which can read
  35. ; the file to access RPC's which don't modify the state of the daemon.
  36. ; readonlymacaroonpath=~/.lnd/readonly.macaroon
  37.  
  38.  
  39. ; Specify the interfaces to listen on for p2p connections. One listen
  40. ; address per line.
  41. ; All ipv4 on port 9735:
  42. listen=0.0.0.0:9735
  43. ; On all ipv4 interfaces on port 9735 and ipv6 localhost port 9736:
  44. ; listen=0.0.0.0:9735
  45. ; listen=[::1]:9736
  46.  
  47. ; Disable listening for incoming p2p connections. This will override all
  48. ; listeners.
  49. ; nolisten=1
  50.  
  51. ; Specify the interfaces to listen on for gRPC connections. One listen
  52. ; address per line.
  53. ; Only ipv4 localhost on port 10009:
  54. ; rpclisten=localhost:10009
  55. ; On ipv4 localhost port 10009 and ipv6 port 10010:
  56. ; rpclisten=localhost:10009
  57. ; rpclisten=[::1]:10010
  58.  
  59. ; Specify the interfaces to listen on for REST connections. One listen
  60. ; address per line.
  61. ; All ipv4 interfaces on port 8080:
  62. ; restlisten=0.0.0.0:8080
  63. ; On ipv4 localhost port 80 and 443:
  64. ; restlisten=localhost:80
  65. ; restlisten=localhost:443
  66.  
  67.  
  68. ; Adding an external IP will advertise your node to the network. This signals
  69. ; that your node is available to accept incoming channels. If you don't wish to
  70. ; advertise your node, this value doesn't need to be set.
  71. ; externalip=
  72.  
  73.  
  74. ; Debug logging level.
  75. ; Valid levels are {trace, debug, info, warn, error, critical}
  76. ; You may also specify <subsystem>=<level>,<subsystem2>=<level>,... to set
  77. ; log level for individual subsystems. Use btcd --debuglevel=show to list
  78. ; available subsystems.
  79. debuglevel=info
  80. ;debuglevel=CRTR=error,ATPL=debug,CMGR=debug
  81.  
  82. ; Write CPU profile to the specified file.
  83. ; cpuprofile=
  84.  
  85. ; Enable HTTP profiling on given port -- NOTE port must be between 1024 and
  86. ; 65536. The profile can be access at: http://localhost:<PORT>/debug/pprof/.
  87. ; profile=
  88.  
  89. ; The maximum number of incoming pending channels permitted per peer.
  90. ; maxpendingchannels=1
  91.  
  92. ; The default number of confirmations a channel must have before it's considered
  93. ; open. We'll require any incoming channel requests to wait this many
  94. ; confirmations before we consider the channel active.
  95. ; defaultchanconfs=3
  96.  
  97. ; If true, then automatic network bootstrapping will not be attempted. This
  98. ; means that your node won't attempt to automatically seek out peers on the
  99. ; network.
  100. nobootstrap=0
  101.  
  102. ; If set, your wallet will be encrypted with the default passphrase. This isn't
  103. ; recommend, as if an attacker gains access to your wallet file, they'll be able
  104. ; to decrypt it. This value is ONLY to be used in testing environments.
  105. ; noencryptwallet=1
  106.  
  107. ; The alias your node will use, which can be up to 32 UTF-8 characters in
  108. ; length.
  109. ; alias=My Lightning ☇
  110.  
  111. ; The color of the node in hex format, used to customize node appearance in
  112. ; intelligence services.
  113. ; color=#3399FF
  114.  
  115.  
  116. [Bitcoin]
  117.  
  118. ; If the Bitcoin chain should be active. Atm, only a single chain can be
  119. ; active.
  120. bitcoin.active=1
  121.  
  122. ; Use Bitcoin's test network.
  123. bitcoin.testnet=1
  124. ;
  125. ; Use Bitcoin's simulation test network
  126. ; bitcoin.simnet=1
  127.  
  128. ; Use Bitcoin's regression test network
  129. ; bitcoin.regtest=false
  130.  
  131. ; Use the btcd back-end
  132. bitcoin.node=btcd
  133.  
  134. ; Use the bitcoind back-end
  135. ; bitcoin.node=bitcoind
  136.  
  137. ; Use the neutrino (light client) back-end
  138. ; bitcoin.node=neutrino
  139.  
  140.  
  141. [Btcd]
  142.  
  143. ; The host that your local btcd daemon is listening on. By default, this
  144. ; setting is assumed to be localhost with the default port for the current
  145. ; network.
  146. ; btcd.rpchost=localhost
  147.  
  148. ; Username for RPC connections to btcd. By default, lnd will attempt to
  149. ; automatically obtain the credentials, so this likely won't need to be set
  150. ; (other than for simnet mode).
  151. ; btcd.rpcuser=kek
  152.  
  153. ; Password for RPC connections to btcd. By default, lnd will attempt to
  154. ; automatically obtain the credentials, so this likely won't need to be set
  155. ; (other than for simnet mode).
  156. ; btcd.rpcpass=kek
  157.  
  158. ; File containing the daemon's certificate file. This only needs to be set if
  159. ; the node isn't on the same host as lnd.
  160. ; btcd.rpccert=~/.btcd/rpc.cert
  161.  
  162. ; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
  163. ; to authenticate the RPC connection. This only needs to be set if the btcd
  164. ; node is on a remote host.
  165. ; btcd.rawrpccert=
  166.  
  167.  
  168. [Bitcoind]
  169.  
  170. ; The host that your local bitcoind daemon is listening on. By default, this
  171. ; setting is assumed to be localhost with the default port for the current
  172. ; network.
  173. ; bitcoind.rpchost=localhost
  174.  
  175. ; Username for RPC connections to bitcoind. By default, lnd will attempt to
  176. ; automatically obtain the credentials, so this likely won't need to be set
  177. ; (other than for a remote bitcoind instance).
  178. ; bitcoind.rpcuser=kek
  179.  
  180. ; Password for RPC connections to bitcoind. By default, lnd will attempt to
  181. ; automatically obtain the credentials, so this likely won't need to be set
  182. ; (other than for a remote bitcoind instance).
  183. ; bitcoind.rpcpass=kek
  184.  
  185. ; ZMQ socket which sends rawblock and (optionally) rawtx notifications from
  186. ; bitcoind. By default, lnd will attempt to automatically obtain this
  187. ; information, so this likely won't need to be set (other than for a remote
  188. ; bitcoind instance).
  189. ; bitcoind.zmqpath=tcp://127.0.0.1:18501
  190.  
  191.  
  192. [neutrino]
  193.  
  194. ; Connect only to the specified peers at startup. This creates a persistent
  195. ; connection to a target peer. This is recommended as there aren't many
  196. ; neutrino compliant full nodes on the test network yet.
  197. ; neutrino.connect=
  198.  
  199. ; Add a peer to connect with at startup.
  200. ; neutrino.addpeer=
  201.  
  202.  
  203. [Litecoin]
  204.  
  205. ; If the Litecoin chain should be active. Atm, only a single chain can be
  206. ; active.
  207. ; litecoin.active=1
  208.  
  209. ; Use Bitcoin's test network.
  210. ; litecoin.testnet=1
  211. ;
  212. ; Use Bitcoin's simulation test network
  213. litecoin.simnet=1
  214.  
  215. ; Use Bitcoin's regression test network
  216. ; litecoin.regtest=false
  217.  
  218. ; Use the ltcd back-end (marked as btcd). No other back-end type is currently
  219. ; supported for litecoin.
  220. litecoin.node=btcd
  221.  
  222.  
  223. [Ltcd]
  224.  
  225. ; The host that your local ltcd daemon is listening on. By default, this
  226. ; setting is assumed to be localhost with the default port for the current
  227. ; network.
  228. ; ltcd.rpchost=localhost
  229.  
  230. ; Username for RPC connections to ltcd. By default, lnd will attempt to
  231. ; automatically obtain the credentials, so this likely won't need to be set
  232. ; (other than for simnet mode).
  233. ; ltcd.rpcuser=kek
  234.  
  235. ; Password for RPC connections to ltcd. By default, lnd will attempt to
  236. ; automatically obtain the credentials, so this likely won't need to be set
  237. ; (other than for simnet mode).
  238. ; ltcd.rpcpass=kek
  239.  
  240. ; File containing the daemon's certificate file. This only needs to be set if
  241. ; the node isn't on the same host as lnd.
  242. ; ltcd.rpccert=~/.ltcd/rpc.cert
  243.  
  244. ; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
  245. ; to authenticate the RPC connection. This only needs to be set if the ltcd
  246. ; node is on a remote host.
  247. ; ltcd.rawrpccert=
  248.  
  249.  
  250. [autopilot]
  251.  
  252. ; If the autopilot agent should be active or not. The autopilot agent will
  253. ; attempt to automatically open up channels to put your node in an advantageous
  254. ; position within the network graph.
  255. ;autopilot.active=0
  256.  
  257. ; The maximum number of channels that should be created.
  258.  
  259. ; The fraction of total funds that should be committed to automatic channel
  260. ; establishment. For example 0.6 means that 60% of the total funds available
  261. ; within the wallet should be used to automatically establish channels. The total
  262. ; amount of attempted channels will still respect the maxchannels param.
  263.  
  264. [tor]
  265. ; The port that Tor's exposed SOCKS5 proxy is listening on. Using Tor allows
  266. ; outbound-only connections (listening will be disabled) -- NOTE port must be
  267. ; between 1024 and 65535
  268. ; tor.socks=9050
  269.  
  270. ; The DNS server as IP:PORT that Tor will use for SRV queries - NOTE must have
  271. ; TCP resolution enabled. The current active DNS sever for Testnet listening is
  272. ; nodes.lightning.directory
  273. ; tor.dns=nodes.lightning.directory
  274.  
  275. ; Enable Tor stream isolation by randomizing user credentials for each
  276. ; connection. With this mode active, each connection will use a new circuit.
  277. ; This means that multiple applications (other than lnd) using Tor won't be mixed
  278. ; in with lnd's traffic.
  279. ; tor.streamisolation=1
  280.  
  281. autopilot.active=1
  282. autopilot.maxchannels=3
  283. autopilot.allocation=0.5
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement