v0.11.0.x Core Testing

[vertoe]

DO NOT* USE V11 ON MAIN NET UNTIL OFFICIAL RELEASE NOTES**.

*) or: at own risk
**) evan's post wasnt an official release comment.

 

[camosoul]

"Works on mainnet" and "Everybody start doing it" are not the same thing, did not mean to imply that it was...

The real test is shifting from testnet to mainnet, always is... I volunteered to be "that guy" as usual... Doesn't mean everyone else should start doing it.

If you used a 'guide' to set up your masternode(s) and you really have no idea how to even linux or how MNs actually work, DO NOT DO IT.

 

[vertoe]

Aside from being left in the dark, and appropriately so, about some changes to function and features, it's working fine... Was a bit confusing to deal with the "undocumented new stuff" but it isn't officially released, so what kinda docs would there be?

Well, try reading the release notes? https://github.com/darkcoin/darkcoin/blob/v0.11.0.x/doc/release-notes/release-notes-0.11.0.md

 

[camosoul]

Well, try reading the release notes? https://github.com/darkcoin/darkcoin/blob/v0.11.0.x/doc/release-notes/release-notes-0.11.0.md

There's only 3 posts on this page... You saying it's not an official release, then trying to troll me for not considering release notes on a non-release that is in testing/progress and may or may not actually do any of that stuff, which the first post, by you, emphasizes is not released... Did you really forget that quickly, or are you just looking for a fight?

[rolls eyes]

That's the only thing you saw in that whole post?

[rolls eyes]

When it becomes a changelog that shows us the wish list that actually made it into the actual RELEASE that doesn't exist yet, then you'll have a point.

This is why I have more important things to do...

Time to make buttloads of guns and make losers mad. Oh, wait...

 

[Sub-Ether]

DO NOT* USE V11 ON MAIN NET UNTIL OFFICIAL RELEASE NOTES**.

*) or: at own risk
**) evan's post wasnt an official release comment.

Vertoe, thats a fine set of realise notes you have, bug quashing to the extreme :grin:

''What is a bug quash? An event where the community comes together with one goal in mind… To quash as many bugs in one day as humanly possible. Don’t just complain, do something about it.''
--Flex developers--

 

[vertoe]

i am not trolling anyone here,
i didnt notice evan is already recommending v11 on main net over at bitcointalk.

well, have fun :what:

 

[camosoul]

Not all/necessarrily directed at vertoe.

i am not trolling anyone here,
i didnt notice evan is already recommending v11 on main net over at bitcointalk.

well, have fun :what:

Evan said it. I'm testing it. Nobody said "Everyone, grab 0.11 and throw it on mainnet!" least of all me. I'm testing it on mainnet, because I have huge clanking balls. I test so you don't have to.

This version has everything and works on mainnet.

Am I lying?

Does it say "Hey everybody, Evan here, everybody update to V0.11 on mainnet?" I'm pretty sure it doesn't say that, and neither did anyone else. Certainly not I.

If you understand what you're doing well enough to sack up, then get in gear and join the REAL testing party. Testnet only gets you so far. You really don't know anything about how it's going to work until you put it in a real, non-sterile environment. Evan said it works, so I sacked up to see how well...

I just barely have what it takes. If you don't, then don't do it. Those who can, must.

Discouraging testing in the testing thread seems kinda not what testing is about... If you'd rather just stand back and let other people do the testing, then do that...

It looks like I'm not alone. I see more nodes than mine on 0.11.0.4 - some were there before mine... If you don't want to test, then don't...

I haven't touched mixing/denomination/darksend... Since November, not a single client I've run on mainnet has denominated even one duff. I don't bother sitting there staring at it anymore. If someone wants to see if 0.11.0.4 does any denom on mainnet, do so at your own risk, but know I'm not doing it... People still report that denom past 8 is a living bug on testnet.... Who knows the consequences... I kinda doubt it'll denom any better considering the hangup isn't addressed...

It may be pre-mixed, but it's still an on-demand mixing function dependent upon other submitting their DRKs, and that's not happening... You need MNs to denom, but you also need coins... My idea for solving this has already gone to the only person on this project that matters in regard to that topic. I won't mention it here because it'll only draw more trolls...

Bye!

 

[eduffield]

I don't think v.11.0.4 is officially released yet. If we use it on Mainnet, use it at our own risk. I think there's still so many things to be fixed.

Yeah, it's not officially released yet. I think everyone got confused because there's someone running a few masternodes on v11.

 

[elbereth]

As far as I could see, mn payments does not work on v11... There was not a single mn payment on testnet since v11 started.

 

[eduffield]

Roadmap for release of v11 eduffield flare UdjinM6 freynder

• darksend balance is not accurate. reproduce: if you try to exactly spend your available anonymous balance, it always throws an error message: not enough denominated funds.
• unchecking and checking the darksend box on send page resets darksend available funds to 0. (Jira-140, Jira-145, Testing-368, Testing-406)
• darksend denominations do not stop at the set limit (e.g. 2000 DRK), it continuosly denominates all available coins. (which is good in my opinion, darksend is very stable recently and we should turn on denominations by default and allow all users to denominate all available coins. maybe we could provide a commandline flag -darksend=0 which disables auto-denominations or -darksendlimit=-1 which sets the denomination amount to unlimited) (Testing-385)
  
• the darksend ui features have several typos and for instance do not use darkcoin units but a hardcoded "DRK" string. this needs some fine tuning. (Testing-398, Testing-399, Testing-400, Testing-401, Testing-403)
  
• another major issue is client performance during scanning the blockchain for darksend transactions. the qt wallet freezes during this process. we really need to put these actions into a seperate thread! it's not releasable, we need to deliver a responsive qt wallet at any time. (Testing-337, Testing-432)
• the darksend progress bar is confusing. maybe improve the label what is 100%, which progress? or simplify it to anon-coins/total-coins. (Testing-415)
• the unlock for anonymization is bugged, it does not reset correctly and shows empty warning messages while sending coins. (Testing-326, Testing-384, Testing-369, Testing-408)
  
• the wallet miner still does not work on some systems (reported win32). (Jira-144)
• a bug in masternode configuration allows to get paid without having 1000 drk (i suspect the masternode=1 flag in config is causing trouble). (Jira-146)
• mac wallet is unusable (not build correctly, doesnt install). (Testing-322, Testing-413)
• miner crashs the wallet while rescanning/reindexing. (Github-89)
• conflicted transactions spam the transaction view. (Testing-336, Testing-355, Testing-429)
• we need automated testing scripts. (Testing-342)
• darksend status enabled/disabled ui issue. (Testing-353, Jira-143)

Anything missing?

eduffield we should not release without having at least fixed the two major highlighted issues.

Thanks for this! I was in the process of compiling this list also. I'll definitely get the red/yellow ones on Monday.

There is a segfault that I'm not sure what's causing though. I'll check into that too. I ran 8 clients over night and 3 crashed, so that's very important.

 

[moli]

Yeah, it's not officially released yet. I think everyone got confused because there's someone running a few masternodes on v11.

Thanks, Evan. Could you also please look at the unresolved issues created on JIRA?

Thank you.

 

[Sub-Ether]

Been doing some benchmarks, wallet took 17 mins to update 24 weeks (seemed to get stuck a little on block 89311 but carried on).
The mixing of 1000 test coins did 19% in 41 minutes,
and now upto 330 darksend tdrk have been mixed in 2 hours and 32 minutes (so 1 third complete)
I make that 2.2 tdrk per minute so far, or 3126 tdrk per day.

Additional:
881 mixed tdrk in 4 hrs 20 mins, so has speeded up to 3.4 tdrk per minute and 4879 tdrk per day is projected..

 

[qwizzie]

the people using v11 on mainnet for testing purposes, will they be doing two pairing mixing with current version (security risk) or does
it automatically switch to three pairing if the wallet is being used on mainnet ?

 

[camosoul]

As far as I could see, mn payments does not work on v11... There was not a single mn payment on testnet since v11 started.

I've gotten plenty of payments with 0.11.0.4 on mainnet... See, it's good that somebody tests this stuff...

<3 drk.mn

There's even a 0.11.0.3 out there...

 

[elbereth]

Well payments are not done with a masternode so you test nothing on that front... Try finding a block with a 0.11.0.4 + masternode payment and then your test will be meaningful.

 

[camosoul]

Well payments are not done with a masternode so you test nothing on that front... Try finding a block with a 0.11.0.4 + masternode payment and then your test will be meaningful.

I'm not mining with it, so point taken.

The pair inquiry is also valid.

I'm also no using darksend, so that isn't tested, either...

DRK has so many things going on, it's more than just loading up a client and getting a green light. Things to do, or not do... Things to test, or not test. So fancy and pretty...

The test's use thus far is that it did not explode and lose coins or do anything else wildly unpredictable/bad. Whee! Evan said it works on mainnet. It does. Wonder how he knew that...

All I cared to see was that start-many was finally working. It is. Yay test! I can run nodes now! People who have been holding off on it can run nodes! People who already run nodes and want to enjoy the process of not sucking really bad can now be happy! It is no longer horrible to run many masternodes! Good thing! Happy time! Test good! There might even be people who didn't want to deal with running their own MN who now have the chance since it's like 100 times easier.

You can use a 0.11.0.4 to fire up 0.10.17.24 nodes if you want it that way. I felt like going all out... Dirty test environment is dirty.

Is that really such a bad thing?

 

[qwizzie]

I seem to have a problem using v11 in combination with IPVanish (a VPN service provider), i can only get v11 to work on Testnet by either
deleting IPVanish or by running IPVanish. If i disconnect IPVanish the UPnP Port Mapping correctly maps my own IP address
but then throws socket receiver error messages at me preventing any peer connections build up.
I dont have any peers connection problems using v.0.10.17.24 (or.25) on Mainnet in combination with IPVanish, i'm a bit worried if v11.0 hits Mainnet i will be having the same peer connection problems.

Debug.log v11.0.4 on Testnet with peer connection problems:

2015-01-11 13:26:14 ERROR: Read : Failed to open file D:\TestDarkcoinData1\testnet3\peers.dat
2015-01-11 13:26:14 Invalid or missing peers.dat; recreating
2015-01-11 13:26:14 Loaded 0 addresses from peers.dat 0ms
2015-01-11 13:26:14 mapBlockIndex.size() = 90338
2015-01-11 13:26:14 chainActive.Tip()->nHeight = 90336
2015-01-11 13:26:14 setKeyPool.size() = 1000
2015-01-11 13:26:14 mapWallet.size() = 5
2015-01-11 13:26:14 mapAddressBook.size() = 1
2015-01-11 13:26:14 AddLocal([2001:0:9d38:6abd:142f:1df1:2685:742b]:19999,1)
2015-01-11 13:26:14 ext-ip thread start
2015-01-11 13:26:14 opencon thread start
2015-01-11 13:26:14 upnp thread start
2015-01-11 13:26:14 net thread start
2015-01-11 13:26:14 addcon thread start
2015-01-11 13:26:14 dnsseed thread start
2015-01-11 13:26:14 init message: Done loading
2015-01-11 13:26:14 msghand thread start
2015-01-11 13:26:14 dumpaddr thread start
2015-01-11 13:26:14 Loading addresses from DNS seeds (could take a while)
2015-01-11 13:26:14 Initialization result: 1
2015-01-11 13:26:15 GetMyExternalIP() received [myownIPaddress] myownIPaddress:0
2015-01-11 13:26:15 GetMyExternalIP() returned myownIPaddress
2015-01-11 13:26:15 AddLocal(myownIPaddress:19999,4)
2015-01-11 13:26:15 ext-ip thread exit
2015-01-11 13:26:16 UPnP: ExternalIPAddress = myownIPaddress
2015-01-11 13:26:16 AddLocal(myownIPaddress:19999,3)
2015-01-11 13:26:19 UPnP Port Mapping successful.
2015-01-11 13:26:21 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:25 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:26 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:26 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:27 5 addresses found from DNS seeds
2015-01-11 13:26:27 dnsseed thread exit
2015-01-11 13:26:28 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:29 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:30 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:31 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:32 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:34 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:34 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:35 socket recv error De externe host heeft een verbinding verbroken. (10054)
2015-01-11 13:26:37 socket recv error De externe host heeft een verbinding verbroken. (10054)

Debug.log of v0.10.17.25 on Mainnet : no problems building up peer connections (8 connections)

2015-01-11 13:51:23 No coin database inconsistencies in last 289 blocks (1704 transactions)
2015-01-11 13:51:23 block index 21500ms
2015-01-11 13:51:24 nFileVersion = 101724
2015-01-11 13:51:24 wallet 313ms
2015-01-11 13:51:24 nInstantXDepth 1
2015-01-11 13:51:24 Darksend rounds 4
2015-01-11 13:51:24 Anonymize Darkcoin Amount 10
2015-01-11 13:51:24 Loaded 10911 addresses from peers.dat 62ms
2015-01-11 13:51:24 RandAddSeed() 239668 bytes
2015-01-11 13:51:24 mapBlockIndex.size() = 196641
2015-01-11 13:51:24 nBestHeight = 196616
2015-01-11 13:51:24 setKeyPool.size() = 1000
2015-01-11 13:51:24 mapWallet.size() = 72
2015-01-11 13:51:24 mapAddressBook.size() = 4
2015-01-11 13:51:24 AddLocal([2001:0:9d38:6abd:142f:1df1:2685:742b]:9999,1)
2015-01-11 13:51:24 dnsseed thread start
2015-01-11 13:51:24 upnp thread start
2015-01-11 13:51:24 net thread start
2015-01-11 13:51:24 addcon thread start
2015-01-11 13:51:24 Loading addresses from DNS seeds (could take a while)
2015-01-11 13:51:24 opencon thread start
2015-01-11 13:51:24 msghand thread start
2015-01-11 13:51:24 dumpaddr thread start
2015-01-11 13:51:24 refreshWallet
2015-01-11 13:51:24 trying connection 82.211.21.16:9999 lastseen=9.0days
2015-01-11 13:51:24 connected 82.211.21.16:9999
2015-01-11 13:51:24 send version message: version 70051, blocks=196616, us=[2001:0:9d38:6abd:142f:1df1:2685:742b]:9999, them=82.211.21.16:9999, peer=1
2015-01-11 13:51:25 Added time data, samples 2, offset -31 (+0 minutes)
2015-01-11 13:51:25 Moving 82.211.21.16:9999 to tried
2015-01-11 13:51:25 receive version message: /Satoshi:0.10.17.25/: version 70051, blocks=201364, us=217.122.139.212:49653, them=82.211.21.16:9999, peer=1
2015-01-11 13:51:25 Added 1 addresses from 5.45.101.232: 182 tried, 10730 new
2015-01-11 13:51:25 27 addresses found from DNS seeds
2015-01-11 13:51:25 dnsseed thread exit
2015-01-11 13:51:25 send initial getblocks peer=1
2015-01-11 13:51:25 ProcessSyncCheckpoint: pending for sync-checkpoint 000000000006223c3f5fd21030586f6cfac2779306429c908afee9b8d7cdea66
2015-01-11 13:51:26 SetBestChain: new best=000000000010fd370fd869484bea5bb18a289c0bc840095294ba9129306ece5d height=196635 log2_work=60.756438 tx=767665 date=2015-01-02 22:57:58 progress=0.990860
2015-01-11 13:51:26 received block 000000000017d143bea3c921feab15722541d1720255b72c68ae46a0ee248bf6 peer=1
2015-01-11 13:51:26 UPnP: ExternalIPAddress = MyownIPaddress
2015-01-11 13:51:26 AddLocal(MyownIPAddress:9999,3)
2015-01-11 13:51:28 UPnP Port Mapping successful.
2015-01-11 13:51:29 connection timeout
2015-01-11 13:51:29 ERROR: GetMyExternalIP() : connection to 91.198.22.70:80 failed
2015-01-11 13:51:34 connection timeout
2015-01-11 13:51:34 ERROR: GetMyExternalIP() : connection to 74.208.43.192:80 failed
2015-01-11 13:51:33 received block 00000000001263dc4989842b4c82699cc7df584aef66df24dd31c97a98d9722a peer=2

 

[vertoe]

I seem to have a problem using v11 in combination with IPVanish (a VPN service provider), i can only get v11 to work on Testnet by either
deleting IPVanish or by running IPVanish. If i disconnect IPVanish the UPnP Port Mapping correctly maps my own IP address
but then throws socket receiver error messages at me preventing any peer connections build up.
I dont have any peers connection problems using v.0.10.17.24 (or.25) on Mainnet in combination with IPVanish, i'm a bit worried if v11.0 hits Mainnet i will be having the same peer connection problems.

Debug.log v11.0.4 on Testnet with peer connection problems:
*snip

Debug.log of v0.10.17.25 on Mainnet : no problems building up peer connections (8 connections)
*snip

did you try to manually add nodes? just asking, the log entry looks like your vpn us cutting the connection. does it work with v10 on testnet? could you check that?

 

[qwizzie]

did you try to manually add nodes? just asking, the log entry looks like your vpn us cutting the connection. does it work with v10 on testnet? could you check that?

i tried adding nodes, tried putting exclusions in my firewall for the v11 test directories (firewall controlled by ESET Smart Security btw). i tried v10 on Testnet, exact same problems.
The problems disappear right after i start IPVanish again, so IPVanish seems to be blocking my Testnet peer connections somehow when its disconnected. Very weird.
I dont even need to close v11 or v10 on Testnet .. i can just keep the client open, start up IPVanish and it starts building peer connections again. And it doesnt behave like this on Mainnet.. very weird.

edit 1: i might i have the excusions in my firewall incorrect (was actually adding exclusion for antivirus .. not the firewall) .. making some changes to see if thats it.

edit 2: yep .. thats it allright. makes perfect sense now, IPVanish overrules Eset's firewall so thats why it could build peer connections when it got activated. I will need to make firewall exclusions for every single test darkcoin-qt.exe

 

[vertoe]

i tried adding nodes, tried putting exclusions in my firewall for the v11 test directories (firewall controlled by ESET Smart Security btw). i tried v10 on Testnet, exact same problems.
The problems disappear right after i start IPVanish again, so IPVanish seems to be blocking my Testnet peer connections somehow when its disconnected. Very weird.
I dont even need to close v11 or v10 on Testnet .. i can just keep the client open, start up IPVanish and it starts building peer connections again. And it doesnt behave like this on Mainnet.. very weird.

edit 1: i might i have the excusions in my firewall incorrect (was actually adding exclusion for antivirus .. not the firewall) .. making some changes to see if thats it.

edit 2: yep .. thats it allright. makes perfect sense now, IPVanish overrules Eset's firewall so thats why it could build peer connections when it got activated. I will need to make firewall exclusions for every single test darkcoin-qt.exe

Testnet is using different ports (19999) than mainnet (9999) that's why maybe.