Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

V12.1 Testnet Launch Thread

Discussion in 'Testing' started by eduffield, May 23, 2016.

  1. eduffield

    eduffield Core Developer
    Dash Core Team

    Joined:
    Mar 9, 2014
    Messages:
    1,084
    Likes Received:
    5,316
    Trophy Points:
    183
    Introduction

    As you are likely aware, development has been progressing rapidly in 2016 as we pursue the next set of objectives on the 2016 roadmap. Because of the multitude of changes needed to facilitate the radical enhancements envisioned to our network’s capabilities and our user experience, we have divided development efforts into two main working groups - Core and Evolution. Today, I am excited to announce that the next set of Core capabilities are ready to begin testing of our 12.1 release.

    Before I provide more details on the extensive changes included in 12.1, I’d like to explain some of the reasoning behind the changes. It is frequently not immediately obvious to outside observers how many of these changes contribute toward the Evolution strategy, so it is helpful to review some of the challenges we’ve faced with our current governance and budgeting system, as well as the foundational capabilities we will need to support a system as complex as Evolution.

    I am very proud of the progress we’ve made up through 12.0. We have established an incredibly powerful set of differentiators using our governance and blockchain-based funding model. We were the first cryptocurrency to recognize the now-obvious idea that transactional security is only one of a multitude of needs the network has - first by incentivizing full nodes and later by providing funding for other critical needs like development, marketing, legal, infrastructure, business partnerships, and so much more.

    However, as could be expected, there are a number of flaws in the first iteration of the budgeting system. Let me provide just two examples. First, we’ve discovered the risks of multi-month proposals being defunded before completed. That might be acceptable in some situations, but we recognize the need in other cases for the network to be able to guarantee its commitments. Another example has been the lack of control proposal owners have once a proposal is submitted. When a proposal is no longer valid or needs to be changed or replaced, the owner is currently unable to cancel or even reduce the requested funding. We have managed to deal with most of the issues that have arisen so far, but clearly improvements are needed to make the entire system more effective.

    Because 12.1 will fix many of these issues, it is understandable that many people immediately conclude (incorrectly) that we’ve been working on governance for the last few months, instead of working toward Evolution. While the benefits to our funding and governance mechanisms are very real, the real development focus has been on foundational elements needed to enable Dash Evolution. Enhanced governance and funding mechanisms are simply the first beneficiaries of this new capability, mainly because the underlying components were already built… 12.1 simply allows us to enhance them easily.

    With that background, allow me to explain in greater detail what we’ve been building. 12.1 is really all about the delivering the foundational components of Dash Evolution in a new and improved network API interface known as Sentinel. 12.1 includes these changes and many other improvements for a brand new and improved user experience.

    Sentinel enables massive flexibility when designing a decentralized application, including massive storage capacity, custom object creation capability, and friendly data query access through a normalized database (mysql in this case). To demonstrate the capabilities of this new type of software, we are going to implement simple governance contracts to start. After 12.1 is released we will begin creating new primitives for users, businesses, projects, milestones, reports, etc.

    What does all this mean for the delivery of Dash Evolution? There are several main benefits. First, it will allow us to iterate software changes extremely rapidly. It also allows much greater flexibility in the types of objects and functionality we want to deploy. We will be able to query the network data with industry standard database and visualization tools so we can understand the activity taking place on the network. And finally, we will have the ability to support API functionality, a requirement for the third network tier.

    Besides the changes required for Dash Evolution, we also have good news for masternode operators. We will now officially support masternodes which are directly ran from hardware wallets. Presently, masternodes are run from cold wallets, which are already quite secure. This new feature will allow our masternode operators an even higher security environment for their masternode collateral and infrastructure.

    You will also notice a new theme engine, a new masternode GUI, and a rebranding of InstantX (now InstantSend) and DarkSend (now PrivateSend).

    Thank you to everyone involved in helping develop 12.1!


    Partial Changelog

    • Generic object storage (network primitives) with attached generic data format
    • Sentinel Implementation
    • UI enhancements
    • Masternode list with start/stop support
    • Merged upstream changes
    • Reset testnet
    • Improved flatfile storage mechanism for data
    • Cleaned up/Refactored InstantSend implementation
    • Masternodebroadcast raw function for hardware wallet support
    • Vote by alias for randomized, more private budget voting
    • Fixed lockup issues
    • New theme support (light theme)
    • Independant Dash icon depending on network and theme
    • Improved dash-syncing code
    • DS Speed Improvements
    • Rebranded Darksend to PrivateSend
    • Rebanded InstantX to InstantSend
    • Fancy new masternode-trezor wallet

    Thx Udjin, Crowning, Tyler, Flare, TheLazier and everyone who contributed!


    Wallet Updates

    Here are some screenshots of the new improved experience.


    [​IMG]


    [​IMG][​IMG]



    Masternode Hardware Wallet support

    This highly anticipated feature allows masternode operators to start and stop their masternode from the Trezor hardware wallet. This allows us a great deal more security for our masternode operators to secure their highly valuable collateral.

    ** NOTE: This feature requires a trezor and our dash-electrum client. It's not available via the core-qt wallet **

    For more information about how to use this, please see the guide here:

    https://github.com/dashpay/electrum-dash/blob/develop/docs/masternodes.md

    [​IMG]


    [​IMG]



    Testnet Agenda


    We’re opening testing to the public and are going to be testing everything in the following order:

    • Phase 1: Configuration / Syncing / Message Propagation
    • Phase 2: Normal Network Functionality (DS/IX)
    • Phase 3: Masternode Trezor Support
    • Phase 4: Enhanced Budget System | Sentinel
    • Phase 5: Pre-launch
    • Phase 6: Launch
    Latest builds (git-1ceca7e) of v0.12.1.x branch

    Linux --> https://dashpay.atlassian.net/builds/browse/DASHL-DEV-535/artifact/JOB1/gitian-linux-dash-dist/
    Windows --> https://dashpay.atlassian.net/builds/browse/DASHW-DEV-484/artifact/JOB1/gitian-win-dash-dist/
    MacOS X --> https://dashpay.atlassian.net/builds/browse/DASHM-DEV-492/artifact/JOB1/gitian-osx-dash-dist/
    Raspberry --> https://dashpay.atlassian.net/builds/browse/DASHP-DEV-488/artifact/JOB1/gitian-RPi2-dash-dist/

    Changelog:

    - QT: right-click to start alias in "My Masternodes": https://github.com/dashpay/dash/pull/786
    - QT: fix truncation in Masternodes tab: https://github.com/dashpay/dash/pull/787
    - DB: fix FlatDB: https://github.com/dashpay/dash/pull/785
    - fix voting: https://github.com/dashpay/dash/pull/783

    Testnet tools (explorers, faucets, pools) --> https://www.dash.org/forum/threads/testnet-tools-resources.1768/
    Please direct your bugreporting to: https://github.com/dashpay/dash/issues/new
     
    #1 eduffield, May 23, 2016
    Last edited: May 23, 2016
    • Like Like x 27
    • Winner Winner x 1
    • Informative Informative x 1
    • Creative Creative x 1
  2. Minotaur

    Minotaur Well-known Member
    Foundation Member

    Joined:
    Apr 7, 2014
    Messages:
    452
    Likes Received:
    1,079
    Trophy Points:
    263
    Great! Lets do this!
     
    • Like Like x 2
    • Agree Agree x 2
  3. splawik21

    splawik21 Grizzled Member
    Dash Core Team Foundation Member Dash Support Group

    Joined:
    Apr 8, 2014
    Messages:
    2,082
    Likes Received:
    1,415
    Trophy Points:
    1,283
    Unslept nights comming again.
    Great to have it officially now.
    Testing activated.
     
    • Like Like x 3
    • Agree Agree x 1
  4. yidakee

    yidakee Well-known Member
    Foundation Member

    Joined:
    Apr 16, 2014
    Messages:
    1,812
    Likes Received:
    1,168
    Trophy Points:
    283
    Ready to rumble. 4 tMN's coming right up.
     
    • Like Like x 3
    • Agree Agree x 1
  5. crowning

    crowning Official Dash Dev
    Core Developer Moderator

    Joined:
    May 29, 2014
    Messages:
    1,430
    Likes Received:
    2,009
    Trophy Points:
    183
    @flare @UdjinM6 : since you manage our transifex account: we should start and coordinate the translations, there's a lot of new strings to translate which must be uploaded to transifex.

    • I'll do (as always) the German translation
    • Russian: Udjin I guess
    • ...
    • ...
     
    • Like Like x 3
    • Agree Agree x 3
  6. fible1

    fible1 Well-known Member
    Dash Core Team Masternode Owner/Operator

    Joined:
    May 11, 2014
    Messages:
    716
    Likes Received:
    726
    Trophy Points:
    163
    Hey All :),
    I have two questions:

    1. Is Trezor going to work with the core wallet now? Is that right? I'm confused.
    2. Can someone please dumb it down and explain sentinel to me? I remember reading the white paper and I still don't get it.

    Thanks in advance,
    Pablo.
     
  7. yidakee

    yidakee Well-known Member
    Foundation Member

    Joined:
    Apr 16, 2014
    Messages:
    1,812
    Likes Received:
    1,168
    Trophy Points:
    283
    Portuguese transifex volunteer here!

    Masternode tab not showing for me - v0.12.1.0-1ceca7e ... I believe Splawik has the same issue

    [​IMG]
     
    • Like Like x 1
  8. UdjinM6

    UdjinM6 Official Dash Dev
    Dash Core Team Moderator

    Joined:
    May 20, 2014
    Messages:
    3,606
    Likes Received:
    3,516
    Trophy Points:
    1,183
    I can try to answer #1 - trezor is working with electrum which in its turn should now utilize new dashd ability to relay masternode broadcast messages signed elsewhere i.e. you should be able to start masternode from electrum wallet.

    copy/paste from slack:
    do you have masternode.conf with at least one legit record there?
    if not it’s not shown by default but you can enable it in preferences -> wallet -> expert -> show masternode tab
     
    • Like Like x 1
  9. fible1

    fible1 Well-known Member
    Dash Core Team Masternode Owner/Operator

    Joined:
    May 11, 2014
    Messages:
    716
    Likes Received:
    726
    Trophy Points:
    163
    @UdjinM6 So I will need to run both Dash-Qt and Electrum at the same time, sort of like armory? Or is electrum stand alone?

    Pablo.
     
  10. yidakee

    yidakee Well-known Member
    Foundation Member

    Joined:
    Apr 16, 2014
    Messages:
    1,812
    Likes Received:
    1,168
    Trophy Points:
    283
    @UdjinM6 - sweet got the MN tab.

    Just to report that in Linux the MN sub-tabs are justified left and not centered, unlike the OSx example above.

    [​IMG]
     
  11. UdjinM6

    UdjinM6 Official Dash Dev
    Dash Core Team Moderator

    Joined:
    May 20, 2014
    Messages:
    3,606
    Likes Received:
    3,516
    Trophy Points:
    1,183
    Electrum only but electrum server you are connecting to has to 1) run dashd 12.1+ 2) use electrum-dash-server latest code
     
    • Agree Agree x 1
    • Informative Informative x 1
  12. fible1

    fible1 Well-known Member
    Dash Core Team Masternode Owner/Operator

    Joined:
    May 11, 2014
    Messages:
    716
    Likes Received:
    726
    Trophy Points:
    163
    Ah cool. Now I just need to wrap my head around Sentinel :).

    Pablo.
     
  13. studioz

    studioz Well-known Member

    Joined:
    Sep 10, 2014
    Messages:
    512
    Likes Received:
    451
    Trophy Points:
    163
    im getting this in console when i :masternode start


    12:19:07

    Not capable masternode: Invalid port: 9999 - 9999 is only supported on mainnet.


    what is the testnet port ?
     
  14. Balych

    Balych Active Member

    Joined:
    Sep 12, 2015
    Messages:
    366
    Likes Received:
    211
    Trophy Points:
    113
    Dash Address:
    Xba1ychX7CjgbRrCKE1LjHjT3jLUhcexs5
    19999
     
    • Like Like x 1
  15. BrainShutdown

    BrainShutdown Well-known Member
    Foundation Member

    Joined:
    Apr 8, 2014
    Messages:
    151
    Likes Received:
    72
    Trophy Points:
    188
    Oh boy that masternode tab is top :D

    Mining, transactions and masternodes are working here, very fast sync congratulations to all involved!

    Now the questions...

    What does PRE_ENABLED status mean? Do I need to do something else?

    Synchronizing additional data always stops at 75% QT windows 64 bit, on budget sync...
     
  16. flare

    flare Administrator
    Dash Core Team Moderator

    Joined:
    May 18, 2014
    Messages:
    2,281
    Likes Received:
    2,419
    Trophy Points:
    1,183
    It means that your node did not ping by itself yet, but it should start after ~15mins if all is setup ok.
     
  17. AjM

    AjM Well-known Member
    Foundation Member Masternode Owner/Operator

    Joined:
    Jun 23, 2014
    Messages:
    1,298
    Likes Received:
    564
    Trophy Points:
    283
    @UdjinM6
    I tried add this report to git 3 times, and every time it was deleted immediately, dunno why, maybe word commandline is no good for git.

    Help menu -> Commandline options -> instantx and darksend commands should be instantsend and privatesend.

    wrongwords.png

    Edit: WTF, now git show all 3 issue i made, how i can delete 2?
    Edit2: closed 2.
    Edit3: typo
     
    #17 AjM, May 23, 2016
    Last edited: May 23, 2016
    • Funny Funny x 1
  18. Balych

    Balych Active Member

    Joined:
    Sep 12, 2015
    Messages:
    366
    Likes Received:
    211
    Trophy Points:
    113
    Dash Address:
    Xba1ychX7CjgbRrCKE1LjHjT3jLUhcexs5
    Same on Windows 2012 R2 x64, log:
    Code:
    2016-05-23 16:46:51 ProcessMessages(dstx, 1827 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
    2016-05-23 16:46:51 ProcessMessages(dstx, 1827 bytes) FAILED peer=31
    2016-05-23 16:46:55 CMasternodeSync::Process() - tick 2737 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:01 CMasternodeSync::Process() - tick 2743 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:07 CMasternodeSync::Process() - tick 2749 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:13 CMasternodeSync::Process() - tick 2755 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:19 CMasternodeSync::Process() - tick 2761 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:25 CMasternodeSync::Process() - tick 2767 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:31 CMasternodeSync::Process() - tick 2773 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:37 CMasternodeSync::Process() - tick 2779 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:43 CMasternodeSync::Process() - tick 2785 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:49 CMasternodeSync::Process() - tick 2791 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:47:55 CMasternodeSync::Process() - tick 2797 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:01 CMasternodeSync::Process() - tick 2803 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:07 CMasternodeSync::Process() - tick 2809 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:13 CMasternodeSync::Process() - tick 2815 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:19 CMasternodeSync::Process() - tick 2821 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:25 CMasternodeSync::Process() - tick 2827 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:27 dseg - Sent 1 Masternode entries to 94.23.248.61:19999
    2016-05-23 16:48:27 dseg - Sent 1 Masternode entries to 188.226.161.128:19999
    2016-05-23 16:48:27 dseg - Sent 1 Masternode entries to 178.62.203.249:19999
    2016-05-23 16:48:27 dseg - Sent 1 Masternode entries to 95.85.48.49:19999
    2016-05-23 16:48:27 dseg - Sent 1 Masternode entries to 162.243.59.230:19999
    2016-05-23 16:48:31 CMasternodeSync::Process() - tick 2833 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:37 CMasternodeSync::Process() - tick 2839 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:43 CMasternodeSync::Process() - tick 2845 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:49 CMasternodeSync::Process() - tick 2851 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:48:51 ProcessMessages(dstx, 1827 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
    2016-05-23 16:48:51 ProcessMessages(dstx, 1827 bytes) FAILED peer=24
    2016-05-23 16:48:55 CMasternodeSync::Process() - tick 2857 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:01 CMasternodeSync::Process() - tick 2863 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:07 CMasternodeSync::Process() - tick 2869 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:13 CMasternodeSync::Process() - tick 2875 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:19 CMasternodeSync::Process() - tick 2881 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:25 CMasternodeSync::Process() - tick 2887 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:31 CMasternodeSync::Process() - tick 2893 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:37 CMasternodeSync::Process() - tick 2899 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:43 CMasternodeSync::Process() - tick 2905 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:49 CMasternodeSync::Process() - tick 2911 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:49:55 CMasternodeSync::Process() - tick 2917 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:50:01 CMasternodeSync::Process() - tick 2923 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:50:07 CMasternodeSync::Process() - tick 2929 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:50:13 CMasternodeSync::Process() - tick 2935 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:50:19 CMasternodeSync::Process() - tick 2941 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000
    2016-05-23 16:50:25 CMasternodeSync::Process() - tick 2947 RequestedMasternodeAttempt 0 RequestedMasternodeAssets 4 nSyncProgress 0.750000

    Dont know if anyone use traditional wallet skin, but:
    [​IMG]
    [​IMG]
     
  19. AjM

    AjM Well-known Member
    Foundation Member Masternode Owner/Operator

    Joined:
    Jun 23, 2014
    Messages:
    1,298
    Likes Received:
    564
    Trophy Points:
    283
    I confirm this.
    Waited one hour, still 75%.
     
    • Like Like x 1
  20. BrainShutdown

    BrainShutdown Well-known Member
    Foundation Member

    Joined:
    Apr 8, 2014
    Messages:
    151
    Likes Received:
    72
    Trophy Points:
    188
    Thanks, that was it just needed to wait.
     
    • Like Like x 1
  21. Comodore

    Comodore Member

    Joined:
    Nov 8, 2015
    Messages:
    185
    Likes Received:
    97
    Trophy Points:
    88
    On my windows 10 64 bit, my instance of dash-qt is not accepting my masternode setting that worked well under previous version. So it does not start.

    Testnet dash-qt does not start at all.

    EDIT: Thanks for advice. Now testnet works.
     
    #21 Comodore, May 23, 2016
    Last edited: May 23, 2016
  22. yidakee

    yidakee Well-known Member
    Foundation Member

    Joined:
    Apr 16, 2014
    Messages:
    1,812
    Likes Received:
    1,168
    Trophy Points:
    283
    On the Ubuntu 15 side of life... Checks barely visible

    [​IMG]

    And...

    [​IMG]
     
  23. flare

    flare Administrator
    Dash Core Team Moderator

    Joined:
    May 18, 2014
    Messages:
    2,281
    Likes Received:
    2,419
    Trophy Points:
    1,183
    What are you refering to? test_dash-qt.exe is NOT testnet. You need to add the parameter

    Code:
    testnet=1
    to your dash.conf and start normal dash-qt.exe instead.
     
    • Like Like x 1
    • Agree Agree x 1
  24. yidakee

    yidakee Well-known Member
    Foundation Member

    Joined:
    Apr 16, 2014
    Messages:
    1,812
    Likes Received:
    1,168
    Trophy Points:
    283
    Ha! Over a year without setting up a node thanks to Node40, haven't lost my touch...

    Code:
    
    {
      "overall": "Successfully started 4 masternodes, failed to start 0, total 4",
      "detail": {
        "status": {
          "alias": "MN1",
          "result": "successful"
        },
        "status": {
          "alias": "MN2",
          "result": "successful"
        },
        "status": {
          "alias": "MN3",
          "result": "successful"
        },
        "status": {
          "alias": "MN4",
          "result": "successful"
        }
      }
    }
    
    The Masternode tab is really really neat!
     
    • Like Like x 1
  25. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder Moderator

    Joined:
    Jul 15, 2014
    Messages:
    2,464
    Likes Received:
    2,497
    Trophy Points:
    1,183
    • Like Like x 2
  26. donho

    donho Member
    Masternode Owner/Operator

    Joined:
    Apr 16, 2014
    Messages:
    98
    Likes Received:
    21
    Trophy Points:
    58
    great news! Makes me even happier that my Trezor just got shipped :) Can't wait to test it
     
    • Like Like x 2
  27. crowning

    crowning Official Dash Dev
    Core Developer Moderator

    Joined:
    May 29, 2014
    Messages:
    1,430
    Likes Received:
    2,009
    Trophy Points:
    183
    I'll take care of those 2 tomorrow.
     
    • Like Like x 2
  28. qwizzie

    qwizzie Well-known Member

    Joined:
    Aug 6, 2014
    Messages:
    1,180
    Likes Received:
    630
    Trophy Points:
    183
    As mentioned before by others i can confirm that my Windows 10, 64-bit wallet stays a long long long time in "synchronising budgets (75%)" stage, sometimes showing "syncing network" before going to "synchronising budgets (75%)" again.

    Explorers:

    - https://test.explorer.dash.org - by flare --> working okay
    - http://test.explorer.dashninja.pl - by elbereth --> working okay
    - http://test.insight.masternode.io:3001 - by coingun ---> not working
    - http://test.insight.dash.siampm.com - by thelazier --> working okay (it first had a "cannot connect to Insight server'' but its fine now)
    update : unfortunetely it still throws some errors :

    Can't connect to dashd to get live updates from the p2p network. (Tried connecting to dashd at {{host}}:{{port}} and failed.)
    Can't connect to insight server. Attempting to reconnect...

    Faucets :

    - http://test.faucet.masternode.io - by coingun --> not much in that faucet i think, got some 750 tDash
    - https://test.faucet.dash.org - by flare --> working, provides 1000 tDash
    - http://test.faucet.dashninja.pl - by elbereth --> working, provided a cool 1271 tDash :)

    Last block is 10458 from 14 minutes ago, we could use some more mining power.
    edit : got a stuck explorer, fixed it by going into private mode.
     
    #28 qwizzie, May 23, 2016
    Last edited: May 23, 2016
    • Like Like x 1
  29. Balych

    Balych Active Member

    Joined:
    Sep 12, 2015
    Messages:
    366
    Likes Received:
    211
    Trophy Points:
    113
    Dash Address:
    Xba1ychX7CjgbRrCKE1LjHjT3jLUhcexs5
    It's 0.12.1-only test and all this banned peers on Peers tab are <0.12.1 version?

    [​IMG]

    And tDASH address looks not compatible with previous version, same privkey on different wallets:
    https://test.explorer.dash.org/address/yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE
    https://test.explorer.dash.org/address/yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT
    23:11:01

    validateaddress yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE


    23:11:01

    {
    "isvalid": false
    }


    23:11:10

    validateaddress yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT


    23:11:10

    {
    "isvalid": true,
    "address": "yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT",
    "scriptPubKey": "76a914fbd4a9ade22c174af44b5c440d13ec130d18f5ad88ac",
    "ismine": true,
    "iswatchonly": false,
    "isscript": false,
    "pubkey": "0375194e15a13b9e2acd07865b0e3ca5ed118dd9879befa4d167f0a64ea71c169b",
    "iscompressed": true,
    "account": ""
    }
    23:10:29

    validateaddress yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE


    23:10:29

    {
    "isvalid" : true,
    "address" : "yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE",
    "ismine" : true,
    "iswatchonly" : false,
    "isscript" : false,
    "pubkey" : "0375194e15a13b9e2acd07865b0e3ca5ed118dd9879befa4d167f0a64ea71c169b",
    "iscompressed" : true,
    "account" : ""
    }


    23:10:39

    validateaddress yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT


    23:10:39

    {
    "isvalid" : false
    }
     
    #29 Balych, May 23, 2016
    Last edited: May 23, 2016
  30. bertlebbert

    bertlebbert Active Member

    Joined:
    Jul 17, 2014
    Messages:
    669
    Likes Received:
    288
    Trophy Points:
    133
    Same here, on Win7 (64 bit) stays stuck at Synchronizing budgets (75%).
     
    • Like Like x 1

Share This Page