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

[qwizzie]

for those looking to personalise their wallet : go to your dash.conf and add in there

windowtitle=whatever_you_feel_like_yr_wallet_should_be_titled

Specially when one has multiple wallets its a good way to differentiate between them.

credits : crowning

"DARKCOIN" for some old-school guys  

or Xcoin for an even older generation  

[1714552142]

1714552142

[1714552142]

1714552142

[1714552142]

1714552142

[Rux]

We're definitely open to improving the pool distribution if anyone has ideas. However, PoS is incompatible with anything that uses masternode quorums. The quorums are chosen based off of the proof-of-work hash, so if we were to switch to a proof-of-stake model, we would end up with less secure hashes and other issues that would have to be addressed. That would allow an attacker to pick the masternodes that approve a transaction lock for example, something that we definitely want to avoid.

I might have an idea, but maybe it is too hard to implement.

I believe as we all want to have as much spread of the hashing on one side and pool owners to have much profit from their miners on another side is really hard to meet.

My idea is to use power of MNs in a way that every block which is mined on a pool with the higher/highest share of total hashrate should earn less DASHes then normal 50% of the block. If it can be implemented dynamical sharing the earnings of a block pool/MN we could dynamically solve spreading of hashes as miner will leave top hashrate pools by himself.

So I am see it as like the more blocks you are finding in time the less profit you are getting from it... at the end of the day whole hash spreading should meet the equilibrium of spreading near to p2p pools.

Also pools could compete again in % of fees as they used to...

Maybe it is not possible to implement easily but I think it is a good idea for dynamically change block rewards for miners and MNs.

I really think that this idea has potential, would like to hear from devs if they see it in a same way?
Dynamically block reward is already achieved = difficulty of the network, so we could adjust it more per block with dynamically sharing block reward miner/MN as it is already on protocol level.

pseudo math just to maybe represent better idea:

DBR = dynamically block reward for miner in DASHs
BR = block reward in DASHs = 5 DASH
NSBR = network percentage of block reward for miner in percentage = 50%
BPT = blocks found per time (defined time frame, lets say 1hr) for a miner ,
      lets agree maxBPT to be 10 just to prove theory, if miner founds more then 10 blocks per time we will still use 10 in equation

DBR = BR * (1- log(BPT)) * NSBR/100

And for MNs reward is = BR - DBR

something like this
 

Well does this sounds interesting ... maybe we are on way to fix that 51% blockchain attack

Good one rentahash, you could be in dev team for ideas

EDIT: congratz on V12 guys, 2 masternodes updated 1 min ago!

when im syncing wallet i get this stuck more than 15min



EDIT2:
finaly INSTANTX working like a bullet!!!!!!!! also now sendtomanyix command will rock DASH world, thank you thank you thank you!!!!

[eduffield]

We're definitely open to improving the pool distribution if anyone has ideas. However, PoS is incompatible with anything that uses masternode quorums. The quorums are chosen based off of the proof-of-work hash, so if we were to switch to a proof-of-stake model, we would end up with less secure hashes and other issues that would have to be addressed. That would allow an attacker to pick the masternodes that approve a transaction lock for example, something that we definitely want to avoid.

I might have an idea, but maybe it is too hard to implement.

I believe as we all want to have as much spread of the hashing on one side and pool owners to have much profit from their miners on another side is really hard to meet.

My idea is to use power of MNs in a way that every block which is mined on a pool with the higher/highest share of total hashrate should earn less DASHes then normal 50% of the block. If it can be implemented dynamical sharing the earnings of a block pool/MN we could dynamically solve spreading of hashes as miner will leave top hashrate pools by himself.

So I am see it as like the more blocks you are finding in time the less profit you are getting from it... at the end of the day whole hash spreading should meet the equilibrium of spreading near to p2p pools.

Also pools could compete again in % of fees as they used to...

Maybe it is not possible to implement easily but I think it is a good idea for dynamically change block rewards for miners and MNs.

I really think that this idea has potential, would like to hear from devs if they see it in a same way?
Dynamically block reward is already achieved = difficulty of the network, so we could adjust it more per block with dynamically sharing block reward miner/MN as it is already on protocol level.

pseudo math just to maybe represent better idea:

DBR = dynamically block reward for miner in DASHs
BR = block reward in DASHs = 5 DASH
NSBR = network percentage of block reward for miner in percentage = 50%
BPT = blocks found per time (defined time frame, lets say 1hr) for a miner ,
      lets agree maxBPT to be 10 just to prove theory, if miner founds more then 10 blocks per time we will still use 10 in equation

DBR = BR * (1- log(BPT)) * NSBR/100

And for MNs reward is = BR - DBR

something like this
 

Well does this sounds interesting ... maybe we are on way to fix that 51% blockchain attack

Good one rentahash, you could be in dev team for ideas

EDIT: congratz on V12 guys, 2 masternodes updated 1 min ago!

when im syncing wallet i get this stuck more than 15min

That's OK. It will start successfully syncing when more of the network gets updated.

[oaxaca]

Updated here. Update was a pain simply because the folder structure changed with the breaking out the new versions (32 and 64) into their own tars.

It would be great to have some dummy instructions for that

as i saw a bunch of social media posts about this already !
can somebody please write that up and post here ?!
tx

wget --no-check-certificate https://www.dashpay.io/binaries/dash-0.12.0.44-linux64.tar.gz
tar zxvf dash-0.12.0.44-linux64.tar.gz
./dashd stop
rm .dash/peers.dat
rm dashd dash-cli               <---(assuming you have dash-cli in the same location)
mv dash-0.12.0/bin/dash-cli .
mv dash-0.12.0/bin/dashd .
chmod +x dash-cli dashd
./dashd --reindex
./dash-cli getinfo

Adjust as needed for where your files are saved.

Don't forget this one:

rm /.dash/mncache.dat

[eduffield]

If you're running linux, please go download the newest version here (protocol version 70103):

https://www.dashpay.io/downloads/

We're fixing a couple other things, then we'll be pushing out 12.0.45 later on today.

[TanteStefana2]

If you're running linux, please go download the newest version here (protocol version 70103):

https://www.dashpay.io/downloads/

We're fixing a couple other things, then we'll be pushing out 12.0.45 later on today.

That sent me back to version 12.43 and protocol 70102, is that correct?

I downloaded this a few minutes later on my other machine, and it was 12.44, don't know how that happened?  I went to your link both times just in case.

Anyway, now I can't start my masternodes again, which probably is no big deal because I don't think they were running anyway.  No idea what the problem is, but they don't show up on dashninja.

[Lebubar]

If you're running linux, please go download the newest version here (protocol version 70103):

https://www.dashpay.io/downloads/

We're fixing a couple other things, then we'll be pushing out 12.0.45 later on today.

That sent me back to version 12.43 and protocol 70102, is that correct?

No
Should be : (

Code:

wget https://www.dashpay.io/binaries/dash-0.12.0.44-linux64.tar.gz --no-check-certificate

)

lebubar@MasterNode14:~$ ./dash-cli getinfo
{
    "version" : 120044,
    "protocolversion" : 70103,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 319804,
    "timeoffset" : 0,
    "connections" : 11,
    "proxy" : "",
    "difficulty" : 2474.52207215,
    "testnet" : false,
    "keypoololdest" : 1431542925,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}

But you can also wait the 0.45 version that will come later

[TanteStefana2]

If you're running linux, please go download the newest version here (protocol version 70103):

https://www.dashpay.io/downloads/

We're fixing a couple other things, then we'll be pushing out 12.0.45 later on today.

That sent me back to version 12.43 and protocol 70102, is that correct?

No
Should be : (

Code:

wget https://www.dashpay.io/binaries/dash-0.12.0.44-linux64.tar.gz --no-check-certificate

)

lebubar@MasterNode14:~$ ./dash-cli getinfo
{
    "version" : 120044,
    "protocolversion" : 70103,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 319804,
    "timeoffset" : 0,
    "connections" : 11,
    "proxy" : "",
    "difficulty" : 2474.52207215,
    "testnet" : false,
    "keypoololdest" : 1431542925,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00010000,
    "errors" : ""
}

But you can also wait the 0.45 version that will come later

I see it's back to version 44, Don't know how I got 43??  Anyway, yah, 44 doesn't work for me anyway, so I think I'll just wait   This is getting too frustrating

[Tyke]

Hello Dash community,


I have begun to research the first year history of Dash.  It has taken me about 4-5 hours to extract the important historical events in the first 150 pages of this thread.  A preliminary front cover has already been designed:



Books on Peercoin and Reddcoin are already available on Amazon.

If anyone would like to donate towards this project, please do: XdoMpS6wX63TVBma9EG53PG2VJnMnSPJ3d

[rentahash]

We're definitely open to improving the pool distribution if anyone has ideas. However, PoS is incompatible with anything that uses masternode quorums. The quorums are chosen based off of the proof-of-work hash, so if we were to switch to a proof-of-stake model, we would end up with less secure hashes and other issues that would have to be addressed. That would allow an attacker to pick the masternodes that approve a transaction lock for example, something that we definitely want to avoid.

I might have an idea, but maybe it is too hard to implement.

I believe as we all want to have as much spread of the hashing on one side and pool owners to have much profit from their miners on another side is really hard to meet.

My idea is to use power of MNs in a way that every block which is mined on a pool with the higher/highest share of total hashrate should earn less DASHes then normal 50% of the block. If it can be implemented dynamical sharing the earnings of a block pool/MN we could dynamically solve spreading of hashes as miner will leave top hashrate pools by himself.

So I am see it as like the more blocks you are finding in time the less profit you are getting from it... at the end of the day whole hash spreading should meet the equilibrium of spreading near to p2p pools.

Also pools could compete again in % of fees as they used to...

Maybe it is not possible to implement easily but I think it is a good idea for dynamically change block rewards for miners and MNs.

I really think that this idea has potential, would like to hear from devs if they see it in a same way?
Dynamically block reward is already achieved = difficulty of the network, so we could adjust it more per block with dynamically sharing block reward miner/MN as it is already on protocol level.

pseudo math just to maybe represent better idea:

DBR = dynamically block reward for miner in DASHs
BR = block reward in DASHs = 5 DASH
NSBR = network percentage of block reward for miner in percentage = 50%
BPT = blocks found per time (defined time frame, lets say 1hr) for a miner ,
      lets agree maxBPT to be 10 just to prove theory, if miner founds more then 10 blocks per time we will still use 10 in equation

DBR = BR * (1- log(BPT)) * NSBR/100

And for MNs reward is = BR - DBR

something like this
 

Well does this sounds interesting ... maybe we are on way to fix that 51% blockchain attack

Good one rentahash, you could be in dev team for ideas

EDIT: congratz on V12 guys, 2 masternodes updated 1 min ago!

when im syncing wallet i get this stuck more than 15min

EDIT2:
finaly INSTANTX working like a bullet!!!!!!!! also now sendtomanyix command will rock DASH world, thank you thank you thank you!!!!

Thnx Rux but maybe we are too subjective

Would really appreciate if anybody from dev team comment idea from their perspective !

Great work devs and congrat on V12! sendtomanyix will be the key command in the future!

[piebeyb]

Hello Dash community,


I have begun to research the first year history of Dash.  It has taken me about 4-5 hours to extract the important historical events in the first 150 pages of this thread.  A preliminary front cover has already been designed:



Books on Peercoin and Reddcoin are already available on Amazon.

If anyone would like to donate towards this project, please do: XdoMpS6wX63TVBma9EG53PG2VJnMnSPJ3d

it seems interesting but still want to see the current DASH trade

[Tyke]

Hello Dash community,


I have begun to research the first year history of Dash.  It has taken me about 4-5 hours to extract the important historical events in the first 150 pages of this thread.  A preliminary front cover has already been designed:



Books on Peercoin and Reddcoin are already available on Amazon.

If anyone would like to donate towards this project, please do: XdoMpS6wX63TVBma9EG53PG2VJnMnSPJ3d

it seems interesting but still want to see the current DASH trade

Please say what you mean by "current DASH trade"?

[bluebit25]

Wallets that mine, hmm that sounds interesting TanteStefana2. Maybe there could be an option to turn on mining inside the wallet. An On/Off button. The algorithm uses your computer's power to mine.

This would mean that everyone that downloads the "wallet" could be a miner, which would lead to more decentralization. Maybe you could even select a mining pool inside the wallet or a random pool.

Maybe you could even limit the size of the pool. It would be cool if there were "DASH POOLS". They have a limit in the number of participants. Each Dash pool get's rewarded a certain number of Dash. The more people in the pool the less Dash you earn, so it incentizes you to start a new pool or to join pools with a low number of Dash wallet miners.

[bigrcanada]

Sorry for a noob question....how long do we have before we HAVE to update our MN's?  I'm waiting for Splwaik to return from vaction.  Do we have a few days?  Thanks.

[Lebubar]

Sorry for a noob question....how long do we have before we HAVE to update our MN's?  I'm waiting for Splwaik to return from vaction.  Do we have a few days?  Thanks.

I saw the date of 5th of September somewhere..

[oblox]

Wallets that mine, hmm that sounds interesting TanteStefana2. Maybe there could be an option to turn on mining inside the wallet. An On/Off button. The algorithm uses your computer's power to mine.

This would mean that everyone that downloads the "wallet" could be a miner, which would lead to more decentralization. Maybe you could even select a mining pool inside the wallet or a random pool.

Maybe you could even limit the size of the pool. It would be cool if there were "DASH POOLS". They have a limit in the number of participants. Each Dash pool get's rewarded a certain number of Dash. The more people in the pool the less Dash you earn, so it incentizes you to start a new pool or to join pools with a low number of Dash wallet miners.

This has been proposed before and is really no different than setting setgenerate to however many cores you want to use. You wouldn't use pools but rather solo mine. Taking this aspect and giving the option to specify pools only leads to a centralized aspect.

[AdamWhite]

If you're running linux, please go download the newest version here (protocol version 70103):

https://www.dashpay.io/downloads/

We're fixing a couple other things, then we'll be pushing out 12.0.45 later on today.

Surely this is when you'll unveil the masternode blinding that you announced would be included in this update, right?

[eduffield]

Sorry for a noob question....how long do we have before we HAVE to update our MN's?  I'm waiting for Splwaik to return from vaction.  Do we have a few days?  Thanks.

I saw the date of 5th of September somewhere..

September 5th is when the networks will split. However, masternodes must be updated when enforcement goes into effect, which is 3-4 days out probably.

[Solarminer]

Since the developers are a little modest, I will add some of the cool features they forgot to show off in the release notes. 

• Masternode inputs are locked automatically.
• GUI Wallet repair tools.
• Specific Spork, Masternode, etc update bars to ensure instanTX and darksend capability.
• Selectable interface themes and customizable wallet title.
• Masternode.conf is created automatically (if existing, the donation columns are ignored).

[rentahash]

Wallets that mine, hmm that sounds interesting TanteStefana2. Maybe there could be an option to turn on mining inside the wallet. An On/Off button. The algorithm uses your computer's power to mine.

This would mean that everyone that downloads the "wallet" could be a miner, which would lead to more decentralization. Maybe you could even select a mining pool inside the wallet or a random pool.

Maybe you could even limit the size of the pool. It would be cool if there were "DASH POOLS". They have a limit in the number of participants. Each Dash pool get's rewarded a certain number of Dash. The more people in the pool the less Dash you earn, so it incentizes you to start a new pool or to join pools with a low number of Dash wallet miners.

problem with this idea is that CPU is not enough powerful to balance GPU miners...