Copay - Beta Version w/ Mainnet Support Available for Test (iOS + Android)

[Liz R]

Dash Community,

We are currently prepping the Copay beta for launch on mainnet. This version will:

• Add mainnet support
• Fix all critical bugs
• Apply the new Dash branding

We are targeting August 17 for the release.

Thank you all for your feedback on the testnet beta version released in June - we appreciate your help in improving our products. We knew when we released it that there was still work to be done, such as implementing the new branding, but wanted to provide the community with the ability to test the functionality as quickly as possible. We are also working to be pragmatic about the use of our resources, ensuring that we continue to maximize time spent on Evolution related work.

The mainnet beta version, while not a full redesign, will include the rebranded look and feel. Some screenshots are included below (though please note, some minor elements may change slightly). We have also fixed all bugs identified as critical (list below).

As mentioned, we are trying to maximize time spent on Evolution, so our goal is to address critical functionality. Some lower priority issues will remain in this beta version with the aim to continue resolving the remaining items in future versions. That said, please continue to report any issues found during testing here: https://www.dash.org/forum/topic/copay-support.139/.

Critical Issues Fixed

1. InstantSend does not work

2. InstantSend errors when trying to send non-InstantSend transactions

3. Adding contact to address book via QR code should cut everything after actual address

4. No options to scroll down to see Remove button on contact’s page (some devices)

5. Dash / BTC / fiat market prices - When trying to tap on USD value in Sent or Received TX (in Recent Transactions) the USD value changes to Bitcoin market price at time of TX

6. Request specific amount confirmation step: BTC is shown

7. Wallet service URL - in description URL: bws.bitpay.com

8. Wrong URL when tapping on Insufficient Funds

9. Have to scan QR code twice when adding a contact

Rebranded Design Screenshots

 

[TaoOfSatoshi]

I’m glad to see this finally rounding into form.

 

[Liz R]

Dash Community,

Wanted to share an update regarding the DashCopay wallet.

The good news is that the new branding has been implemented and the app now reflects the brighter color scheme, fonts and icon set.

However, continued testing revealed a critical issue that, while intermittent, impacts ‘send’ functionality for shared wallets. While we are trying to limit resources spent on CoPay as we maximize efforts on Evolution, this problem impacts a key function of the CoPay app and must be fixed.

Our target date to push the beta to mainnet was August 17, but we must push this back. We are actively working on issue resolution and will keep you all updated when we have a new target release date.

Thank you all for your help testing the app. We have a small team at DCG working on CoPay as most folks are working hard on Evolution, so your help finding bugs and recommending changes has been extremely valuable for the improvement of this product.

Thank you for your patience and understanding as we work through this.

 

[Stealth923]

Thank you very much for the update. Glad to see core updating us now when there are issues and delays instead of silence. Well done!

 

[Liz R]

Quick update to keep our CoPay watchers informed -

The team is still working on a solution to the critical issue, but the good news is we believe the root cause has been identified. Below are some details the team shared regarding the status.

Issue Summary
When trying to send funds from a shared wallet user intermittently encounters "error querying the blockchain" message and transaction fails.

Root Cause

• The issue appears to be caused by a fee that is beneath the network minimum (1000 duffs / kb).
• There is a discrepancy between the fee estimated by dashd and the fee reported by Insight API. Transaction Fee estimates provided by BWS are drawn directly from Insight API.
• The fee levels provided by dashd are correct and the fee levels provided by Insight API are not.
  
• The transaction fails and the "Error querying blockchain" occurs because it attempts to query a non-existent transaction.
• The default fee levels for testnet allowed for normal transactions to broadcast, effectively hiding this Insight API issue up until this week when we began testing on mainnet.

Next Steps

• Team has set up local instance of Insight API.
• Waiting for correct fee estimates to be returned (need to build up a tx history before it will start returning valid estimates).
• Identify where/how the fee estimated by dashd is getting transformed to a different value as reported by Insight API.
• No ETA yet on the fix but if this is indeed the issue we hope to have a resolution soon.

Stay tuned...

 

[Efietskop]

@Liz R Is this issue related to the default Trezor wallet (wallet.trezor.io) also having difficulty automatically determining the correct fee for transactions? It may be worth it to reach out to Trezor about it.

It is easily circumvented by using electrum-Dash. But it is kind of annoying that you always have to set a custom fee with the Trezor web wallet (and on top of that the fee is too high because the web page doesn't accept a 1 duff/byte custom transaction fee).

Edit: I just submitted a support ticket about the issues to Trezor/Satoshi Labs. Should have done that earlier but the form to submit a support ticket is difficult to find.

 

[Liz R]

@Liz R Is this issue related to the default Trezor wallet (wallet.trezor.io) also having difficulty automatically determining the correct fee for transactions? It may be worth it to reach out to Trezor about it.

It is easily circumvented by using electrum-Dash. But it is kind of annoying that you always have to set a custom fee with the Trezor web wallet (and on top of that the fee is too high because the web page doesn't accept a 1 duff/byte custom transaction fee).

Edit: I just submitted a support ticket about the issues to Trezor/Satoshi Labs. Should have done that earlier but the form to submit a support ticket is difficult to find.

Interesting - I am not sure of this myself, but will pass along to the dev team and ask if it's related. Thanks for the heads up. The team's applied a patch to BWS that hopefully should resolve the issue for the time being (at least for CoPay - unsure about Trezor but we'll look into it). We're testing currently and hope to have the latest build ready for public test soon.

 

[Liz R]

CoPay watchers:

The team has tested the fix for the critical issue mentioned above, and we believe we have our release candidate for the mainnet beta. This build includes fixes for all the critical issues mentioned above, plus this most recent issue.

Barring any other issues we aim to have the build ready in the Google Play Store within the next couple days. We will also be submitting the build to Testflight for iOS testers. (The date of availability for iOS will be based on how long it takes Apple to review the build.)

We will share an update once the build is ready for test on Android, and another when it is approved by Testflight and ready for test on iOS. If you are not already on the public tester list for iOS, please shoot me an email at [email protected] and I will add you to the list.

Thanks for hanging in there with us!

 

[Stealth923]

CoPay watchers:

The team has tested the fix for the critical issue mentioned above, and we believe we have our release candidate for the mainnet beta. This build includes fixes for all the critical issues mentioned above, plus this most recent issue.

Barring any other issues we aim to have the build ready in the Google Play Store within the next couple days. We will also be submitting the build to Testflight for iOS testers. (The date of availability for iOS will be based on how long it takes Apple to review the build.)

We will share an update once the build is ready for test on Android, and another when it is approved by Testflight and ready for test on iOS. If you are not already on the public tester list for iOS, please shoot me an email at [email protected] and I will add you to the list.

Thanks for hanging in there with us!

Great job - excellent communication and updates

Dont forget the PR news release when its live on both app stores

 

[Efietskop]

Just an update on my Trezor issue earlier in this thread. They (SatoshiLabs) told me they are aware of the issue and that it will be fixed in the next release.

 

[Liz R]

Just an update on my Trezor issue earlier in this thread. They (SatoshiLabs) told me they are aware of the issue and that it will be fixed in the next release.

Nice - thanks for the update!

 

[Liz R]

CoPay friends:

The beta version DashCoPay, with mainnet support, is now available for test on both Android in the Google Play Store and on iPhone through Apple Testflight.

Few things to note:

• This build defaults to mainnet instead of testnet. This means real money can be exchanged using the wallet now. That said, please remember this app is still in beta, so please proceed with caution. If you prefer to test on testnet, you may toggle to testnet when creating a new wallet by tapping 'advanced options' and toggling 'testnet' on.

• Team advises testers to please uninstall previous versions of the beta, and reinstall the new version to ensure effective testing.

We welcome your help testing critical functionality - e.g. core functions like send and receive. We would also love to hear your feedback on the application of the new Dash branding. Your input will not only give us guidance on how we proceed with CoPay, but also contribute to a better experience in all apps - including DashPay (a.k.a. The “Evo” wallet). Please continue to report bugs and provide feedback here: https://www.dash.org/forum/topic/copay-support.139/

As mentioned previously, we are trying to maximize time spent on Evolution - so beyond applying the new branding, we aimed to address only critical functionality for this beta release. We do have some known, non-critical issues that we opted to fix as time and resources allow in subsequent releases. Below is a list of known (non-critical) bugs at this time.

1. When swiping to send, may accidentally swipe the app itself on iPhone
2. Push notifications should be suppressed due to notifications server issues
3. When opening app for first time, “CoPay” incorrect font sometimes shows on iPhone
4. Keyboard covers input field when creating spending PIN on iPhone X preventing user from seeing what they are typing
5. Lock option says “Lock with Fingerprint” instead of “Lock with FaceID” on iPhone X
6. Back arrows too high in some places

Thank you for your help and partnership on this effort.

 

[Stealth923]

CoPay friends:

The beta version DashCoPay, with mainnet support, is now available for test on both Android in the Google Play Store and on iPhone through Apple Testflight.

Few things to note:

• This build defaults to mainnet instead of testnet. This means real money can be exchanged using the wallet now. That said, please remember this app is still in beta, so please proceed with caution. If you prefer to test on testnet, you may toggle to testnet when creating a new wallet by tapping 'advanced options' and toggling 'testnet' on.

• Team advises testers to please uninstall previous versions of the beta, and reinstall the new version to ensure effective testing.

We welcome your help testing critical functionality - e.g. core functions like send and receive. We would also love to hear your feedback on the application of the new Dash branding. Your input will not only give us guidance on how we proceed with CoPay, but also contribute to a better experience in all apps - including DashPay (a.k.a. The “Evo” wallet). Please continue to report bugs and provide feedback here: https://www.dash.org/forum/topic/copay-support.139/

As mentioned previously, we are trying to maximize time spent on Evolution - so beyond applying the new branding, we aimed to address only critical functionality for this beta release. We do have some known, non-critical issues that we opted to fix as time and resources allow in subsequent releases. Below is a list of known (non-critical) bugs at this time.

1. When swiping to send, may accidentally swipe the app itself on iPhone
2. Push notifications should be suppressed due to notifications server issues
3. When opening app for first time, “CoPay” incorrect font sometimes shows on iPhone
4. Keyboard covers input field when creating spending PIN on iPhone X preventing user from seeing what they are typing
5. Lock option says “Lock with Fingerprint” instead of “Lock with FaceID” on iPhone X
6. Back arrows too high in some places

Thank you for your help and partnership on this effort.

Just did some quick testing on iOS and finally this looks like a good release!!! - The UI has been fixed and now looks sleek, and love the cohesive branding. The performance has also been greatly optimized and is now very snappy, compared to previous release.

Will do more testing later - congrats on a high quality release so far!

 

[Liz R]

Just did some quick testing on iOS and finally this looks like a good release!!! - The UI has been fixed and now looks sleek, and love the cohesive branding. The performance has also been greatly optimized and is now very snappy, compared to previous release.

Will do more testing later - congrats on a high quality release so far!

Thanks - so glad you are pleased. Thanks for the feedback and your help with testing!

 

[JGCMiner]

Thanks - so glad you are pleased. Thanks for the feedback and your help with testing!

This was posted on Reddit.

“In the Chinese language interface, all Dash words are translated into Bitcoin”

https://www.reddit.com/r/dashpay/comments/9aratd/comment/e4y5z9q

I can’t personally verify, but it may be worth double checking.

 

[InhumanPerfection]

This was posted on Reddit.

“In the Chinese language interface, all Dash words are translated into Bitcoin”

https://www.reddit.com/r/dashpay/comments/9aratd/comment/e4y5z9q

I can’t personally verify, but it may be worth double checking.

This is from my review of previous version. As I see nothing changed in regard of translation in new version.

...
Bitcoins instead of Dash

• in japanese and chinese:
  • everywhere is bitcoin
• in russian:
  • in Home when no wallets: "Create bitcoin-wallet"
  • in Send
    • when no wallet: "...get some bitcoin"
    • when no funds: "...buy bitcoin" "...receive bitcoin" "Show bitcoin address"
    • in "Recepient" field "... enter bitcoin address"
  • in Settings: "Bitcoin fee policy"
  • Settings - Wallet settings - More options - Wallet addresses: "Each bitcoin wallet..."

...

Edit: And am I only one for whom InstantSend doesn't work? (see my second review of the new version):

InstantSend: still not working when you scanning address (if you paste address - IS works fine)

Edit2: And everybody else is ok with current fees? It's 20 duff/byte on "Super Economy"! Huh?

 

[Liz R]

Hey folks,

Today we released a few updates to the Copay beta in the Google Play store. We submitted this build to Testflight as well and are waiting on Apple to push it. This build includes the following fixes:

• Fixed positioning of back arrows on some screens
• Resolved issue with 'Hide balance' option resetting after hitting 'Tap and hold to show' (improvement on the original Copay)
• Suppressed the invitation to enable push notifications on first download until larger notification server issues are resolved
• Fixed the incorrect logo that loads on first install of app
• Fixed issue with the keyboard covering input field when creating a spending PIN
• Resolved InstantSend issues

We continue to collect, prioritize and fix as many reproducible issues as we can alongside our other priorities. Thanks again for everyone's help with testing.