Eclair (French for Lightning) is a Scala implementation of the Lightning Network.
This software follows the Lightning Network Specifications (BOLTs). Other implementations include c-lightning, lnd, electrum, and rust-lightning.
Please see the latest release note for detailed information on BOLT compliance.
Eclair offers a feature-rich HTTP API that enables application developers to easily integrate.
For more information please visit the API documentation website.
Please visit our docs and wiki to find detailed instructions on how to configure yournode, connect to other nodes, open channels, send and receive payments, and more advanced scenario.
You will find detailed guides and frequently asked questions there.
Eclair needs a synchronized, segwit-ready, zeromq-enabled, wallet-enabled, non-pruning, tx-indexing Bitcoin Core node.
You must configure your Bitcoin node to use bech32
(segwit) addresses.If your wallet has "non-segwit UTXOs" (outputs that are neither p2sh-segwit
or bech32
), you must send them to a bech32
address before running eclair.
Run bitcoind with the following minimal bitcoin.conf
:
server=1
rpcuser=foo
rpcpassword=bar
txindex=1
zmqpubhashblock=tcp://127.0.0.1:29000
zmqpubrawtx=tcp://127.0.0.1:29000
Depending on the actual hardware configuration, it may be useful to provide increased dbcache
parameter value for faster verification and rpcworkqueue
parameter value for better handling of API requests on bitcoind
side.
# UTXO database cache size, in MiB
dbcache=2048
# Number of allowed pending RPC requests (default is 16)
rpcworkqueue=128
# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpcclienttimeout=30
Eclair is developed in Scala, a powerful functional language that runs on the JVM, and is packaged as a ZIP archive.
To run Eclair, you first need to install Java, we recommend that you use OpenJDK 11. Other runtimes also work, but we don't recommend using them.
Then download our latest release, unzip the archive and run the following command:
eclair-node-<version>-<commit_id>/bin/eclair-node.sh
You can then control your node via the eclair-cli or the API.
Eclair reads its configuration file, and write its logs, to ~/.eclair
by default.
To change your node's configuration, create a file named eclair.conf
in ~/.eclair
. Here's an example configuration file:
eclair.node-alias=eclair
eclair.node-color=49daaa
Here are some of the most common options:
name | description | default value |
---|---|---|
eclair.chain | Which blockchain to use: regtest, testnet or mainnet | mainnet |
eclair.server.port | Lightning TCP port | 9735 |
eclair.api.enabled | Enable/disable the API | false. By default the API is disabled. If you want to enable it, you must set a password. |
eclair.api.port | API HTTP port | 8080 |
eclair.api.password | API password (BASIC) | "" (must be set if the API is enabled) |
eclair.bitcoind.rpcuser | Bitcoin Core RPC user | foo |
eclair.bitcoind.rpcpassword | Bitcoin Core RPC password | bar |
eclair.bitcoind.zmqblock | Bitcoin Core ZMQ block address | "tcp://127.0.0.1:29000" |
eclair.bitcoind.zmqtx | Bitcoin Core ZMQ tx address | "tcp://127.0.0.1:29000" |
eclair.bitcoind.wallet | Bitcoin Core wallet name | "" |
Quotes are not required unless the value contains special characters. Full syntax guide here.
→ see here for more configuration options.
Eclair will use the default loaded Bitcoin Core wallet to fund any channels you choose to open.If you want to use a different wallet from the default one, you must set eclair.bitcoind.wallet
accordingly in your eclair.conf
.
Eclair will return BTC from closed channels to the wallet configured.Any BTC found in the wallet can be used to fund the channels you choose to open.
Some advanced parameters can be changed with java environment variables. Most users won't need this and can skip this section.
However, if you're seeing Java heap size errors, you can try increasing the maximum memory allocated to the JVM with the -Xmx
parameter.
You can for example set it to use up to 512 MB (or any value that fits the amount of RAM on your machine) with:
export JAVA_OPTS=-Xmx512m
datadir
is mandatory if you want to run several instances of eclair on the same machine. You will also have to change ports in eclair.conf
(see above).
name | description | default value |
---|---|---|
eclair.datadir | Path to the data directory | ~/.eclair |
eclair.printToConsole | Log to stdout (in addition to eclair.log) |
For example, to specify a different data directory you would run the following command:
eclair-node-<version>-<commit_id>/bin/eclair-node.sh -Declair.datadir=/tmp/node1
Eclair uses logback
for logging. To use a different configuration, and override the internal logback.xml, run:
eclair-node-<version>-<commit_id>/bin/eclair-node.sh -Dlogback.configurationFile=/path/to/logback-custom.xml
The files that you need to backup are located in your data directory. You must backup:
node_seed.dat
and channel_seed.dat
)eclair.sqlite.bak
under directory mainnet
, testnet
or regtest
depending on which chain you're running on)Your seeds never change once they have been created, but your channels will change whenever you receive or send payments. Eclair willcreate and maintain a snapshot of its database, named eclair.sqlite.bak
, in your data directory, and update it when needed. This file isalways consistent and safe to use even when Eclair is running, and this is what you should back up regularly.
For example, you could configure a cron
task for your backup job. Or you could configure an optional notification script to be called by eclair once a new database snapshot has been created, using the following option:
eclair.file-backup.notify-script = "/absolute/path/to/script.sh"
Make sure your script is executable and uses an absolute path name for eclair.sqlite.bak
.
Note that depending on your filesystem, in your backup process we recommend first moving eclair.sqlite.bak
to some temporary filebefore copying that file to your final backup location.
A Dockerfile image is built on each commit on docker hub for running a dockerized eclair-node.
You can use the JAVA_OPTS
environment variable to set arguments to eclair-node
.
docker run -ti --rm -e "JAVA_OPTS=-Xmx512m -Declair.api.binding-ip=0.0.0.0 -Declair.node-alias=node-pm -Declair.printToConsole" acinq/eclair
If you want to persist the data directory, you can make the volume to your host with the -v
argument, as the following example:
docker run -ti --rm -v "/path_on_host:/data" -e "JAVA_OPTS=-Declair.printToConsole" acinq/eclair
If you enabled the API you can check the status of eclair using the command line tool:
docker exec <container_name> eclair-cli -p foobar getinfo
For advanced usage, Eclair supports plugins written in Scala, Java, or any JVM-compatible language.
A valid plugin is a jar that contains an implementation of the Plugin interface, and a manifest entry for Main-Class
with the FQDN of the implementation.
Here is how to run Eclair with plugins:
eclair-node-<version>-<commit_id>/bin/eclair-node.sh <plugin1.jar> <plugin2.jar> <...>
Here are some plugins created by the eclair community.If you need support for these plugins, head over to their respective github repository.
Eclair is configured to run on mainnet by default, but you can still run it on testnet (or regtest): start your Bitcoin Node intestnet mode (add testnet=1
in bitcoin.conf
or start with -testnet
), and change Eclair's chain parameter and Bitcoin RPC port:
eclair.chain=testnet
eclair.bitcoind.rpcport=18332
You may also want to take advantage of the new configuration sections in bitcoin.conf
to manage parameters that are network specific,so you can easily run your bitcoin node on both mainnet and testnet. For example you could use:
server=1
txindex=1
[main]
rpcuser=<your-mainnet-rpc-user-here>
rpcpassword=<your-mainnet-rpc-password-here>
zmqpubhashblock=tcp://127.0.0.1:29000
zmqpubrawtx=tcp://127.0.0.1:29000
[test]
rpcuser=<your-testnet-rpc-user-here>
rpcpassword=<your-testnet-rpc-password-here>
zmqpubhashblock=tcp://127.0.0.1:29001
zmqpubrawtx=tcp://127.0.0.1:29001
Rainux早上留言说,CM的 5.0.7开始支持G1了,而且速度很快。这让我又痒痒了。看了眼xda,现在还是test1,得等等才能用。为了用的时候马上就能爽,于是又跑进eclair的代码里,寻找拼音检索的解决方案。 折腾了一天,得出的结论是: Eclair已经可以用email地址中@前的字符,以及nickname(编辑联系人时点more可以添加多个nickname)检索联系人; 所以,我认为结合
转自: http://blog.csdn.net/milo103/article/details/5175445 1、Git的安装 sudo apt-get install git-core 2、安装Repo 2.1首先确保在当前用户的主目录下创建一个~/bin目录(如果没有的话), 2.2然后把它(~/bin)加到PATH环境变量中; echo “export PATH=$PATH:~/bi
http://geek.gfan.com/aosp-android-2-1-eclair-source-for-htc-g1/ 1. 说明 1) 下载编译最基本的android源码,无法在真机上使用(不能生成boot.img),只能在模拟器上使用。这是因为没有编译相关机型的内核和硬件驱动。以下介绍的是用android源码编译出对应HTC G1的版本,和烧写的过程。编译生成的版本除相机不能用
其实这个blog已经晚了一天了。昨天就发布了。 对于最终用户来说,这个版本补全了之前的缺憾: 蓝牙、多点。但也同时为诸多G1用户带来了新的折磨: G1究竟能不能顺利的升到2.0呢?SDK出来的 Eclair ROM已经达到的了史无前例71M,目前解决方案就剩下: 1、阉割部分应用程序内容或者通过App2SD曲线救国 2、修改SPL饮鸩止渴。 对此,我们还是应该抱有良好的期望,毕竟到目前为止,dev
if you have troubles with “repo sync” Android Eclair release (something like “remote end hung up unexpectedly“) – here is a solution! The problem is that during heavy load repo cannot connect to the s
1. 说明 1) 下载编译最基本的android源码,无法在真机上使用(不能生成boot.img),只能在模拟器上使用。这是因为没有编译相关机型的内核和硬件驱动。以下介绍的是用android源码编译出对应HTC G1的版本,和烧写的过程。编译生成的版本除相机不能用之外,其它绝大部分功能都能正常使用,在G1上运行2.1版的速度也不错。 2) 本文主要参考日文文档G1/G2烧机指南,感谢原文作者,原文
camera will call the callback to let upper layer to deal with preview/still image/video image. code: CameraService::Client::dataCallback switch (msgType) { case CAMERA_MSG_PREVIEW_FRAME
装了个ubuntu9.10虚拟机,使用默认配置,拖了好久把源代码搞下来,接着将ubuntu编译全部需要的软件都更新了 。 接着在eclair目录执行make,等了好几个小时,一直停在某个地方,但是又没有死掉,硬盘一直在闪! 后来实在受不了了,终止了编译过程,退出系统并调整内存从256MB到1GB,这样再进入系统里编译,之前卡壳的地方 很快跳过去了,一个多小时后编译完成。 export
Eclair need java 5 to compile 1. install java 5 on Ubuntu sudo apt-get install sun-java5-jdk if installed java6 already, need to change current java and javac sudo update-alternatives --set javac /u