-
Notifications
You must be signed in to change notification settings - Fork 906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faster startup #7175
Faster startup #7175
Commits on Mar 26, 2024
-
lightningd: use get_network_blockheight() not get_block_height() for …
…pay. This is useful once we allow pay before full sync. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 0597610 - Browse repository at this point
Copy the full SHA 0597610View commit details
Commits on Mar 27, 2024
-
lightningd: allow *outgoing* HTLCs before full bitcoind sync.
This allows for faster startup for Greenlight. We still require full sync before *incoming* htlcs, and onchain operations. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 023bb51 - Browse repository at this point
Copy the full SHA 023bb51View commit details -
lightningd: debug log when we send a notification to a command.
For testing. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 2f882bd - Browse repository at this point
Copy the full SHA 2f882bdView commit details -
openchannel: delay, don't refuse, if node not synced.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for a4d8a0f - Browse repository at this point
Copy the full SHA a4d8a0fView commit details -
openchannel_bump: delay, don't refuse, if node not synced.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for d8faf73 - Browse repository at this point
Copy the full SHA d8faf73View commit details
Commits on Mar 28, 2024
-
pytest: rename lightning nodes to reduce confusion.
I was trying to debug test_zeroconf_open and getting very confused. The reason: l0 is lightning-1, l1 is lightning-2, etc! And there are two other tests where an l0 has been added at the front: fix them all to avoid future confusion! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 1c968ee - Browse repository at this point
Copy the full SHA 1c968eeView commit details -
fundchannel_start: delay, don't refuse, if node not synced.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 818ce4d - Browse repository at this point
Copy the full SHA 818ce4dView commit details -
lightningd: don't allow mindepth != 0 if they specify channel_type ze…
…roconf. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Fixed: JSON-RPC: `fundchannel_start` now disallows a non-zero `mindepth` parameter if you ask for a zeroconf `channel_type`.
Configuration menu - View commit details
-
Copy full SHA for c155e42 - Browse repository at this point
Copy the full SHA c155e42View commit details