v0.10.12.x RC4 Testing

Status
Not open for further replies.
Propulsion said:
I didn't know of the faucet. Awesome! Thanks borkanagar and UdjinM6!

Is there a testnet mpos or p2pool ready? If not, I'll be more than happy to set one up.
Click to expand...

borkanagar said:
By looking to the original post of Evan I think that there are two testnet pools:

Mpos + Stratum: http://ec2-54-91-161-78.compute-1.amazonaws.com/index.php
-- connection string: sgminer.exe -o stratum+tcp://54.91.161.78:3333 -u eduffield.1 -p x

Nomp : http://54.183.73.24/
Click to expand...

All pools & tools available are listed here --> https://darkcointalk.org/threads/sticky-testnet-tools-resources.1768/
 
****** Please Update To 10.12.14 or 9.12.14 *******

- Fixed an issue where clients weren't connected to the correct masternode
- Fixed masternode relay issues
- Anonymous Balance now calculates correctly
- Inc protocol to kick old users odd again

Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
 
 
If I understood correctly what the "darkSend Status => Idle" button does, it would be better if it was disabled after clicking it and the text would be changed to "Anonymizing... Please wait"?
 
Because I haven't been able to follow testing closely, I'm wondering if anyone can foresee complications when updating current masternodes. Do you think we'll just have to update our remote servers? ie: turn remote off, delete-replace darksend, start darksend back up. It is all I needed to do in the past, quick and simple with no need to bother the offline wallet. Just hoping that will still be the case. Anyone have an opinion? I know we haven't been able to update for this test due to the corruption on the testnet blockchain, so that's why I'm wondering. Thanks for any speculation :)

Also, I sent myself 1200 coins to see if I could get my wallet to denominate again. apparently, I forgot to keep mining on, LOL. Otherwise, it looked as though my entire wallet denominated completely.
 
TanteStefana said:
Because I haven't been able to follow testing closely, I'm wondering if anyone can foresee complications when updating current masternodes. Do you think we'll just have to update our remote servers? ie: turn remote off, delete-replace darksend, start darksend back up. It is all I needed to do in the past, quick and simple with no need to bother the offline wallet. Just hoping that will still be the case. Anyone have an opinion? I know we haven't been able to update for this test due to the corruption on the testnet blockchain, so that's why I'm wondering. Thanks for any speculation :)

Also, I sent myself 1200 coins to see if I could get my wallet to denominate again. apparently, I forgot to keep mining on, LOL. Otherwise, it looked as though my entire wallet denominated completely.
Click to expand...
I have always needed to update darkcoind on the server, then 'masternode start' from local using the correct wallet and darkcoin.conf file. Although on testnet I'm just running a hot server wallet.
 
flare said:
Here are the CI-builds for v0.9.12.14

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DWD-DRK/QTL/build-86/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...tian-win-darkcoin-bin/32/daemon/darkcoind.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DOD-DRK-69/artifact/QTL/gitian-osx-darkcoin/DarkCoin-Qt.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-62/gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-62/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-62/gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-62/gitian-linux-darkcoin-bin/bin/64/darkcoind
Click to expand...

And here are the CI-builds for v0.10.12.14

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/...arkcoin-rc-darkcoin-qt-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...coin-rc-darkcoind-bin/32/daemon/darkcoind.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DOD-DRKRC-2/artifact/QTL/gitian-osx-darkcoin-rc/DarkCoin-Qt.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/...tian-linux-darkcoin-rc-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...gitian-linux-darkcoin-rc-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/...tian-linux-darkcoin-rc-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...gitian-linux-darkcoin-rc-bin/bin/64/darkcoind
 
So with the new wallet 10.12.14, I'm seeing multiple entries for Darksend Collateral Payment, but no funds are being added to the "anonymized" string.

Can I use coin control to send coins through darksend to a new address in the wallet to anonymize the coins?
 
New (encrypted) wallet & freshly synced x.12.14 client:
1000 tDRK initial balance, Denominating processed one time.
Had repeated password prompts (1x "Payment to yoursel"f, 1x "Darksend denominate").
1.JPG


Debug log now states: "DoAutomaticDenominating : No funds detected in need of denominating"

2.JPG

Balance is not displayed as "Anonymized".
Good(?) thing is, have not seen any collateral payments (first time for my setup).
 
Latest wallet denominated 2000DRK to 3 (some are 4) rounds of DS in about 90 minutes at a cost of 0.006DRK. So: £7000 rendered untraceable for a cost of £0.02. :cool:
 
tdrkmn01-08 updated to 0.10.12.14 (and masternode started).
tp2pool compiled from master-rc4 to 0.9.12.14.
Portchecker now fakes 70026 & 0.9.12.14.

Don't know why but I think .15 will be released once I get to sleep. :p
 
Status
Not open for further replies.
Back
Top