mutinywallet / mutiny-web Goto Github PK

• lightning
• onchain
• uttxo

TBD on what goes into it, but at least needs a page or something for the payment part and hiding something simple like a "supporter page" until we got some things to go in there.

Depends on MutinyWallet/mutiny-node#392

I opened a channel, then clicked the home button, and my home page was filled with a javascript exception error:

Cannot read properties of undefined (reading 'time')

Clear errors and retry
TypeError: Cannot read properties of undefined (reading 'time')
    at get children [as children] (http://localhost:3420/src/components/Activity.tsx:110:120)
    at http://localhost:3420/src/components/Activity.tsx:39:32
    at Object.fn (http://localhost:3420/node_modules/.vite/deps/chunk-4GRR7IEI.js?v=4e54f4ba:337:60)
    at runComputation (http://localhost:3420/node_modules/.vite/deps/chunk-D6EXEMZE.js?v=4e54f4ba:755:22)
    at updateComputation (http://localhost:3420/node_modules/.vite/deps/chunk-D6EXEMZE.js?v=4e54f4ba:738:3)
    at createRenderEffect (http://localhost:3420/node_modules/.vite/deps/chunk-D6EXEMZE.js?v=4e54f4ba:229:5)
    at insert (http://localhost:3420/node_modules/.vite/deps/chunk-4GRR7IEI.js?v=4e54f4ba:337:3)
    at http://localhost:3420/src/components/Activity.tsx:39:5
    at _$$component.location (http://localhost:3420/src/components/Activity.tsx:41:5)
    at http://localhost:3420/@solid-refresh:25:42

• need to remember inputted amount to compare it with lsp invoice amount

I hit some pages sometimes and vite keeps trying to "optimize dependencies" and it reloads all my instances sparatically. Not sure what I need to do to turn that off.

5:05:02 PM [vite] ✨ new dependencies optimized: qr-scanner
5:05:02 PM [vite] ✨ optimized dependencies changed. reloading

If a payment "fails" with a PaymentTimeout we want to show some sort of status like "it might be in flight but idk"

Fails to persist to storage otherwise. Need to figure out why that happens and how we can tell users to get around it.

Now that we can open channels to the CLN LSP (MutinyWallet/mutiny-node#429), we should have some screen or some easy way to open channels to the configured LSP. Right now the only way to get funds onto lightning is to receive a lightning invoice.

I'm not sure if anything is required on the mutiny-node side for this but something we should probably have for the friends and family release.

Uncaught TypeError: navigator.clipboard.readText is not a function
    handlePaste Send.tsx:114
    eventHandler dev.js:389
    delegateEvents dev.js:138
    <anonymous> ErrorBoundary.tsx:60
[Send.tsx:114:28](http://localhost:3420/src/routes/Send.tsx)
    handlePaste Send.tsx:114
    eventHandler dev.js:389
    (Async: EventListener.handleEvent)
    delegateEvents dev.js:138
    <anonymous> ErrorBoundary.tsx:60

Because I can't paste on firefox, I can't spend transactions since I can't manually type out into an input box.

Also, it is reasonable to have users decline clipboard access to websites and applications, so we need an input box.

Depends on a few things:

• MutinyWallet/mutiny-node#237
• MutinyWallet/mutiny-node#390
• #21
• #190

Whenever a payment failed trying to pay a unified address, it goes back to the home page when I click on the button.

If this failed because of lightning, I can see a few things happening to improve the experience here and not make the user scan the QR code again. Nobody likes having to do that twice.

• Try Again Button
• Offer to pay on chain instead
• Always go back to the payment screen and let them try again or select on chain themselves

I think maybe clicking the X button might go back instead?

TBH Im not sure if it makes sense to have both an X button at the top and a button at the bottom. Button colored buttons are just much nicer, especially if we are taking up the whole page anyways.

• polling indicator
• under 10k warning
• instructions for sharing the qr code / invoice
• truncated preview string
• real edit icons
• disable unified / lightning when not available (under 10k case)

Depends on: MutinyWallet/mutiny-node#312

No complaint is too small. What do you hate? What functionality are you missing? What could be more efficient to accomplish? Etc. No hard feelings, let it all out.

• general ui

  • toast
  • modal
  • confirm dialog

• Waitlist

  • You can sign up for the waitlist
  • You can be "approved" and see the actual wallet
  • Fix the flash on load
  • actually check with the backend for approval

• Integration

  • Pull in node manager package and put it into a "context" object
  • Pick a better solution that react-query for doing async calls to node manager

- [ ] Setup
- [ ] a welcome screen prompting them to write down their seed
Setup moved to: #30

• Home screen

  • show balance
  • balance polling
  • list activity
    • sends
    • receives (make sure to hide ones that we gave up on)

• Send

  • scan qr codes
  • paste stuff
    - [ ] "WAILA" (what am I looking at... take the string and figure out what it is) #31
  • send lightning
  • send on-chain
    - [ ] send lnurl / lightning address #31
  • add amounts when relevant
  • add memo
    - [ ] confirm #32
  • success
    - [ ] fail #32

• Receive

  • create lightning invoice
  • use lsp method for lightning invoice
  • create on-chain address (or should we do lightning receives only for now?)
  • display QR code
  • unified
  • success screen

- [ ] error page #33

- [ ] Settings
- [ ] seed info
- [ ] backup wallet to json (temp, for dev purposes)
- [ ] restore wallet from json (temp, for dev purposes)
- [ ] edit service servers (network, blocks, lsp, ws proxy)
#34

• kitchen sink admin stuff
  • list peers
  • disconnect / delete peers
  • list channels
  • close channels

• dismiss link
• close button
• smaller CTA button
• icon

The whole app fails to load on a blank gray screen.

Uncaught (in promise) non-precached-url: non-precached-url :: [{"url":"index.html"}]
    at O.createHandlerBoundToURL (https://signet-app.mutinywallet.com/workbox-30e9d199.js:1:13245)
    at Object.createHandlerBoundToURL (https://signet-app.mutinywallet.com/workbox-30e9d199.js:1:14916)
    at https://signet-app.mutinywallet.com/sw.js:1:2329
    at https://signet-app.mutinywallet.com/sw.js:1:565

Would be cool to have proof of payment when you click on an invoice. We should have all this data already available.

• Setup
  • a welcome screen prompting them to write down their seed

• Settings
  • seed info
  • backup wallet to json (temp, for dev purposes)
  • restore wallet from json (temp, for dev purposes)
  • edit service servers (network, blocks, lsp, ws proxy)

We also really gotta figure out how to make desktop not look like it's meant for blind grandma's, probably should have a good layout for that before we start building too many pages and stuff.

Our waitlist page seems to do a decent job at not stretching things all the way to the ends. Maybe start with something like that just for a quick win?

Originally posted by @TonyGiorgio in #13 (comment)

It is no longer needed now that BDK does not log very much now. Other logs have and are still falling into the category and get hidden.

Currently when you dismiss the backup notification, it comes right back when you switch pages. This should ideally wait a little bit before showing again. Perhaps keep in memory until next reload should be fine without storing additional state?

After sending or receiving some bitcoin, it takes you to an empty send/receive screen. I don't think it's typical that users want to send more, or receive more after the first one. But even so, the home screen makes it really accessible to do so.

I think that makes the most sense but open to feedback.

I cant tell how much I have to send when I am trying to withdraw all

Doing a send, then later doing another send will show the invoice details of the last send instead of allowing the scanning of another invoice.