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

V12 Release

About the payment :
2 of my MN received both 4 payment in the last 24h
All the other : nada for the moment.

I updated all MN at same time.

If enforcement is OFF : the payments are random?
 
Last edited by a moderator:
Sub-Ether said:
I was referring to the runtime fatal error when the password is entered, I tried all of the wallet repair features in testnet, and using V11 was the only workaround, this is an inherited error from bitcoin and something to be aware of because otherwise you will never be able to access your funds if the V11 becomes no longer compatible with the network
Click to expand...
Do you still see this happening in v0.12.0.46-3425223 ? If so you should report to the devs with the debug log and screenshot...
 
Lebubar said:
About the payment :
2 of my MN received both 4 payment in the last 24h
All the other : nada for the moment.

I updated all MN at same time.

If enforcement is OFF : the payments are random?
Click to expand...
IMO, The list of payment is consensus by network no matter enforcement is on or off. The enforcement is OFF allow miners with different list of payment (v11) or miners with no payment can submit new block to network. This is called hijacking.
 
Well, something weird.
One of the 2 just received a fifth payment, lol (and I don't hijack nobody)

2015-08-19 19:44:55 + 3.25 DASH1,029.11181388 DASH
2015-08-19 17:07:45 + 2.78 DASH1,025.86181388 DASH
2015-08-19 13:47:03 + 2.78 DASH1,023.07609965 DASH
2015-08-19 06:26:31 + 3.25 DASH1,020.29038542 DASH
2015-08-19 00:11:58 + 3.25 DASH1,017.04038542 DASH
 
just looked into masternode winners and found something odd


"322229" : "Xpfv6vKUmCa7nGvGnSrJjAKAT135R7Svju:3",
"322230" : "Xk8KPR6WrSiKGW6PDyBUsmHeYxagL5pVJu:4",
"322231" : "Xaor98Mu5iZAAvT2LaxaYGjjRZMtNqAVm3:2",
"322232" : "Xjat1H6uLMffECUVFaBPPfdGxWh4dXtFcL:6",
"322233" : "Xxcj6wPCzkwFa2nQf7X4hLru5rNDz4YLRP:3",
"322234" : "Xj6VmfzMbe5gt4eSBVTZeVg7CGZTxuyLeC:2",
"322235" : "XuKu5bymCVcQW9ZawyPjwihv4HZAUFdhup:3",
"322236" : "Xev6Ln2k5ZkexQX1qfkjcVLsotM44VVY9w:110",
"322237" : "Unknown",
"322238" : "Unknown",
"322239" : "Unknown",
"322240" : "Unknown",
"322241" : "Unknown",
"322242" : "Unknown",
"322243" : "Unknown",
"322244" : "Unknown",
"322245" : "Unknown"
 
Sapereaude said:
just looked into masternode winners and found something odd


"322229" : "Xpfv6vKUmCa7nGvGnSrJjAKAT135R7Svju:3",
"322230" : "Xk8KPR6WrSiKGW6PDyBUsmHeYxagL5pVJu:4",
"322231" : "Xaor98Mu5iZAAvT2LaxaYGjjRZMtNqAVm3:2",
"322232" : "Xjat1H6uLMffECUVFaBPPfdGxWh4dXtFcL:6",
"322233" : "Xxcj6wPCzkwFa2nQf7X4hLru5rNDz4YLRP:3",
"322234" : "Xj6VmfzMbe5gt4eSBVTZeVg7CGZTxuyLeC:2",
"322235" : "XuKu5bymCVcQW9ZawyPjwihv4HZAUFdhup:3",
"322236" : "Xev6Ln2k5ZkexQX1qfkjcVLsotM44VVY9w:110",
"322237" : "Unknown",
"322238" : "Unknown",
"322239" : "Unknown",
"322240" : "Unknown",
"322241" : "Unknown",
"322242" : "Unknown",
"322243" : "Unknown",
"322244" : "Unknown",
"322245" : "Unknown"
Click to expand...
Here's what my wallet is showing right now:

upload_2015-8-19_22-33-8.png
 
I have four masternodes, two haven't received any payments in 9 and 10 days, and the other two have received 5 payments in the last 48 hours.
 
eduffield said:
New Payment Logic

The masternode payments system is entirely rewritten for v12, in a way that doesn't require the reference node to run. However, a lot has changed and it might get confusing if you don't understand what's going on, so I thought I would make a post to show how it works.

SPORK_10_MASTERNODE_PAY_UPDATED_NODES

When this is enabled on the network it means that the masternode network will only elect newer versions to get paid. This has nothing to do with enforcement and payments can still be stolen while this is enabled

In the next stage we wait till the network looks like there is consensus of the order of masternodes to pay. When the network has not gained consensus the masternode winners list will look something like this:

Masternode Winners:


If you look at "masternode winners" right now on mainnet, we have gained consensus and are ready to enforce! When the payment system has consensus it will look like this:

masternode winners


Other new things about the masternode payment system:
- When you restart your masternode, you are forced to the back of the queue. When you update from v11 to v12, this goes into effect and you will not be paid for the first payment period.
- The network prefers to pay people that are not subject to this penalty, meaning that when we upgrade the first nodes to upgrade will get substantial rewards when SPORK_10_MASTERNODE_PAY_UPDATED_NODES gets activated due to the small amount of qualifying nodes. Over time the rest of the network will also qualify for payment and the payment period will extend until it is normal again. This is our new "fast upgrade" incentive system, the faster you upgrade the more you get :wink:
- Multiple payments in a row are possible and OK. There should be about a 1/100 chance of this happening and you will not skip your next payment, it's something like the daily network lottery.
Click to expand...

Hi Evan, I am seeing this masternode winners result:

"322440" : "XtE4rJZpY4vNsuyg63cG13s6UvTGVzeiBh:110",
"322441" : "XdArLjWreVwfJwBQhpJuVoLvpmVjwmiy7s:110",
"322442" : "Xx58KPWYCxghvQS17EUs8Pvu4SWraS4Qg2:110",
"322443" : "XbcKhc1gBw9bXmmvM16TbE6uqJs5i8Boas:110",
"322444" : "XkV6vADZgerLitafDntPNtte2bundHiqXm:110",
"322445" : "XfpGe5TX4YyUFBebCjCe5Y1WSAJV9qPq4S:110",
"322446" : "XfDT5x7CUmHv1FAtj88rPHr1wSYgccAvXv:110",
"322447" : "XghcwFhDu5Eg58Cq6iZjw86tTiyBnN28mw:110",
"322448" : "XgLFmgEWsGwXjMUMzkqy6b56xB25jSYnC4:110",
"322449" : "XdXga3rHvp7E5CoaKfSo48zRFoRigG9vaT:110",
"322450" : "XyudyuPQWLzvMRL4zLzpFHRRig8ZWg7Kj8:110",
"322451" : "Xn1FYbib4KKAaE2jG8yUmywvGSVjjxhUe5:110",
"322452" : "Xj6VmfzMbe5gt4eSBVTZeVg7CGZTxuyLeC:110",
"322453" : "XtE4rJZpY4vNsuyg63cG13s6UvTGVzeiBh:110",
"322454" : "XnxZdk1NyCYReDccLv5Rvwy1SUbaK2Wyn6:110",
"322455" : "XtNGprrYUuVe2FqwJ89V4EMqKtPjB7qZUm:110",
"322456" : "Xz1o69FjBvPyTq7U9zYaCAUvyHJeaqnTvj:110",
"322457" : "XeJx2DpjLh93DubRjmSgrhoCfhhvXHojFS:110",
"322458" : "Xu3Cv4YZDunHpy3xxs3Ki6zejEgnZnfnL5:109",
"322459" : "Xgwh7cMG2v1C1u2VALuqZAAnZJwxvv9aRq:110",
"322460" : "XufBcpCfsbBGVa3towftbBjZoKCGDgpSum:110",
"322461" : "Unknown",
"322462" : "Unknown",
"322463" : "Unknown",
"322464" : "Unknown",
"322465" : "Unknown",
"322466" : "Unknown",
"322467" : "Unknown",
"322468" : "Unknown",
"322469" : "Unknown"

According to your post, this has enforcement enabled. However, spork active returns:

"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : false,

And, spark show returns:

"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : 1640014069,

Does that 1640014069 (i.e. Mon Dec 20 15:27:49 UTC 2021) mean we will not be activating the enforcement and will rely on the new algorithm to do its job? I am confused.
 
GermanRed+ said:
Hi Evan, I am seeing this masternode winners result:

"322440" : "XtE4rJZpY4vNsuyg63cG13s6UvTGVzeiBh:110",
"322441" : "XdArLjWreVwfJwBQhpJuVoLvpmVjwmiy7s:110",
"322442" : "Xx58KPWYCxghvQS17EUs8Pvu4SWraS4Qg2:110",
"322443" : "XbcKhc1gBw9bXmmvM16TbE6uqJs5i8Boas:110",
"322444" : "XkV6vADZgerLitafDntPNtte2bundHiqXm:110",
"322445" : "XfpGe5TX4YyUFBebCjCe5Y1WSAJV9qPq4S:110",
"322446" : "XfDT5x7CUmHv1FAtj88rPHr1wSYgccAvXv:110",
"322447" : "XghcwFhDu5Eg58Cq6iZjw86tTiyBnN28mw:110",
"322448" : "XgLFmgEWsGwXjMUMzkqy6b56xB25jSYnC4:110",
"322449" : "XdXga3rHvp7E5CoaKfSo48zRFoRigG9vaT:110",
"322450" : "XyudyuPQWLzvMRL4zLzpFHRRig8ZWg7Kj8:110",
"322451" : "Xn1FYbib4KKAaE2jG8yUmywvGSVjjxhUe5:110",
"322452" : "Xj6VmfzMbe5gt4eSBVTZeVg7CGZTxuyLeC:110",
"322453" : "XtE4rJZpY4vNsuyg63cG13s6UvTGVzeiBh:110",
"322454" : "XnxZdk1NyCYReDccLv5Rvwy1SUbaK2Wyn6:110",
"322455" : "XtNGprrYUuVe2FqwJ89V4EMqKtPjB7qZUm:110",
"322456" : "Xz1o69FjBvPyTq7U9zYaCAUvyHJeaqnTvj:110",
"322457" : "XeJx2DpjLh93DubRjmSgrhoCfhhvXHojFS:110",
"322458" : "Xu3Cv4YZDunHpy3xxs3Ki6zejEgnZnfnL5:109",
"322459" : "Xgwh7cMG2v1C1u2VALuqZAAnZJwxvv9aRq:110",
"322460" : "XufBcpCfsbBGVa3towftbBjZoKCGDgpSum:110",
"322461" : "Unknown",
"322462" : "Unknown",
"322463" : "Unknown",
"322464" : "Unknown",
"322465" : "Unknown",
"322466" : "Unknown",
"322467" : "Unknown",
"322468" : "Unknown",
"322469" : "Unknown"

According to your post, this has enforcement enabled. However, spork active returns:

"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : false,

And, spark show returns:

"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : 1640014069,

Does that 1640014069 (i.e. Mon Dec 20 15:27:49 UTC 2021) mean we will not be activating the enforcement and will rely on the new algorithm to do its job? I am confused.
Click to expand...
The enforcement is off. Relax. The devs are on it. Just relax.
That list looks good. It means the payment system is working without the reference node. And this is the goal!
 
moli said:
The enforcement is off. Relax. The devs are on it. Just relax.
Click to expand...
Thanks, Moli. Glad to hear that you guys are on it. Just in case this hasn't been reported yet, the dashninja.pl website is not reporting the correct amount of DASH in the cold wallets since I noticed the number of MNs dropped from almost 3000 down to 1700.

Another issue that we haven't discussed on this thread is the over 51% issue. It has been discussed on another thread. Can something on top of the MN network be implemented in the future to prevent the 51% attacks?
 
Anyone experienced a deadlock with v0.12.0.46? I don't have a debug log and the last thing I saw is "STOP" state on "top" for the dashd daemon process. The memory usage went over 500MB. Maybe, there are still some memory related bugs.

EDIT: It started with 300 something MB. It grew slowly. Hope this is just a faulty filesystem on my computer.
 
Last edited by a moderator:
Any chance of getting updates during office friendly hours and within a specific timeframe, such as on specifiy days only? That would make an admin's live a lot easier. Preparing and testing virtual appliances for distribution is a hell of a lot work.

Is there some kind of mailinglist for dash updates? Something which states whether an update is really needed or can be postponed a week or so. I really don't know how your development cycles are. Do you tag a new version with every non critical code submission?
It would be nice if you could differentiate between important (critical) and less important changes which don't affect stability and compatibility.
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top