mirror of
https://github.com/aljazceru/lightning.git
synced 2025-12-20 15:44:21 +01:00
1. If the tool changes, you need to regenerate since the output may change. 2. This didn't just filter that out, ignored all but the first dependency, which made bisecting the bookkeeper plugin a nightmare: it didn't regenerate the .po file, causing random crashes. If we want this, try $(filter-out tools/fromschema.py) instead. But I don't think we want that. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
43 lines
1.1 KiB
Markdown
43 lines
1.1 KiB
Markdown
lightning-waitblockheight -- Command for waiting for blocks on the blockchain
|
|
=============================================================================
|
|
|
|
SYNOPSIS
|
|
--------
|
|
|
|
**waitblockheight** *blockheight* [*timeout*]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
The **waitblockheight** RPC command waits until the blockchain
|
|
has reached the specified *blockheight*.
|
|
It will only wait up to *timeout* seconds (default 60).
|
|
|
|
If the *blockheight* is a present or past block height, then this
|
|
command returns immediately.
|
|
|
|
RETURN VALUE
|
|
------------
|
|
|
|
[comment]: # (GENERATE-FROM-SCHEMA-START)
|
|
On success, an object is returned, containing:
|
|
|
|
- **blockheight** (u32): The current block height (>= *blockheight* parameter)
|
|
|
|
[comment]: # (GENERATE-FROM-SCHEMA-END)
|
|
|
|
If *timeout* seconds is reached without the specified blockheight
|
|
being reached, this command will fail with a code of `2000`.
|
|
|
|
AUTHOR
|
|
------
|
|
|
|
ZmnSCPxj <<ZmnSCPxj@protonmail.com>> is mainly responsible.
|
|
|
|
RESOURCES
|
|
---------
|
|
|
|
Main web site: <https://github.com/ElementsProject/lightning>
|
|
|
|
[comment]: # ( SHA256STAMP:7db14bcda8226b184a2cdccb41e0db717d257683bb69b684a61e065af7ab076d)
|