v0.10.15 - Onyx Release

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,280
1,283
crowning: 76
give ppl time as always...
 

kryptofoo

Member
Jul 21, 2014
114
36
78
Germany
Nice work, thanks!

Bummed that you decided to wait one month for enforcement. Two weeks seems like more than adequate time to notify people and get the majority updated. :(
 

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
OK, I just deleted a wallet with over 10,000DRK in it. This is why we have backups people! :eek:
Man, that would have been a great service to the Darkcoin community ;)

p.s. be careful in the future because that might actually pump the price a bit ))
 

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
eduffield, CryptoSiD noted in IRC that there is a typo on the update link for NOMP Users. It shows "404". He still managed to access by deleting "-" but others might struggle. Thanks.
 
Last edited by a moderator:
  • Like
Reactions: Raico and flare

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
Are DRK.MN and Poolhash.org showing inactive for updated masternodes because they aren't updated? I masternode started all from local after updating the remote daemons and my masternode IP is showing up in the MN list as 1. Just curious if these two sites will not reflect active/inactive or what the deal is.
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
Something is srewy with the masternode list. My local qt wallet currently has half of them including 2 of mine as :0. All my MNs report themselves as :1 but one of them appears as :0 in the lists of the others.

Updated server, restarted them all locally from an updated qt wallet.
 

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
Something is srewy with the masternode list. My local qt wallet currently has half of them including 2 of mine as :0. All my MNs report themselves as :1 but one of them appears as :0 in the lists of the others.

Updated server, restarted them all locally from an updated qt wallet.
What is the IP, I can check it for you again.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
Something is srewy with the masternode list. My local qt wallet currently has half of them including 2 of mine as :0. All my MNs report themselves as :1 but one of them appears as :0 in the lists of the others.

Updated server, restarted them all locally from an updated qt wallet.
Let the network settle down, it takes some time to find consensus. Look at it in 24h :)
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
Something is srewy with the masternode list. My local qt wallet currently has half of them including 2 of mine as :0. All my MNs report themselves as :1 but one of them appears as :0 in the lists of the others.

Updated server, restarted them all locally from an updated qt wallet.
This is the masternode list that suchpool has: http://paste.ubuntu.com/8575582/

All my masternodes are on there. :)
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Through linux the MN's I manage are :1 ... at least they were when I activated them... Let me go check again...

Yup... all are :1
 

stonehedge

Well-known Member
Foundation Member
Jul 31, 2014
696
333
233
You are still my hero^^

Hope to join you at London Marathon 2016 ;-)
Lets see if I hit my targets for 2015 first. It might be my last one! I might never walk again! I'll cheer you on and buy you a beer either way!
 
  • Like
Reactions: flare

coingun

Active Member
Masternode Owner/Operator
Jul 8, 2014
489
402
133
masternode.io



ATTENTION: POOL OPERATORS

This update includes a fork, all daemons and stratum deployments must update their code to pay the correct masternodes and correct reward amounts.

Software Updates:

Stratum Users:
https://github.com/darkcoin/darkcoin-stratum/commit/4abf08bd0d3de7fae2311f54edb8a5f86f9ab39a

NOMP Users:
https://github.com/darkcoin/node-stratum-pool/commit/e598fb0b6b643191304b257e0d8b0f47f8a5d34a-

P2Pool Users:
https://github.com/darkcoin/p2pool-drk/commit/98a77c90d5dc460695cab71daed8d8aaab955289

Deployment Schedule:

Immediately: Enforcement will be turned off, allowing for pools to update their software without risk of orphaned blocks

Oct 23, 2014: Rewards will step up to 25%. Darkcoin users are encouraged to contact pools that have not updated and politely ask them to update.

Nov 14, 2014: Enforcement will be turned on, any pools that have not update will have their blocks rejected.

Who Needs To Update?

All Darkcoin users must update their clients.

What’s New?

Part of securing the Darkcoin network is creating a strong and healthy network of full nodes to back it up. These nodes provide many tasks for users such as propagating messages, syncing clients and mixing users funds via Darksend.

To make the network resistant to attack we required these nodes to hold 1000DRK (these coins are held in a completely trustless way in cold storage in most cases, so they can’t be stolen). In return for holding the coins and running the node, these users are paid 20% of the block reward.

Security for Darksend and InstantX is provided by selecting masternodes deterministically from the total set, then using multiple of these nodes to make decisions. Vastly greater security becomes possible when you add more nodes due to the cost associated with controlling a majority of said nodes. For statistical analysis of this please checkout the InstantX whitepaper .

Increasing Rewards Schedule

With this release we will progressively change the reward to incentivize the creation of more masternodes, this should strengthen the network and protect it from sybil attacks making it more expensive for attackers to control an important portion of the nodes.

This is also key for instant transaction confirmations to be a reality, the network needs to be robust enough to handle a large amount of transactions as we strive for adoption on real world applications. The features that give value to Darkcoin need to be protected as that is what will ensure the long term success of the project for the benefit of all Darkcoin supporters, current and those that will join DRK in the future.



*Currently there are 900 active masternodes. Numbers are expected to increase as profitability rises.
** ROI calculation is ((1/t)*b*(r*s)*365)/1000

Where:
t = Total number of masternodes
b = Blocks per day on average (576 for Darkcoin)
r = Average reward per block
s = Masternode mining share

Steady Payments and Proof-of-Service

Another issue in the past has been the volatility in return due to the random nature of masternode payments. This is being dealt with by creating an algorithm to pay the masternodes evenly. Each masternode can expect a payment every N blocks with a variance of about 10%.

Also included in this release is a framework that we can build a true proof-of-service platform on. This means only masternodes actually providing services will be paid for those services.

To only pay active masternodes, pay masternodes evenly and ensure that all pools pay the correct node and amount we’ve introduced a new type of node, the reference node. This node has a special key that allows it to tell the network which nodes get paid, on which blocks in the future. Anyone on the network can verify these nodes are doing their job (i.e. not tampering with the results) by running the code and comparing the payee’s due to the deterministic algorithm used. In case of DDOS or a service failure, the network default to paying random masternodes as it does now.

This setup is non-exploitable and will serve as a mechanism of enforcement till we can revisit this in the future. A better future solution would be an in-blockchain voting mechanism like RC3 or a second blockchain updated by the miners that stores the masternode list.

Masternode Setup

Flare’s Trustless Masternode Hosting Service:
https://darkcointalk.org/threads/service-masternode-hosting-service.2648/

Yidakee’s Service:
https://darkcointalk.org/threads/yi...tup-services-ghostplayer-on-bitcointalk.1633/

MangledBlue’s Service:
https://darkcointalk.org/threads/services-mn-shared-admin.2678/

How To Guide:
https://darkcointalk.org/threads/taos-masternode-setup-guide-for-dummies.2680/

How To Guide 2:
https://darkcointalk.org/threads/remote-masternode-guide-updated.410/

Just for fun:

Darksend Improvements

Recently after open sourcing, Darksend has been undergoing an exhaustive evaluation of it’s security to many different kinds of attacks. This update includes over 15 measures to prevent abuses of the system and keep it healthy.

To prevent such attacks, we require users to post a collateral payment to the masternode they wish to use. Parts of the Darksend process in the past were not using this protective measures and were quickly identified and attacked. This update includes many improvements to the way collateral is used to make attacking expensive.

One of the notable improvements is that collateral transactions pay the fee directly to miners. This creates a situation where to double spend attack the collateral transaction, one would have to pay a higher fee to the miners. Since the collateral fee is payed to the miners already, double spending attacks against the system are impossible.

What’s next?

We had to take a short detour from InstantX to focus on Darksend after it gained enough attention to be actively attacked by our competitors. Now that we’re confident of the security of the system, we’ll be moving back to working on InstantX.

The first version of InstantX will be a soft-fork. It will simply show when transactions have been successfully validated by the observer network. This will give us some real world testing of the framework.

We have some other projects and exciting things in the works. We’ll be announcing those in the following months.

Downloads

10.15.13 Onyx Binaries: All Users


Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.13-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.13-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.13-linux.tar.gz
p2pool code needs a version bump on line 22 of the ~/p2pool/bitcoin/p2p.py file. It's still showing version 70038 and this now won't let the new wallets update. I have manually adjusted it to 70058 and finally my p2pool nodes started working again.
 

TaoOfSatoshi

Grizzled Member
Jul 15, 2014
2,800
2,615
1,183
Dash Nation
www.dashnation.com



ATTENTION: POOL OPERATORS

This update includes a fork, all daemons and stratum deployments must update their code to pay the correct masternodes and correct reward amounts.

Software Updates:

Stratum Users:
https://github.com/darkcoin/darkcoin-stratum/commit/4abf08bd0d3de7fae2311f54edb8a5f86f9ab39a

NOMP Users:
https://github.com/darkcoin/node-stratum-pool/commit/e598fb0b6b643191304b257e0d8b0f47f8a5d34a-

P2Pool Users:
https://github.com/darkcoin/p2pool-drk/commit/98a77c90d5dc460695cab71daed8d8aaab955289

Deployment Schedule:

Immediately: Enforcement will be turned off, allowing for pools to update their software without risk of orphaned blocks

Oct 23, 2014: Rewards will step up to 25%. Darkcoin users are encouraged to contact pools that have not updated and politely ask them to update.

Nov 14, 2014: Enforcement will be turned on, any pools that have not update will have their blocks rejected.

Who Needs To Update?

All Darkcoin users must update their clients.

What’s New?

Part of securing the Darkcoin network is creating a strong and healthy network of full nodes to back it up. These nodes provide many tasks for users such as propagating messages, syncing clients and mixing users funds via Darksend.

To make the network resistant to attack we required these nodes to hold 1000DRK (these coins are held in a completely trustless way in cold storage in most cases, so they can’t be stolen). In return for holding the coins and running the node, these users are paid 20% of the block reward.

Security for Darksend and InstantX is provided by selecting masternodes deterministically from the total set, then using multiple of these nodes to make decisions. Vastly greater security becomes possible when you add more nodes due to the cost associated with controlling a majority of said nodes. For statistical analysis of this please checkout the InstantX whitepaper .

Increasing Rewards Schedule

With this release we will progressively change the reward to incentivize the creation of more masternodes, this should strengthen the network and protect it from sybil attacks making it more expensive for attackers to control an important portion of the nodes.

This is also key for instant transaction confirmations to be a reality, the network needs to be robust enough to handle a large amount of transactions as we strive for adoption on real world applications. The features that give value to Darkcoin need to be protected as that is what will ensure the long term success of the project for the benefit of all Darkcoin supporters, current and those that will join DRK in the future.



*Currently there are 900 active masternodes. Numbers are expected to increase as profitability rises.
** ROI calculation is ((1/t)*b*(r*s)*365)/1000

Where:
t = Total number of masternodes
b = Blocks per day on average (576 for Darkcoin)
r = Average reward per block
s = Masternode mining share

Steady Payments and Proof-of-Service

Another issue in the past has been the volatility in return due to the random nature of masternode payments. This is being dealt with by creating an algorithm to pay the masternodes evenly. Each masternode can expect a payment every N blocks with a variance of about 10%.

Also included in this release is a framework that we can build a true proof-of-service platform on. This means only masternodes actually providing services will be paid for those services.

To only pay active masternodes, pay masternodes evenly and ensure that all pools pay the correct node and amount we’ve introduced a new type of node, the reference node. This node has a special key that allows it to tell the network which nodes get paid, on which blocks in the future. Anyone on the network can verify these nodes are doing their job (i.e. not tampering with the results) by running the code and comparing the payee’s due to the deterministic algorithm used. In case of DDOS or a service failure, the network default to paying random masternodes as it does now.

This setup is non-exploitable and will serve as a mechanism of enforcement till we can revisit this in the future. A better future solution would be an in-blockchain voting mechanism like RC3 or a second blockchain updated by the miners that stores the masternode list.

Masternode Setup

Flare’s Trustless Masternode Hosting Service:
https://darkcointalk.org/threads/service-masternode-hosting-service.2648/

Yidakee’s Service:
https://darkcointalk.org/threads/yi...tup-services-ghostplayer-on-bitcointalk.1633/

MangledBlue’s Service:
https://darkcointalk.org/threads/services-mn-shared-admin.2678/

How To Guide:
https://darkcointalk.org/threads/taos-masternode-setup-guide-for-dummies.2680/

How To Guide 2:
https://darkcointalk.org/threads/remote-masternode-guide-updated.410/

Just for fun:

Darksend Improvements

Recently after open sourcing, Darksend has been undergoing an exhaustive evaluation of it’s security to many different kinds of attacks. This update includes over 15 measures to prevent abuses of the system and keep it healthy.

To prevent such attacks, we require users to post a collateral payment to the masternode they wish to use. Parts of the Darksend process in the past were not using this protective measures and were quickly identified and attacked. This update includes many improvements to the way collateral is used to make attacking expensive.

One of the notable improvements is that collateral transactions pay the fee directly to miners. This creates a situation where to double spend attack the collateral transaction, one would have to pay a higher fee to the miners. Since the collateral fee is payed to the miners already, double spending attacks against the system are impossible.

What’s next?

We had to take a short detour from InstantX to focus on Darksend after it gained enough attention to be actively attacked by our competitors. Now that we’re confident of the security of the system, we’ll be moving back to working on InstantX.

The first version of InstantX will be a soft-fork. It will simply show when transactions have been successfully validated by the observer network. This will give us some real world testing of the framework.

We have some other projects and exciting things in the works. We’ll be announcing those in the following months.

Downloads

10.15.13 Onyx Binaries: All Users


Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.13-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.13-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.13-linux.tar.gz
eduffield I guess I'm late to the party! Damn sleep! Thanks for including my newly created guide in your post!

Hopefully it will help a lot of people to set up 2000 Masternodes....
 
  • Like
Reactions: Raico and Roslyn

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,280
1,283
Rule of thumb in case of MN protocol updates: update MN, start, forget it for 24h, then check :)
Suddenly got demention...18h left :)
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
p2pool code needs a version bump on line 22 of the ~/p2pool/bitcoin/p2p.py file. It's still showing version 70038 and this now won't let the new wallets update. I have manually adjusted it to 70058 and finally my p2pool nodes started working again.
why did you put 70058? should be 70043 I guess...
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
Updated the masternode daemon and my local wallet to 0.10.15.13. My masternode appears on http://drk.poolhash.org/masternode.html but not on my "./darkcoind masternode list".

Different queries?
El Presidente hasn't updated his servers at poolhash.org yet, I wouldn't rely on it. If your MN reports :1 you're OK. Did you restart your MN from the local wallet? I think you might need to if an update includes a protocol bump, at least this was my recent experience on testnet.
 

oaxaca

Well-known Member
Foundation Member
Jul 8, 2014
573
832
263
El Presidente hasn't updated his servers at poolhash.org yet, I wouldn't rely on it. If your MN reports :1 you're OK. Did you restart your MN from the local wallet? I think you might need to if an update includes a protocol bump, at least this was my recent experience on testnet.
That's what I thought. :1 on the terminal. BTW, how else would I restart the MN except from the local wallet?