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

v0.10.13.x RC5 Testing

Status
Not open for further replies.
Evan, if we have 1000 drk to be anonymized and we stop the anonymizing midway, we have 0 anon drk, right? This is like a batch processing. I'm thinking if somehow we can have 1 drk anonymized at a time and throw the 1 anon drk in the box, then the next drk.. and so on..

Exactly what I was trying to say. It's like batch processing. One denomination may finish before another, but each denomination must make it all the way through the Darksend process before you have any anonymized coins at all.
 
Darksend Overview Proposal

7pO99LtNlgXZao08vr59u0x-jGg5XJ4F6fR5_uCctW8cFNtQ7IxBltGBLggcIQ7viaM-lIlLzO7_yTs2QBkO-9SmQpnBPhi_VMRK2MeHaosaTtIVRLYu5h_Hp40CS3aNIg


To make the wallet less intrusive (starting when you boot up the wallet and asking for info) I've added a big "start anon" button, along with removing a lot of the more advanced functionality (you could still set rounds via commandline, but "Amount to anon" would be gone).

What's everyone think of this?

I think this is good - but - does Anon actually STOP right now? Maybe it should have a progress bar pop-up when you click STOP to show when the current Anon funds have and/or will be completed.
 
Exact, they are not backward compatible on protocol level - actually this was already done with RC3 and RC4 :)
Would it be possible for someone to spoof the version number?
 
Exact, they are not backward compatible on protocol level - actually this was already done with RC3 and RC4 :)
If users compile it themselves they could simply bump the protocol version of a previous client and compile it? Is there any way to prevent this, e.g. check for a certain block of code that is unique and required for the current protocol version and compare that to the stated version, and then error out if they don't match?

Edit: never mind, I guess they could change that logic before compiling too!
 
Last edited by a moderator:
Exactly what I was trying to say. It's like batch processing. One denomination may finish before another, but each denomination must make it all the way through the Darksend process before you have any anonymized coins at all.
Unless if the threshold is built into the code, 1 drk gets anonymized at a time.. AND FAST... then shows up on the "Anonymized: xxx DRK" box... It can be like a jackpot ... lol... Hey, i think it can happen :)
 
20% additional mining payments (not paying MNs).
You don't need to change the protocol version for that - simply don't pay the MN. As long as the MN payments are not enforced (i don't like the term) MN operators are relying on volunteer MN payments - but that's well known and has been discussed several times.
 
You don't need to change the protocol version for that - simply don't pay the MN. As long as the MN payments are not enforced (i don't like the term) MN operators are relying on volunteer MN payments - but that's well known and has been discussed several times.

OK, so I don't understand the point? Evan said in a different post that kicking off old protocol versions would give us 90+% payments?
 
I think after anonymizing the backup screen should appear with a message stating its Extremely Important To Backup wallet .dat or something similar. I could see this being a problem for newbies.

sorry if already mentioned else where
 
Last edited by a moderator:
I think after anonymizing the backup screen should appear with a message stating its Extremely Imported To Backup wallet .dat or something similar. I could see this being a problem for newbies.

sorry if already mentioned else where

Good point--and possibly a button to do it (select directory to save in, etc.). With wallet.dat being in %appdata%, not many novices will ever be able to find it.
 
OK, so I don't understand the point? Evan said in a different post that kicking off old protocol versions would give us 90+% payments?

I think you are refering to this post:

I'm going to kick older protocol versions off of the network with RC5. We should be able to get 90%+ because of this. This is also another reason enforcement isn't needed right now, I'd like to try this first.

I don't know how Evan comes to the conclusion that solely the protocol version has a impact on MN payment rate - actually ~90% is the status quo. Even if we kick all pre RC5 clients from the network, the pools that did not update their stratum code will still pay whatever they want.

loAMr.jpg
 
I think you are refering to this post:



I don't know how Evan comes to the conclusion that solely the protocol version has a impact on MN payment rate - actually ~90% is the status quo. Even if we kick all pre RC5 clients from the network, the pools that did not update their stratum code will still pay whatever they want.

loAMr.jpg

It blows my mind that the core of our entire technology relies on people *voluntarily* sacrificing 20% of their mining revenue...

It's not that 90% payment rate is insufficient, it's that I don't like the entire protocol depending on altruism!
 
It blows my mind that the core of our entire technology relies on people *voluntarily* sacrificing 20% of their mining revenue...

It's not that 90% payment rate is insufficient, it's that I don't like the entire protocol depending on altruism!
Welcome to my world :)
 
compiling
CI-builds for v0.9.13.5-g6bdeb35

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

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

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

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

CI-builds for v0.10.13.5-g62f08ce

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-35/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
 
Thank you, flare, for doing all the compiling for us ... :)
BTW, the testnet faucet is down. Is there another faucet?
Thank you.
 
Status
Not open for further replies.
Back
Top