RC3: Hard Fork on June 20th!

[elbereth]

Thanks for the update dstorm. Hope you are feeling better. I have updated darkcoin.fr:7903.

 

[coderbob]

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!

 

[mattmct]

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.

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!

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

 

[coderbob]

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

Unfortunately there are multiple "lazy exchange" owners. Some exchanges do not bother to update their wallets until either:
1. Developer tells them they need to by a certain date to avoid a problem
2. They encounter a problem

PLEASE contact all the exchanges listed on the bitcointalk announcement page. I am afraid that failure to do so (especially after the last fork) will lead to a lot of faith being lost in the community if # 2 above occurs instead of #1

I think everyone in the DRK community loves the progress our developers have made from a technical standpoint. However communication has been a big weakness (updating links on websites, communicating with exchanges prior to last fork, etc)

Going forward (after RC3 is proven successful) I have some great ideas to spread DRK adoption. If you need help with other areas (communication, marketing, etc) please ask. Many will be happy to help as we know you are busy coding. Please just don't underestimate the importance of communication in keeping the community happy and ensuring DRK can maintain its market leading advantage.

We cannot afford a situation like the last fork

 

[TsuyokuNaritai]

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

+1. Please name any pools or exchanges that didn't update last time here unless they've already confirmed they've updated this time.

 

[elbereth]

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.

 

[TsuyokuNaritai]

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.

Evan has also pushed out an alert to all older versions telling them to update.

 

[weirdgod]

I've published a guide MasterNode Windows-Linux combo here.
Spread the word. Comments/feedback welcome.

More masternodes = stronger network for upcoming RC4 (which will focus on privacy) = less DRKs available on market = pushing the price higher.
Win Win

 

[chaeplin]

I saw this msg on testnet and mainnet
[email protected]:~/.darkcoin> ./darkcoind getinfo
{
"version" : 101001,
"protocolversion" : 70018,
"walletversion" : 60000,
"balance" : 4129.53600000,
"blocks" : 21112,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.19315620,
"testnet" : true,
"keypoololdest" : 1402636400,
"keypoolsize" : 100,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : "Hard Fork Alert: Masternode Payments begin on Friday. Please update! http://goo.gl/ucp4m7"
}

[email protected]:~> darkcoind getinfo

{
"version" : 100811,
"protocolversion" : 70015,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 81461,
"timeoffset" : 0,
"connections" : 5,
"proxy" : "",
"difficulty" : 4933.41377068,
"testnet" : false,
"keypoololdest" : 1401880149,
"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"

}

 

[miningpoolhub]

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.

if (rpcData.payee) {
- var payeeReward = Math.ceil(reward / 10);
+ var payeeReward = Math.ceil(reward / 5);

I have checked https://github.com/zone117x/node-stratum-pool .
Already merged.
https://github.com/zone117x/node-stratum-pool/commit/a28752a9dbf4c9f142c69d0e2c9ed3f7030ab9d5



nomp on testnet has unusual config on rewardRecipients.

[email protected]:~# cat /opt/nomp/pool_configs/darkcoin.json
{
    "enabled": true,
    "coin": "darkcoin.json",
    "address": "mq6hAJRXkH94a2Dp38akBj1LwNNP8tubJV",
    "rewardRecipients": {
        "muduy36Y9rLcpWEoT14p1TGXNggwSRZSa4": 25,
        "moQD1AbtbDgPhDCXhK5x9rkUQrTHK3ZE7H": 1
    },

One of block found by nomp.
http://184.73.179.148:1234/block/000000002affe7e260cde6405d71ff4545d1832bea47febc16c986f15bc8b859

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 * 0.2 = 30.4 / masternode payment
* 152 - 30.4 = 121.6
* 121.6 * 0.25 = 30.4 / rewardRecipients

tested on testnet, and it works well only by changing reward value. I didn't need to change other codes.
Thanks.

 

[fabioganga]

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!

 

[flare]

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!

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

 

[fabioganga]

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

Thanks for the welcome! I have downloaded it from Github and compiled.

I'll now run this version... thanks a lot!

Fabio

 

[mattmct]

Bugger.

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

 

[ourlink]

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.

Just wanted to say thanks to everyone on the forum here, especially dstorm for the updates for P2Pool!
I followed through with the update and I am happy to say that we are up and ready for the hardfork on Friday.
http://pool.ourlink.net:7903 (shameless plug for our pool)

 

[rango]

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?

 

[elbereth]

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?

Use bind and externalip in the configuration file.
Beware that the rpc will still bind on all regardless (from my experience).

 

[chaeplin]

Use bind and externalip in the configuration file.
Beware that the rpc will still bind on all regardless (from my experience).

Settings like this will help
int a / daemon a / user a

bind=127.0.0.1
bind=a.a.a.a
externalip=a.a.a.a
rpcport=99998
rpcallowip=127.0.0.1

int b / daemon b / user b

bind=127.0.0.2
bind=b.b.b.b
externalip=b.b.b.b
rpcport=9997
rpcallowip=127.0.0.1

 

[flare]

Masternode 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.

Quoting my call from last Friday as we have less than 30 hours left to go

Here we stand: Masternode network is in very good shape, 242 active nodes - 98.7% open port 9999 (a lot different from RC2). From chaeplins stats at http://drk.poolhash.org/subver.html we get that there is potentially a supply of 42 old RC2 masternode clients left - and when updated will bring us to 280 nodes at payment start.

Masternode network is stable so far and is behaving a lot different/better/more error tolerant that RC2 - seems like the joint effort the team took testing in testnet is paying off.

I do not expect major problems with the fork, as long as all pools and exchanges have updated to 0.9.10.1

Some glitches we may experience:

- miners with 0.9.10.0 may cause some unpaid blocks due to vote expiration --> some deviation from 100%, but will level out at 98%
- miners with outdated versions < 0.9.10.0 will have their blocks rejected from network --> update!

So long, enjoy the ride. Looking forward to test RC4

 

[rango]

Thank you very much, elbereth & chaeplin. Interface settings work.

More academic question: How does the thing running a masterserver in the coldwallet setting from technical perspective work? Is the masternodeprivkey a hash over masterserver IP, the address where the 1000 DRK are stored and the wallet passphrase? So even if you run your masterserver with an empty wallet, the masternodeprivkey allows darkcoind to validate if the funds are stored within the network at the given address?

 

[elbereth]

I don't know what the privkey is used for, but when you do masternode start the pubkey (for the payments) is associated with the IP used in masternodeaddr. That's how the link is done and how the verification for the 1000 DRK is done.
Using the same masternodeprivkey in both config file local/remote makes sure you cannot hijack remote nodes.

 

[mattmct]

Bugger.

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

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.

 

[chaeplin]

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.

My experience in testnet might help.
https://www.darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-44#post-8910
In essence, move 1K to a NEW address, make a new masternodeprivkey, then restart.

 

[mattmct]

Interesting, thanks chaeplin . I was wondering if the genkey command gave a different output depending if I had masternodeadd in the config file or not, but I see it makes a different key every time the command is issued.

I was tempted to move back to a hot wallet, but maybe the wallet address is now banned? Cheers

 

[mattmct]

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?

 

[chaeplin]

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?

Banning is done by ip address.
So changing ip will help.

You don't need to make a New wallet.
Backup wallet. darkcoind backupwallet new_name_01_wallet.dat

Using same wallet, make a new address, send 1k DRK to the new address.
Backup wallet. darkcoind backupwallet new_name_02_wallet.dat

And then use setaccount to change previous account 0 address to new account name.
And set the new address to account 0.
Backup wallet. darkcoind backupwallet new_name_03_wallet.dat

You need +7 confirmation to start masternode.

this one was using same wallet : https://www.darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-44#post-8910

 

[mattmct]

Cheers chaeplin , once again, you're awesome!

 

[guugll]

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.

Thanks 4 the update.

 

[n00b_miner]

Ok all updated on http://drk.p2pool.n00bsys0p.co.uk:7903/static/

Thanks for all your hard work guys! All looking good thus far!

 

[Light]

Could anybody please write the exact time of the hard fork with the time zone. Thanks.