-
Toast message -as fall back during own node
Only during send and Refresh
Toast - We could not connect to your own node.
Refreshed/Sent using the BitHyve node....
If the fall back was not selected…
-
Send To Contacts Flow: 'last seen active" color indicators on contact avatars.
![tempFileForShare_20201118-141522](https://user-images.githubusercontent.com/62699947/99509947-7771ea00-29ac-11eb-8474-…
-
I do not see all the transactions (when I connect to the own node)which I have done using the BitHyve node.
-While using Bithyve node:
![Screenshot_20210111-194630_hexa stage](https://user-images.…
-
We need to have appropriate assets for the hard refresh functionality(icon and text). Also, the navigation needs to be sorted, right now clicking on hard refresh does dispatch the corresponding action…
Parsh updated
3 years ago
-
After successfully connecting to own node, when I switch to the bithyve node, the app is crashing.
-Steps to follow:
1.Connect to own node.
2.Tick the fallback option(or without fallback option).
…
-
https://github.com/bithyve/hexa/pull/2552/files
-
-
This applies to service accounts like Wyre, FBTC, Swan etc.
The option to add an account or the option to buy with a service should only be provided to the user if its available in their region.
-
The T&C were last updated on 13th January 2021.
https://hexawallet.io/terms-of-service/
for
This Agreement may be amended by BitHyve **without** providing you advance notice of any proposed change…
-
A web hook needs to be provided by BitHyve(Hexa) to Wyre so that Wyre test environment can be configured for Hexa Wallet.