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

[GhostPlayer]

I'm updating to V12 and started dashd on my VPS and then after a short while I got the message "You need to rebuild the database using -reindex to change -txindex. Do you want to rebuild the block database now?" I entered "yes" and now it's just printing a bunch of y's. Is this normal? I also tried to do ./dashd getinfo but it said something about RPC calls or something not being supported anymore and to use dash-cli? How do I do ./dashd getinfo now? Sorry for the newb questions  

Edit: I'm using the 64 bit version if it matters.

 No problem. We advance so fast, documentation gets behind... There are no noob questions around here! All questions are legit.

 ./dashd is only to start the daemon. You can use -reindex here.

 For everything else use

 ./dash-cli getinfo, masternode start, getmininginfo, getblockhash etc etc.

 you can also do;

 ./dash-cli help

 For a full list of calls.

[1714539663]

1714539663

[coins101]

Talking about head scratching.....trolls are slow today.

[GhostPlayer]

Talking about head scratching.....trolls are slow today.

 They must be busy updating their MN's 

[Jestah]

^^^^^^^Too funny^^^^^^^^^^^^^



I'm due soon for a payment, I might hold off updating....unless someone knows that it won't disrupt payment.

[bluebit25]

Awesome!!!! Nice update!!!

[bluebit25]

My wallet says "Synchronizing masternodes..." a really looooooooong time. What do I do?

I'm connected to masternodes that are not even on V12

[tungfa]

My wallet says "Synchronizing masternodes..." a really looooooooong time. What do I do?

I'm connected to masternodes that are not even on V12

In case stuck on masternodes list:
https://github.com/dashpay/dash/issues/527

[LucD88]

Urgent message to DASH miners:
Spread out the hash more evenly, move away from coinmine.pl ASAP!

Pool statistics: https://chainz.cryptoid.info/dash/#!extraction

In all our excitement, let's not forget about evenly spreading the hashrate. We're at ~48% now which still isn't far enough from the danger zone, slowly we're getting there!

[kadrek]

I'm updating to V12 and started dashd on my VPS and then after a short while I got the message "You need to rebuild the database using -reindex to change -txindex. Do you want to rebuild the block database now?" I entered "yes" and now it's just printing a bunch of y's. Is this normal? I also tried to do ./dashd getinfo but it said something about RPC calls or something not being supported anymore and to use dash-cli? How do I do ./dashd getinfo now? Sorry for the newb questions  

Edit: I'm using the 64 bit version if it matters.

 No problem. We advance so fast, documentation gets behind... There are no noob questions around here! All questions are legit.

 ./dashd is only to start the daemon. You can use -reindex here.

 For everything else use

 ./dash-cli getinfo, masternode start, getmininginfo, getblockhash etc etc.

 you can also do;

 ./dash-cli help

 For a full list of calls.

Okay, so I was able to stop the y's with ctrl-c (thanks Mangled). I restarted the vps and then did ./dashd --reindex and it said the usual "Dash server starting." When I try any dash-cli commands, such as ./dash-cli getinfo, I get the message "-bash: ./dash-cli: No such file or directory." Is this because the dashd is in a wrong folder or something?

[LucD88]

Okay, so I was able to stop the y's with ctrl-c (thanks Mangled). I restarted the vps and then did ./dashd --reindex and it said the usual "Dash server starting." When I try any dash-cli commands, such as ./dash-cli getinfo, I get the message "-bash: ./dash-cli: No such file or directory." Is this because the dashd is in a wrong folder or something?

No, because the "dash-cli" file is not in the root directory of your VPS.

You probably forgot to move the selected file ("dash-cli") to the same directory as the "dashd" file on your VPS:


And don't forget chmod +x ./dash-cli ofcourse.

[qwizzie]

My wallet says "Synchronizing masternodes..." a really looooooooong time. What do I do?

I'm connected to masternodes that are not even on V12

that is normal i think, older masternodes are still allowed to connect to V12 to get them MN payments (that is untill the august deadline expires i assume).
Synchronisation will go through a few stages :  synchronising blockchain, synchronising masternodes, synchronising masternode winners, synchronising budgets.
Just be patient and await the outcome or if it really does not move any further stop dashd, delete peers.dat & mncache.dat and retry the -reindex.

[Freckleg]

V12 awesome!!

Well done devs and all that helped!

The decentralised budgeting system will ensure Dash growth and adaptability for a long long long time. genius!

[kadrek]

Okay, so I was able to stop the y's with ctrl-c (thanks Mangled). I restarted the vps and then did ./dashd --reindex and it said the usual "Dash server starting." When I try any dash-cli commands, such as ./dash-cli getinfo, I get the message "-bash: ./dash-cli: No such file or directory." Is this because the dashd is in a wrong folder or something?

No, because the "dash-cli" file is not in the root directory of your VPS.

You probably forgot to move the selected file ("dash-cli") to the same directory as the "dashd" file on your VPS:

Oh! I didn't know I had to do that. I'll try it now. Thanks!

[bluebit25]

V12 awesome!!

Well done devs and all that helped!

The decentralised budgeting system will ensure Dash growth and adaptability for a long long long time. genius!

What is "synchronising masternode winners"? What does that mean?

[qwizzie]

Okay, so I was able to stop the y's with ctrl-c (thanks Mangled). I restarted the vps and then did ./dashd --reindex and it said the usual "Dash server starting." When I try any dash-cli commands, such as ./dash-cli getinfo, I get the message "-bash: ./dash-cli: No such file or directory." Is this because the dashd is in a wrong folder or something?

No, because the "dash-cli" file is not in the root directory of your VPS.

You probably forgot to move the selected file ("dash-cli") to the same directory as the "dashd" file on your VPS:

Oh! I didn't know I had to do that. I'll try it now. Thanks!

i think you will need to chmod +x ./dash-cli as well

[LucD88]

Oh! I didn't know I had to do that. I'll try it now. Thanks!

And don't forget chmod +x ./dash-cli ofcourse.

EDIT:
qwizzie beat me to it!

[qwizzie]

Update with protocol change & command-option reindex for windows users with help of WINSCP

Hot wallet :

./dashd stop
replace old dashd with new extracted dashd with help of WINSCP
add new extracted dash-cli to same location as dashd
chmod +x ./dashd
chmod +x ./dash-cli
rm ~/.dash/peers.dat
rm ~/.dash/mncache.dat
./dashd --reindex
./dash-cli getinfo
wait for full sync

Cold wallet :

replace old dash-qt.exe with new dash-qt.exe
delete peers.dat & mncache.dat
start wallet with commandline option -reindex
wait for full sync
issue "masternode start passphrase"

Hot wallet :

./dash-cli masternode list | grep $IP --> ./dash-cli masternode list addr | grep -e SERVER_IP -e SERVER_IP -e etc.
update :  ./masternodelist full` shows ip as well as status. --> ./dash-cli masternodelist full | grep -e SERVER_IP -e SERVER_IP -e etc.

It could take a few hours on dashninja.pl to catch up but if masternode list addr | grep -e SERVER_IP shows "ENABLED" your good to go.

[TanteStefana2]

Thx,-reindex on both side or only local wallet(del mncache and peers) ?

Gotta reindex every wallet else dash just stop

I like to delete everything except the conf files and wallet.dat (and backups JIC) then start.  Gives ya a fresh begining

I just updated as well, still waiting for syncing to finish

[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
 

[LucD88]

...

Hot wallet :

./dash-cli masternode list | grep $IP

...

The correct command for v12 is ./dash-cli masternode list addr | grep -e SERVER_IP -e SERVER_IP -e etc.