v1.0.0

Announcing Verus Mobile Wallet - Testflight v1.0.0 with DeFi, PBaaS, VerusID, VerusAuth, testnet and mainnet support. This release addresses the known issues in v.0.9.9 and its features will become available in the Verus Mobile app store releases in the next few days.

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

This privacy policy applies to the version linking to this page. Future upgrades may amend this privacy policy without explicit notice to application users, and if so, will provide the new privacy policy or links to the new privacy policy as part of the upgraded version.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.9.9

Announcing Verus Mobile Wallet - Testflight v0.9.9 with DeFi, PBaaS, VerusID, VerusAuth, testnet and mainnet support.

We’re excited to make available the first fully open source, fully non-custodial, DeFi-enabled Verus mobile wallet, ready to support all currencies on or available on Verus, Verus testnet, and capable of supporting all currencies on any compatible PBaaS chain, which all PBaaS chains are unless a community running one decides to change that.

Because Verus DeFi is a rent-free, permissionless decentralized protocol, sending a DeFi transaction is not much different than sending any other transaction, except that it can include currency conversions, cross-chain transfers or both. The Verus Mobile Wallet enables you to create DeFi transactions locally on your own phone, sign them with your private keys, which never leave your phone, and broadcast those signed transactions to the network, whether sending them to yourself or someone else, while providing you with an estimate of your results and fees before you send. The wallet does not track or add any fees of its own for any transactions or ever access your keys. As expected from a non-custodial wallet, it simply serves as an interface to the blockchain RPC protocol.

Version 0.9.9 of Verus Mobile Wallet, is mainnet ready, but will only be released now on Testflight because the app store releases will be much better after we get the broader community’s help testing this first and giving feedback.

At present, we know of two issues with v0.9.9, but as they are both quite minor, we feel it is better to release this for testing as we prepare the final build for the app stores and incorporate all feedback we can. There is no need to report either of these two issues, and you should be able to work around them quite easily. The following are known:

1. When sending cross-chain from a PBaaS chain into VRSCTEST, the fee isn't calculated correctly in the confirmation display. This leads to the max amount not successfully being able to decrease the send amount and a "not enough utxos" error if trying to send max. If you decrease the send amount, you will see the amount to send as the correct amount including all fees, but under "Transaction fees" too little tx fees will be displayed.

2. Certain paths shown in the conversion path suggestion list may fail. For example, VRSCTEST -> Bridge.Andromeda -> Andromeda on VRSCTEST shows it will work, but will not bounce back to VRSCTEST in this version.

Aside from that, you can send normally, send cross-chain, login with IDs, or convert between currencies to your heart’s content. The conversion estimates do their best to take slippage into account, so overall, we hope that the experience will be more seamless, fair, and resistant to MEV than any prior liquidity protocol in all of crypto or actually TradFi as well. Once we get the ETH bridge up on testnet, we intend to enable direct access to it from Verus Mobile, making it possible to send back and forth from Ethereum (or Goerli testnet) and VRSC (or VRSCTEST) simply and easily from your phone.

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

This privacy policy applies to the version linking to this page. Future upgrades may amend this privacy policy without explicit notice to application users, and if so, will provide the new privacy policy or links to the new privacy policy as part of the upgraded version.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.9.0-2

This release includes the following improvements:

• Fixed a bug preventing transactions for Ethereum and ERC20 tokens from being sent.

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

This privacy policy applies to the version linking to this page. Future upgrades may amend this privacy policy without explicit notice to application users, and if so, will provide the new privacy policy or links to the new privacy policy as part of the upgraded version.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.9.0-1

Announcing Verus Mobile upgrade v0.9.0-1

This release includes the following improvements and updates:

• Added vrsc testnet support. To use vrsctest, create a test account by selecting the test tub in the "Create My Wallet" screen

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

This privacy policy applies to the version linking to this page. Future upgrades may amend this privacy policy without explicit notice to application users, and if so, will provide the new privacy policy or links to the new privacy policy as part of the upgraded version.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.9.0

We are excited to announce the release of Verus Mobile version 0.9.0 to Github (Android) and TestFlight (iOS)! This update introduces important fixes and enhancements to improve your overall experience with the app, and has been submitted to the iOS App Store and Play Store for approval!

Here are the highlights:

• Add link to learn more about VerusIDs to VerusID intro: To help users better understand VerusIDs, we've added a link in the VerusID intro to provide more information.

• Prioritize URI redirects on login deep links over webhooks if multiple redirect options are detected: We've made sure that URI redirects take precedence over webhooks when handling login deep links.

• Fix issue where send button was hidden for z-sends: We've resolved the issue that caused the send button to be hidden for z-sends.

• Add a setting to disable automatic card dragging on home screen to increase performance: Users now have the option to disable automatic card dragging on the home screen, which can help boost performance on certain devices.

• Fix issue with Android date picker preventing dates from being selectable: We've addressed a problem with the Android date picker that previously prevented users from selecting dates.

• Minor number formatting and wording fixes: We've made some small adjustments to improve the overall readability and clarity of the app.

We're eager for you to test the latest update and continue providing valuable feedback through the #verus-mobile-wallet channel. Your input is essential in helping us refine the app to better serve your needs.

Thank you for your ongoing support and feedback.

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

This privacy policy applies to the version linking to this page. Future upgrades may amend this privacy policy without explicit notice to application users, and if so, will provide the new privacy policy or links to the new privacy policy as part of the upgraded version.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.3.0-30

Announcing Verus Mobile upgrade v0.3.0-30

This release includes the following improvements and updates:

• Minor UI improvements

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.3.0-29

Announcing Verus Mobile upgrade v0.3.0-29

This release includes the following improvements and updates:

• Fixed issue with generating VerusPay QR codes
• Added display of currently selected card to send modal
• Made qr scanning a tab on the home screen
• Future-proofed Verus tx creation by avoiding utxos with non-native currencies in them
• Misc. minor UI changes and fixes
• Made QR scanner initialise correctly on first launch after permissions are enabled
• Added discoverable VerusID button to home screen

Thank you for your continued support and feedback.

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.3.0-28

Announcing Verus Mobile upgrade v0.3.0-28

This release includes the following improvements and updates:

• Improved performance on home screen and fixed stuttering issue on Android devices

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.3.0-27

We are excited to announce the release of Verus Mobile version 0.3.0-27! This update brings many improvements and features to the app to enhance your user experience. This release is also a milestone for Verus Mobile, as it is the first release candidate for our App Store/Play Store release, hopefully following soon after this test release.

Here are some of the highlights:

• Redesigned app onboarding process: We've modernised the user interface and added helpful tools to minimise profile creating difficulty, like the 24-word seed import helper. This makes it easier for new users to get started with Verus Mobile.

• Updated VerusID login protocol: We've updated various aspects of the VerusID login protocol to ready it for mainstream app-store release.

• Disabled deprecated Wyre features: Wyre features are now deprecated by default and can be re-enabled if desired in profile settings.

• Increased performance: We've decreased the number of web requests to improve app performance.

• Redesigned wallet home screen: We've redesigned the wallet home screen to use draggable widgets, allowing for customisation and modularity for future features.

As we are very close to our first App/Play store release, we encourage all users to submit any feedback or test data in the #verus-mobile-wallet channel of verus.io/discord. Your feedback is crucial in helping us improve the app and ensure that it meets your needs.

Thank you for your continued support and feedback.

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

v0.3.0-24

Announcing Immediate Availability of Verus Mobile v0.3.0-24 multi-currency mobile wallet on iOS Testflight and for APK install on Android.

Changes:

• Enable addition of VerusIDs as wallet cards to store funds and for authentication
• Supports secure VerusID authentication with web or mobile apps, enabling password-less sign-in with either QR code scan or deep-link
• Supports smart-transaction parsing for spending from IDs, preparing for PBaaS, and supporting a broader range of transaction types
• Switch from ElectrumX servers to Verus-rpc server for advanced VRSC lite mode
• Update dependencies

Bug Fixes:

• Change Android storage database to support dynamic scaling, fixing database full error
• Fix formatting issues with text fields on smaller devices
• Fix issue with security cover making modals close on iOS
• Make image storage under personal profile persist correctlyThis version of Verus Mobile takes a major leap forward, enabling sending and receiving funds to and from VerusIDs, and also use of your VerusID for a password-free, secure web or mobile sign-on, using the VerusID authentication protocol. Verus Mobile v0.x.x supports the latest version of the VerusID authentication protocol, which prepares for the PBaaS upgrade with support for application provisioning of IDs, which simplifies onboarding of users and enables easy, self sovereign payments, markets for IDs/virtual assets, and more securely in any application, all by leveraging the VerusID protocol.

If you are an app developer who wants to benefit from and help pioneer a better, more user-centric, inherently commerce and proof-capable application model for a true Internet of Value, this is the release that enables you! If you've got mobile or web applications that you are seriously building and would like to integrate VerusID authentication, contact one of the community developers for more details

Installation Instructions

To install, simply navigate to this page on your Android device, download and install the APK. You may need to enable apps from outside sources.

Feel free to report any discovered bugs, issues, or suggestions by either publicly asking for community support on one of our mobile channels at https://discord.gg/VRKMP2S, or, for more discretion, emailing development@verus.io.

Privacy and Permissions

No personal data is stored or collected by the Verus Mobile application, except as necessary for authentication. All authentication data is stored locally.

The Verus Mobile application uses the following permissions for the following reasons:
Internet connectivity:
To fetch and post data and communicate with the blockchain through Electrum servers, the app requires internet connectivity. The signing of transactions is done locally and private keys are not shared over any network.

Access to system alerts:
To notify the user of important ongoing events while using the Verus Mobile application, the Verus Mobile application uses the system alert framework on both iOS and Android.

Camera and Audio access:
The Verus Mobile application's VerusPay QR code scanner is designed to read and parse VerusQR codes, or VerusPay invoices through the camera, and requires camera access to work properly. The user will be prompted to allow camera access upon first opening the VerusPay feature. Due to the current constraints of the library being used for VerusPay, the user will be asked to enable audio by default when starting VerusPay for the first time. Choosing to disable audio should in no way affect VerusPay's functionality.

Permission to vibrate the mobile device:
The Verus Mobile application uses the vibration feature of the mobile device it is running on for VerusPay, in order to give feedback upon the scan of a QR code invoice.

Permission to read/write to phone memory:
The Verus Mobile application uses the mobile devices AsyncStorage memory storage to hold encrypted account data while the application isn't running.

Disclaimer

This is experimental and unfinished software. Use at your own risk! No warranty for any kind of damage!
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The enclosed copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.