v0.10.15 - Onyx Release

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183


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.21 Onyx Binaries: All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.21-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.21-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.21-linux.tar.gz

v0.10.15.14

Adds a fix for a DOS style attack against the masternode list that was attempted earlier today. This attack didn’t result in any harm to the network or extra payments for the attacker, but I've patched it to stop the list from bloating up. This is not mandatory, but please update if you can.

v0.10.15.15 - Onyx Masternode Stability Update

There have been some masternode stability problems (masternodes not staying active on the network) for some users, this was caused by the masternode operators changing the masternodeprivkey and then starting the masternode again. This lead to some of the networking have one pinging key and parts of the network having another. This update fixes that issue and will allow masternodes to change that key.

An alternative solution is to move the 1000DRK input to a brand new address that the network has not seen. Then start the masternode normally. Once the network updates to v15.15, we won't have these issues anymore.

Enforcement:

At block 158,000 masternode rewards will jump to 25%, if more than 80% of the network is updating and paying the correct rewards enforcement will be activated then. From the looks of it, we're very close to those numbers already. Once enforcement is active, payments will be completely 100% fair and equal between all masternodes.

v0.10.15.16 - Onyx Masternode Stability Update 2

After some more inspection I found there were multiple Masternode announcement messages propagating around the network. This update filters out all but the newest one to ensure the list is correct and up-to-date. It's not manditory to update, but please do if you can.

v0.10.15.17 - GetBlockPayee fix for enforcement

v0.10.15.18/19 - Allow for out of order blocks when checking for masternode payments

v0.10.15.20/21 - added bloom filters for dsee/dseep broadcasts, moved expensive dsee search, masternode vote caching
 
Last edited by a moderator:

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
ROFL to the set up video :D

Super excited about ONYX!
 

defunctec

Member
Jul 11, 2014
103
36
78
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.

Wow! Does this mean there has been 15 separate attacks on the network since open source?
 

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,280
1,283
Great Evan!
elbereth Can you please update you masternodes/blocks service so we can start informing not updated pools?
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
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.

Wow! Does this mean there has been 15 separate attacks on the network since open source?
No, I just found a few weak points that I hardened. It'll be interesting to see what they try to attack now...
 

defunctec

Member
Jul 11, 2014
103
36
78
No, I just found a few weak points that I hardened. It'll be interesting to see what they try to attack now...
I'd like to see them really test you haha.

As far as i'm aware there has only been the masternode exploit so far? How long did it take to fix, an hour? Pha!

I want to see heavy, difficult attacks to fix. We and the world would see just how resilient DRK is.

BTW WELL DONE WITH ONYX CLAP CLAP CLAP
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Firing up my Linux! Well done Evan, once again!

Note to all my customers, I unfortunately have to leave town from Saturday the 18th until Monday the 27th. I will have very limited internet connection.

I will do my very best to be in touch and if this update is as simple as RC5 and does not require local masternode start, I think I may very well be able to cater to everyone.

Sorry for the inconvenience.
 
Last edited by a moderator:

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
Looks like I will need to start them locally again. Masternode daemons updated but won't be able to start from updated local wallet for another hour or so. Was hoping that wouldn't be the case. After they are started, are they now good to go for future update with an autostart (I believe that was one of the things discussed).
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
No, I just found a few weak points that I hardened. It'll be interesting to see what they try to attack now...
Evan, in the back of my mind.. what I'm afraid is somehow during the mixing.... my DRKs disappear.. won't come back to my wallet... Is this possible?
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
Evan, in the back of my mind.. what I'm afraid is somehow during the mixing.... my DRKs disappear.. won't come back to my wallet... Is this possible?
No, they never leave your wallet. The only way to lose DRK while mixing is corruption. The wallet uses a keypool of 1000, so the change addresses it will use are actually already known. As long as you have a backup, you won't lose anything.
 
  • Like
Reactions: Raico

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
No, they never leave your wallet. The only way to lose DRK while mixing is corruption. The wallet uses a keypool of 1000, so the change addresses it will use are actually already known. As long as you have a backup, you won't lose anything.
Ah.. Thanks, good to know. I thought I read somewhere that the drk amount is split up.. each denominated amount goes out of your wallet to be in a MN pool to mix (and this is why we see "Unconfirmed" amount during mixing)... then after the rounds, they match up and go back to your wallet.. I guess I need to read it up again.
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Yup... seems like you really do need to restart the MN from the local wallet.
 

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,280
1,283
Yup... seems like you really do need to restart the MN from the local wallet.
YES, after updating the wallet in mandatory release both wallets need to be chnged and restarted masternode from local wallet too.

All my MNs updated and running.

Thnx Evan!
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
[email protected]:~$ darkcoind getinfo
{
"version" : 101513,
"protocolversion" : 70043,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 153651,
"timeoffset" : 0,
"connections" : 9,
"proxy" : "",
"difficulty" : 2005.65788718,
"testnet" : false,
"keypoololdest" : 1408550160,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
[email protected]:~$ darkcoind masternode count
47
 

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,280
1,283
[email protected]:~$ darkcoind getinfo
{
"version" : 101513,
"protocolversion" : 70043,
"walletversion" : 60000,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 153651,
"timeoffset" : 0,
"connections" : 9,
"proxy" : "",
"difficulty" : 2005.65788718,
"testnet" : false,
"keypoololdest" : 1408550160,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
[email protected]:~$ darkcoind masternode count
47
56 ;) - I`ve finished starting my local part ;)
 

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,280
1,283
So Evan after this release what is next step?
 

crowning

Well-known Member
May 29, 2014
1,415
1,997
183
Alpha Centauri Bc
0.10.15.13: "darkcoind masternode list" does not return any masternodes...

0.10.14.1 shows 867

Edit: nevermind, it just need unusually long to get the list. It now shows 67 Masternodes
 
Last edited by a moderator:

emmo

New Member
May 23, 2014
37
11
8
Any update on the official website. Update procedure(something different from - copy the new .exe file and run it) from the old wallet 0.10.14.1 for windows (normal user) and linux MN operator to 10.15 ,please . . .Thx