• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.11.0.x Core Testing

Status
Not open for further replies.
Some of the resources in this list are outdated or don't exist. I recall someone making a post (not sure if it was on these forums) with some updated material for testing. I would like to help test I'm just not 100% sure where to start. Anyone remember that post at all or can point me in the right direction, thanks.
 
Darksend is hustling along now that the wallet has finally synced. :smile:

Could we have some tooltips though - what does the 'Try Mix' button do for example?
 
I am still on the road from years end holiday - back tomorrow, will have a look then.

Hope you enjoyed your holiday! Safe trip home.

I'm just setting up a build-environment under Win7 with mingw....let's see if the Berkeley-DB build has finished before you'll be back, mingw is _really_ slow :rolleyes:

I've never build a wallet with Windows...so far I've only build mining software.

I'll come back to you if I should have troubles finding/building all the dependent packages.

Good luck crowning, I'm anxious to start testing...
 
Some of the resources in this list are outdated or don't exist. I recall someone making a post (not sure if it was on these forums) with some updated material for testing. I would like to help test I'm just not 100% sure where to start. Anyone remember that post at all or can point me in the right direction, thanks.
What would you like to help with? This is a new version forked from Bitcoin v0.9.3 so there are a lot of changes, and I'm sure that sticky thread will be updated, but it takes time.

I think right now for this test version, only the linux wallet is working. So if you want to grab the linux wallet, make a darkcoin.conf file with just one line "testnet=1" in the file, and put the file in the same directory with "Darkcoin", you can run the wallet on Testnet. Have fun. :)
 
Having trouble getting connections, have a 'addnode=188.40.57.201' but no relief, yet. Anybody got some ips for me?

Been maybe an hour, have deleted peers.dat once or twice

{
"version" : 110000,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 1000.00000000,
"blocks" : 85432,
"timeoffset" : 0,
"connections" : 0,
"proxy" : "",
"difficulty" : 0.12185734,
"testnet" : true,
"keypoololdest" : 1420144221,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
 
src/version.h

// disconnect from peers older than this proto version
-static const int MIN_PEER_PROTO_VERSION = 70052; //70046
+static const int MIN_PEER_PROTO_VERSION = 70046;

Does this mean peers from the older wallet version 0.10.17.x can connect too ?
I was exspecting something like this i guess for this new 0.11.0.x version :

+static const int MIN_PEER_PROTO_VERSION = 70052;

Also i'm wondering if the compilings on page 1 are including the hotfix or not ?
 
Last edited by a moderator:
Handy tDrk faucet link: https://drkipn.com/test/faucet/
is it updated to 0.11 yet? teamer?


Tried the faucet, didn't complain about a bad address, but the count didn't go down and I didn't get the coin.


I'll take 21,000 tDRK if you have it: yF7Gv2WG5fAaARA7wcDpXQTuBujsC1LvHT

I have 20k tDRK spread amongst 20 wallet.dats -- is there an easy way to migrate to 'x/y' addresses?


-- Also, is it prudent/possible to increment the testnet address constant to guarantee 'y' prefixes?
The 'x' addresses that do appear are near the top of their base-encoding range 'xv' and 'xw' for example. Anecdotally, the highest 'y' address I've seen so far is 'yL' about middle of the available 'y' range.


-- found a UI control issue in 'Amount of Darkcoin to keep anonymized' : numeric (keyboard) input is constrained to values of 1000 or below -- arrow increment control allows setting beyond 1000 limit.
 
Last edited by a moderator:
windows 64bits version not working, application crashed once try to open. I see that it has been mentioned above, so I proceed to try linux version.

for my case, 0-1 active connection to darkcoin network (most of the time is 0), with no block source available.
i have added below to the .darkcoin/darkcoin.conf
testnet=1
addnode=188.40.57.201
(i didn't add testnet=1 the first time i started the qt, not sure if testnet address will be generated or not)

my first time running testnet for darkcoin, hence 49 weeks behind. any bootstrap dat file to download?

thanks
 
Having trouble getting connections, have a 'addnode=188.40.57.201' but no relief, yet. Anybody got some ips for me?

Been maybe an hour, have deleted peers.dat once or twice

{
"version" : 110000,
"protocolversion" : 70052,
"walletversion" : 60001,
"balance" : 1000.00000000,
"blocks" : 85432,
"timeoffset" : 0,
"connections" : 0,
"proxy" : "",
"difficulty" : 0.12185734,
"testnet" : true,
"keypoololdest" : 1420144221,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
debug log to [email protected] please.

we have 3 seed nodes in place, if you dont get connections, something is wrong. cc: flare coingun
 
src/version.h

// disconnect from peers older than this proto version
-static const int MIN_PEER_PROTO_VERSION = 70052; //70046
+static const int MIN_PEER_PROTO_VERSION = 70046;

Does this mean peers from the older wallet version 0.10.17.x can connect too ?
I was exspecting something like this i guess for this new 0.11.0.x version :

+static const int MIN_PEER_PROTO_VERSION = 70052;

Also i'm wondering if the compilings on page 1 are including the hotfix or not ?
This diff is outdated, the clients still connect to 0.10.17.x instances.
 
Tried the faucet, didn't complain about a bad address, but the count didn't go down and I didn't get the coin.


I'll take 21,000 tDRK if you have it: yF7Gv2WG5fAaARA7wcDpXQTuBujsC1LvHT

I have 20k tDRK spread amongst 20 wallet.dats -- is there an easy way to migrate to 'x/y' addresses?


-- Also, is it prudent/possible to increment the testnet address constant to guarantee 'y' prefixes?
The 'x' addresses that do appear are near the top of their base-encoding range 'xv' and 'xw' for example. Anecdotally, the highest 'y' address I've seen so far is 'yL' about middle of the available 'y' range.


-- found a UI control issue in 'Amount of Darkcoin to keep anonymized' : numeric (keyboard) input is constrained to values of 1000 or below -- arrow increment control allows setting beyond 1000 limit.

I've send you 4k tDRK using Darksend: (first v11 Darksend transaction? \:D/)
http://test.explorer.darkcoin.fr/tx/c0f242ae517b240d5f40836a9c04759ee472d2e21bf3e9b755bd156303dbfc4e

You dont need to migrate wallets, private key versions didnt change, just reuse your old wallets.
 
windows 64bits version not working, application crashed once try to open. I see that it has been mentioned above, so I proceed to try linux version.

for my case, 0-1 active connection to darkcoin network (most of the time is 0), with no block source available.
i have added below to the .darkcoin/darkcoin.conf
testnet=1
addnode=188.40.57.201
(i didn't add testnet=1 the first time i started the qt, not sure if testnet address will be generated or not)

my first time running testnet for darkcoin, hence 49 weeks behind. any bootstrap dat file to download?

thanks

please send debug.log to [email protected]
 
Here are some addnodes for testing:

Code:
S 81.169.177.196    Sat 0.10.17.23    0.3MB     0.3MB     11:37:40  85340
I 104.156.253.63... Cor 0.11.0        0.3MB     0.3MB     11:37:38  85340
I 104.190.200.36... Sat 0.10.16.16    0.2MB     0.4MB     11:37:36  85340
  198.50.148.87     Sat 0.10.17.23    0.4MB     0.3MB     11:37:33  85339
  108.61.164.106    Sat 0.10.17.24    0.4MB     0.3MB     11:37:15  85340
  211.99.224.173    Sat 0.10.17.18    0.3MB     0.3MB     11:36:34  85341
I 134.119.17.131    Sat 0.10.16.16    0.1MB     0.3MB     11:36:10  85341
  178.62.203.249    Sat 0.10.17.24    0.3MB     0.3MB     11:36:09  85341
  142.179.227.96    Sat 0.10.17.24    0.2MB     0.3MB     11:35:31  85341
  94.23.248.61      Sat 0.10.17.23    0.1MB     0.3MB     11:35:30  85341
  85.214.22.190     Sat 0.10.17.23    0.3MB     0.3MB     11:35:19  85341
I 185.69.55.203     Sat 0.10.17.24    0.2MB     0.3MB     11:34:27  85341
I 211.99.224.162    Sat 0.10.17.18    0.3MB     0.3MB     11:33:57  85341
I 54.93.55.12       Cor 0.11.0        0.1MB     0.3MB     11:29:50  85341
I 107.191.48.59     Sat 0.10.17.16    0.3MB     0.3MB     11:29:21  85342
I 2003:45:4941:5... Cor 0.11.0        0.1MB     0.3MB     11:15:22  85346
I 2003:45:4941:5... Cor 0.11.0        0.1MB     0.3MB     11:13:53  85346
I 78.46.66.139      Cor 0.11.0        0.3MB     0.3MB     11:13:19  85346
I 50.254.73.145     Cor 0.11.0        0.1MB     0.2MB     04:59:51  85168
I 50.88.201.1       Cor 0.11.0        0.0MB     0.1MB     03:52:20  85519
I 86.154.222.162    Cor 0.11.0        0.0MB     0.1MB     03:50:41  85519
 
Status
Not open for further replies.
Back
Top