v0.10.12.x RC4 Testing

Status
Not open for further replies.
eduffield said:
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
Click to expand...

Hmm, on mainnet I figure that most will have their wallets protected -- which is in conflict with the fact that the more wallets participating in the autoDeom the better. Also it would mean that a requirement for anonymity would be leaving the wallet unprotected, a condition most would find unpalatable.

Given that, is there a plan for how password protected wallets will be handled in the future?
 
JGCMiner said:
Hmm, on mainnet I figure that most will have their wallets protected -- which is in conflict with the fact that the more wallets participating in the autoDeom the better. Also it would mean that a requirement for anonymity would be leaving the wallet unprotected, a condition most would find unpalatable.

Given that, is there a plan for how password protected wallets will be handled in the future?
Click to expand...
The GUI will ask for the password in much the same way the Send dialog does when it detects it needs to anonymity some inputs. For a daemon, most are not encrypted that will be sending and receiving funds. Otherwise, the user will have to unlock the wallet just while it anonymizes the funds, once anonymized they can sit encrypted until the user needs to send money.
 
JGCMiner said:
Hmm, on mainnet I figure that most will have their wallets protected -- which is in conflict with the fact that the more wallets participating in the autoDeom the better. Also it would mean that a requirement for anonymity would be leaving the wallet unprotected, a condition most would find unpalatable.

Given that, is there a plan for how password protected wallets will be handled in the future?
Click to expand...

I suppose that with auto-demoninations working, manual denominations will work even swifter. You un-encrypt the wallet to anonymize and shut it sown right after

Edit: boom .. lol ..
 
Hold on a few before upgrading, some important lines were commented out for testing. Sec, compiling again.

Edit: Noticed a couple of things that could use fixing before we all upgrade again. I'll fix them, then I'll push .8 again.
 
Last edited by a moderator:
I have one problem, I thought earlier that it's because of my virtual machine, but this problem is repeating on my notebook too. So, when blockchain download finishes after client startup, new blocks aren't downloaded until I restart client. The problem is in RC2 and RC4.
 
CODERsp said:
I have one problem, I thought earlier that it's because of my virtual machine, but this problem is repeating on my notebook too. So, when blockchain download finishes after client startup, new blocks aren't downloaded until I restart client. The problem is in RC2 and RC4.
Click to expand...
Hmm, heard that for the first time. What OS? Do you have a firewall/NAT in place?
 
flare said:
Hmm, heard that for the first time. What OS? Do you have a firewall/NAT in place?
Click to expand...
It's funny, but after I wrote about this problem, client began to download new blocks))) OS - clean Ubuntu 12, 14 without any additional settings.

I'm newbie in practical testing of DarkSend+ (only theory) and I don't understand what does my client do)) If you can, please explain to me.

My command line: ./darkcoin-qt -listen=0 -darksendrounds=8 -testnet
I sent 3 transactions throw faucet, so I have 3000 DRK.
After that my client sent 2 transactions to myself (2000 DRK), 1000 DRK left.
Next, there was one outgoing transaction for 0.002 DRK.
I watched blockchain and saw, that DRK sent to some address, that I don't know and this address now have 1000 DRK, but client shows 2999.998 DRK in my wallet. It's mystery))

My questions are: Why only 2 transactions for 2000 DRK and 1000 DRK left? Is 0.002 DRK a fee for DarkSend+? How can I find my anonymized 2000 DRK? Which address? I don't see it in client. How can I see the progress of denomination and understand that it was finished?

And several more questions about DarkSend+, that I had in my mind.

1. What if my balance was 997 DRK and I send it to some address. Is it easier to track them by transaction amount? Somebody see, that one address had 997 and some time ago another address have 997 DRK.

2. Masternode mixing. In scheme we see that txs go throw masternodes from 1 to 8. Does first masternode have all info about tx (inputs and outputs)? Or how mixing works?

Thanks.
 
CODERsp said:
After that my client sent 2 transactions to myself (2000 DRK), 1000 DRK left.
Next, there was one outgoing transaction for 0.002 DRK.
Click to expand...
If you send DRK to your own wallet, this is considered a "internal transaction" - so you will only see the fees in the transaction list, as the DRK actually never leaves your wallet. Additionally it seems one of the transaction was done with fee 0 - which means the comlexity was very low (e.g. one input, one output)

CODERsp said:
I watched blockchain and saw, that DRK sent to some address, that I don't know and this address now have 1000 DRK, but client shows 2999.998 DRK in my wallet. It's mystery))
Click to expand...
That's the way every *coin wallet works :) The address you are seeing is a change address, where your change of the transaction was transferred to. This change address is part of your wallet. So the summary of your account is correct: 2999.998 - bitcoin magic :)


CODERsp said:
My questions are: Why only 2 transactions for 2000 DRK and 1000 DRK left?
Click to expand...

See above - change address.

CODERsp said:
Is 0.002 DRK a fee for DarkSend+?
Click to expand...
Normal transaction fee, not specific for DarkSend+

CODERsp said:
How can I find my anonymized 2000 DRK? Which address? I don't see it in client. How can I see the progress of denomination and understand that it was finished?
Click to expand...

Would be helpful if you post the transaction in the blockchain explorer so we can help you with this question :D Did you use a 0.10.12.x client? DarkSend+ is currently in its early testing phase, so there still might be issues with denomination, anonymization and such - that's we are here for to figure out.

CODERsp said:
And several more questions about DarkSend+, that I had in my mind.

1. What if my balance was 997 DRK and I send it to some address. Is it easier to track them by transaction amount? Somebody see, that one address had 997 and some time ago another address have 997 DRK.

2. Masternode mixing. In scheme we see that txs go throw masternodes from 1 to 8. Does first masternode have all info about tx (inputs and outputs)? Or how mixing works?
Click to expand...
Basically this is what we are here for during testing RC4 - you are welcome to join in ;)
 
****** Please Update To 10.12.8 (update if this is the first time seeing this message, even if you're running .8) *******

-Fixed some coin select issues
-Collateral selection issues
-SplitUpMoney was sending denominated inputs and destroying the anonymity

Also, including:

- 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.

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

I suppose a really privacy aware user (or group of users) could have their own private masternode using these commands too. Another use case I hadn't thought of.

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
 
I'm very glad to join your community ;) Thanks for answers. I see, that my client didn't finish the job. I think, I need to wait it finishes and than I'll try to understand how it works)) http://test.explorer.darkcoin.qa/address/mvFokwqXwNsA3SqdrqqwR93MfhFuPxFiv2 Here is my input address, as you see, it's balance - 1000 DRK, it's not change address, so these coins aren't deanonimized. One moment - BALANCE OF INPUT ADDRESS IS ZERO DRK. God, it works!!! P.S. I use the latest version 0.10.12.8.

All the DRKs were anonymized and I have 3 fee transactions: 0.001, 0.002, 0.002. My final balance is 2999.995 DRK.
 
 
tdrkmn01-08 updated to 0.10.12.8-2
tp2pool compiled to latest master-rc4 from github (0.9.12.8).
Port checker now reports 0.9.12.8.
 
Moving, but still failing - now autodenominate needs a collateral :)

Code: 
2014-07-28 19:16:46 DoAutomaticDenominating : Running darksend denominate for 95908000000 coins. Return 'Error: Darksend requires a collateral transaction and could not locate an acceptable input!'
2014-07-28 19:16:46 DoAutomaticDenominating : Error running denominate, Error: Darksend requires a collateral transaction and could not locate an acceptable input!

Code: 
2014-07-28 19:15:29 found coins 13
2014-07-28 19:15:29  vin nValue 19980000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 19980000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 23976000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 23977000000
2014-07-28 19:15:29  vin nValue 19980000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 43957000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 47953000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 47954000000
2014-07-28 19:15:29  vin nValue 19980000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 67934000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 71930000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 71931000000
2014-07-28 19:15:29  vin nValue 19980000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 91911000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 95907000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 95908000000
2014-07-28 19:15:29 found coins 13
2014-07-28 19:15:29  vin nValue 19980000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 19980000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 23976000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 23977000000
2014-07-28 19:15:29  vin nValue 19980000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 43957000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 47953000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 47954000000
2014-07-28 19:15:29  vin nValue 19980000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 67934000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 71930000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 71931000000
2014-07-28 19:15:29  vin nValue 3996000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 75927000000
2014-07-28 19:15:29  vin nValue 1000000
2014-07-28 19:15:29  -- rounds -2
2014-07-28 19:15:29  -- rounds continue
2014-07-28 19:15:29  -- nValueRet 75928000000
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 0)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 1)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 2)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 4)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 5)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 6)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 7)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 8)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 9)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 11)
2014-07-28 19:15:29 CWallet::LockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 12)
2014-07-28 19:15:29 found coins 2
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 0)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 1)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 2)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 4)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 5)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 6)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 7)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 8)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 9)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 11)
2014-07-28 19:15:29 CWallet::UnlockCoin - COutPoint(144a1334ee3f16606860fc491e626f507ed7923267351098717ad40428bfdd62, 12)
2014-07-28 19:15:29 DoAutomaticDenominating : Running darksend denominate for 95908000000 coins. Return 'Error: Darksend requires a collateral transaction and could not locate an acceptable input!'
2014-07-28 19:15:29 DoAutomaticDenominating : Error running denominate, Error: Darksend requires a collateral transaction and could not locate an acceptable input!
 
flare said:
Moving, but still failing - now autodenominate needs a collateral :)

Code: 
2014-07-28 19:16:46 DoAutomaticDenominating : Running darksend denominate for 95908000000 coins. Return 'Error: Darksend requires a collateral transaction and could not locate an acceptable input!'
2014-07-28 19:16:46 DoAutomaticDenominating : Error running denominate, Error: Darksend requires a collateral transaction and could not locate an acceptable input!
Click to expand...
Same error here testing v0.10.12.8-2-g8e282f2-beta. Mine is attempting to denominate 563400000 coins, but my testing address (mfuNdNYZeHytU3mBbu3eUaA1FrYNan1ubK) only has 999.63400000 remaining.
 
Status
Not open for further replies.
Back
Top