fix: consume vss-client 0.5.23 - #673
Open
ovitrif wants to merge 1 commit into
Open
Conversation
2 tasks
Greptile SummaryThis PR upgrades vss-rust-client-ffi to 0.5.23 and makes VSS initialization fail closed when LNURL-auth configuration is blank.
Confidence Score: 5/5The PR appears safe to merge, with authenticated VSS initialization consistently replacing the removed unauthenticated fallback. The changed setup paths reject blank authentication configuration, retain correct failure cleanup, and use the authenticated VSS APIs pinned by the coordinated dependency update; no reachable blocking failure remains.
|
| Filename | Overview |
|---|---|
| Bitkit/Services/LightningService.swift | Removes fixed-header VSS fallback and requires a nonblank LNURL-auth URL before building the Lightning node. |
| Bitkit/Services/VssBackupClient.swift | Routes app and debug VSS setup exclusively through authenticated client initialization. |
| Bitkit/Utilities/Errors.swift | Adds the dedicated vssAuthRequired service error and its AppError mapping. |
| Bitkit.xcodeproj/project.pbxproj | Updates the exact vss-rust-client-ffi package requirement to 0.5.23. |
| Bitkit.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved | Pins vss-rust-client-ffi 0.5.23 at the corresponding resolved revision. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Backup or Lightning setup] --> B[Read and trim LNURL-auth URL]
B --> C{URL present?}
C -- No --> D[Throw vssAuthRequired]
C -- Yes --> E[Initialize authenticated VSS client]
E --> F[Proceed with backup or Lightning node]
Reviews (1): Last reviewed commit: "fix: consume vss-client 0.5.23" | Re-trigger Greptile
1 task
ovitrif
force-pushed
the
fix/consume-vss-0.5.23
branch
from
August 18, 2026 11:12
78f71e8 to
734ffb2
Compare
ovitrif
changed the base branch from
master
to
fix/fail-closed-unauthenticated-vss
August 18, 2026 11:12
Bump vss-rust-client-ffi to 0.5.23 so unauthenticated VSS encryption is rejected in the library. Related: synonymdev/audit#55, synonymdev/vss-rust-client-ffi#20
ovitrif
force-pushed
the
fix/consume-vss-0.5.23
branch
from
August 18, 2026 13:03
734ffb2 to
8a59735
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.
This PR bumps vss-rust-client-ffi from 0.5.21 to 0.5.23.
Description
0.5.23 includes synonymdev/vss-rust-client-ffi#20. Unauthenticated client setup now returns AuthError instead of encrypting with a public all-zero key.
Companion Android PR: synonymdev/bitkit-android#1164
Linked Issues/Tasks
Screenshot / Video
N/A
QA Notes
Manual Tests
regression:Fresh wallet → backup/Lightning start with current Env LNURL-auth URL: setup still succeeds.Automated Checks