0xMiden / 0xMiden/wallet

Fund Wallet needs a clear pending state and less alarming recovery copy

Open
#476 1 comment 0 reactions 1 assignee Claimed by @dotsolo View on GitHub
Dominant language
TypeScript
Stars
5
Forks
28
Avg merge
9h 50m
Merged PRs (30d)
123

Description

Consolidates feedback ticket #144 (https://app.notion.com/3b199411cf908138a1a9c67266479804) and the funding/recovery context in ticket #159 (https://app.notion.com/3b199411cf9081aca177d28c6f3963c0).

## Problem

On iOS, roughly 30 seconds passed after **Fund this wallet** before the note/free-float notification appeared, with the network transaction completing within about a minute. During that gap, the flow did not make the pending state clear.

The recovery/security prompt then appeared immediately after funding, making the tester think recovery confirmation was required to receive the free tokens. Copy about “bad actors” also felt more alarming than informative.

## Expected

- Show an explicit funding state from request through note availability and consumption.
- Separate funding completion from the recovery-confirmation prompt so they do not appear causally linked.
- Use neutral, concrete security copy that explains the benefit without implying an immediate threat.

Feedback DB refs: tickets 144 and 159.

Contributor guide

Open the contributing guide

Research direction

Look for the iOS wallet UI components handling the funding flow and recovery prompts. The issue mentions a 30-second gap before a note appears; find where the funding request is made and where the UI state is managed. Check for existing state management (like loading/pending states) and the copy text for security prompts. Testing will involve verifying the UI transitions and copy changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.