Recent content by john smithson

YESSS! Back to Normality. Thanks, now it works. P.S. The link that appeared on the DMT did not work, as it sent me to: https://github.com/Bertrand256/dash-masternode-tool/releases/download/v0.9.25/DashMasternodeTool_0.9.25-hotfix1.mac.dmg instead of...

Sure, I replied you on DM. Cheers

Hi @Bertrand256 thank you very much for looking into this. Yes, I am aware the calculation can be imprecise but not of so much. What is happening here is that the program is consistently saying that I need to be paid in 6 hours and x minutes, with x slowly moving from 44 minutes to 39 minutes...

Thanks, @tungfa

The good news is that I just got paid. The bad news is that the Dash Masternode Tool is STILL telling me I will be paid again in 6 hours 42 minutes. There is definitely a bug. Can someone who knows how to do it place a bug report with a link to here, please. Thanks.

Thanks. Following your suggestion I just moved to alice.dash-masternode-tool.org, so far it is giving me still the same time to next payment. My understanding was that my masternode had a fully synced wallet. In any case here the problem seem to be that the "Next Payment Block" seem to change...

More time passed, still at 6 hours and 42 minutes. Now I checked the block# which should be assigned to me, and it has changed. So somehow my masternode place in the queue is not fixed.

Some more hours are passing, and the time is not progressing, on the other side, I have noticed that the number of blocks between the last block that was assigned to my masternode and this one use to be on average 4830 circa. Now the new block "should" be after only 4300. The mystery deepens.

Hello, I have a masternode. A couple of weeks ago I had problems and thanks to the help from this community (@strophy in particular) we were able to fix it. Now it seems to be working alright. And the masternode started paying back again. At least it paid one time. Then now we are approaching...

After @strophy followed me, I was able to find the error. Basically the line masternode=1 was commented. In the set up instructions in the first part it says to keep i commented "for now". But then later it says to uncomment it, and that part I missed. Very grateful for the personalised help...

By the way, if I wanted to reinstall the masternode, do I have to go back from moving the 1000 DASH, or I can just thanks. It said: ~/.dashcore/sentinel$ git pull Already up to date. Regards.

Hi @strophy thank you very much for your offer to help me. I sent you a PM with the info you asked for. Regarding Discord I discovered that a proxy through which the email passes through flagged them as spam. So it was sent into a spam folder, but not one under my control.

For the records, Discord is not working for me. I have tried to register, but the email did not appear on my gmail. I tried several times, even changing the email address. And of course I also checked the spam messages. I looked online and apparently I am not the first person who had problems...

Thanks. Since my posts are not translated in any language, I shall write in details my passages, just in case they help someone. no, not Vim users. ;-) Ok, I had the minimum requirements. I just upgraded. Still I doubt that was the problem, so I will go on. Ok, so I am keeping my Dash in a...

Hello, there are a number of points in the explanation that are not clear. For example: * Ensure that the BLS private key on the masternode is unique on the network and not shared with any other masternodes How would you do that? I suppose it is not (statistically) but how can I ensure it? *...