mirror of
https://github.com/aljazceru/lightning.git
synced 2025-12-24 09:34:24 +01:00
13b1d922bb
broadcast_remainder() does two things: get the error message for the previous transaction, and send the next one (shrinking the array). But it has two bugs: 1) It logs results on the tx at the end of the array, which is the one it is *about* to send, and 2) The initial caller (rebroadcast_txs) hands it the complete array, so the first tx gets broadcast twice. The correct thing to do is to strip the array, then send the tail for the next callback. And use nicely-named vars to help document what we're doing. Reported-by: Christian Decker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
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:
- 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.
- 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.