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

[110110101]

MooCowMoo's very handy toolset for masternode operators, Dashman:

https://github.com/moocowmoo/dashman

makes updating a walk in the park, a must have for the casual Masternode operator! 

[1714063974]

1714063974

[1714063974]

1714063974

[1714063974]

1714063974

[1714063974]

1714063974

[1714063974]

1714063974

[1714063974]

1714063974

[qwizzie]

I hope we are not introducing a fork possibility in the future with running
two versions on the same protocol, specifically regarding masternodes.

I remember we had some problems in the past when the masternode network
got largely divided over two different versions on the same protocol and at
some point accidentally forked ?
   

[Lukas_Jackson]

I hope we are not introducing a fork possibility in the future with running
two versions on the same protocol, specifically regarding masternodes.

I remember we had some problems in the past when the masternode network
got largely divided over two different versions on the same protocol and at
some point accidentally forked ?

I don't think they would push it just like that. There wasn't any major changes.
https://github.com/dashpay/dash/releases/tag/v0.12.1.1
It's mostly for QT users.

[mexicantarget]

How many coins do you generate per day with a MN?

[Lukas_Jackson]

How many coins do you generate per day with a MN?

http://178.254.23.111/~pub/Dash/Dash_Info.html

[UdjinM6]

I hope we are not introducing a fork possibility in the future with running
two versions on the same protocol, specifically regarding masternodes.

I remember we had some problems in the past when the masternode network
got largely divided over two different versions on the same protocol and at
some point accidentally forked ?

I don't think they would push it just like that. There wasn't any major changes.
https://github.com/dashpay/dash/releases/tag/v0.12.1.1
It's mostly for QT users.

Yes, 12.1.1 should be fully compatible with 12.1.0 and no, sync issues were not Qt-only, it's a common issue in 12.1.0 which wasn't discovered in testnet due to relatively small number of masternodes there (~100). 12.1.1 also manages so called service connections in a better way (the reason we missed this one is basically the same).
With that being said, update is recommended for everyone

[AzzAz]

I hope we are not introducing a fork possibility in the future with running
two versions on the same protocol, specifically regarding masternodes.

I remember we had some problems in the past when the masternode network
got largely divided over two different versions on the same protocol and at
some point accidentally forked ?

I don't think they would push it just like that. There wasn't any major changes.
https://github.com/dashpay/dash/releases/tag/v0.12.1.1
It's mostly for QT users.

Yes, 12.1.1 should be fully compatible with 12.1.0 and no, sync issues were not Qt-only, it's a common issue in 12.1.0 which wasn't discovered in testnet due to relatively small number of masternodes there (~100). 12.1.1 also manages so called service connections in a better way (the reason we missed this one is basically the same).
With that being said, update is recommended for everyone

12.1.1. wallet: excellent! Fast. Perfect!

[qwizzie]

I hope we are not introducing a fork possibility in the future with running
two versions on the same protocol, specifically regarding masternodes.

I remember we had some problems in the past when the masternode network
got largely divided over two different versions on the same protocol and at
some point accidentally forked ?

I don't think they would push it just like that. There wasn't any major changes.
https://github.com/dashpay/dash/releases/tag/v0.12.1.1
It's mostly for QT users.

Yes, 12.1.1 should be fully compatible with 12.1.0 and no, sync issues were not Qt-only, it's a common issue in 12.1.0 which wasn't discovered in testnet due to relatively small number of masternodes there (~100). 12.1.1 also manages so called service connections in a better way (the reason we missed this one is basically the same).
With that being said, update is recommended for everyone

Thank you for the fast feedback.

[toknormal]

MooCowMoo's very handy toolset for masternode operators, Dashman:

https://github.com/moocowmoo/dashman

makes updating a walk in the park, a must have for the casual Masternode operator! 

I just tried this. It's absolutely awesome (+ zero learning curve).

[gadado]

12.1.1 is out
Highly Recommended - some Bugs fixed
(12.1.0 will still be paid)

+ no start-<mode> required, just replace the daemon (if running mn)

Release Notes
https://github.com/dashpay/dash/releases/tag/v0.12.1.1

please update

https://www.dash.org/wallets/

Can anyone tell me what is wrong with my MasterNode Dash-Wallet when
 start-missing

simple does not work?
No matter what I tried a week ago it always said 0 of 0 successfull started and the masternode status said not started.

I use the dash client zip file for windows (not the installer) copied all the content in one single costum named folder and I worked with the client.config start method before. ( For some reason they blocked that start method now. :/)

While some got double and tripple the usual pay outs I lost over a week payout by starting them with
start-alias

Not complaining I am glad I could start it at the end but I just want to know the issue for the next time so I can fix that. If the Dash value rises a payment drop out can become a significant lose in the future.

[UdjinM6]

12.1.1 is out
Highly Recommended - some Bugs fixed
(12.1.0 will still be paid)

+ no start-<mode> required, just replace the daemon (if running mn)

Release Notes
https://github.com/dashpay/dash/releases/tag/v0.12.1.1

please update

https://www.dash.org/wallets/

Can anyone tell me what is wrong with my MasterNode Dash-Wallet when
 start-missing

simple does not work?
No matter what I tried a week ago it always said 0 of 0 successfull started and the masternode status said not started.

I use the dash client zip file for windows (not the installer) copied all the content in one single costum named folder and I worked with the client.config start method before. ( For some reason they blocked that start method now. :/)

While some got double and tripple the usual pay outs I lost over a week payout by starting them with
start-alias

Not complaining I am glad I could start it at the end but I just want to know the issue for the next time so I can fix that. If the Dash value rises a payment drop out can become a significant lose in the future.

start-missing is a helper command which you should use when your MNs are not in the list at all e.g. you have 10 MNs and you just started remote nodes for few more MNs but haven't issued start yet - new MNs will be in "missing" state and you can easily start them all using start-missing without affecting MNs in "enabled" state.

If your MNs are already in the list start-missing is NOT going to work for you. If some of your MNs are not in "enabled" state you can use start-disabled to start them all without affecting MNs in "enabled" state.

Make sure to fully sync and verify that wallet recognizes active MNs as "enabled", or otherwise they are going to be restarted too.

[iCEBREAKER]

Can anyone tell me what is wrong with my MasterNode Dash-Wallet when
 start-missing

simple does not work?
No matter what I tried a week ago it always said 0 of 0 successfull started and the masternode status said not started.

I use the dash client zip file for windows (not the installer) copied all the content in one single costum named folder and I worked with the client.config start method before. ( For some reason they blocked that start method now. :/)

While some got double and tripple the usual pay outs I lost over a week payout by starting them with
start-alias

Not complaining I am glad I could start it at the end but I just want to know the issue for the next time so I can fix that. If the Dash value rises a payment drop out can become a significant lose in the future.

Are you using IPv6?  I know it seems absurd, but Dash version 12.1 broke the IPv6 functionality it inherited from Bitcoin.

IPv6 is a thing of the past. 

According to the Dash forum, Dash's future is now married to the fate of IPv4.

[qwizzie]

I hope we are not introducing a fork possibility in the future with running
two versions on the same protocol, specifically regarding masternodes.

I remember we had some problems in the past when the masternode network
got largely divided over two different versions on the same protocol and at
some point accidentally forked ?

I don't think they would push it just like that. There wasn't any major changes.
https://github.com/dashpay/dash/releases/tag/v0.12.1.1
It's mostly for QT users.

Yes, 12.1.1 should be fully compatible with 12.1.0 and no, sync issues were not Qt-only, it's a common issue in 12.1.0 which wasn't discovered in testnet due to relatively small number of masternodes there (~100). 12.1.1 also manages so called service connections in a better way (the reason we missed this one is basically the same).
With that being said, update is recommended for everyone

12.1.1. wallet: excellent! Fast. Perfect!

Very fast syncing with this new update, it just breezes through the governance objects now. I was amazed at how fast it reached full sync on the remote server.
Nice job.

[TaoOfSaatoshi]

CATV | User Experience: Why Erik Voorhees May Want To "ShapeShift" To Dash



https://youtu.be/V9Ikh4Q5mk4

#DashNation #CashAlternative

[iCEBREAKER]

CATV | User Experience: Why Erik Voorhees May Want To "ShapeShift" To Dash



https://youtu.be/V9Ikh4Q5mk4

#DashNation #CashAlternative

You already posted this here:

CATV | User Experience: Why Erik Voorhees May Want To "ShapeShift" To Dash



https://youtu.be/V9Ikh4Q5mk4

#DashNation #CashAlternative

Please stop making duplicate posts.

Also, the #DashSpam advertisements belong in your signature (where we may ignore them), not in the main body.

[ddink7]

Hey icebreaker...how's it going =)

Did you ever get around to de-anonymizing that PrivateSend transaction from last year?

[megges]

Hey icebreaker...how's it going =)

Did you ever get around to de-anonymizing that PrivateSend transaction from last year?

don't you know, dashs marketcap is still to small to make that "profitable"

[iCEBREAKER]

Hey icebreaker...how's it going =)

Did you ever get around to de-anonymizing that PrivateSend transaction from last year?

 

Dont give away too many of the secrets before the fun begins

[ddink7]

I guess that emoji means you weren't able to do it. That was a 4 round PrivateSend; I could create a much simpler 2 round PrivateSend for you to try and crack, if you'd like? Maybe we should take baby steps?

[Macno]

Dont give away too many of the secrets before the fun begins

Very entertaining thread you have there. Looking forward to your "trolling at the protocol level".
 
Even your Monero buddies are warning you that the XMR vs DASH meme is backfiring, but you are really  obsessed with it.