RC2 Hard Fork on May 14th!
- Thread starter eduffield
- Start date
Scriptiee
Member
think one of the next updates should address the issue of the password being passed via the command line as raised by vertoe here: http://serverfault.com/q/592744/116529
chaeplin
Well-known member
It is really sad! I really think p2pool is important especially for DRK. We as a community who a give great deal about anonymization and truslessnes should embrace the decentralised nature of p2pools.
Hope it will be patchable!
And thx chaeplin for your great work for p2p mining so far!
We just need help. Hopefully Evan will figure it out before the 14th. Please don't close down your p2pools until the fork, 'cause they'll work until then!
I'm still having issues starting my masternode with my balance in another wallet. I opened port 9999 to my computer, then I started darkcoind via ./darkcoind -masternodeaddr="server's ip address" then I unlocked my wallet for 300 seconds, and tried to start my masternode on my server via darkcoind masternode start "mypassphrase" and I get "not capable masternode" I even opened my server up to the whole internet, and it didn't help. Is this working for anyone else? Have I forgotten a step? Do I need to do anything from the server's end to reach the wallet with the coins?
Thanks for any help
Thanks for any help
Same problem still as above, if anyone can help me? I did do a ./darkcoind getaccountaddress 0 and got a different address, I sent the coin to that address, tried again to start my local wallet up with ./darkcoind -masternodeaddr="server's ip address" , then went to my server address and tried to start the MasterNode, and got "not capable masternode" again. I wanted to check my "address 0" to make sure that it was correct, so I did ./darkcoind getaccountaddress 0 again, and got a completely new address (I think it just generates new addresses??)
Please, can anyone suggest what I might be forgetting or where to look for issues? Thanks so much!!
Please, can anyone suggest what I might be forgetting or where to look for issues? Thanks so much!!
I went to check on my MN, and yeah weird. Dont masternode addresses start with "m" ?
Here is my 1k deposit
I ran getaaccountaddress 0 a few times, generates a NEW address, starting with "n" ... but always the same.
vertoe
Three of Nine
I just browsed the p2pool code, this is quite some task.
Who fixed the other mining pool backends? We really need this p2pool update.
Yes, our masternodes must be updated by May 14th to be functional and to participate in the payment system.
Were you able to run a masternode with a remote wallet holding your coin?
When I do "getaccountaddress" I get an X address. I have something wrong obviously, but no idea what. I tried, after starting my wallet with the ip address of my remote wallet, to turn my local account into a masternode with masternode start, it started up as a masternode, then I did getaccountaddress 0 and got another X address. What is my problem?
Last edited by a moderator:
miningpoolhub
New member
Can you clarify what this mean?
-> (Without DarkSend. For pool operators and anyone else that wants to compile from opensource):
Why pool operators have to use without Darksend version?
What is the different between with DarkSend and without DarkSend.
With DarkSend version -> send all coins in DarkSend by default? so pool operators must not use it?
Without DarkSend version -> includes masternode payouts but DarkSend is not included? or disable?
-> (Without DarkSend. For pool operators and anyone else that wants to compile from opensource):
Why pool operators have to use without Darksend version?
What is the different between with DarkSend and without DarkSend.
With DarkSend version -> send all coins in DarkSend by default? so pool operators must not use it?
Without DarkSend version -> includes masternode payouts but DarkSend is not included? or disable?
The update changes how mining works. payments will be made to masternodes. This part of the code has been open sourced. However, DarkSEnd is still "under the hood". If you compile your own wallets, you will not get DarkSEnd, however, you will get what you need to continue to communicate with the network after we hit whatever block Evan chose to fork at for the new payment system. This will effect all transactions, so everyone, regardless if they use DarkSend beta or not, must update their wallets by May 14th.
Is there a reason the downloads are off line?
vertoe
Three of Nine
This. Your pool needs to know how to pay out masternodes without taking care about the rest of the darksend stuff.
mattmct
Active member
Thanks, I suspected as much, but then read about a whole bunch of people who updated but weren't able to launch the master node.
Also, I started a thread here, for a request of a guide for runing a remote masternode, without the 1000DRK on the server. As there hasn't been any official instructions or decent guides on this
https://darkcointalk.org/threads/ne...e-remotely-without-the-1000drk-on-server.386/
Hopefully someone can chime in!
yidakee, I think you might be using the testnet wallet? I just remembered that those addresses start with m's or something
Also, I just realized, all the talk about running a remote wallet happened before May 1st when we got this new version (RC2) and it may be this version doesn't have it. either by accident or for a reason?? It was April 27th when I read these comments:
https://bitcointalk.org/index.php?topic=421615.msg6427569#msg6427569