test: add penalty transaction test - #172
Draft
ABallarini wants to merge 1 commit into
Draft
ABallarini wants to merge 1 commit into
ABallarini wants to merge 1 commit into
Conversation
ABallarini
force-pushed
the
upstream-penalty-tx-tests
branch
from
September 15, 2026 09:22
8f6b8f0 to
b3274eb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a deterministic integration test (
src/test/penalty_transaction.rs) that verifies protocol penalty behavior when a node broadcasts a revoked commitment state (per BOLT 3 / BOLT 5).High-Level Overview
ldk.log, constructs and mines a justice (penalty) transaction and processes the output consolidation sweep.node2_btc_before + sweep_out) using structural transaction checks (1-in/1-out) and a bounded fee-sensitivity invariant (< 5_000sats total fees).Assert RGB asset balances):There is currently an issue in the RGB asset assertion phase. While Node A correctly retains its uncommitted 400 RGB units (
ISSUE_AMT - RGB_ON_NODE_A), the honest node (Node B) does not currently receive the 600 RGB units carried by the revokedto_localoutput upon sweeping but are burnt. The test framework currently flags this discrepancy during the asset balance assertion step.📖 Specification & Step-by-Step Flow: View HackMD Specification