Skip to content

v1.0.8
Compare
Choose a tag to compare
@Asherda Asherda released this 10 Feb 19:54
· 132 commits to master since this release
v1.0.8
64890dd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Announcing RC1 release candidate for Verus Mobile v1.0.8, Mobile Wallet for Android and iOS
This release includes the new Verus PBaaS Universal Payment and Verus PBaaS Identity Provisioning (VPUP and VPIP), QR and deep-link enabled protocols for next generation payments and ID-based onboarding and sales for application development on Verus and all PBaaS chains.
Due to the magnitude of these new capabilities, the impact we believe they can have on identity and payments adoption, and our goal of the highest quality rollout possible, we are making RC1 available on TestFlight and as an APK before the app stores and requesting your testing and feedback! As soon as we feel that these new capabilities are rock solid, which we hope will be very soon, we will roll this out on both the iOS App Store and Google Play.

New Feature Highlights

Verus Mobile 1.0.8 premiers two major new features, VerusID provisioning and VerusPay invoices payable through conversion!

VerusID Provisioning

Verus Mobile 1.0.8 now allows users to receive their own VerusID from an app or service, and then use it to log in to said app/service. This update puts you in control of your online profile and gives developers the freedom to run their apps without relying on centralized accounts.

VerusPay v3 Invoices

VerusPay v3 invoices, supported in the 1.0.8 release, leverage existing PBaaS currency infrastructure to facilitate payments through conversion, or across systems. Users can pay conversion-supporting invoices in any currency they want, provided it fulfills the built in parameters that protect the payee from price slippage.

Community Testing Initiative

Due to the magnitude and number of changes in Verus Mobile 1.0.8, we have put together new ways to test and give feedback to harden and ensure the App/Play store release is as solid as possible. The presentation PDF attached to this announcement contains instructions and links for anyone looking to contribute to the main release of 1.0.8 through testing, and information about any bugs found can be submitted through the bug report form at https://forms.gle/TBdaCrbP62pSUdgS9 (also present in the slide deck).

The current test version of 1.0.8 is available for Android as an APK on the GitHub releases page at https://github.com/VerusCoin/Verus-Mobile/releases/, and for iOS in the TestFlight program at https://testflight.apple.com/join/ZS43lYcw.

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.

Assets 3
Loading