Really appreciate your work on this.
Make it go ‘ping’ when funds arrive 
Only other things I can imagine are to do with messaging - inbox, compose, send, etc - but to be honest I’d rather use it for moving money around
3 Likes
Ok - “wallet goes ping” will be added, but we don’t want to be the kind of app that releases versions with trivial changes.
Messages aren’t really the purpose of a wallet either.
Are there any features of ZecWallet, NH or others that you find missing and valuable?
How about other fiat currencies & not just USD?
Another app I’m found of is CoinLib for exactly that reason, shows value in almost all fiats including Chilean Pesos.
Sounds good but the problem is that fx rate providers cap the number of requests and require an API key.
We are working to standardize the practice of using a privacy preserving price data stream from lightwalletd, see Price API by adityapk00 · Pull Request #354 · zcash/lightwalletd · GitHub
If you need a steady stream, we have https://api.lightwalletd.com/price.json
I see it is the median price of various sources. Why is it “privacy preserving”?
I just checked, Coinlib provided an API for pricing & it’s required for all API calls - too clumsy.
Coingecko?
https://www.coingecko.com/api/documentations/v3#/simple/get_simple_supported_vs_currencies
Yeah - I was referring to the prices between fiat and USD.
The price being fetched via lightwalletd’s getInfo call makes it difficult for adversarial party to track IP address of the devices querying for price data, which can be used to geo-locate and track transaction/public data.
*As long as the user relies on the lightwalletd they are connecting to.
I see. Well, we are talking about connections to two different services: Coin Gecko for price and Lwd for transaction. They would need to collude.
I think it is actually easier to track when both price and transaction are available on the same service.
Besides, we were talking about non USD prices.
Not necessarily, CoinGecko would simply sell the end point query data to Chainanalysis/CrystalBlockchain to co-relate public transaction data.
The user is already connecting to lightwalletd service and the user can run their own service.
Even in this scenario, they would need the lwd data. It’s two locks vs one, which ever way you cut it.
No they do not need lightwalletd data. The blockchain data for shielded tx, deshielding, shielding is all public. The more the data points, the easier it gets to track.
Not the IP address
Great !! Think there’s a problem with the exchange rate though, 1 ZEC = 95444 CLP right now, approx 121 USD
There are more Chilean Pesos in the world than Dogecoin
Oh no -
Large fx rates are returned differently.
Fix is queued for Google Store publication.
Edit: published to beta testers now.
2 Likes
Really like the extra fiat currency support, it makes the wallet relevant to everyone as that’s how muggles measure value.
1 Like
Another idea…add UI components where a wallet can request payment by generating a QR code creates another use mode.
Thinking on my ‘banana shop’ concept, where it’s the person doing the selling who defines the payment and not the owner of the wallet.
Perhaps an option in the settings to define what goes in the memo field, ie: name of shop & that gets encoded in the payment URI.
EDIT: Usage would be something like :-
Seller - Here are your bananas, that’ll be 5000 CLP
Buyer - Can I pay with ZEC ?
Seller - Sure (enters 5000 CLP into Zwallet, phone shows QR for ZEC amount at current price & name of shop)
Buyer - scans code, approves payment
Seller - phone beeps… Have a nice day
QR codes have to follow ZIP321 ZIP 321: Payment Request URIs & I have no clue what UA will do to this, so present it as just another ‘ChileBob Daft Idea ™’ 
EDIT: Additional thought…when paying a scanned URI, the wallet should not allow any details to be changed. The payment should happen as specified & only require approval.
2 Likes