Skip to content

Cbf chain source#26

Merged
febyeji merged 5 commits into
febyeji:cbf-chain-source-cleanupfrom
randomlogin:cbf-chain-source
Jun 7, 2026
Merged

Cbf chain source#26
febyeji merged 5 commits into
febyeji:cbf-chain-source-cleanupfrom
randomlogin:cbf-chain-source

Conversation

@randomlogin

Copy link
Copy Markdown
Collaborator

Add sender and listener of ChainOps

When process_kyoto_events processes events it decides whether we need
to take any action (e.g. apply block). These actions are sent to a new
abstraction — BlockApplicator which holds ChainListener
(which in turn has wallets and can apply blocks / filtered blocks). This
BlockApplicator has to have a receiver of a channel (and
process_kyoto_events has to have a sender to this channel. Thus we
cannot create them in new, because we would own them at
CbfChainSource, so they are created in start.

Also this commit ran cargo fmt --all which was missed previously.

randomlogin and others added 5 commits June 3, 2026 01:06
Add stub methods/functions, add basic build and start of the CBF chain
source as well as basic struct containing the fields which undoubtedtly
are needed.
Previously tests assumed that the chain source of the lightning node and
is node which mines. This is not the case with CBF chain source which
needs to wait until after mining a new block a new tips propagates to
it.

`wait_for_block` is made to return a new height and a new function
`wait_for_node_tip` is added which waits until the given height is
processed (returned via `status.best_block` ) on a given node.
Ask wallet for revealed spks, register them. Implement `Listen` trait
ans add register_script method as well as implementation of registered
scripts/outputs.
When `process_kyoto_events` processes events it decides whether we need
to take any action (e.g. apply block). These actions are sent to a new
abstraction — `BlockApplicator` which holds `ChainListener`
(which in turn has wallets and can apply blocks / filtered blocks). This
`BlockApplicator` has to have a receiver of a channel (and
`process_kyoto_events` has to have a sender to this channel. Thus we
cannot create them in `new`, because we would own them at
`CbfChainSource`, so they are created in `start`.

Also this commit ran `cargo fmt --all` which was missed previously.
Co-authored-by: febyeji <yeji.han@sf.snu.ac.kr>
@febyeji febyeji merged commit 946d7a6 into febyeji:cbf-chain-source-cleanup Jun 7, 2026
12 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants