• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12 Release

Some of MN on linux updated to 103 protocol version.
Start OK, detected and listed by all old and new version OK.
So far so good.

Anyway will wait for version 0.45 for the remaining MN.
 
Looks like the masternode.conf file is automatically generated now, so I'm wondering if we need a masternode.conf file in both the hot and the cold wallet now (if we're using start-many) or if it's even required no matter (IE, the old dash.conf only setup is no longer valid) 'cause I used the dash.conf setup throughout testnet??
And if the masternode.conf is required, do the right columns for donations need to be removed?
 
With all my MN on 70103 I also observe dropping off an on randomly. On dashninja some of them are partially unlisted or partially inactive.

Edit: Ok, let's wait for a solution.
Is Dashninja working? My masternodes server-side show as enabled yet none appear on the site. I know E was resyncing things but you make it sound like yours at least appear on the list whereas none of mine do.

Just read there is a new protocol version. Will try.
 
Any idears what happend here:

3c543


Why thers so many darksend entrys?

Hint: The user started mixing, and used tor to submit this action any idears?


PS: It seems theres currently issues registering on dashtalk:

You completed the registration faster than the min registration time

User: "i definitely waited longer than a minute this time, yet i still get that error msg"
 
I don't see any reason not to bring it back up if a large enough portion of the community wants it. Sure, it's an attack vector. But that's a risk MN operators would have to accept -- secure your masternode.conf file. It seems that to simply state "no, that's not going to happen because security" without discussion doesn't make it a very collaborative process — even if Evan's the one who said it. There are other security professionals in the community, and there are probably other ways of implementing it as well.
I asked about this again on Slack and here's the answer:

"eduffield[9:48 AM]@moli, re donations: It was incompatible with decentralized payments"

The reference node is gone, donations feature is not compatible with the current payment system, the budget system is implemented... I don't think it's wise to have insecurity in the system opened to attacks. If anyone can improve this, they're always welcomed to submit their code to github. :)
 
eduffield When you release v45 later today, can you at least keep the extracted folder structure to match the build (dash-0.12.0.45) vs just dash-0.12.0? Not sure why this was dropped from the process.
 
And if the masternode.conf is required, do the right columns for donations need to be removed?
masternode.conf is not required, it's just created there as a template with some simple instructions for you how to start using it.
Donation settings should be ignored automatically. Pls report if you have any issues with donations not being ignored or breaking mn start or anything else (though there should not be any).
 
Is Dashninja working? My masternodes server-side show as enabled yet none appear on the site. I know E was resyncing things but you make it sound like yours at least appear on the list whereas none of mine do.

Just read there is a new protocol version. Will try.
Looks like it's working atm. All my MN are reported as Active(100%).
 
I asked about this again on Slack and here's the answer:

"eduffield[9:48 AM]@moli, re donations: It was incompatible with decentralized payments"

The reference node is gone, donations feature is not compatible with the current payment system, the budget system is implemented... I don't think it's wise to have insecurity in the system opened to attacks. If anyone can improve this, they're always welcomed to submit their code to github. :)

Can we add this information to the release post/notes? If any feature (like donations) is removed, it should be clear and obvious.

There are plenty of other features that have been added that would be helpful to put in the release notes. Maybe this is a a list on github that each developer updates as they complete instead of Evan trying to put it in a single post. I am listing some great features not in the release post below. It is ok to show off all the effort put into each release! :)
  • Masternode.conf is created automatically and if existing, the donation columns are ignored.
  • Masternode inputs are locked automatically.
  • GUI Wallet repair tools
  • Specific Spork, Masternode, etc update bars to ensure instanTX and darksend(privaTX) capability.
  • Selectable interface themes.
 
masternode.conf is not required, it's just created there as a template with some simple instructions for you how to start using it.
Donation settings should be ignored automatically. Pls report if you have any issues with donations not being ignored or breaking mn start or anything else (though there should not be any).
Thanks. It looks like it used my old masternode.conf file without problems.
 
Can we add this information to the release post/notes? If any feature (like donations) is removed, it should be clear and obvious.

There are plenty of other features that have been added that would be helpful to put in the release notes. Maybe this is a a list on github that each developer updates as they complete instead of Evan trying to put it in a single post. I am listing some great features not in the release post below. It is ok to show off all the effort put into each release! :)
  • Masternode.conf is created automatically and if existing, the donation columns are ignored.
  • Masternode inputs are locked automatically.
  • GUI Wallet repair tools
  • Specific Spork, Masternode, etc update bars to ensure instanTX and darksend(privaTX) capability.
  • Selectable interface themes.
This is a huge release that took the devs several months to get it all together. It also took testers many hours to test... I know it's frustrating not to have all of the info in one place.. but I passed on your suggestion to the dev team, and I'm waiting to see what we can do.
 
So - no more: start-many? or just no more donations setups in masternode.conf??
 
This is a huge release that took the devs several months to get it all together. It also took testers many hours to test... I know it's frustrating not to have all of the info in one place.. but I passed on your suggestion to the dev team, and I'm waiting to see what we can do.
In a production environment any features removed can cause big problems - even if they seem minor. Just pointing out that this is critical to put in release notes.

Not frustrated at all. This is an awesome release. Show it off!
 
The CPU hogging dashd thread is, please fix it, if possible:
from top -H:
21921 xxxxx 22 2 908200 179908 36092 R 58.1 8.8 49:39.70 dash-msghand

getting messages like this, continious flood, like screen is scrolling as fast as it can..
strace -p 21921:
endto(39, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(31, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(35, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(36, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(37, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(33, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(20, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(26, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(24, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(28, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(30, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(32, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(21, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(23, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(29, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(27, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(39, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(31, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(35, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(36, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(37, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(33, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\356\247\370\"\16\274\242\260Q\r\220\336"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(20, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(26, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(24, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(28, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(30, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(32, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(21, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(23, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(29, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(27, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(39, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
sendto(31, "\277\fk\275dseep\0\0\0\0\0\0\0t\0\0\0\373\257\264\272,\226\312<\375\35\242\304"..., 140, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0) = 140
 
Back
Top