AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 25 Bitcoin

common: reintroduce "ignored" primary tag.

Public commit record

What the developer wrote

Authored by Rusty Russell

88/100 · Strong
common: reintroduce "ignored" primary tag.

Prior to 23.05, we used this tag to mark onchain to-self inputs we didn't
wait for (because they were too small). This fixes migration if that happened
(and we are debating whether we should re-introduce this!).

```
lightningd: FATAL SIGNAL 6 (version v25.09rc2)
0x100c8683 send_backtrace
common/daemon.c:33
0x100c876f crashdump
common/daemon.c:78
0x7fffb2080493 ???
???:0
0x7fffb1ab0cac ???
__pthread_kill_implementation+0x1bc:0
0x7fffb1a48a5b ???
__GI_raise+0x2b:0
0x7fffb1a2a3db ???
__GI_abort+0x153:0
0x100935b7 migrate_from_account_db
wallet/account_migration.c:424
0x10093ff7 db_migrate
wallet/db.c:1139
0x10096763 db_setup
wallet/db.c:1185
0x100a1bcb wallet_new
wallet/wallet.c:223
0x1004485f main
lightningd/lightningd.c:1311
0x7fffb1a2aba3 ???
__libc_start_call_main+0x93:0
0x7fffb1a2adeb ???
__libc_start_main_alias_1+0x1ab:0
0xffffffffffffffff ???
???:0
lightningd: Died with signal 6
```

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Fixes: https://github.com/ElementsProject/lightning/issues/8484
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit fixes a crash that could occur when upgrading an older Core Lightning node. If the node had previously marked certain tiny on-chain payments as 'ignored' (a label used before version 23.05), the newer software's database migration code did not recognize that label and would abort startup with a fatal error. The patch re-adds the 'ignored' tag so the migration can complete normally. It is a bug fix for a denial-of-service-on-startup condition, not an exploitable vulnerability that a remote attacker could trigger.

Recommended action

Apply the patch before releasing v25.09. No additional hardening is required beyond restoring the tag; however, consider adding a migration test that exercises all historical coin-movement tags to prevent future regressions when tags are removed.

Security signals we found

01

Abort/crash during database migration

02

Reintroduction of previously removed enum/tag to prevent fatal startup failure

03

No input validation or memory-safety defect; root cause is missing enum case

Risk score

Why this scored 25/100

Our methodology →
Potential impact 8/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 5/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.