-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Milestone 1.7: Send bitcoin - specs & progress #65
Comments
#28 is an older issue on this topic form our design discovery in September 2022. Closing that one now in favor of this new one here that is in-line with our milestone schedule. |
Minor thing, we could indicate which characters are wrong when there are typos in addresses (under certain circumstances). Sees this PR. |
Listened to this podcast, and they mentioned how it would be nice to have a feature for automated test transactions. Here's how it would work:
Reason for this feature is that there is anxiety around making a mistake setting up the follow-up transaction. That anxiety could be removed by making this simple logic a formal wallet feature. This might lead to more people doing test transactions and therefore fewer losses related to them. Of course, there's the downside of paying fees for two transactions. This idea is probably more of future addition beyond the MVP, etc. But we could still do a quick exploration on it and document it, for reference, and to ask around if it would be useful. |
Taking another look at this, I think the scoping for the MVP makes sense. But why split up the fee selection into two parts? Is it too much work on the development side? |
Post-MVP we should probably also include child-pays-for-parent |
This is a tracker/discssion issue for the 1.7 milestone (design docs).
Goal is to add send features, including address/contacts and coin selection. Due to the complexity of this screen and user flow, we need to split design & development into smaller parts:
Requirements by phases:
Note that this is more of a guess. We can refine this as we go.
MVP
Launch
Future additions
The text was updated successfully, but these errors were encountered: