[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[ErrorId]

Dunno it's prolly just me but the point around which the D rotates is somehow misplaced.. it looks a bit... restless? Otherwise it's luscious.

I think the spoiler is causing that effect. That's right I said it we have a god damn spoiler cause once InstantX comes out we'll need it.  

err movement....

Step away from the charts Artoo... just leave them alone. 

[Jengo]

Dunno it's prolly just me but the point around which the D rotates is somehow misplaced.. it looks a bit... restless? Otherwise it's luscious.

Thanks for the feedback
I will edit it a bit.. it's not that hard to change

[Rux]

oblox, otoh ... dont move the price up PLEASE

wait for 2 days lol

[g4q34g4qg47ww]

https://darkcointalk.org/threads/v0-11-1-instantx-release-development-update.3769/#post-38773

Now that the network has updated to version 11 and is stable, I thought it might be a good idea to lay out what the next we have in store for the next release and future plans. We’ll be leveraging our larger development team and working on a few projects at once to enable to a few new exciting features at once.

Enforcement
Network fragmentation has been corrected on the network and we’ve enabled enforcement. Those not paying the correct node after today will simply be rejected by the network.

InstantX
A couple months ago I open sourced the design so that I could work with researchers on perfecting it. However, it’s not presently done and the code is a simple prototype of what I intended. I would recommend other crypto-currencies from not using it until we’ve had a chance to thoroughly test and refine the logic, otherwise grave damage could be done to your network.
We’ll begin finishing development on instantX immediately and work on the stability of the system. This will be done over the next few weeks on testnet and will be a completely open public testing phase.

Masternode Changes / Improvements
As an upgrade to the masternode system, we’re going to be moving to a token-based system, where you’ll only be required to gain access to your cold wallet every few months. When starting a masternode, one will simply execute the “masternode generate-token” command, which will sign the key and generate a tokenized string to put into the masternode.conf. Using this signature masternodes can be restarted multiple times, even with protocol version updates.

The pinging system (dseep) is going to be replaced with a “challege request” system, which will be done in a completely decentralized way. Other masternodes on the network will be elected each block to check on their peers by initiating a “challenge request”, if a masternode fails multiple of these in a row by failing to respond it will be removed from the list.

As be move forward into the future, static IPv4 IPs will continue to get more scarce. In the next release we will begin to allow non-static IPs to be used as long as the client is reachable and can answer challenge requests.

Beyond version 11.1 (will not be in the InstantX release)

Masternode Blinding
Recently a paper by 3 researches at Saarland University came out describing a new technique, while there are some serious problems with the approach they take, the concept of blinding the users they use is novel. In CoinShuffle, each output is sent to the next peer in a circle, one at a time. The new peer adds an output, shuffles and then sends the list again. We can do this and actually improve upon it.

To implement blinding, each user would connect to one completely random masternode and say "Send masternode X this output/value for mix N" and pass a single output. That output would be passed to the leading masternode. It would take access to all masternodes used to know who did what, which is as solid as M rounds mathematically (M = number of outputs). This is great because all users can submit all inputs at once. So it's super fast compared to CoinShuffle and even more secure.

Decentralization of the masternode payment system
Currently, there is a node that signs a message for each block and says which masternode should be paid for that specific block. As many of our users know, the centralized reference node was a temporary solution to the problem of enforcing masternode payments. Miners use this when creating the block to ensure they comply, if a miner tries to cheat the system, the block will be rejected by the network. This is a great solution temporarily, but isn’t decentralized enough.

To explain the new completely decentralized strategy, first we have to explain exactly how masternodes work. When a masternode starts, it relays a message called the “masternode election entry”. This puts the masternode into a list on all clients on the network and allows them to be used by all of the clients on the network. Every few minutes, these masternodes ping the network saying they’re still alive and allowing them to earn interest payments.

To decentralize this system, we propose a new system we’ll call “Masternode mining”. This simply means that when miners receive a new “masternode election entry” and solve a block, they will append the masternode to the block. Each block can contain up to 10 masternode list changes. So by following the normal progression of the blockchain, you will be able to compile a list of all known masternodes. This system is also highly resistant to attack and the same list can be compiled by any client on the network.

For example:
Block 1: Add mn1, mn2, mn3
Block 2: Add mn4, mn5
Block 3: Remove mn2  //mn2 fell off the network
-- currently the masternode list contains mn1, mn3, mn4, mn5
Block 4: Add mn6, mn7
Block 5: Add mn2  //mn2 came back

-- example attack: --
Block 6: Remove mn1, mn2, mn3, mn4, mn5, mn6  //miner owns masternode 7, wants control of the network
Block 7: Add mn1, mn2, mn3, mn4, mn5, mn6

In this case a majority of mining power is required to control the masternode list. If a miner has enough computing power to alter the masternode list, they will also have enough power to double spend with a 51% attack. Therefore this is the safest solution to decentralizing the payment.

[crowning]

What traffic does one node generate a month?

Right now about 500 MB per day.

[coins101]

https://darkcointalk.org/threads/v0-11-1-instantx-release-development-update.3769/#post-38773

Now that the network has updated to version 11 and is stable, I thought it might be a good idea to lay out what the next we have in store for the next release and future plans. We’ll be leveraging our larger development team and working on a few projects at once to enable to a few new exciting features at once.

Enforcement
Network fragmentation has been corrected on the network and we’ve enabled enforcement. Those not paying the correct node after today will simply be rejected by the network.

InstantX
A couple months ago I open sourced the design so that I could work with researchers on perfecting it. However, it’s not presently done and the code is a simple prototype of what I intended. I would recommend other crypto-currencies from not using it until we’ve had a chance to thoroughly test and refine the logic, otherwise grave damage could be done to your network.
We’ll begin finishing development on instantX immediately and work on the stability of the system. This will be done over the next few weeks on testnet and will be a completely open public testing phase.

Masternode Changes / Improvements
As an upgrade to the masternode system, we’re going to be moving to a token-based system, where you’ll only be required to gain access to your cold wallet every few months. When starting a masternode, one will simply execute the “masternode generate-token” command, which will sign the key and generate a tokenized string to put into the masternode.conf. Using this signature masternodes can be restarted multiple times, even with protocol version updates.

The pinging system (dseep) is going to be replaced with a “challege request” system, which will be done in a completely decentralized way. Other masternodes on the network will be elected each block to check on their peers by initiating a “challenge request”, if a masternode fails multiple of these in a row by failing to respond it will be removed from the list.

As be move forward into the future, static IPv4 IPs will continue to get more scarce. In the next release we will begin to allow non-static IPs to be used as long as the client is reachable and can answer challenge requests.

Beyond version 11.1 (will not be in the InstantX release)

Masternode Blinding
Recently a paper by 3 researches at Saarland University came out describing a new technique, while there are some serious problems with the approach they take, the concept of blinding the users they use is novel. In CoinShuffle, each output is sent to the next peer in a circle, one at a time. The new peer adds an output, shuffles and then sends the list again. We can do this and actually improve upon it.

To implement blinding, each user would connect to one completely random masternode and say "Send masternode X this output/value for mix N" and pass a single output. That output would be passed to the leading masternode. It would take access to all masternodes used to know who did what, which is as solid as M rounds mathematically (M = number of outputs). This is great because all users can submit all inputs at once. So it's super fast compared to CoinShuffle and even more secure.

Decentralization of the masternode payment system
Currently, there is a node that signs a message for each block and says which masternode should be paid for that specific block. As many of our users know, the centralized reference node was a temporary solution to the problem of enforcing masternode payments. Miners use this when creating the block to ensure they comply, if a miner tries to cheat the system, the block will be rejected by the network. This is a great solution temporarily, but isn’t decentralized enough.

To explain the new completely decentralized strategy, first we have to explain exactly how masternodes work. When a masternode starts, it relays a message called the “masternode election entry”. This puts the masternode into a list on all clients on the network and allows them to be used by all of the clients on the network. Every few minutes, these masternodes ping the network saying they’re still alive and allowing them to earn interest payments.

To decentralize this system, we propose a new system we’ll call “Masternode mining”. This simply means that when miners receive a new “masternode election entry” and solve a block, they will append the masternode to the block. Each block can contain up to 10 masternode list changes. So by following the normal progression of the blockchain, you will be able to compile a list of all known masternodes. This system is also highly resistant to attack and the same list can be compiled by any client on the network.

For example:
Block 1: Add mn1, mn2, mn3
Block 2: Add mn4, mn5
Block 3: Remove mn2  //mn2 fell off the network
-- currently the masternode list contains mn1, mn3, mn4, mn5
Block 4: Add mn6, mn7
Block 5: Add mn2  //mn2 came back

-- example attack: --
Block 6: Remove mn1, mn2, mn3, mn4, mn5, mn6  //miner owns masternode 7, wants control of the network
Block 7: Add mn1, mn2, mn3, mn4, mn5, mn6

In this case a majority of mining power is required to control the masternode list. If a miner has enough computing power to alter the masternode list, they will also have enough power to double spend with a 51% attack. Therefore this is the safest solution to decentralizing the payment.

Wow. Just wow.

[toknormal]

Major Paycoin dump in progress....the action's here https://bitcoinwisdom.com/markets/cryptsy/xpybtc

Already vacated 1 marketcap ranking in the last hour (to Bitshares). The price hasn't moved much but there are high volume exits every half hour or so.

Seething tempers and bubbling retribution characterise discussion threads. The toxic environment is erroding the valuation despite the $20 per coin pot of gold buyback promise holding everything up.

May leave space for DRK eventually if things continue as they are.

[TanteStefana2]

Thanks for being cool about answering questions and whatnot Otoh.

P.S. , looks like our block reward has been decreased by 7%!

YVW! As promised, I've topped the Crsptsy wall back up to > 100 BTC now



So if anyone feels like unloading a few, please to feel free

It seems your title of "Legendary" is well deserved, LOL   I'm in AWE of you!

[Lebubar]

drk.mn indicate that we must be in 11.0.14... Bug from the site ? Or the annoucment didn't arrive here?

"Masternode operators MUST be running 0.11.0.14 or greater!"

[oblox]

drk.mn indicate that we must be in 11.0.14... Bug from the site ? Or the annoucment didn't arrive here?

Not that you must but there is some commits and a tag for v14.

[Lebubar]

drk.mn indicate that we must be in 11.0.14... Bug from the site ? Or the annoucment didn't arrive here?

Not that you must but there is some commits and a tag for v14.

I always wait the green light from the boss...

Edit : Anyway, little bug on the site, on my pc it say 0.11.0.13 on my tablet it say 0.11.0.14 :p

[toknormal]

Paycoin selloff continuing. It's now into the 0.007's.

Always happens at 2.00 AM European time. Let's see, that's around 8 in the evening East Coast U.S. and 5 West coast.

Must be people coming home from work and getting a shock. It needs to get to about 0.003 to be within target range of DRK.

Paycoin 4-hour MACD nicely poised for a sustained descent...



Meanwhile the 5-minute momentum is bent over backwards to accommodate the selling pressure...



UPDATE: While I've been watching these markets I've also been updating my 2 masternodes to 11.0.13.

[RenegadeMan]

Paycoin selloff continuing. It's now into the 0.007's.

Always happens at 2.00 AM European time. Let's see, that's around 8 in the evening East Coast U.S. and 5 West coast.

Must be people coming home from work and getting a shock. It needs to get to about 0.003 to be within target range of DRK.

Paycoin 4-hour MACD nicely poised for a sustained descent...



Meanwhile the 5-minute momentum is bent over backwards to accommodate the selling pressure...



UPDATE: While I've been watching these markets I've also been updating my 2 masternodes to 11.0.13.

I've been keeping abreast of this Tok. It's absolutely fascinating to see how the $20 buyback program is being discussed on Hashtalk.org. There's still an overall consensus on there that Josh Garza is going to come through with the $20 per paycoin via the honor program which starts on 1st Feb. But then there are posts like this where people are starting to push for prioritisation as to who gets paid first.

@gawceo @GAW-Staff @GAW_Darren @GAW_CENO @GAW_Amber @GAW_Brian @GAW_CE0
For the love of God, please tell me that you will be taking care of your actual customers first. The people who "mined" hashpoints for months deserve to be first in line no matter what. The people who picked up cheap coins on the exchanges and never were your customers deserve to be last. Please clarify this ASAP

I can see this turning into quite a mess if many original and early supporters feel they're not getting priority over regular traders. Trying to administer such a thing is diabolical as another poster pointed out they mined a lot of coins early but then did some trading and they shouldn't be de-prioritised for that. Josh has stated in the Q&A that all coins are valid, even if bought off an exchange. But you'll have many people from the paycoin community upset and some getting quite demanding

@GAWCEO why have you not responded to such a genuine, honest, and down to earth post?

As at time of my post here, there's been no response and that was about 24 hours ago now.

Lots of drama yet to play out I would suspect.

It makes me grateful we haven't had these sorts of outlandish and unwise financial incentive "programs" in Darkcoin as they're extremely troublesome and way more complex to execute than the initial idea would suggest.

[1echo]

cant with for DRK on btc-e

[eduffield]

v0.11.0.14 - This update is not required

https://darkcointalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-34#post-38830

[RenegadeMan]

cant with for DRK on btc-e

Did you mean "can't wait for DRK to be on BTC-e"?

You'll probably be waiting for a long time. They're pretty much a closed shop that's intensely LTC centric. As at a couple of months ago they hadn't added a new coin type for over a year. Not sure if that's still the case but people here in the DRK community have tried contacting them without much success.

[tungfa]

v0.11.0.14 - This update is not required

https://darkcointalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-34#post-38830

11.0.14 Core - All Users

https://darkcointalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-34#post-38830

- Improved syncing speed (eduffield)
- Improved pre-mixing to create denominated amounts (UdjinM6)
- Update darkcoin-qt.desktop (vertoe)
- fix overpaying for DSTX - If you're using Darksend, please update (eduffield)
- make collateral inputs from all available inputs but not from mn-like (UdjinM6)
- 4 rounds default for DS, litemode changes for mining
- Catch UTXO set read errors and shutdown (UdjinM6)
- dseg limitations (eduffield)
- more fixes/cleanup/debug output to DS mixing (UdjinM6)
- Moved the note about masternode private keys. (Perry Woodin)
- Made the distinction between masternode private key and wallet private key more clear. (Perry Woodin)

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

[italeffect]

...
11.0.14 Core - All Users
https://darkcointalk.org/threads/v0-11-0-darkcoin-core-release.3601/page-34#post-38830
...
Mac OSX: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.11.0.14-osx.dmg
...

400: Invalid request

For the link to the mac wallet. I assume this means it's just not uploaded yet?

[oblox]

http://www.zdnet.com/article/critical-linux-security-hole-found/

[RenegadeMan]

http://www.zdnet.com/article/critical-linux-security-hole-found/

Thanks for posting.

Article says:

Ubuntu has patched the bug both for 12.04 and the older 10.04

Does this mean if you're on Ubuntu 14.04 the issue's already been rectified so there's no action needed?