V12.1 Testnet Launch Thread

[flare]

Latest builds (v0.12.1.0-de7b2b6) of v0.12.1.x branch

Linux --> https://dashpay.atlassian.net/builds/browse/DASHL-DEV-597/artifact/JOB1/gitian-linux-dash-dist/
Windows --> https://dashpay.atlassian.net/builds/browse/DASHW-DEV-544/artifact/JOB1/gitian-win-dash-dist/
MacOS X --> https://dashpay.atlassian.net/builds/browse/DASHM-DEV-553/artifact/JOB1/gitian-osx-dash-dist/
Raspberry --> https://dashpay.atlassian.net/builds/browse/DASHP-DEV-549/artifact/JOB1/gitian-RPi2-dash-dist/

Changelog:

Merge https://github.com/dashpay/dash/pull/910: Refactor CActiveMasternode
Merge https://github.com/dashpay/dash/pull/909: Randomize DoAuto timeouts
Merge https://github.com/dashpay/dash/pull/908: Remove global strMasterNodePrivKey
Merge https://github.com/dashpay/dash/pull/903: Implement transaction lock zmq notifications
Merge https://github.com/dashpay/dash/pull/906: Improve CreateDenominated and MakeCollateralAmounts
Merge https://github.com/dashpay/dash/pull/913: Further SelectCoinsGrouppedByAddresses / mixing process improvements/fixes
Merge https://github.com/dashpay/dash/pull/915: Store block hash in CDiskBlockIndex
Merge https://github.com/dashpay/dash/pull/918: Change anonymizedashamount -> privatesendamount for consistency
Merge https://github.com/dashpay/dash/pull/920: Slightly refactor FindRandomNotInVec
Merge https://github.com/dashpay/dash/pull/921: Fix project name Dash -> Dash Core
Merge https://github.com/dashpay/dash/pull/917: Move broadcast creation to CMasternodeBroadcast
Merge https://github.com/dashpay/dash/pull/919: Add option to hide warning about low keys
Merge https://github.com/dashpay/dash/pull/923: Backport prevector fixes
Merge https://github.com/dashpay/dash/pull/922: Refactor/fix spork
Merge https://github.com/dashpay/dash/pull/924: Fix AddRef() usage
Merge https://github.com/dashpay/dash/pull/925: fix a bug in #920
Merge https://github.com/dashpay/dash/pull/926: Change extended key version bytes to BIP32
Merge https://github.com/dashpay/dash/pull/911: Fix sync process
Merge https://github.com/dashpay/dash/pull/927: Fix GUI MN list
Merge https://github.com/dashpay/dash/pull/930: [UI] IPv4, IPv6 and TOR stats added to Information tab
Merge https://github.com/dashpay/dash/pull/931: Fix GetBlockHash
Merge https://github.com/dashpay/dash/pull/895: Refactor InstantSend to use block count instead of local time
Merge https://github.com/dashpay/dash/pull/905: Change default datadir
Merge https://github.com/dashpay/dash/pull/914: Merge Bitpay's version of Bitcoin Core (additional indexes)
Merge https://github.com/dashpay/dash/pull/934: Fix Inv Bugs
Merge https://github.com/dashpay/dash/pull/935: Slightly refactor keepass module / replace magic number
Merge https://github.com/dashpay/dash/pull/936: Bump NO_BLOOM_VERSION and SENDHEADERS_VERSION to match PROTOCOL_VERSION
Merge https://github.com/dashpay/dash/pull/937: Fix/improve upon previous DS refactoring
Merge https://github.com/dashpay/dash/pull/938: Fix bug in #895
Merge https://github.com/dashpay/dash/pull/939: More IS refactoring
Merge https://github.com/dashpay/dash/pull/940: Adjust block download timeouts to match Dash avg block time (bitcoin/4)
Merge https://github.com/dashpay/dash/pull/941: Simplify CountByIP()
Merge https://github.com/dashpay/dash/pull/942: Leave some space for free transactions by defaut (10000)
Merge https://github.com/dashpay/dash/pull/943: Fixed non-deterministic CSporkMessage hash function
Merge https://github.com/dashpay/dash/pull/944: V0.12.1.x governance pr - part 1 - base functionality


Testnet tools (explorers, faucets, pools) --> https://www.dash.org/forum/threads/testnet-tools-resources.1768/

 

[Comodore]

Nope

Agent 'Elastic Agent on i-d126f65a' went offline while building DASHW-DEV-JOB1-544. The results of that build will not be available.

(17 Aug 2016, 11:01:16 AM)

 

[MangledBlue]

Nope

Agent 'Elastic Agent on i-d126f65a' went offline while building DASHW-DEV-JOB1-544. The results of that build will not be available.

(17 Aug 2016, 11:01:16 AM)

beat me to it - lol

edit for spelling

 

[GNULinuxGuy]

Dedicated tMN updated. Be warned it defaults to a working directory of ~/.dashcore now, so if you just update the code and start the daemon it won't be using your old configuration.

 

[GNULinuxGuy]

Dedicated tMN running v0.12.1.0-de7b2b6 is stuck on block 56763. Deleting *.dat except wallet.dat and reindexing didn't help.

 

[UdjinM6]

Dedicated tMN running v0.12.1.0-de7b2b6 is stuck on block 56763. Deleting *.dat except wallet.dat and reindexing didn't help.

yep, testnet is broken atm, working on it...

 

[Comodore]

https://dashpay.atlassian.net/builds/browse/DASHW-DEV-545/artifact/JOB1/gitian-win-dash-dist/ Last build here

 

[GNULinuxGuy]

Should I build the latest git myself, or wait on another official test release? Feeling a bit impatient. In part because I've been working hard to make more time to help out lately.

 

[Comodore]

I am on latest build, not forking anymore.

Is there some guide for MNs? I would like to try to work with that.

 

[camosoul]

Should I build the latest git myself, or wait on another official test release? Feeling a bit impatient. In part because I've been working hard to make more time to help out lately.

I tried to get involved with testnet, but this put me off of it as well... When I have the time, it's in total disarray and nobody is around. When the ball is rolling, I've got other things I need to do... I guess it's just the nature of the thing, but the scheduling is keeping a lot of would-be contributors out.

 

[UdjinM6]

We are trying to get it up and running smoothly before inviting testers. There are invalid blocks in testnet chain already and probably there will be few more while we implement new code. We don't want to confuse people too much (yet ). Stay tuned

PS. of course you can compile from source, give different versions (from PRs) a try and leave some feedback (PR comments or in general issues) on github as usual.

 

[qwizzie]

I took the build of today for a ride (https://dashpay.atlassian.net/builds/browse/DASHW-DEV/latest/artifact/JOB1/gitian-win-dash-dist/) and its looking good
with regards to mixing. I did notice some messages "masternode unknown" & "request incomplete : unknown response", but i got 900 Dash mixed in 8 rounds in 90 minutes.
I let it sync from scratch and did not find any problems syncing it to latest block.

On a sidenote : it would be nice if we could somehow add the dash vote tracker (http://dashvotetracker.com/)
to our wallet, through a seperate tab perhaps? (Overview - Send - Receive - Transactions - Masternodes - Project Proposals) or have it implemented in Dash Evolution ?

 

[TanteStefana]

I've had a couple of MN running all this time, should I turn them off?

 

[TanteStefana]

I'm wondering if we can test the new electrum wallet for trezor with MN support in this round?

If so, how would I do it?

 

[qwizzie]

I've had a couple of MN running all this time, should I turn them off?

with only 11 masternodes on Testnet it could be wise to upgrade your masternodes to latest version if you plan on keeping them running...

 

[TanteStefana]

I think I just did The thing is, the protocol is 70201 and if I'm not mistaken, that's the previous protocol, no? Did they forget to update the number perhaps? Or do I remember incorrectly?

 

[qwizzie]

Sentinel pr 1 just got merged :

getgovernanceinfo

23:20:54

{"governanceminquorum": 1,
"superblockcycle": 24}

edit :

consensus.nGovernanceMinQuorum = 10;

good thing we have 11 masternodes on Testnet. They all appearently form (or could form) 1 quorum currently.

getsuperblockbudget 1

23:24:45

0.00

getsuperblockbudget index

23:27:09

Error: Error parsing JSON:index

I guess we have to add a superblock first to it..

Edit : Another merge, looks like integration of Sentinel is in full swing.

Edit : a merge to activate superblocks at block 61000 (not merged yet, it had a failure merging)

 

[TanteStefana]

That's weird, last night I started my two tMNs with the MN tab, my remote MNs didn't actually say they started, but the wallet assured me they were started, so I just left everything as is. Now I just noticed that they never did start up, and my wallet shows them as having not started. The local walet says they're pre-enabled again (whatever that means) but no go on the remotes. I don't know what I should do. I remember them just turning on after a long wait before on testnet, but it aint happening.

I did reindex, but I'm going to try dumping all the files and rebuilding. That'll probably work

Wow, after cleaning out my .dash folder and restarting, I realized there are no files like we used to have (don't remember, debug.log, mnpayments.dat peers.dat, etc.... all not being recreated like they normally would be, yet my wallets are open???


Yah, I think I had trouble last time making this work. Maybe I forgot something? But I'm too tired right now to work on this I'll be back.............tomorrow!

 

[qwizzie]

That's weird, last night I started my two tMNs with the MN tab, my remote MNs didn't actually say they started, but the wallet assured me they were started, so I just left everything as is. Now I just noticed that they never did start up, and my wallet shows them as having not started. The local walet says they're pre-enabled again (whatever that means) but no go on the remotes. I don't know what I should do. I remember them just turning on after a long wait before on testnet, but it aint happening.

I did reindex, but I'm going to try dumping all the files and rebuilding. That'll probably work

Wow, after cleaning out my .dash folder and restarting, I realized there are no files like we used to have (don't remember, debug.log, mnpayments.dat peers.dat, etc.... all not being recreated like they normally would be, yet my wallets are open???


Yah, I think I had trouble last time making this work. Maybe I forgot something? But I'm too tired right now to work on this I'll be back.............tomorrow!

This is how my folder currently looks like from one of my normal wallets (i'm not running a masternode on Testnet) :

i would wait untill the pulls that got merged 30 minutes ago (https://github.com/dashpay/dash/commits/v0.12.1.x) are included in a new build and then build from scratch (with only wallet and masternode.conf / dash.conf left)

 

[TanteStefana]

Yah, I'm waiting

 

[GNULinuxGuy]

Wow, after cleaning out my .dash folder and restarting, I realized there are no files like we used to have (don't remember, debug.log, mnpayments.dat peers.dat, etc.... all not being recreated like they normally would be, yet my wallets are open???

A few posts back I mentioned that the working directory (-datadir) has changed from ".dash" to ".dashcore". That change probably explains your confusion.

Really eager to start testing all this new code, but it seems they're still not quite ready for us.

 

[qwizzie]

Yep, we are still awaiting official announcement for testing on Testnet as they are still ironing out the bugs.
For me this is just some personal testing.

Talking about bugs :

Bug 1

v0.12.1.0-d48fe53
Windows 10, 64bit
Windows qt wallet 64bit

Syncing from scratch (delete everything but wallet.dat and dash.conf file)
Synced to latest block
Synchronizing with network : 0 hours behind
Wallet get stuck in endless synchronization "0 hours behind" and wont move further

Close and restart wallet fixes this..

Bug 2 (or maybe it just works that way)

Using keypool refill 10000 in windows wallet (in debug console) freezes the wallet for some time.
Once it responds again you need to close and restart the windows wallet in order to get the extra keys.

 

[TanteStefana]

A few posts back I mentioned that the working directory (-datadir) has changed from ".dash" to ".dashcore". That change probably explains your confusion.

Really eager to start testing all this new code, but it seems they're still not quite ready for us.

Ah, well, thank you Now to fix!

 

[MangledBlue]

Still no word on when testing is to resume?

Can we get a report an ETA - something?

 

[TanteStefana]

I'm concerned that the folder was changed from .dash to .dashcore. This has allowed me to believe my MNs were running, which they weren't - at least not on the updated version.

I'm afraid this is going to cause all kinds of havoc when we fork. Was there a strong and necessary reason for this?

 

[UdjinM6]

@TanteStefana https://github.com/dashpay/dash/issues/898 , we'll mention this change in release notes as a major one and will also provide instructions how to upgrade with minimal effort on each platform win/linux/mac.

 

[MangledBlue]

Still no word on when testing is to resume?

Can we get a report an ETA - something?

I must be on ignore - OR - nobody can/will answer my question......... fairly typical ,,,,,,

 

[AjM]

I must be on ignore - OR - nobody can/will answer my question......... fairly typical ,,,,,,

https://www.dash.org/forum/threads/august-2016-development-update.10018/

Testing is currently progressing for 12.1, and we are presently working on getting superblocks to be created and accepted on the network. This introduces a lot of new code and needs some work before community-wide public testing would be beneficial. The current one is a process of debugging thousands of new lines of code, and making sure most of the work flows are tested and function on a basic level without critical errors. We should expect to shift to public testing of version 12.1 within the next two weeks.

Evans message was Aug 2, so, pub testing is 2 weeks late.

 

[GNULinuxGuy]

Evans message was Aug 2, so, pub testing is 2 weeks late.

Given the latest testing release is dated Aug 17th, I wouldn't say his estimate was off. That said, I'm really hoping to see a new testnet release this weekend!

 

[fible1]

Does anyone know what the new "secret" features we were supposed to get are? Have these been released yet? Asking because I haven't been to testnet in a while.

Pablo.