feat(ffi): add satscard waitStep for auth delay progress#63
Draft
reez wants to merge 1 commit intobitcoindevkit:masterfrom
Draft
feat(ffi): add satscard waitStep for auth delay progress#63reez wants to merge 1 commit intobitcoindevkit:masterfrom
reez wants to merge 1 commit intobitcoindevkit:masterfrom
Conversation
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.
Description
This PR adds a SATSCARD-only
waitStepAPI torust-cktapso clients can render cooldown progress one second at a time instead of estimating locally.The immediate motivation is SatsBuddy PR #139, which added a UI countdown for SATSCARD cooldown recovery during send/sign. That PR is good enough for now on the app side, and this PR is the upstream follow-up that exposes a cleaner stepwise primitive for that flow.
Notes to the reviewers
This is intentionally scoped to SATSCARD only for now, since that is the current consumer. If we want the same API on TAPSIGNER or SATSCHIP, that can follow in a separate PR.
Changelog notice
Checklists
All Submissions:
cargo fmtandcargo clippybefore committingNew Features:
Bugfixes: