[Frontend] [Bug] Fix UI state inconsistency when toggling between Public and KMS in Wizard

[Tybravo]

🎯 Goal

Ensure toggling updates related sub-options correctly.

📋 Requirements

• Clear KMS-specific settings if user switches back to Public.

🔧 Technical Scope

• React State Logic

📂 Affected Path

frontend/features/verification/components/steps/SPVPrivacyStep.tsx

✅ Acceptance Criteria

• State remains consistent and clean.

🔗 PR Requirements

• PR description must include: Closes #[issue_id]

[aojomo]

@aojomo has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer, Please I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @aojomo to this issue.

[chigozirim007]

@chigozirim007 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello please I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @chigozirim007 to this issue.

[drips-wave]

Congratulations, @chigozirim007! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @chigozirim007: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[Ofoedu-Ifeanyi]

@Ofoedu-Ifeanyi has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer
I’m very interested in contributing to this project and would be glad to take on a task. I have the relevant skills and experience required to make a meaningful contribution and help bring the project to a high standard.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ofoedu-Ifeanyi to this issue.

[Abuh-Bakar]

@Abuh-Bakar has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I would love to work on this. I have implemeted similar solutions on several projects and I can do same here cleanly and efficiently. Allow me the opportunity to contribute to your project while following contribution guidelines for your project. Kindly assign.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abuh-Bakar to this issue.

[Perfected1]

@Perfected1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I’d like to take on issue #435. I’ve reviewed the requirements and can fix the React state logic in SPVPrivacyStep.tsx so that switching from KMS back to Public properly clears any KMS-specific settings and keeps the wizard state consistent.

I’ll also ensure the change is properly tested and include Closes #435 in the PR description as required.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Perfected1 to this issue.

[chriseffects01]

@chriseffects01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to work on this issue because I enjoy frontend development and debugging UI problems

ℹ️ Repo Maintainers: To accept this application, review their application or assign @chriseffects01 to this issue.

[QueenColly]

@QueenColly has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Application

Dear Tybravo Team,

I’d be happy to contribute to #435 and fix the state inconsistency in the verification wizard. I have experience with React state management and handling conditional UI flows where related state must remain synchronized.

I’ll update SPVPrivacyStep.tsx so switching from KMS back to Public reliably clears KMS-specific settings while preserving the expected Public configuration. I’ll keep the change focused, avoid unrelated refactoring, and verify the relevant UI states to ensure toggling behaves predictably in both directions.

I’ll also include the required Closes #[issue_id] reference in the PR.

A focused fix to keep the wizard’s state predictable, clean, and user-friendly.

Best regards,
QueenColly

ℹ️ Repo Maintainers: To accept this application, review their application or assign @QueenColly to this issue.