Yah, we'll never understand the moderator
anyway, how is it going? Did any more funds come through? And I'm curious, will you be going to Mexico or to the Florida conferences?Florida conference?
Miami Jan 2016
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 1596. (Read 9723706 times)
November 16, 2015, 09:21:56 AM
Yah, we'll never understand the moderator
anyway, how is it going? Did any more funds come through? And I'm curious, will you be going to Mexico or to the Florida conferences?Florida conference?
Miami Jan 2016
November 16, 2015, 09:10:20 AM
November 16, 2015, 08:52:40 AM
Yah, we'll never understand the moderator
anyway, how is it going? Did any more funds come through? And I'm curious, will you be going to Mexico or to the Florida conferences?Florida conference?
November 16, 2015, 07:15:54 AM
How much do l need to have in wallet, for running masternode_ 
1.000 Dash
https://dashpay.atlassian.net/wiki/display/DOC/Masternodes+for+Newcomers
November 16, 2015, 06:54:41 AM
How much do l need to have in wallet, for running masternode_
November 16, 2015, 06:54:26 AM
It's all clear about variance.
The weird thing is incremented "lastpayment" entry in the list without real payment occured. I believe updated "lastpayment" (from ./dash-cli masternodelist full, I observe it from 3 of mine vps) means that consensus decided some mn must be paid - and there're no ways to avoid that since the enforcement is active. Correct me if I'm wrong.
It's not about bugs in the monitoring scripts. Looks like dashninja.pl calculates "Last Paid=1d8h37m20s" based on "masternodelist full" output and dashwhale shows "Lastpay=6 days ago" based on the real payment transactions in the blockchain.
Anyway I'll inform about next payment.
The weird thing is incremented "lastpayment" entry in the list without real payment occured. I believe updated "lastpayment" (from ./dash-cli masternodelist full, I observe it from 3 of mine vps) means that consensus decided some mn must be paid - and there're no ways to avoid that since the enforcement is active. Correct me if I'm wrong.
It's not about bugs in the monitoring scripts. Looks like dashninja.pl calculates "Last Paid=1d8h37m20s" based on "masternodelist full" output and dashwhale shows "Lastpay=6 days ago" based on the real payment transactions in the blockchain.
Anyway I'll inform about next payment.
Yes, that's correct! Dashwhale lastpay status is derived from the blockchain, nextpay is derived from dashd. So your node moved from the 10% of masternodes, which will be paid within a few hours to the bottom of the payment queue without getting paid and without having been offline, which might indicate a rare bug. Since it's so rare, i suppose it's more worth to dedicate the core team's devpower to Evolution.
Actually, the way the masternode payments work is slightly different. Once your masternode moves into the 10% of masternodes eligible for payment, the system just uses some simple math to determine when you'll get paid. There's not a set time that nodes get paid, instead it's defined with probabilities.
Moocowmoo explains it really nicely here:
I think the math is correct here.
A node is eligible for for selection when 90% of the other nodes have already been selected.
Once you're due to be selected, your chances are 1 in 326 (10% of masternodes, the length of the selection queue) or about:
63% in the first 13 hours (326 blocks)
82% in the first 24 hours (576 blocks)
97% in the first 48 hours (1152 blocks)
99.5% in the first 72 hours (1728 blocks)
99.91% in the first 96 hours (2304 blocks)
where probability P = (325/326)^blocks
This will shift a little as the total masternode count changes, but the probabilities will stay close to these numbers.
Now, since other unpaid masternodes are constantly being swapped into the selection queue
and that selection depends on a competition between cryptographic hashes,
it is possible your node will fall OUT of the queue before being paid. (causing a skipped payment cycle)
This is a rare occurrence, but, double payments occur about 0.6% of the time, so over time payments should average out.
A node is eligible for for selection when 90% of the other nodes have already been selected.
Once you're due to be selected, your chances are 1 in 326 (10% of masternodes, the length of the selection queue) or about:
63% in the first 13 hours (326 blocks)
82% in the first 24 hours (576 blocks)
97% in the first 48 hours (1152 blocks)
99.5% in the first 72 hours (1728 blocks)
99.91% in the first 96 hours (2304 blocks)
where probability P = (325/326)^blocks
This will shift a little as the total masternode count changes, but the probabilities will stay close to these numbers.
Now, since other unpaid masternodes are constantly being swapped into the selection queue
and that selection depends on a competition between cryptographic hashes,
it is possible your node will fall OUT of the queue before being paid. (causing a skipped payment cycle)
This is a rare occurrence, but, double payments occur about 0.6% of the time, so over time payments should average out.
As moo points out, there is a possibility to fall out of the queue and not receive payment within a cycle. This only can happen when your node receives two votes for a given block and another node received more at the same time. This is extremely rare, as it would require a concensus disagreement among the masternode network; those are more common shortly after upgrading to a new version, then they quickly are solved and do not occur again but for very uncommon situations.
This is also not a bug, but will go away with evolution as well as the probability based design. I found another design that is much more memory efficient and isn't based off of probabilities, but instead will establish a set list of payees. I believe that's a lot better for the long term solution for us, so we'll move to that.
November 16, 2015, 05:41:26 AM
Hello! Where I can see how much masternode pay in month?
Here you can see the estimated payment per masternode per day:
http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html
November 16, 2015, 04:13:45 AM
Hello! Where I can see how much masternode pay in month?
Here you can see the estimated payment per masternode per day:
http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html
November 16, 2015, 04:11:59 AM
It's all clear about variance.
The weird thing is incremented "lastpayment" entry in the list without real payment occured. I believe updated "lastpayment" (from ./dash-cli masternodelist full, I observe it from 3 of mine vps) means that consensus decided some mn must be paid - and there're no ways to avoid that since the enforcement is active. Correct me if I'm wrong.
It's not about bugs in the monitoring scripts. Looks like dashninja.pl calculates "Last Paid=1d8h37m20s" based on "masternodelist full" output and dashwhale shows "Lastpay=6 days ago" based on the real payment transactions in the blockchain.
Anyway I'll inform about next payment.
The weird thing is incremented "lastpayment" entry in the list without real payment occured. I believe updated "lastpayment" (from ./dash-cli masternodelist full, I observe it from 3 of mine vps) means that consensus decided some mn must be paid - and there're no ways to avoid that since the enforcement is active. Correct me if I'm wrong.
It's not about bugs in the monitoring scripts. Looks like dashninja.pl calculates "Last Paid=1d8h37m20s" based on "masternodelist full" output and dashwhale shows "Lastpay=6 days ago" based on the real payment transactions in the blockchain.
Anyway I'll inform about next payment.
Yes, that's correct! Dashwhale lastpay status is derived from the blockchain, nextpay is derived from dashd. So your node moved from the 10% of masternodes, which will be paid within a few hours to the bottom of the payment queue without getting paid and without having been offline, which might indicate a rare bug. Since it's so rare, i suppose it's more worth to dedicate the core team's devpower to Evolution.
November 16, 2015, 04:11:37 AM
Hello! Where I can see how much masternode pay in month?
November 16, 2015, 02:07:05 AM
I have to be honest... I start getting worried when I don't see our pet trolls on here... DRKlvr/Adam, Adam White, arielbit, icebreaker just to name a few.
Phew... I know that everything is going well with DASH when their all on here spending time spewing their troll BS.
Phew... I know that everything is going well with DASH when their all on here spending time spewing their troll BS.
Looks like Adam got 2 week ban (which is the reason he got active on his DrkLvr_ account) and while the ban is now over he must be too embarrassed to post until he figures out a "vacation" explanation.
Did I mention AdamWhite and TheDasher were both MIA until the other night they logged in again within 10 minutes from each other? I had doubted they'd be the same person because the style seems different and activity profiles are a couple of hours off whereas DrkLvr_ is a 1:1 copy of AdamWhite all the way to the obsession with CLAMs and mimicking the style of the posts where he himself gets humiliated.
November 16, 2015, 12:16:20 AM
I have to be honest... I start getting worried when I don't see our pet trolls on here... DRKlvr/Adam, Adam White, arielbit, icebreaker just to name a few.
Phew... I know that everything is going well with DASH when their all on here spending time spewing their troll BS.
I
Phew... I know that everything is going well with DASH when their all on here spending time spewing their troll BS.
I
November 15, 2015, 10:07:02 PM
DASH
Quote
Nothing like the squeals you kicked out after going all in on dashcoin ay Adam??
I'm into dashcoin and I'm not crying
Hi guys! missed you all.. i like this thread more than watching sports LOL
the offense has new/revised weapons.
the defense will develop a new defense style.
and you all go round and round again
November 15, 2015, 08:23:38 PM
good to hear you are making progress with your withdraws !!
do not worry about the mods here
i had a recent discussion with them as well
and they are obviously writing their own rules reg deleting posts or not !
November 15, 2015, 08:09:28 PM
Yah, we'll never understand the moderator
anyway, how is it going? Did any more funds come through? And I'm curious, will you be going to Mexico or to the Florida conferences? 
November 15, 2015, 04:49:48 PM
Crazy good news! Congrats and a big thanks to all involved.
Amazing! Well done to the people who arranged and negotiated it.
November 15, 2015, 04:39:56 PM
It's all clear about variance.
The weird thing is incremented "lastpayment" entry in the list without real payment occured. I believe updated "lastpayment" (from ./dash-cli masternodelist full, I observe it from 3 of mine vps) means that consensus decided some mn must be paid - and there're no ways to avoid that since the enforcement is active. Correct me if I'm wrong.
It's not about bugs in the monitoring scripts. Looks like dashninja.pl calculates "Last Paid=1d8h37m20s" based on "masternodelist full" output and dashwhale shows "Lastpay=6 days ago" based on the real payment transactions in the blockchain.
Anyway I'll inform about next payment.
The weird thing is incremented "lastpayment" entry in the list without real payment occured. I believe updated "lastpayment" (from ./dash-cli masternodelist full, I observe it from 3 of mine vps) means that consensus decided some mn must be paid - and there're no ways to avoid that since the enforcement is active. Correct me if I'm wrong.
It's not about bugs in the monitoring scripts. Looks like dashninja.pl calculates "Last Paid=1d8h37m20s" based on "masternodelist full" output and dashwhale shows "Lastpay=6 days ago" based on the real payment transactions in the blockchain.
Anyway I'll inform about next payment.
November 15, 2015, 04:25:48 PM
Crazy good news! Congrats and a big thanks to all involved.
November 15, 2015, 03:23:22 PM
One of my masternodes went for almost 13 days before payment, so variances may occur. I agree, let the masternode do its work, and most likely within a few days, the next payment will come through
November 15, 2015, 03:11:19 PM
i had a masternode that got paid after 8 days once. Dashninja restarted the count with last paid then too because it felt outside
their calculation period or something. In the end it got paid just fine, just a little bit later then normal.
I think variance is still playing a rol in here, so you either get a masternode that gets paid a little later than normal or you get paid twice, both
are rare ocurrences.
Gil's masternode was last paid the 9th.. which makes it 6 days. Give it a few more days.
their calculation period or something. In the end it got paid just fine, just a little bit later then normal.
I think variance is still playing a rol in here, so you either get a masternode that gets paid a little later than normal or you get paid twice, both
are rare ocurrences.
Gil's masternode was last paid the 9th.. which makes it 6 days. Give it a few more days.
Oh that would be good then, let us know, Gil, if that happens. I obviously can't count, six days, ROFL. I'm still the same girl I was as a youth... and I won't tell you my nick name back then. But you can guess the jist of it
If I hadn't always been such an air head, I'd be worried I was going senile Jump to: