DarkSend RC1 Official Release!

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
The last couple of weeks I've been focusing on stability of the beta version of the client and I think we're ready to leave beta. So this will be the first release candiate! There a few things that will need to be done before opensourcing, but everything is moving along pretty well.

Here's everything that changed:
- Masternode's sign their inputs to message the network that they're still active
- Various stability improvements and bug fixes

- If you run a masternode with an encrypted wallet, use "masternode start mypassphrase" to start the masternode. Upon running this command the client will decrypt your wallet, find the matching masternode input then sign and propagate a message starting the masternode
- Masternodes now can run with their wallets encrypted
- Election code (for selecting the rounds masternode) is greatly improved
- Found a few situations where darksend failed and fees were charged and fixed them

RC1.1 Changes (mandatory update)
- Moved many log prints to debug mode (sorry for the spam...)
- Changed masternode ping time to 25 minutes
- Fixed a bug with status update spam
- Incremented protocol version to kick off old masternodes

Next:
- Writing the code to pay the masternodes
- Users testing to find edge cases
- Forking mainnet to begin payments
- Adding queues for more than 10DRK

Download Here:

http://www.darkcoin.io/downloads/DarkSendDocumentation.pdf
 
Last edited by a moderator:

BrainShutdown

Well-known Member
Foundation Member
Apr 8, 2014
149
71
188
Great news!
Node up & running :)

Congratulations on achieving this important milestone!
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
I don't get it... shouldn't there be a download link somewhere? darkcoin.io still has 0.9.1.2
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Ok, got it. I'm on a Mac so guess I'll have to wait a while. By the way, got 2 mining p2p payments at the exact time after about 2 hour and a half of nothing. I suppose that means I can resume mining as usual and wait for an OSX RC1?
 

RasNetworks

New Member
Mar 14, 2014
6
0
1
So how do you start the masternode with darkcoind with an encrypted wallet now?
Mine isnt running
--Edit
Gee its the Unbuntu requirement
 
Last edited by a moderator:

rumple

New Member
Apr 3, 2014
13
0
1
Is there an argument to generate a darkcoin.conf? One is not provided in the Ubuntu 64-bit download, and running darkcoin-qt doesn't generate one in ~/.darkcoin.
 

Propulsion

The buck stops here.
Feb 26, 2014
1,008
468
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
Is there an argument to generate a darkcoin.conf? One is not provided in the Ubuntu 64-bit download, and running darkcoin-qt doesn't generate one in ~/.darkcoin.
It's as simple as opening up a text editor and saving the file as darkcoin.conf in your //home/user name/.darkcoin directory.
 

rumple

New Member
Apr 3, 2014
13
0
1
It's as simple as opening up a text editor and saving the file as darkcoin.conf in your //home/user name/.darkcoin directory.
Is there any structure/syntax to it or can it be just that one line from the doc?
addnode=23.23.186.131
 

mattmct

Member
Mar 13, 2014
259
92
88
Awesome work!

Although I have run in to a problem, my own silly fault I guess.

When starting up the new masternode, I get an error,
-bash: !.?S5*c: event not found

Which is part of my password. ... I used a long password with some symbols. Is there any way around this? Or do I need to change my password on the wallet? If so, any suggestions on the best way to do it? I originally made the 1000DRK wallet, encrypted via a windows laptop, when send the wallet.dat over.

Many thanks.
 

zuperdoge

New Member
Apr 1, 2014
12
2
3
I also have a super long password. If there are spaces, use quotes around it.
Example: darkcoind masternode start "stupid long but very secure password"
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,863
1,854
1,283
After starting my masternode, I got "successfully started masternode" and it's been like 15 minutes but I still don't show up on the list. Any clue what's wrong or can it be the network is a bit slow?

Or, do I have to unlock my wallet somehow?
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
After starting my masternode, I got "successfully started masternode" and it's been like 15 minutes but I still don't show up on the list. Any clue what's wrong or can it be the network is a bit slow?

Or, do I have to unlock my wallet somehow?
Have you changed ami_public_ip of darkcoin.conf ?
Code:
externalip=ami_public_ip
 

mattmct

Member
Mar 13, 2014
259
92
88
I also have a super long password. If there are spaces, use quotes around it.
Example: darkcoind masternode start "stupid long but very secure password"
I'm still getting the same error, even with the " " aroudn my pass. I tried using ' ' and it comes back with another error "
-bash: syntax error near unexpected token `)'"

Also related to my password I think. I guess I really shouldn't have used a password with symbols in it!

I'm now looking up how to change wallet password in unix. If not, all I can think is taking wallet.dat, and changing it via the client on my spare windows laptop, then sending the wallet.dat back to the EC2. Would think work okay? Any potential problems? Thoughts?! anything? lol thanks guys.
 

BrainShutdown

Well-known Member
Foundation Member
Apr 8, 2014
149
71
188
I'm still getting the same error, even with the " " aroudn my pass. I tried using ' ' and it comes back with another error "
-bash: syntax error near unexpected token `)'"

Also related to my password I think. I guess I really shouldn't have used a password with symbols in it!

I'm now looking up how to change wallet password in unix. If not, all I can think is taking wallet.dat, and changing it via the client on my spare windows laptop, then sending the wallet.dat back to the EC2. Would think work okay? Any potential problems? Thoughts?! anything? lol thanks guys.
I had similar issue with some symbols in the password that generated errors in linux bash, so I moved to the laptop and changed it.
Be sure not to include symbols that have meaning in the linux prompt. I had problems with ! , & and $.

Oh and don't forget to backup wallet after password change and delete the old wallets :)
 
  • Like
Reactions: zuperdoge

mattmct

Member
Mar 13, 2014
259
92
88
I had similar issue with some symbols in the password that generated errors in linux bash, so I moved to the laptop and changed it.
Be sure not to include symbols that have meaning in the linux prompt. I had problems with ! , & and $.

Oh and don't forget to backup wallet after password change and delete the old wallets :)
Cheers for this, yeah I thought as much.

I'll stop darkcoind, change the password on my windows laptop, then replace the wallet on the EC2, and fire it up. Hoping this is all there is too it. Along with backing up and deleting of course.

Cheers!

Update: Nice and easy, 5 min job. Seems to have worked. The node fired up well. I didn't notice the node number go up, it's still at 18. But my node IP is listed on "masternode list". So I guess we're all good! :)
 
Last edited by a moderator:

BrainShutdown

Well-known Member
Foundation Member
Apr 8, 2014
149
71
188
Do any of you have your masternode's IP address duplicated on the masternode list?
I have both my nodes with duplicated self IP address entries... is it normal?

masternode list
{
"112.175.123.94:9999" : 1,
"54.238.156.138:9999" : 1,
"54.215.215.6:9999" : 1,
"142.161.23.40:9999" : 1,
"141.255.184.191:9999" : 1,
"95.85.59.159:9999" : 1,
"107.170.15.238:9999" : 1,
"54.213.217.28:9999" : 1,
"54.86.15.235:9999" : 1,
"94.23.22.195:9999" : 1,
"176.31.113.167:9999" : 1,
"54.85.112.223:9999" : 1,
"98.101.247.254:9999" : 1,
"212.101.16.116:9999" : 1,
"54.72.206.41:9999" : 1,
"54.245.240.204:9999" : 1,
"75.84.123.125:9999" : 1,
"54.215.250.146:9999" : 1,
"54.72.206.41:9999" : 1,
"54.72.58.75:9999" : 1
}
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
Do any of you have your masternode's IP address duplicated on the masternode list?
I have both my nodes with duplicated self IP address entries... is it normal?

masternode list
{
"112.175.123.94:9999" : 1,
"54.238.156.138:9999" : 1,
"54.215.215.6:9999" : 1,
"142.161.23.40:9999" : 1,
"141.255.184.191:9999" : 1,
"95.85.59.159:9999" : 1,
"107.170.15.238:9999" : 1,
"54.213.217.28:9999" : 1,
"54.86.15.235:9999" : 1,
"94.23.22.195:9999" : 1,
"176.31.113.167:9999" : 1,
"54.85.112.223:9999" : 1,
"98.101.247.254:9999" : 1,
"212.101.16.116:9999" : 1,
"54.72.206.41:9999" : 1,
"54.245.240.204:9999" : 1,
"75.84.123.125:9999" : 1,
"54.215.250.146:9999" : 1,
"54.72.206.41:9999" : 1,
"54.72.58.75:9999" : 1
}
Is that EC2 instance ?

Once my ec2 t1.micro had.
Now my m3.medium has.

I think there may be an issue with NAT(node ip differ from public ip).
 

BrainShutdown

Well-known Member
Foundation Member
Apr 8, 2014
149
71
188
Is that EC2 instance ?

Once my ec2 t1.micro had.
Now my m3.medium has.

I think there may be an issue with NAT(node ip differ from public ip).
Yes, they're both ec2 t1.micro.
The externalip in darkcoin.conf is correctly set.
Maybe the devs can tell us what to do or if this is normal... :)
 
  • Like
Reactions: chaeplin

yellowcox

New Member
Apr 23, 2014
15
3
3
Hi,
Same problem for my masternode on ec2 t1.micro

masternode list
{
"112.175.123.94:9999" : 1,
"54.238.156.138:9999" : 1,
"54.215.215.6:9999" : 1,
"142.161.23.40:9999" : 1,
"141.255.184.191:9999" : 1,
"95.85.59.159:9999" : 1,
"107.170.15.238:9999" : 1,
"54.213.217.28:9999" : 1,
"54.86.15.235:9999" : 1,
"94.23.22.195:9999" : 1,
"176.31.113.167:9999" : 1,
"54.85.112.223:9999" : 1,
"98.101.247.254:9999" : 1,
"212.101.16.116:9999" : 1,
"54.72.206.41:9999" : 1,
"54.245.240.204:9999" : 1,
"75.84.123.125:9999" : 1,
"54.215.250.146:9999" : 1,
"54.72.58.75:9999" : 1,
"54.72.58.75:9999" : 1,

"83.248.99.134:9999" : 1
}

I just restarted the daemon yesterday...
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
guys, I'm still on v0.9.1.2-g54fd5f3-beta because RC1 is still not compiled for Mac
Is that why 85% of the time the QT is showing "out of sync" constantly, but I'm getting mining payments ok. I close the client, re-open, and its clean and in sync. After some payments, same thing happens.

Please advise
 
Last edited by a moderator: