What changed, and why it matters
This commit only changes user-facing help text in the wallet settings screen. It updates the descriptions for wallet policy types (single signature, multisignature, silent payments) and script types (Segwit, Taproot, Legacy). There are no code logic changes, no security fixes, and no behavior changes.
No security action needed. This is a documentation/UX string update.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies two HelpLabel strings in settings.fxml. The first adds a description of Silent Payments wallets and simplifies the multisignature wording. The second rewrites the script type guidance to mention Taproot and emphasize matching restored wallet types. No controllers, handlers, cryptographic code, or validation logic were changed.
Changed components
src/main/resources/com/sparrowwallet/sparrow/wallet/settings.fxmlInspect captured patch +2 / −2
diff --git a/src/main/resources/com/sparrowwallet/sparrow/wallet/settings.fxml b/src/main/resources/com/sparrowwallet/sparrow/wallet/settings.fxml
index 3623cd1..09ac76b 100644
--- a/src/main/resources/com/sparrowwallet/sparrow/wallet/settings.fxml
+++ b/src/main/resources/com/sparrowwallet/sparrow/wallet/settings.fxml
@@ -41,7 +41,7 @@
</FXCollections>
</items>
</ComboBox>
- <HelpLabel helpText="Single signature wallets use a single keystore (hardware wallet or seed).\nMultisignature wallets require multiple keystores (N), of which a certain number (M) need to sign." />
+ <HelpLabel helpText="Single signature wallets use a single keystore (hardware wallet or seed).\nMultisignature wallets require multiple keystores, of which a certain number need to sign.\nSilent Payments wallets also use a single keystore and can receive privately to a reusable address." />
</Field>
<Field text="Script Type:">
<ComboBox fx:id="scriptType">
@@ -57,7 +57,7 @@
</FXCollections>
</items>
</ComboBox>
- <HelpLabel helpText="Native Segwit types are the default and are usually the best choice.\nNested Segwit types are a good choice for the widest compatibility with older wallets.\nLegacy types should be avoided, unless configuring an old wallet." />
+ <HelpLabel helpText="Native Segwit the type chosen for most new wallets.\nTaproot is a newer type useful for specific needs.\nNested Segwit and Legacy are useful for recovering older wallets.\nFor existing wallets, be sure to choose the type that matches the wallet you are restoring." />
</Field>
</Fieldset>
</Form>
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.