• 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.
I just realized, if people are able to mix their denominated funds with non-denominated funds, then the coins that were mixed with them (other people's coins) might be exposed??? Please correct me if I'm wrong. I'd think at least if you've only denominated 2 rounds (how many mixing partners are in a round?) You could be exposed by someone exposing their darksend funds.?? What do you all think?
Yes thats a huge issue and I vote for popping up at least 15 warning message boxes where you have to enter random stuff to really confirm you want to do this and understand what it means mixing both input types.

I had that issue in my who am i game. I was able to track myself down because I did exactly that.
 
Yes thats a huge issue and I vote for popping up at least 15 warning message boxes where you have to enter random stuff to really confirm you want to do this and understand what it means mixing both input types.

I had that issue in my who am i game. I was able to track myself down because I did exactly that.
I think mixing inputs should not be allowed, ever. it might expose other people who think they're safe.

Can anyone say how exposed a person's wallet is during the time it is unlocked for denominating? I mean if it takes hours and hours, are you a sitting duck? One good thing is that each round, you have to re-unlock your wallet but still, I'm kind of weary about this when we go live...

For me it's not that big a deal because most of my coins are masternode coins, I only have a few otherwise, so .... but I don't understand my risk when the wallet is open, and how I might minimize it?

BTW collateral damage: a30c29f218cd26664d2481512bac65e233445ae62bc84845c1c2efcbe28007d8
 
Last edited by a moderator:
Yes thats a huge issue and I vote for popping up at least 15 warning message boxes where you have to enter random stuff to really confirm you want to do this and understand what it means mixing both input types.

I had that issue in my who am i game. I was able to track myself down because I did exactly that.
DS+ should be on by default. If you don't want anonymous transactions, use Bitcoin. Yes, DS+ incurs fees. They are tiny.

It's an anonymous currency, it should be used as such. Fools complaining they got charged a pittance because they didn't read the instructions should be ignored.
 
DS+ should be on by default. If you don't want anonymous transactions, use Bitcoin. Yes, DS+ incurs fees. They are tiny.

It's an anonymous currency, it should be used as such. Fools complaining they got charged a pittance because they didn't read the instructions should be ignored.
I also vote for enabling DS+ by default. This also ensures that wallets are denominating by default and lots of denomination transactions are available.
 
****** Please Update To 10.12.19 or 9.12.19 *******

I'm going to do one last update tomorrow morning, then we'll launch Monday or Tuesday.

- Added GUI configuration for Darksend Rounds, Enable Darksend and Anonymize amount of DRK
- Removed 5000DRK hard limit
- Fixed another cause of getting hit by collateral
- Send dialog now shows selected balance (Anon, non-anon and Total)

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
Good morning, fresh CI-builds which fixes the "Darksend round GUI" bug


CI-builds for v0.9.12.19-gc33e2e8

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

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

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

CI-builds for v0.10.12.19-g0aebfe1

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-11/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
 
Can anyone say how exposed a person's wallet is during the time it is unlocked for denominating? I mean if it takes hours and hours, are you a sitting duck?

Imho if your system is compromised, it doesn't make a difference if you unlock your wallet for hours or just a split second. Any malware that aims at stealing DRK will do so as soon as you entered the passphrase.

The scenario where an attacker gains access to your system in the very few hours your wallet is unlocked is rather unlikely.
 
Good morning, fresh CI-builds which fixes the "Darksend round GUI" bug


CI-builds for v0.9.12.19-gc33e2e8

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

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

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

CI-builds for v0.10.12.19-g0aebfe1

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-11/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


Can someone please send me the link to the Mac OS wallet without Darksend but with correct address font. I know that dev team are gonna release the fixed version with RC4 but I need it now. Have to send an urgent payment but cannot recognize addresses.
 

Attachments

  • 1111.png
    1111.png
    65.3 KB · Views: 109
DS+ should be on by default. If you don't want anonymous transactions, use Bitcoin. Yes, DS+ incurs fees. They are tiny.

It's an anonymous currency, it should be used as such. Fools complaining they got charged a pittance because they didn't read the instructions should be ignored.
Bitcoin is sloooooooow. Litecoin is dead. In Dark we trust. :smile:
Almost nobody in real world really read instructions and instead everyone seems to act just like "If nothing helps RTFM!" you know :wink: so you'll be ignoring literally everyone.
Simple dialog box on first run only that tell you that you'll be charged a small fee to make you funds anonymized and asking if you agree or not will be enough.
 
Almost nobody in real world really read instructions and instead everyone seems to act just like "If nothing helps RTFM!" you know :wink:
Won't change anything. To those people every pop-up dialog looks like this

blankmessage.jpg


I really don't like the idea of facilitating laziness and ignorance. But for the sake of DRK it should be done :tongue:
 
Last edited by a moderator:
Won't change anything. To those people every pop-up dialog looks like this

blankmessage.jpg


I really don't like the idea of facilitating laziness and ignorance. But for the sake of DRK it should be done :tongue:
LOL:grin::grin:

Playing with wallet a little bit more... I set 100 in "Amount of Darkcoin to keep anonymized" option, got some DRKs from faucet and now after a while there is 198.00000036 DRK in my Anonymized balance...
I don't get it... Is that the right way that option should work?
 
Phew, started drafting the release notes for RC4 - quite impressive what we've seen the last three weeks since page one :)

-> https://gist.github.com/schinzelh/5dfb350441833a9731f2

Code:
0.9.12.19 / 10.12.19 Release notes
----------------------------------

- Added GUI configuration for Darksend Rounds, Enable Darksend and Anonymize
  amount of DRK
- Removed 5000DRK hard limit
- Fixed another cause of getting hit by collateral
- Send dialog now shows selected balance (Anon, non-anon and Total)


0.9.12.18 / 10.12.18 Release notes
----------------------------------

This version uses the new queuing system to seek out compatible transactions
(where the same denominations are used). It's also enforcing these limitations
now, so it might be a bit slower.

All transactions after this should look like this one:

http://test.explorer.darkcoin.fr/tx/6de2c5204abdea451da930f61bae0f954eef13188a3a37a572a24c9d92057d5d


0.9.12.17 / 10.12.17 Release notes
----------------------------------

- I've switched up the way the masternode network works.
    1.) Users now will join a random masternode (1 of the entire list, just
        completely randomly)
    2.) Upon joining if it's the first user, the masternode will propagate
        a message stating it's taking partisipants for a merge
    3.) Another user will check that queue, if it's got a recent node, it will
        try that node first, otherwise it will go to 1.)

- Darksend limited to 5000DRK per wallet.dat. Client will warn about this the
  first time it's opened, then disable darksend from then on.
- Fixed some bugs with connecting to the correct masternodes
- Send was sending way too many coins for all modes, (I sent 100DRK anon and it
  sent 2000DRK, then sent me change for the rest causing a whole reprocess of
  everything in the wallet)
- Client now updates Anonymized balance when you send money out
- Fixed coin locking issues


0.9.12.16 / 10.12.16 Release notes
----------------------------------

- bugfixes


0.9.12.15 / 10.12.15 Release notes
----------------------------------

- 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


0.9.12.14 / 10.12.14 Release notes
----------------------------------

- 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


0.9.12.13 / 10.12.13 Release notes
----------------------------------

- This version automatically resets the masternode state machine after a short
  period of inactivity.
- Updated protocol version to kick old masternodes off


0.9.12.12 / 10.12.12 Release notes
----------------------------------

- Fixed change calc for Denominations in GUI
- Flare found a logging error for dseep, fixed
- Collateral now includes a fee (sometimes they took forever to get into a block)
- Found race condition with new blocks and clearing darksend entries that was
  causing some collateral fees
- Found a communication mix up where clients would see messages from the wrong
  masternode and think it was theirs, also causing collateral fees
- Added "Anonymized Balance" to overview
- Added "anonymized_balance" to getinfo
- Changed dropbox box on Send Dialog to be clearer
- Added text to the confirmation screen with what funds will be sent
- incremented protocol version to force masternode updates


0.9.12.11 / 10.12.11 Release notes
----------------------------------

- Darksend Denominate Outputs are now in a random order:

http://test.explorer.darkcoin.fr/tx/072ca56cbf705b87749513a2d2ee02080d506adcf8fe178f6dc2967f0711788e
http://test.explorer.darkcoin.fr/tx/32daa8ca46462e7e99f3532251d68a8c3835a080c937bd83b11db74e47b770ff

- Darksend now uses 3 participants instead of two.
- SplitUpMoney can now make collateral inputs when needed
- Transactions now shows darksend transaction types for easier understanding
  of what's going on:
- Fixed a couple more cases where collateral was charged when it shouldn't
  have happened (let me know if it happens after this version)
- Fixed the money destruction bug, it was caused by "darksend denominate 8000".
  I missed a reference and the client passed an empty address to
  SendMoneyToDestination. rcp darksend source: http://pastebin.com/r14piKuq
- Unlocking/Locking wallet fixes (was spamming the logs)
- Unencrypted wallet fixes (was trying to lock every 10 seconds)
- Flare found and fixed an issue with DGW3 for win32
- Added Darksend detection to the UI
- fixed senttoaddress, it will use all inputs when darksend is disabled now.
  Otherwise it will ONLY use non-denom.
- "darksend addr amount" now returns the hash of the transaction it creates


0.9.12.10 / 10.12.10 Release notes
----------------------------------

Another huge update to the RC client, most of these are stability fixes and
anonymity improvements:

- Removed "darksend denominate", darksend now will figure out the most it can
  denominate. Use "darksend auto" instead.
- Fixed "Unknown State" display error
- Fixed 0.0025 collateral issues caused by issues in the state machine, you
  should only be charged this amount now if you shutdown your client during
  the Darksend process.
- Client will only submit 1 transaction into the pool fixing possible
  anonymity issues
- Masternodes will only merge compatible transactions using the same
  denominations. For example (500,500,100) would be able to merge
  with (500,100), (10,1) with (10,1,1), but not (500,1) with (10,1).
  This improves the anonmity by not allowing someone to follow transactions by
  the missing denominations.
- Transactions use unique change addresses for every output of each round.
- QT GUI will now ask to unlock the wallet when it detects Darksend wants to do
  something and lock it when it's done again.
- Darksend is turned off by default in the daemon now. In most cases daemons
  won't want to run with anonymity (pools, exchanges, etc), if a user does they
  can override the default setting with -enabledaemondarksend=true
- Fees per round of Darksend are 0.001DRK or $0.00538 at current prices. This
  means to anonymize 1000DRK with 3 rounds (an average use case) it would cost
  a user 1.5 cents.
- Protocol version is updated to kick old clients off testnet


0.9.12.9 / 10.12.9 Release notes
--------------------------------


DS+ seems to be pretty stable now :-)

- SplitUpMoney now calculates the balance correctly
- Denominations are now 1 satoshi higher (denominated inputs will have to be
  regenerated as the client will not recognize the old ones)
- SplitUpMoney does a better job of splitting up really large wallets now
- Fixed crashing issues
- Added possible fix for masternode list syncing

- RPC calls are changed a bit:

    darksend denominate 100 - Will denominate 100DRK
    darksend auto - Will run AutoDenominate
    darksend Xaddr 100 - Will send 100 denominated DRK to Xaddr
    sendtoaddress Xaddr 100 - Will send 100 non-denominated DRK to Xaddr


0.9.12.8 / 10.12.8 Release notes
--------------------------------

- Fixed a few issues with input selection causing the
  "Insufficent Funds 2" error
- Masternodes now reset themselves when they give "entries is full".
  Not sure what's causing it but a client will just try again
- Improved the split up function
- Fixed issues with AutoDenom in wallets larger than a few hundred
- Fixed a case for collateral charges where the client gave up
  when it shouldn't have
- Input selection will now only select denominated, non-denominated or
  all inputs. This caused ds+ inputs to get interrupted by the splitting
  mechanism sometimes.
- Added new GUI element for selecting which inputs you want to send
- Fixed darksend+ rounds function, it was returning bad data in some cases
  causing darksend inputs to never stop being sent through darksend.
- Fixed "Send" dialog to be able to use the different kinds of inputs available.
  Sending anonymous transactions should now work properly.
- Fixed some coin select issues
- Collateral selection issues
- SplitUpMoney was sending denominated inputs and destroying the anonymity


DoAutoDenominate should work in nearly all cases now.
However, there are some known issues:

- Random collateral charges (still will happen, but it's more uncommon.)
- Password protected wallets


Testing commands, you can start multiple wallets up and all denominate
on the same masternode for testing purposes:
/darkcoin-qt -datadir=/home/user/.darkcoin -listen=0 -darksendrounds=8 -usemasternode="192.168.56.102:19999"
/darkcoin-qt -datadir=/home/user/.darkcoin2 -listen=0 -darksendrounds=8 -usemasternode="192.168.56.102:19999"

and even disable darksend auto-denom if wanted:
/darkcoin-qt -datadir=/home/user/.darkcoin -listen=0 -darksendrounds=8 -usemasternode="192.168.56.102:19999" -disabledarksend=1
 
continued

Code:
0.9.12.7 / 10.12.7 Release notes
--------------------------------

- Added a smart input splitting method. Place 1000+DRK into a brand new wallet
  and it will be split into many inputs compatible with Darksend
- DoAutodenomination now tries the correct balance (it was getting stuck on
  the wrong inputs)
- "entries is full" fix for at least one of the causes
- Changed merging parties to two for easier debugging.
- Fixed mod again (missed the one for the actual command you guys are using,
  I was overriding the default there)


0.9.12.6 / 10.12.6 Release notes
--------------------------------

- Fixed AutoDenominate. It seems to work pretty well now.
- Inputs that are large will be broken up automatically for denomination
- Masternodes should change every block now (missed a mod=10 last time)
- Mixing requires 5 clients to merge now, should improve anonymity.
- Mixing rounds are limited to 1000DRK, per block


0.9.12.5 / 10.12.5 Release notes
--------------------------------

- Masternodes should change every block now
- DoAutomaticDenomination should happen every block now
- DarkSendRounds had a bug that I fixed, should calculate correctly now


0.9.12.4 / 10.12.4 Release notes
--------------------------------

This is a pretty large update to the RC client.

- New column "Darksend Rounds" in coincontrol to show how secure a given input is
- Fixed a few issues causing darksend to fail. We should see many more darksends
  occuring now if it's fixed.
- Redid denominations to 1, 10, 100, and 500. Maybe this is too simple, but it
  seems effective, all change from transactions will de denominated automatically
  again through darksend for the next transactions. We'll see how it works.
- usemasternode option, will override active masternode (only in RC, just for testing)

0.9.12.3 / 10.12.3 Release notes
--------------------------------

- min merged transactions

0.9.12.2 / 10.12.2 Release notes
--------------------------------

- Fixed payout issues (masternode consessus was paying out to vout(0) by default)
- Improved DarksendInput add entry verification. Masternodes will now reject
  transactions that look like fees are too low, too high, have spent inputs, etc.
- Incremented protocol version to kick off clients with vout(0) payment bug
- DoAutomaticDenominations 100DRK limit changed to 500DRK (we should see a bunch
  of denominations happen now)


0.9.12.1 / 10.12.1 Release notes
--------------------------------

- Fixed a signing bug with the masternode voting system causing a bunch of issues
- Updated unit tests
- Incremented protocol version to kick off clients with signing bug
 
That's amazing!! :). A lot if hard work has gone into this.

One other question. How are exchanges going to handle dark given it now mixes?
 
Status
Not open for further replies.
Back
Top