Evan, is there any way you could update the first post on bitcointalk with this info (and links) as well as temporarily change the thread title name to mention the hard fork?
I think everybody involved with DRK wants this to be as smooth as possible (considering the last hard fork) and judging by the number of people still on old clients there will be a lot of unwanted confusion on the 20th.
Thanks.![]()
I'm thinking the exact same, and I'm sure everyone else here is also. Not everyone reads the forums every especially the rate that the threads are growing, updating the main page / thread would be a good start. I hope they aren't any lazy exchange owners!IMPORTANT!!!!!!!!!!!!!!!!!!!!
Have ALL the major exchanges and pool operators updated to the latest software so we dont have any problems after the 6/20 fork (like we did last time)?
I think the dev should contact all the exchanges to make sure so that the problem from last time is not repeated! We cant just assume they will update on their own without us contacting them. As we know (from last time) the exchanges handle many coins and have many other priorities in addition to ours.
Thanks in advance!
Unfortunately there are multiple "lazy exchange" owners. Some exchanges do not bother to update their wallets until either:I'm thinking the exact same, and I'm sure everyone else here is also. Not everyone reads the forums every especially the rate that the threads are growing, updating the main page / thread would be a good start. I hope they aren't any lazy exchange owners!
eduffield / InternetApe
+1. Please name any pools or exchanges that didn't update last time here unless they've already confirmed they've updated this time.Unfortunately there are multiple "lazy exchange" owners. Some exchanges do not bother to update their wallets
...
We cannot afford a situation like the last fork
Evan has also pushed out an alert to all older versions telling them to update.I received a mail from Evan telling me to update to 0.10.10 or 0.9.10 on 12/06/2014 part of the mailing list for all service owners, so unless a fool is running an exchange without been subscribed to the mailing list, we should be ok on that front.
So they at least did that. Unfortunately no mail for 0.10.10.1 and 0.9.10.1 that was released the day after.
Check http://tdrk.poolhash.org/
As stated in https://www.darkcointalk.org/threads/rc3-hard-fork-on-june-20th.1241/ ,
https://github.com/darkcoinproject/node-stratum-pool/commit/c37103907007d517650cb61360826b0112895cc5
required chages is number 10 to 5.
I have checked https://github.com/zone117x/node-stratum-pool .Code:if (rpcData.payee) { - var payeeReward = Math.ceil(reward / 10); + var payeeReward = Math.ceil(reward / 5);
Already merged.
https://github.com/zone117x/node-stratum-pool/commit/a28752a9dbf4c9f142c69d0e2c9ed3f7030ab9d5
nomp on testnet has unusual config on rewardRecipients.
One of block found by nomp.Code:[email protected]:~# cat /opt/nomp/pool_configs/darkcoin.json { "enabled": true, "coin": "darkcoin.json", "address": "mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV", "rewardRecipients": { "muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4": 25, "moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H": 1 },
http://184.73.179.148:1234/block/000000002affe7e260cde6405d71ff4545d1832bea47febc16c986f15bc8b859
* 152 * 0.2 = 30.4 / masternode paymentCode:Transactions TransactionFeeSize (kB)From (amount)To (amount) cc620612f5...00.225Generation: 152 + 0 total fees mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV: 89.984 mtRuEbzakYd8vb98szxiHE8unB1mqaXJPY: 30.4 muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4: 30.4 moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H: 1.216
* 152 - 30.4 = 121.6
* 121.6 * 0.25 = 30.4 / rewardRecipients
Welcome to the forum!Hi everyone! I'm new here..
I've just compiled the darkcoind deamon today, from the official Github repo.
However, I'm unable to launch my p2pool as the message is that my version is too old.
This is what I get:
"version" : 90400,
"protocolversion" : 70015,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 50834,
"timeoffset" : -1,
"connections" : 17,
"proxy" : "",
"difficulty" : 483.51374719,
"testnet" : false,
"keypoololdest" : 1403088260,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"
Why am I getting this version of the daemon considering that I just downloaded it today? Should it not be darksend compatible as I have downloaded as per link on the OT?
How can I have the latest darksend compatible version running on my Ubuntu P2P?
Thanks!
Thanks for the welcome! I have downloaded it from Github and compiled.Welcome to the forum!
The version you have is rather old (0.9.4.0) recent is 0.9.10.1 - did you clone github repo or download source-package?
Additionally Darksend is not part of github version currently, if you want to use/test darksend you need to download the binary RC3 from main website --> http://www.darkcoin.io/downloads/rc/darkcoind
Just wanted to say thanks to everyone on the forum here, especially dstorm for the updates for P2Pool!P2Pool update is now available. Sorry about the delay. I have been sick for almost two weeks.
https://bitbucket.org/dstorm/p2pool-drk
It supports both block types so you can update now. It will detect when masternode payments start.
Use bind and externalip in the configuration file.When running a masternode its listens on all network interfaces on port 9999.
Is there a config command to make it listen only on one specific interface?
Settings like this will helpUse bind and externalip in the configuration file.
Beware that the rpc will still bind on all regardless (from my experience).
bind=127.0.0.1
bind=a.a.a.a
externalip=a.a.a.a
rpcport=99998
rpcallowip=127.0.0.1
bind=127.0.0.2
bind=b.b.b.b
externalip=b.b.b.b
rpcport=9997
rpcallowip=127.0.0.1
Quoting my call from last Friday as we have less than 30 hours left to goMasternode network is gaining traction: 49 nodes, 100% operational
[...]
My last measures of mainnet RC2 revealed that there were 170 listening nodes. Taking into account that some nodes may have had blocked ports i expect node count to be 200ish by June 20th.
[...]
800mn were not a correct count, due to flaws in RC2 masternode protocol.
Hey guys, I"m hoping someone can help me with the above. As quoted above, one of my masternodes is working fine with the cold wallet. But I launched two yesterday with the cold wallet option (they were hot, now cold), and they showed for an hour or so, now listed as inactive. BUT shows with open ports. https://elbzo.net/masternodes.htmlBugger.
Two days ago I started my first masternode via the cold wallet method using windows. It's still running along nicely.
Earlier today, I changed my hot nodes to cold nodes. They were showing up nicely a few hours ago, but now they're showing as "unlisted / inactive" over at https://elbzo.net/masternodes.html :/ .
I used unique wallets for each masternode launch, with their own gen key etc. Pretty sure I did it right! Not sure why they are now inactive...
I launched them from my local / hot wallet, which had the same IP address, not sure if that could cause any problems?
Is there anyway to diagnose?I appreciate any help.
My debug log says this:
2014-06-19 00:27:39 CDarkSendPool::NewBlock - Is Masternode, resetting
2014-06-19 00:27:39 ProcessBlock: ACCEPTED
CDarkSendPool::RegisterAsMasterNode() - Masternode input = CTxIn(COutPoint(remov, 0), scriptSig=)
2014-06-19 00:30:39 socket closed
2014-06-19 00:30:39 disconnecting node 109.128.232.160:59909
2014-06-19 00:30:40 socket closed
2014-06-19 00:30:40 disconnecting node 128.199.243.115:42307
2014-06-19 00:31:40 Added 1 addresses from 98.26.88.87: 4090 tried, 10489 new
2014-06-19 00:33:46 dsee - Got NEW masternode entry 37.139.20.245:9999
2014-06-19 00:33:46 dsee - Accepted masternode entry -1 -1
My experience in testnet might help.Hey guys, I"m hoping someone can help me with the above. As quoted above, one of my masternodes is working fine with the cold wallet. But I launched two yesterday with the cold wallet option (they were hot, now cold), and they showed for an hour or so, now listed as inactive. BUT shows with open ports. https://elbzo.net/masternodes.html
Any ideas? The only thing I can think is that they were launched from my hot wallets, client from the same IP address. (cold masternodes have own IP of course). But I heave read that other have managed to launch multiple from same IP.
I'm really quite lost. Maybe just maybe I did the genkey command before I added the masternodeaddr to the local wallet? Would that change things?
Cheers guys.
Banning is done by ip address.I changed it back to a hot node just to test, same thing, it showed fine at first, then unlisted. I guess like you say, the wallet is now banned?
I'll make a new wallet as you say, and try that way. Not sure to go for hot or cold on this attempt.
If my wallet is banned, is there a chance my masternode IP could be banned also? or is it all wallet based?
Thanks 4 the update.P2Pool update is now available. Sorry about the delay. I have been sick for almost two weeks.
https://bitbucket.org/dstorm/p2pool-drk
It supports both block types so you can update now. It will detect when masternode payments start.