Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

Copay Beta - Mainnet Launch (Target date TBD - critical issue found in testing)

Discussion in 'Official Announcements' started by Liz R, Aug 3, 2018.

  1. Liz R

    Liz R New Member
    Dash Core Team

    Joined:
    Mar 2, 2018
    Messages:
    8
    Likes Received:
    56
    Trophy Points:
    13
    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

    [​IMG]

    [​IMG]

    [​IMG]
     
    • Like Like x 6
    • Winner Winner x 1
  2. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder Moderator

    Joined:
    Jul 15, 2014
    Messages:
    2,520
    Likes Received:
    2,528
    Trophy Points:
    1,183
    I’m glad to see this finally rounding into form.
     
    • Like Like x 1
  3. Liz R

    Liz R New Member
    Dash Core Team

    Joined:
    Mar 2, 2018
    Messages:
    8
    Likes Received:
    56
    Trophy Points:
    13
    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.
     
    • Informative Informative x 3
    • Winner Winner x 1
  4. Stealth923

    Stealth923 Well-known Member
    Foundation Member

    Joined:
    Mar 9, 2014
    Messages:
    336
    Likes Received:
    351
    Trophy Points:
    233
    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!
     
    • Like Like x 2
    • Agree Agree x 1
  5. strangerman

    strangerman New Member

    Joined:
    Jun 15, 2018
    Messages:
    3
    Likes Received:
    1
    Trophy Points:
    3
    Information about this update is a rocket for me :)
    Great! Thank you
     
    • Like Like x 1
  6. Liz R

    Liz R New Member
    Dash Core Team

    Joined:
    Mar 2, 2018
    Messages:
    8
    Likes Received:
    56
    Trophy Points:
    13
    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...
     
    • Informative Informative x 3
    • Like Like x 1
    • Winner Winner x 1

Share This Page