-
Notifications
You must be signed in to change notification settings - Fork 62
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
get rid of unified receive #1089
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The API calls need to be different. You're still calling for a bip21 address, as indicated by the logs that are checking for an address even when the lightning invoice is the only thing present.
eb21126
to
465dd2a
Compare
Deploying mutiny-web with Cloudflare Pages
|
Also, we should allow someone to just hit continue for 0 amount on chain. There's no reason they need to do anything for it. |
bb54b63
to
b6bdd14
Compare
addressed @TonyGiorgio comments and also @benthecarman I think I fixed the flicker #1125 |
closes #1126 as well |
I also fix dust amount errors in my fedimint onchain mutiny-node PR, but good to have it in both. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works great! Only nit, why not auto select and minimize once onchain or lightning is clicked? We did that before and I liked it. Not sure if you felt one way or another, but that's the only thing that's weird to me.
Good idea, i think i had to get rid of that when we had the remember selection checkbox |
only do one at a time, address or invoice move method chooser to receive amount screen fix flicker on send / swap pages amountless on-chain, fix receive warnings fix unnecessary "Failed to conduct wallet operation" errors close receive method chooser automatically
26d81b2
to
b0b1d1a
Compare
No more bip21, just lightning and bitcoin address. need to test this out with ben's upcoming pr so we make sure we can handle all the potential scenarios