Separate names with a comma.
Please sign up to discuss the most innovative cryptocurrency!
Discussion in 'Testing' started by eduffield, Sep 3, 2014.
I'm in with 50k now
****** PLEASE UPDATE TO v9.13.13 (Stable) OR 10.13.13 (RC) *******
This should fix everything Kristov found except for a possible DOS issue that will have to be fixed later, including the privacy issue. So we should be solid for Monday now.
- Bounds checking in a few places where it was lacking
- Output list in transactions lacked random seeding
- masternode constants for communication are much easier to read now
Everything should still work (Nothing structural was changed), but it would be great it we could anonymize some funds to double check before going live on Monday
eduffield did you get a chance to look at my micro wallet on JIRA before the site went down?
Nope, could you post it again pls?
Forum won't let me attach the .dat file. What's your email and I'll shoot off both the wallet and the debug file.
Sent. I also emailed you with what the problem is I am having. Any questions, feel free to email me direct.
and eduffield what about the missing masternode entries of masternode list command. i also reported that on jira (#88) including ip and wallet addresses.
Will do, running 3 wallets on Windows 8, no issues recently, good job!
Should have been fixed. There was a mismatch in the protocol when that was reported. Do you still experience an issue? This shouldn't be a problem, nothing dealing with masternodes were changed at all in RC5.
Hi vertoe, sorry was busy had to shut down my computer. I'm back running 50k, 2 rounds. I guess you're sleeping but just to let you know
It's an RC4 issue, so I guess it's not fixed. I'm experiencing it with v0.10.12.32
XfHiR2RkKm1H6GhTeZaE4XnnfNpm22zKbh recieved two payments tonight
But the IP 188.8.131.52 is not listed on masternode list output:
$ darkcoind masternode list | grep 184.108.40.206
create a masternode, let it run for a while
take it down, change the privkey and public ip but not the wallet input on address 0
recreate same masternode with old wallet but with new ip and privkey
missing in masternode list command
i'm missing around 20 nodes on that list.
CI-builds for v0.9.13.13-g1909341
Mac OS X:
CI-builds for v0.10.13.13-g8f8e309
Mac OS X:
I just updated 12 nodes on testnet with 0.10.13.13 (but no active masternodes, no time for that, sorry).
updated p2pool and masternode to 0.10.13.13
v0.10.13.13 is looking good .. two large wallet of mine are happily denominating. i will do some smaller wallet testing later..
I've barely had a chance to play with any of the RC5 versions so I have only just jumped in.
Really happy with how it works.
Ah, ok. I know what's causing that and it can be avoided by using "masternode stop" and waiting 30 minutes before firing up the new node. I'm afraid fixing that is structural and I don't want to do it this close to release. I'll fix it next release though.
*****GUYS.... Last call for testing before RC5 goes live... There will always be weekends, but this is your last special weekend before RC5 is released... Please join Testnet and get busy!*****
I'm running 100 tdrk, 2 rounds. If anyone is testing small amounts, please let me know. Thanks!
Im running, please send some to
I also put about 9Mh on testnet
jimbit, you can get plenty of tdrk from the faucet: https://drkipn.com/test/faucet/
eduffield, could you please make the field a bit wider to avoid the overflow to the next line?
It will look better. The "." and ".." stay on the top line, but when we have "..." (3 dots) it starts new line.
Testers... please try small amounts. 10, 20, 25 etc.
will be faster to pair.
Edit: 10 DRK 2 rounds. Was charged 4 x 0.0125
Thought its only 0.0125/round.
Could someone explain the fee structure?
Is JIRA site still down? It says "502 Bad Gateway".
It's not just you! http://jira.darkcoin.qa looks down from here.
It's still down, working on the DB restore. Give me another 2 hours
Ok, thanks, flare! Take your time, I'll bbl.
Just a thought, wouldnt be an automated, internal masternode stop signal on client shutdown (e.g. SIGTERM) sufficient?
Unfortunatly the last usable backup was 7 days old, so we lost tickets DRK-74 to DRK-91. I have manually recreated the tickets as far as possible, so if you are missing something please comment on the corresponding tickets.
Sorry for the inconvencience,
Damn, just when RC5 is going to release.
If i remember correct, there was 13 TODO issues.
Maybe Evan should take 'export backup' every day.
There is good export button...