The log message removes the decimal separation.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.
The log message removes the decimal separation.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.
Yes, it's darkoshiThe log message removes the decimal separation.![]()
Unfortunatly not, during testphase only linux binary is available for 0.10.12.xIs there v0.10.12.8 (including darksend+) for windows 32/64bit?
On closer inspection this version of DoAutomaticDenominating() has attempted to denominate 563400000 and 50563400000 coins. All my other errors with previous versions were much smaller numbers, so it was a bit surprising/confusing. :smile:Yes, it's darkoshi![]()
I see. BTW v0.9.12.8 for windows is working perfectly.Unfortunatly not, during testphase only linux binary is available for 0.10.12.x
I envy you - my denominations still down work. Want to start flooding the blockchain with darksend-txOK denomination is working. What next, should we play darksend-pingpong again?
Someone do a DS+ transaction to this address msRPwRCoF2DkVMdUTtR9sNyUPEZLWA99iB and share another address to reply with a DS+ tx.
Well its only denominated, did you do a Darksend transaction yet? If not, please do so: msRPwRCoF2DkVMdUTtR9sNyUPEZLWA99iBMy denominations finished, so I want to summarize.
I have public input address: http://test.explorer.darkcoin.qa/address/mvFokwqXwNsA3SqdrqqwR93MfhFuPxFiv2.
There were 3 transactions for 1000 DRK every.
After denominations I have 3 new addresses.
Two of them have non-zero balances, 0.3 DRK and 0.4 DRK. In logs I see "Too little to denominate (must have 1.1DRK)". These addresses inherit from public address and there is a direct relationship between public address and these two.
The last transaction http://test.explorer.darkcoin.qa/tx/39d69edfef80ab5ea95bf488914675c5df7e5a84a5449f578f6d20bc349e5541 is very interesting, because blockchain shows us only 2 addresses and one of them is my third address http://test.explorer.darkcoin.qa/address/n3JEHNGv2tjE4RokGxwASHgfW6Gr3zCEtT which has 2999.256 DRK (3000 DRK input). Another address http://test.explorer.darkcoin.qa/address/mfuNdNYZeHytU3mBbu3eUaA1FrYNan1ubK I can't view, because there is an error: I'm sorry, this address has too many records to display.
So, as for me, in exactly my situation it's very easy to track money. How do you think? Maybe, I wasn't considered something?
Done! I didn't see "use DarkSend+" checkbox, such in RC2. Do I need additional actions to use DarkSend or it's by default now? Seems, I did common transaction.Well its only denominated, did you do a Darksend transaction yet? If not, please do so: msRPwRCoF2DkVMdUTtR9sNyUPEZLWA99iB
I just sent you 69 tDRK with DS+ inputs; feel free to send some back to n4mJmycicjbcRbETpiSdGXCBzjDEMNzsHUWell its only denominated, did you do a Darksend transaction yet? If not, please do so: msRPwRCoF2DkVMdUTtR9sNyUPEZLWA99iB
Same for me, seems Evan changed the parameter format to JSON, but i was not able to figure out the correct format.darksend msRPwRCoF2DkVMdUTtR9sNyUPEZLWA99iB 450
Error: Error parsing JSON:msRPwRCoF2DkVMdUTtR9sNyUPEZLWA99iB
./darkcoind darksend '{"mmQuoVyRHF595ZZPk4gDzWYNY9cGhZJ9bZ":1}'
error: value is type obj, expected real
I just sent you 69 tDRK with DS+ inputs; feel free to send some back to n4mJmycicjbcRbETpiSdGXCBzjDEMNzsHU
Had a chat with Evan, andSame for me, seems Evan changed the parameter format to JSON, but i was not able to figure out the correct format.
Code:./darkcoind darksend '{"mmQuoVyRHF595ZZPk4gDzWYNY9cGhZJ9bZ":1}' error: value is type obj, expected real
"darksend <darkcoinaddress> <amount>
No, denom != anonhttp://test.explorer.darkcoin.qa/tx/19d597b3a3f9b0ea43439c87173a0075e771e751da112a474e0fdcad39300f5c
If so, this is the common transaction from denominated inputs. As I understand, denomination is an anonymization process, not sending. So, why my denominated outputs are easy trackable?
No, denom != anon
The combination of denom plus x rounds of mixing through masternodes == anon