Masternode Payment Testing - Now vs Later?

[eduffield]

Despite the forking issues with enforcing masternode payments, the code and strategy that we're using now is looking really good. The problem was simply blocks coming in out of order, which are now properly ordered before being checked for the correct payment. I reviewed many different logs and this was the only issue I found, which caused all problems we had.

The question to the community:

It's pretty much impossible to test mastenode payments on testnet and some users/mining pools are very sick of updating. Should I have everyone update again, and enable enforcement on Friday? Alternatively we could wait until InstantX, which is what I'm also working on. Testing InstantX is probably still a couple weeks out, then we have the testing phase, so that could add another month or so. Alternatively, we just have the network update until it works and we move on.

 

[moocowmoo]

Have everyone update again, and enable enforcement on Friday. Let's shake out the bugs one layer at a time.

 

[AjM]

I vote for waiting.

 

[moli]

I vote for waiting also.

 

[oblox]

I guess the most pertinent question would be how far out is InstantX. I think the overwhelming majority of the masternode owners would be for enforcement sooner than later, just from the standpoint of normalizing payouts.

 

[Ignition75]

Yes I think waiting is going to be a better option, next update can be all about Instant(tx) as well, it will create quite a lot of fan fair.

 

[coingun]

I'm with moocowmoo. Update once more and allow for enforcement to get turned on and work successfully.

 

[Scriptiee]

I say update and enforce.

Throwing both into the same update at a later date might hinder troubleshooting any issues with InstatntX, lets get one of these behind us asap.

 

[illodin]

I'm fine with updating often, but I only run masternodes, not pools. If people can't handle development they should gtfo and wait until it's stable imo.

 

[moli]

Evan said InstantX isn't going to use a fork:

 

[BrainShutdown]

I agree with moocowmoo.
Bug correction should occur one layer at a time.

 

[thelonecrouton]

I vote update again now. I don't really care about MN payment variance with the RC3 code, it's good enough, but if enforcement is part of the roadmap I think it's better to tackle it now.

Updating a Masternode takes 60 seconds or less. I don't know how long updating a pool takes but I doubt it's much longer. This is an evolving coin, a few minutes of someones day now and again isn't much to ask.

Friday sounds good - it shouldn't take weeks.

 

[Dr.Crypto]

Update now, enforce on Friday, get a healthy network by the time InstantX is to be tested!

 

[eduffield]

Alright, 80% wants to update. I'll push up the code and compile the update Thanks everyone!

 

[defunctec]

Update now, enforce asap.

People have their eye on dark atm, the network update should happen fast.

But if we leave it until Friday, we have the weekend where people are away from their computers
not able to update.

Update the network until enforcement works. One update over two days then enforcement. If fail, repeat.

Price may drop, mining activity could slide...

But who cares about price at this point?

We need a solid platform for instantx, simple as that.

EDIT: Evan already replied!

 

[ourlink]

Update... It's not a big deal to update the nodes and I think it would be better to work through bugs one layer at a time like other have expressed. Besides, we need to enforce asap!

 

[GermanRed+]

Have everyone update again, and enable enforcement on Friday. Let's shake out the bugs one layer at a time.

+1. We never know if there are other bugs or exploits until it works without any flaw.

 

[GermanRed+]

Update... It's not a big deal to update the nodes and I think it would be better to work through bugs one layer at a time like other have expressed. Besides, we need to enforce asap!

+1 for "enforce asap".

 

[GilAlexander]

Update & enforce on Friday. It has already taken too long.

 

[italx]

agree. It makes sense to make sure it's working and stable before making other changes.

 

[MangledBlue]

I'm with MOOCOWMOO ! !
Have everyone update again, and enable enforcement on Friday. Let's shake out the bugs one layer at a time.


Fix an issue - update


edit: just seen Evans statement :-D

I WILL UPDATE AFTER WORK!!!! tonight :-D



I just love fixes :-D
(sorry moli you lose :-* kisses)

 

[jimbit]

As much as I would rather leave well enough alone for a while.... doing things one layer at a time does make sense.

 

[Ignition75]

The more I think about it the more I'm advising you to wait.

How about Splawik/Moli/Tungfa/Tao and I work on a communication pack over the next couple of days and pre-warn Pool Operators, Exchanges, Masternode Operators and regular users?

We can still do things in stages, however it might be better to pro-actively communicate this first.

 

[moli]

The more I think about it the more I'm advising you to wait.

How about Splawik/Moli/Tungfa/Tao and I work on a communication pack over the next couple of days and pre-warn Pool Operators, Exchanges, Masternode Operators and regular users?

We can still do things in stages, however it might be better to pro-actively communicate this first.

It's ok, we'll just update and enforce on Friday. I'm with the "pool friendly reminder" with splawik21 and oblox and we're going to email them. We'll be okay.

And yes please do whatever you can help to get this going. That will be great! Thank you

Edit: splawik21 said Evan will send out mass emails also.

 

[crowning]

yeah one layer at a time makes sense! maybe let people update and wait 2 or 3 weeks instead of enforcing friday. This way pools got more time and you can concentrate on instantx and got a stable base when its finished

Actually if you give the usual suspects (yes, that's YOU, niceass) 1 year time until enforcement they'll update exactly after 365 days.
366 if it happens to be a leap year.

Enforcement NOW so we'll get that sorted!

 

[splawik21]

We will wait till tomorrow and start till tomorrow to contact with the pools.
Evan already have sent the email to all on the google doc list.
Not there yet? Subscribe: https://docs.google.com/forms/d/1t_iWT-M-_4FV_RqqLPNtlrEqQaD0GPO76cUrMMGiUFI/viewform

 

[Sub-Ether]

The Sheep wants to update immediately and also feels this is the best way to solve each layer of complexity during the bug quashing phases.

 

[Stealth923]

Happy to update as often as required. We are still in bug fixing and very close to a stable platform.

As previously said lets layer fixes one at a time to limit troubleshooting complications later on. InstantX is such a large update I would rather have everything else perfect before we attempt it

 

[Raico]

progress is never easy.
Dev team, just do what you need to do~
Vote for Friday~

 

[tungfa]

voting done ? (sorry just woke up)

I trust in evan (as always)
you know best how to handle this ! it is great that you involfe us in the voting, but I belive you know best how the code will react between IT and enforcement , fork here and fork there !
development takes time and we are doing the right thing, ether way !

MN payment enforcement is important as we want/ need more MN's and we promise 20% return, so we gotta deliver as MN investors want to see that return !

IT has caught a bit of hype there but it can wait if it has to !

We did so many updates (which only show how much work is done in a good way) so if there has to be more, so be it !

sorry, am on my 2nd coffee and started rambling there a bit ...>