df4df8679d
getchaintips returns tips even if we don't have the body for them, so
we need to look for the active tip, not just the first (most-work) one.
Here's what happens in the log:
+2849.963414597 lightningd(26779):BROKEN: bitcoin-cli getblock 0000000000000000018626ff7160bdf38a602e6650bd04ec258759ea578b106d false exited 91: 'error code: -32603
error message:
Can't read block from disk
'
And here's an example problematic getchaintips output:
[
{
"height": 419635,
"hash": "0000000000000000000fd32d87fce19efb7ccd07aa4ddaf1b94b9a219deec0f9",
"branchlen": 1,
"status": "headers-only"
},
{
"height": 419634,
"hash": "000000000000000002988d6512719697147cf252b2f64d247cf229266615d2bb",
"branchlen": 0,
"status": "active"
},
{
"height": 416372,
"hash": "0000000000000000004d0a54341c992ae174a91c8dd3981a9f2b3d3f6221ba59",
"branchlen": 1,
"status": "valid-headers"
},
{
"height": 416231,
"hash": "0000000000000000044d0d2c25f33cb48931540366149cde3fb0154f55b58c76",
"branchlen": 1,
"status": "headers-only"
}
]
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
|
||
|---|---|---|
| bitcoin | ||
| ccan | ||
| daemon | ||
| doc | ||
| secp256k1 | ||
| test | ||
| .gitignore | ||
| .gitmodules | ||
| check-bolt.c | ||
| close_tx.c | ||
| close_tx.h | ||
| commit_tx.c | ||
| commit_tx.h | ||
| find_p2sh_out.c | ||
| find_p2sh_out.h | ||
| HACKING.md | ||
| INSTALL.md | ||
| LICENSE | ||
| lightning.pb-c.c | ||
| lightning.pb-c.h | ||
| lightning.proto | ||
| Makefile | ||
| names.c | ||
| names.h | ||
| opt_bits.c | ||
| opt_bits.h | ||
| overflows.h | ||
| permute_tx.c | ||
| permute_tx.h | ||
| protobuf_convert.c | ||
| protobuf_convert.h | ||
| README.md | ||
| remove_dust.c | ||
| remove_dust.h | ||
| state_types.h | ||
| state.c | ||
| state.h | ||
| TODO.md | ||
| utils.c | ||
| utils.h | ||
| version.c | ||
| version.h | ||
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.
So far, we are working on the inter-node encryption and transaction negotiation phases.
Later steps will enhance the protocol to network individual daemons, advertise their IP addresses, publish routes and fees, and use that information to pay specific nodes. These details are currently being hashed out on the mailing list and the IRC channel #lightning-dev on Freenode.
Final note: This is very much a testbed and work in progress; expect All The Things to change, all the time.
Welcome aboard!
Rusty.