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

v0.10.12.x RC4 Testing

Status
Not open for further replies.
****** Please Update To 10.12.15 or 9.12.15 *******

We shouldn't see anymore collateral fees now, plus processing large amounts of funds will go MUCH faster. Try to make a wallet with 5000-100k DRK and let it run, let's see how well this works now.

- Added session IDs for masternode communication. Clients were getting confused when they got messages about other sessions (sometimes happened when they all jumped on the same masternode at once)
- Added a pre-session state where the client will query a random masternode and ask if they can perform a merge on N darkcoin without giving any other information. If that amount is compatible without losing anonymity, the client will then add it's entry for merging
- Added code to randomly use the top 20 masternodes, this can dynamically be increased as more transaction traffic starts to happen (although it's not implemented but it could be done later)
- After successful transactions clients will now automatically attempt another session on a random masternode, then repeat until they get any kind of error or run out of funds that need to be processed.
- Fixed a change address reuse issue
- Fixed an issue with the compatible join algorithm (Masternodes will only join the same denominations, this wasn't always the case before)
- Inc protocol to kick old users odd again

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt

CI-builds for v0.9.12.15


Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DWD-DRK/QTL/build-87/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-70/artifact/QTL/gitian-osx-darkcoin/DarkCoin-Qt.dmg

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

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-63/gitian-linux-darkcoin-bin/bin/64/darkcoinqt
http://bamboo.darkcoin.qa/artifact/BL-DRK/QTL/build-63/gitian-linux-darkcoin-bin/bin/64/darkcoind


CI-builds for v0.10.12.15

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-4/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
 
I was going to report the ver 14 this morning had ZERO collateral payments
Not sure if it's because I have 50Mb/s connection??
But yesterday night was the 1st time I could get on test net - LOVE it so far.
Gonna play with it all night tonight and tomorrow - no work tomorrow.
Hope there's somebody to play with tonight - lol

Great job Evan - will update to V15 tonight
 
this will be sorted by CI builds

EDIT: Will need to invest in more CPU instances on AWS :grin:
Ha! Off topic, but you wouldn't believe the bill I received for my Masternodes on Amazon.
Will definitely have to look into other options...
 
latestCoinControl.png

Wallet is now showing all of the addresses with funds in it in coincontrol. No denomination has taken place as of yet.
 
tdrkmn01-08 updated to 0.10.12.15 (and masternode started).
tp2pool compiled from master-rc4 to 0.9.12.15.
Portchecker now indicates 0.9.12.15 and protocol version 70027.
 
Sorry if this has been addressed already, but I had ~2,500 tDRK anonymized, and I sent 123.456789 tDRK to my other wallet, and then tried to send 1 tDRK immediately after, but couldn't. "Unable to locate enough Darksend denominated funds for this transaction". Are there plans on getting this optimized somehow, or maybe ideas already? Maybe having more small inputs than "necessary" even if it means more bloat, or starting denominating immediately after sending funds.. what's the reason for all inputs becoming non-anonymized after send?
I think this is an issue to do with the wallet not intelligently choosing pre-denominated funds. I think it chooses all the smaller funds first or something, because if you chose a fund (usually the highest possible available, because it's easy) then you can send again and again and again. So this needs work IMO
 
The thing is, once you've sent coins, they are no longer 'clean.' They need to be remixed on arrival to maintain perfect privacy. I'm not sure there's an easy way around that, but maybe having a default of say 5 'proper' addresses in the wallet that got anonymised separately would alleviate the have-to-wait-before-sending-again-from-that-wallet problem. This could be user configurable as to how many 'readied' addresses you maintained.
If that's the case, then people should have the option to premix what they expect they'll need. Say I need to pay a bill this month of 150 dark, then I'd probably choose to mix only 200 dark in preparation. Otherwise, I'd feel like I'm going to be nickeled and dimed to death
 
Ok, so I've updated to newest wallet, encrypted it and sent 2000 drk to it. It is 1:56PM Pacific time, lets see how long it takes for the coins to start denominating and if having the wallet encrypted causes any troubles :)

Ok, wallet immediately asked for my pass phrase.... the second the 2000 tDRK cleared
2:49PM was asked to input password again :) that's 53 minutes...

I'm wondering what the "DarkSend round" and -2 means?
3dzkOs.jpg


Anyways, that's what it looked like after my first darksend round I guess, it must be doing a new round now because I had to sign the second time, right?

3:13 PM another pop up, I signed, and sent it on it's way. Now my coin control looks like this:
Errr, actually it hasn't changed? AND I haven't been charged any transaction fees yet either?
 
Last edited by a moderator:
I have expanded my testnet MN portfolio and can report that new UK masternode 149.255.109.167 was recently started and showed up in both chaeplin's and elbereth's lists in less than 20 seconds. Forgot to add port 19999 to the externalip in the conf file too, didn't seem to matter.
 
Status
Not open for further replies.
Back
Top