when-will-oisy-wallet-be-officially-launched
n-e-x-t cycle I guess
Playing around with OISY for the first time. Very impressed with how easy it all is.
Are there any plans to integrate DEX screener, or something along those lines, into the swap option on OISY?
I don’t do much coin swapping, but having the option to see candles would be very beneficial.
Adding trading support is definitively on our list, but I surely see challenges displaying visual information on smaller devices.
We are currently investigating our next steps in this direction, and our first choice so far will be AI and/or agent based trade orders. But we keep an open mind on that, and are always up for low hanging fruits.
Some questions about the user experience.
-
After I log in with II there is the step “Retrieving your public keys” which takes a long time, in the order of 15-20 seconds. What exactly is happening in this time?
-
When I make a Bitcoin transaction the “Review” window open with the “Send” button grayed out. It takes some time before the “Send” button becomes blue. It seems the fee is being determined. What exactly is happening in this time?
-
After having made one Bitcoin transaction, do we really have to wait for 6 confirmations before being able to send another one?
Hi @timo
-
About retrieving the public keys for all the supported networks, I have to investigate a bit further on why it takes this long. I know the keys are stored using chain-key cryptography, so they can’t just be looked up, but have to be retrieved through a consensus process via multiple subnets. This makes it highly secure, but of course costs some time. We will look into possibilities to load them asynchronously, so a user can still already enter the wallet without all network address reliably retrieved yet.
-
The send button is inactive as long as the fees are not yet calculated, but then becomes active right when they are known. Calculating the expected fees for a BTC transaction is a larger process and is dependent on all available utxos of the user.
But we are about to improve the send flow for BTC, and start calculating the fees right after the send amount was entered. This will then hopefully make the fee available when the user switches to the review screen. -
It was an intentional decision, to not allow a 2nd BTC send transaction until a current one has at least some confirmations, to reduce the chance of multiple failed transactions in case one fails. I will have to check with someone who was involved in that decision to find out more about the reason.
I hope this could so far help you out. I will get back to you once I have more infos on 1) and 3)
The fee calculation really needs to improve. It simply takes too long and I also noticed that the “Max” button does not work.
Oisy let’s its backend canister do all the work and calls btc_select_user_utxos_fee
with an amount to be sent. This is painfully slow (1 minute) and it seems the function is not designed for a “max” amount. Why doesn’t the frontend download all the available utxos and does the selection and fee calculation itself? Why leave it to the backend?