Feature Parity 22: Wallet Interface Improvement Proposals Log (Future Versions)

[johnny9]

Summary

Track wallet/node interface improvement proposals discovered during parity implementation without changing interfaces in this release.

Complexity

• S (ongoing)

Dependencies

• None

Global Constraints

• All implementation lives under gui-qml/.
• No GUI runtime dependency on bitcoin/src/qt components. Reused logic must be moved/ported into gui-qml/.
• Do not change interfaces::Wallet or interfaces::Node in this version.
• Issue completion must satisfy DefinitionOfDone.md.

Scope

• Maintain proposal entries with problem statement, feature impact, and suggested interface shape.
• Link each proposal to originating parity issue(s).
• Record trade-offs and migration concerns.

Acceptance Criteria (DoD-Aligned)

1. Every major parity issue that encounters interface friction logs at least one concrete proposal or explicitly notes none found.
2. Proposal log remains current and reviewable throughout implementation.

Required Tests

• C++ unit tests: N/A
• QML QTest: N/A
• Python E2E (qml/test/testbridge.h): N/A

Implementation Notes

• This is documentation/process work, not runtime behavior.

[GBKS]

Can you please clarify if "interface" always refers to code interfaces in this issue? Or does "Wallet Interface Improvement Proposals" refer to the user interface?