mirror of
https://github.com/aljazceru/lightning.git
synced 2025-12-19 07:04:22 +01:00
f24aab1916489aab422f9c41b080778de3dfff1c
Mainly switching from the old include to the new include and adjusting the actual size of the onion packet. It also moves `channel.c` to use `struct hop_data`. It introduces a dummy next hop in `channel.c` that will be replaced in the next commit.
Lightning Protocol Reference Implementation
In this repository we're developing a reference implementation of bitcoin lightning (see: http://lightning.network which proposed the original "lightning network").
This implementation is being developed in parallel with the protocol definition, which you can find on my fork of the protocol description repository.
If you're interested in using the daemon to test payments, the JSON-RPC interface is documented in the following manual pages:
Steps:
- If you're running a previous version, you'll need to shut it down (maybe close channels first) and delete the $HOME/.lightning directory.
- Install and compile the requirements.
- Make sure bitcoind is running in testnet mode, and has the latest blocks.
- Get some test bitcoins, such as from TPs' testnet faucet.
- If you want others to connect to your lightningd, create $HOME/.lightning/config and put
port=8334in it (or any other port). - Run
daemon/lightningd. - Run
daemon/lightning-cli getinfoto check it's working. - Find a node using
daemon/lightning-cli getnodes(this will populate over time). - Create a new connection to the node using
contrib/lightning-open-channel ADDRESS PORT AMOUNTwhere AMOUNT is in BTC (.04294967 is the maximum possible). If successful, this will return only once a block has been mined with the funding transaction in it. - You can create more channels if you wish.
- You can accept payment using
daemon/lightning-cli invoice MILLISATOSHI LABEL; it will give you a payment hash to give to the payer. - You can send payments using
contrib/lightning-pay DEST-ID MILLISATOSHI PAYMENT-HASH.
Final note: This is very much a testbed and work in progress; expect All The Things to change, all the time.
Welcome aboard!
Rusty.
Languages
C
74.9%
Python
20.7%
Rust
1.5%
Makefile
1.1%
Assembly
0.9%
Other
0.8%