What the developer wrote
Authored by ziggie
chanrestore: use channel state open channel
Build restored channel shells with chanstate.OpenChannel instead of the
channeldb alias.
The restored shell is channel state data, so this keeps the constructor
aligned with the package that now owns the type.
What changed, and why it matters
This is a one-line code cleanup change. It swaps which internal Go package provides an empty 'OpenChannel' data structure when building a restored channel shell. The actual fields being filled in are identical, and there is no functional change to how data is read, written, or validated.
No security action needed. Treat as a normal refactoring/relocation commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit changes the type used to construct a ChannelShell.Chan from channeldb.OpenChannel to chanstate.OpenChannel. Both types are the same underlying struct (chanstate is the package that now owns the type, and channeldb re-exports it as an alias). The diff shows no logic, validation, serialization, or permission changes—only the package qualifier of the constructed value.
Changed components
chanrestore.go: openChannelShell()Inspect captured patch +1 / −1
diff --git a/chanrestore.go b/chanrestore.go
index d97e50f..dfa1ea5 100644
--- a/chanrestore.go
+++ b/chanrestore.go
@@ -187,7 +187,7 @@ func (c *chanDBRestorer) openChannelShell(backup chanbackup.Single) (
chanShell := channeldb.ChannelShell{
NodeAddrs: backup.Addresses,
- Chan: &channeldb.OpenChannel{
+ Chan: &chanstate.OpenChannel{
ChanType: chanType,
ChainHash: backup.ChainHash,
IsInitiator: backup.IsInitiator,
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.