either in browser or in OS to keep track of the status and get notified.

affected 3

importance 2

difficulty 6

https://core.telegram.org/reproducible-builds

Kind of a pain cause apple uses PlayFair, but it's possible with a Jailbroken device & 90GB of space on your mac, apparently

test password before receive / when backup

affected: 3
importance: 10
difficulty: 2

e.g Authenticate with password post wallet creation to solve the same problem as #56 where people lose money after creation by funding a wallet they don't have the password for.

This could also be solved by using the operating system / device encryption as in Green

affected 5
importance 3
difficulty 8

https://twitter.com/s_5Q2X8mgeGR/status/1298030671940800512

Suggest labels & add a custom field

affected: 8
importance: 7
difficulty: 3

if send max then change fee max does not update til off then on

See Yegor gif

affected: 7 (not everyone changes the fee)
importance 8 unexpected financial behavior
difficulty 2 only ui I think

program files (.cs) should be tabs
.xaml\css\markup should be 2 spaces

change .gitattributes and change all current files to conform

• Understand CcjRoundConfig and document
• • ConfirmationReductionRate reduces the fee for unconfirmed CJ. don't want too many unconfirms chained togheter
• • MaximumMixingLevelCount: n sets max mixable output = denomination * 2^n
• Enable Queue
• Enable Dequeue
• Test statuses
• Testnet CoinJoin with 2 Peers
• Mainnet coinjoin with WasabiWallet?

4500 Commits -> 7500 commits

ignore HWI / what I already ignored but didn't .gitignore

A process for doing this each version of WasabiWallet should also be established

to prevent lock out. Pretty common problem

affected 9

importance 10

difficulty 3

e.g. in green "Add a note(only you can see it)."

affected 10
importance 5
difficulty 4

I tried to do this with in CustomBuildActions.targets using CreateAppBundleDependsOn, but that's MacOS bundle only. We have to have this script fire for GTK#

It's not being used as a standalone

for ux

It's confusing when you open the wallet for the first time. Tell a user what there password is for

a stepcount for

• Wallet Generation
• Restore
• Receive funds
• Send funds
• CoinJoin

funnel people to coinjoin as soon as they have new coins so they know WHAT/HOW/WHEN to do it. Basic cal to cation

WalletWasabi/WalletWasabi#3194

affected: 7
importance: 9
difficulty: 5

in global. Instead of Stop()

This is what we want: https://reactiveui.net/docs/handbook/data-binding/xamarin-forms

Xamarin.Forms uses {Binding <data>}. Right now our views bind inconsitently.

Within lists with templates, we probably need to keep using the curly brace binding.

For example, PassphraseView uses both types, and should ONLY use the ReactiveUI type. That should be a good place to start.

Bindings happen in the codebehind .xaml.cs file and are bound to an x:Name="" in the xaml view.

Check casa / bluewallet for inspiration

affected: 1
importance: 1
difficulty: 1

v1.1.4 Global.cs uses Coins_CollecionChanged and v1.1.10 uses TransactionProcessor_WalletRelevantTransactionProcessed and ChaumianClient_OnDequeued to set up notifications within Global. Those should be handled within the user interface project because they rely on WalletWasabi.Gui.Helpers in WalletWasabi source

• define objective-c native library c# api definition
• confirm contact with the binding by some interaction from c# to objective-c
• establish tor connection from iOS
• comprehensively test the bindings (i.e. run the TorController tests in C# w/ bindings)
• Make a request from Tor from Chaincase.iOS
• Integrate TorProcessManager & WasabiSynchroniser with Tor.framework
  !Important! Use latest master version of TorProcessManager from WasabiWallet
• Run sync & send in emulator
• Run in iOS hardware (iphone, ipad)
• Determine minimum iOS version we can target safely

If you close the wallet before verifying, you won't launch a wallet which you don't have keys for

~3 minutes allowed
Can do background refresh from time-to-time to check for receive

Maybe create auto double transaction for funding legacy address. This is a serious sticking point for new wasabi users.

importance 8
affected 9
difficulty 3

amount is just permanently set to 0

affected: 1
importance: 1
difficulty: 2

set label != null on first run to resolve

night mode

affected: 8
importance: 7
difficulty: 2

in "CoinJoin" page

In general, conveying status would create a feeling of security and less confusion about what to do next (hopefully none)

affected 10 (even me)
importance 10 (key feature)
difficulty 7 (gotta think about both what to show and how to show it)

DO NOT USE LOCALSTORAGE

keep in mind OWASP M4 & M6

https://owasp.org/www-project-mobile-top-10/2016-risks/m4-insecure-authentication
https://owasp.org/www-project-mobile-top-10/2016-risks/m6-insecure-authorization

for those pretty A points

Amount =0 just makes a 0 request. A button that says BACK and clears the amount or the like could fix this

affected 2 (those using URIs)
importance 1
difficulty 1

e.g. when there isn't a Memo, when the password is wrong, when you're not synced

It shouldn't end up in the wrapped app. we'll separate the coordinator

helps with accounting, cleaner than txid

• launch in device
• attach gdb to objective c process

Right now the UI doesn't show up until the wallet loads on the back end. This can take up to 30 seconds. This is because it has been hacked together and isn't making proper use of async calls.

Get the time before a User sees something <5s

Bonus: improve boot for testing the UI with a dummy wallet service, or something that could replace launching tor, syncing with the network 等等

https://twitter.com/ChristopherA/status/1255654540986265600?s=20