RC2 Hard Fork on May 14th!
- Thread starter eduffield
- Start date
miningpoolhub
New member
No, on May 1st when Evan said RC2 was live, his announcement was confusing because I think he made a typo 
I suspected it was a typo but didn't know either at the time
What he meant was that the source was available to compile a wallet that would allow for payments to masternodes, and thus be functional after May 14th. But DarkSend is separate from that, and still closed source. His mind is running ahead, and he doesn't realize we have no idea what's going on, LOL. But that's what we have InternetApe for, he's the interface between machine language (Evan) and human language (us) LOL
I suspected it was a typo but didn't know either at the time What he meant was that the source was available to compile a wallet that would allow for payments to masternodes, and thus be functional after May 14th. But DarkSend is separate from that, and still closed source. His mind is running ahead, and he doesn't realize we have no idea what's going on, LOL. But that's what we have InternetApe for, he's the interface between machine language (Evan) and human language (us) LOL
miningpoolhub
New member
Is it okay to run RC2 version before the hardfork for pools?
It may sound silly since it must run smoothly between the hardfork, but just asking for sure.
It may sound silly since it must run smoothly between the hardfork, but just asking for sure.
Pools need to run the RC2 version, at least just before the fork to keep miners on the right fork and not waste their time mining a wrong fork. There is a testnet, and a version for this, so you can test it out. In fact, I believe they have a pool set up on testnet (see the other thread, testing RC2) I think it's ongoing but have been too busy to check???
miningpoolhub
New member
I was concerned about RC2 not working with old pool software which doesn't know anything about masternode.
Thanks for answering.
just_mike
Member
MPOS and NOMP have been patched for RC2. p2pool is remaining. There is 300DRK and US$100 in bounty so far.
Info here - https://darkcointalk.org/threads/developement-work-for-p2pool-and-nomp-stratum-patch.360/
Info here - https://darkcointalk.org/threads/developement-work-for-p2pool-and-nomp-stratum-patch.360/
Thanks Mike
I'm still unable to get my ip:0 off of the masternode list. I've turned off my computers, I've rebooted and made sure neither one had darkcoind running, and now, I've even sent off my 1000 coin deposit. None of these things have taken the ip address off the list.
And I think the fact that my ip address is on the list is keeping me from being able to take my wallet with coins off to cold storage, as my correct ip:9999 drops off the list when I do. Am I the only person with this problem?
I'm still unable to get my ip:0 off of the masternode list. I've turned off my computers, I've rebooted and made sure neither one had darkcoind running, and now, I've even sent off my 1000 coin deposit. None of these things have taken the ip address off the list.
And I think the fact that my ip address is on the list is keeping me from being able to take my wallet with coins off to cold storage, as my correct ip:9999 drops off the list when I do. Am I the only person with this problem?
I have both issues, yours and Tante's, on different local/remote masternodes and different providers - hope someone could explain.
I decided to try the remote/local setup.
- deleted masternode's wallet
- configured local wallet to point to masternode (as per Tante's tutorial) - yes, I sent myself 1000 DRK to address 0
- opened TCP port 9999 in local router
- not capable masternode
- deleted masternode's wallet
- configured local wallet to point to masternode (as per Tante's tutorial) - yes, I sent myself 1000 DRK to address 0
- opened TCP port 9999 in local router
- not capable masternode
i managed to get my masternode working completely, with remote and local server.
I had a problem of it not showing on the list. It was showing on my local list but not on any other wallets list.
Also I had an old ip that i couldn't remove from the list too Tante. ( have you tried starting that wallet with masternode=0 in the config? )
Here is how I fixed it.
I withdrew my coins from the master node wallet back to my original wallet ( windows ).
I installed a new ubuntu Darkcoind ( daemon) wallet on my system.
I sent the 1000 coins to that address. Encrypt.
Start Remote server darkcoind.
Start local server with -
Darkcoind -masternodeaddr=YOURSERVERIP:9999
unlock wallet with -
walletpassphrase YOURPASSPHRASE 300
Then start masternode with
masternode start YOURPASSPHRASE
thats it, you do not have to start masternode on your remote server.
check now that your masternode shows on both darkcoind daemons. darkcoind masternode list
make sure it is on both.
I was having all these problems until I redid it all. Once i resent the 1000 to a new address everything was fine. Make sure you send the 1000 coins to a Darkcoind daemon.
I hope this works for you.
Also you can turn your local machines darkcoind off after. It should stay on the list.
Tante just to be sure. Assign a new elastic ip to your remote server before doing this. That way you can forget about the old ip. It will be moved eventually and you will have a new ip linked to a new transaction id ( i assume this is how it works)
I had a problem of it not showing on the list. It was showing on my local list but not on any other wallets list.
Also I had an old ip that i couldn't remove from the list too Tante. ( have you tried starting that wallet with masternode=0 in the config? )
Here is how I fixed it.
I withdrew my coins from the master node wallet back to my original wallet ( windows ).
I installed a new ubuntu Darkcoind ( daemon) wallet on my system.
I sent the 1000 coins to that address. Encrypt.
Start Remote server darkcoind.
Start local server with -
Darkcoind -masternodeaddr=YOURSERVERIP:9999
unlock wallet with -
walletpassphrase YOURPASSPHRASE 300
Then start masternode with
masternode start YOURPASSPHRASE
thats it, you do not have to start masternode on your remote server.
check now that your masternode shows on both darkcoind daemons. darkcoind masternode list
make sure it is on both.
I was having all these problems until I redid it all. Once i resent the 1000 to a new address everything was fine. Make sure you send the 1000 coins to a Darkcoind daemon.
I hope this works for you.
Also you can turn your local machines darkcoind off after. It should stay on the list.
Tante just to be sure. Assign a new elastic ip to your remote server before doing this. That way you can forget about the old ip. It will be moved eventually and you will have a new ip linked to a new transaction id ( i assume this is how it works)
Last edited by a moderator:
Are you trying to start your remote darkcoind as a masternode? It's really weird but you start your local darkcoind, the one with the 1000 coins, as the masternode. Then you stop it, and put it in cold storage
Are you trying to start your remote darkcoind as a masternode? It's really weird but you start your local darkcoind, the one with the 1000 coins, as the masternode. Then you stop it, and put it in cold storage
Sorry, a bit tired back there... Just one note, my server has an un-encryted wallet
- Stopped remote darkcoind, deleted remote masternode wallet, start remote daemon with "darkcoind" only.
- configured local wallet to point to masternode (as per Tante's tutorial) - yes, I sent myself 1000 DRK to address 0 - encrypted -
- stopped local darkcoind, restart as darkcoind masternode=Ip etc -> darkcoind walletpassphrase MYPASS 60 -> darkcoind masternode start
- Get error, not capable masternode
Troubleshooting stuff I tried
- Opened TCP port 9999 on router
- delete peers.dat on both sides
- set masternode=0 and =1 on remote machine
- deleted masternode entry all together.
- on local daemon, darkcoind masternote start REMOTE_RCP_PASSWORD_IN_CONF_FILE
- on local daemon,
Nothing, still same issue - not capable masternode
Here is the 1k deposit on local wallet
Local Wallet getinfo
And server side
The version number do not match... masternode payment WAS working on a single remote setup, so thats not it...
Getting nervous about my DRK's...
Last edited by a moderator:
InternetApe
I am root, bow before me!
We have updated the RC2 wallet so everyone please upgrade.
And this is what I had to do to get another person working:
1) Windows: from console: getaccountaddres 0
Linux: ./darkcoind getaccountaddress 0
This will give you the main address for the wallet
2) Windows: from console: walletpassphrase {your wallet pass phrase} 60
Linux: from command line: ./darkcoind walletpassphrase {your wallet pass phrase} 60
3) Windows: from console: sendtoaddress {the wallet address from step 1}
Linux: from command line: ./darkcoind sendtoaddress {the wallet address from step 1}
4) When you see the transaction shutdown the wallet
Windows; Just close the wallet
Linux: ./darkcoind stop
5) Restart the wallet and wait for sync
6) Windows: from console: walletpassphrase {your wallet pass phrase} 60
Linux: from command line: ./darkcoind walletpassphrase {your wallet pass phrase} 60
7) Windows: from console: masternode start
Linux: from command line: ./darkcoind masternode start
That should start the masternode you can run masternode debug command to get the status.
And this is what I had to do to get another person working:
1) Windows: from console: getaccountaddres 0
Linux: ./darkcoind getaccountaddress 0
This will give you the main address for the wallet
2) Windows: from console: walletpassphrase {your wallet pass phrase} 60
Linux: from command line: ./darkcoind walletpassphrase {your wallet pass phrase} 60
3) Windows: from console: sendtoaddress {the wallet address from step 1}
Linux: from command line: ./darkcoind sendtoaddress {the wallet address from step 1}
4) When you see the transaction shutdown the wallet
Windows; Just close the wallet
Linux: ./darkcoind stop
5) Restart the wallet and wait for sync
6) Windows: from console: walletpassphrase {your wallet pass phrase} 60
Linux: from command line: ./darkcoind walletpassphrase {your wallet pass phrase} 60
7) Windows: from console: masternode start
Linux: from command line: ./darkcoind masternode start
That should start the masternode you can run masternode debug command to get the status.
Just wondering, I installed the new RC2 version from today and getaccountaddress 0 returns an empty list...
That's exactly what I did with previous version 0.10.6.3 and it worked fine (address was returned successfully).
Can we use the address for account "" now? I see on my currently running masternode that the account 0 does not exist anymore and the 1000 DRK are on "".
Code:
$ darkcoind getaddressesbyaccount 0
[
]That's exactly what I did with previous version 0.10.6.3 and it worked fine (address was returned successfully).
Can we use the address for account "" now? I see on my currently running masternode that the account 0 does not exist anymore and the 1000 DRK are on "".
vertoe
Three of Nine
You have mixed the commands:
getaccountaddress <account> Returns the current bitcoin address for receiving payments to this account. If <account> does not exist, it will be created along with an associated new address that will be returned.
getaddressesbyaccount <account> Returns the list of addresses for the given account.