feat: user provided addresses

[qiwi1272]

allow user to specify known addresses. similar to 'payees' in a bank app.
allows for more intuitive prompts (see screenshots).
decreases risk for user error when specifying addresses.

if needed, addresses.tsx and corresponding names can be refactored to 'payees' or 'contacts'

If merged, ill request for 2 weights. PR

[betterbrand]

How do you propose to protect the address.txt file? Seems like a single point of attack for someone to change all send addresses and just display the right ones.

[qiwi1272]

How do you propose to protect the address.txt file? Seems like a single point of attack for someone to change all send addresses and just display the right ones.

I used localStorage, no .txt file. Could probably sign the data with a users wallet as a form of encryption.
In my opinion localStorage is considered safe, another option would be httpOnly cookies, but because the server is local: the security increase would be minimal.

[betterbrand]

Were you able to get this to run locally? I'm assuming so. Having an issue with the build. Might you pull development and test?

https://github.com/MorpheusAIs/Lite-Client/actions/runs/8410641765/job/23224325868?pr=61

[qiwi1272]

Were you able to get this to run locally? I'm assuming so. Having an issue with the build. Might you pull development and test?

https://github.com/MorpheusAIs/Lite-Client/actions/runs/8410641765/job/23224325868?pr=61

I haven't been able to build dev since cloning.
This builds when merged with main, but i figured it might not belong there yet.

I'll take another look today.

[betterbrand]

@qiwi1272 please advise on your finding. I see you've already received the weights from @DavidAJohnston . Please update with a fix to keep the weights.

[qiwi1272]

@qiwi1272 please advise on your finding. I see you've already received the weights from @DavidAJohnston . Please update with a fix to keep the weights.

hey my bad, been busy getting things running again, have time now to fix this.
the build error with is every line of prompts.ts, which I didn't change, hopefully just a parsing error.

[qiwi1272]

alright, I can build fine locally, hope the tests work.
David used this feature as an example in the podcast, he said the model would ask to make sure it has the right address for 'bob'.
That's what ill work on next, as it solves the security issue.

Would it be considered bad practice to generate the question programmatically, and only accept responses matching 'y', 'yes', 'yea'?
I only ask because using a model for a yes/no question could be a burden on the user-end.

[betterbrand]

Please post an example that can be tested

[betterbrand]

Would it be considered bad practice to generate the question programmatically, and only accept responses matching 'y', 'yes', 'yea'?

I only ask because using a model for a yes/no question could be a burden on the user-end.

Good idea. Please suggest a solution