vertoe
Three of Nine
eduffield something is wrong with the masternode list command on x.12.32, we should address this in RC5, too. http://jira.darkcoin.qa/browse/DRK-88
Do you mind putting this in the documentation wiki? --> http://wiki.darkcoin.qa/display/DRK/Darkcoin+Administrator+Guidejust found out how to run multiple darkcoin clients on one PC for Windows users:
- make seperate folders for both darkcoin-qt.exe and the datafolders
- place shortcuts from each seperate darkcoin-qt.exe to yr desktop
- in each shortcut add following in the target field: -datadir=yrspecificdatadirectoryfolder -listen=0
voila... you can now run multiple darkcoin clients on one PC .. increasing the chance of finding pairs for all testers.
For non-windows users who want to try this see if you can do something with these parameters (-datadir & listen=0)
i have been running 2 darkcoin clients all night without problems, denominations coming in regarly.
The sybil attack issues will be fixed, but the snooping attack will be fixed later, it's a bit more involved than it seems. However, for snooping to work you would need to control all masternodes that a specific input went through(8 rounds = 8 separate masternodes). So it's not a very feasible attack anyway.
LOL !!! I believe there's a hidden message from Evan in every dot!LOL I was waiting for the image to load.
I would prefer a text label with counting dots:
"Doing stuff ."
"Doing stuff .."
"Doing stuff ..."
"Doing stuff ...."
"Doing stuff ....."
"Doing stuff ."
"Doing stuff .."
"Doing stuff ..."
I think eduffield should write a new paper about the fixed darksend implementation, the old one is very outdated.Thank you ! This cleared the picture for me .
It looks like this hard to solve issue "sybil attack" is not that hard for you .
Its pretty difficult to find the information about the advantages of Darksend. Every user here should make some effort to spread the word !
teamer, get into this thread please! We need people like you! Call for devs: Software adoption - chose your language and go!Guys i really want to help in development, i have >10 years experience but not in C (C is fine with me, but i never had a working IDE setup) if anyone can help me in setting up an IDE and how to compile and test on Ubuntu i will be able to do some stuff on darkcoin
with a spinning smiley face
Or if time prohibits, then for now add a banner at the top saying it's outdated with a link to a couple of already existing posts that describe the differences.I think eduffield should write a new paper about the fixed darksend implementation, the old one is very outdated.
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
Any thought's as to what would be causing this?
I would think he is testing the rejecting of certain wallets but it doesn't make sense why the 13.10 client is throwing that error. I'm not choosing to not pay blocks. This wallet does run some of my testnet tools though so now that its offline so its the p2pool node and the faucet.Maybe something to do with this: https://darkcointalk.org/threads/rc5-testing.2245/page-35#post-20417 ...?
Awesome.
I would think he is testing the rejecting of certain wallets but it doesn't make sense why the 13.10 client is throwing that error. I'm not choosing to not pay blocks. This wallet does run some of my testnet tools though so now that its offline so its the p2pool node and the faucet.
Problem is I can't get that wallet to do anything. Doesn't matter if its a new wallet.dat file, old or new version of the wallet, it's just stuck like that with that error can't send or receive coins.
Windows wallet v.10 has a strange error:
View attachment 461
getinfo
{
"version" : 101310,
"protocolversion" : 70038,
"walletversion" : 60001,
"balance" : 1000.00000000,
"anonymized_balance" : 0.00000000,
"blocks" : 32440,
"timeoffset" : 7,
"connections" : 11,
"proxy" : "",
"difficulty" : 0.01029224,
"testnet" : true,
"keypoololdest" : 1410852157,
"keypoolsize" : 1000,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}