Search results

OK, so you don't have answers to any of my questions. Got it. Sorry, but no. That makes no sense I have my family and lots of friends here in my hometown, a rich social life, my job that I love, a condo I own - I'm not going to throw everything in the wind to go proselytize what you call...

I watched your video. You're talking about changing the course of the DIF to a totally different direction, because investing crypto in regulated companies makes no sense. You want to focus on developing countries, potentially even invest in influencers from the 3rd world. I do agree that Dash...

Both output the HTML of the homepage. I didn't hash it to compare, but looks identical to me.

Yes, that's my setup. Here is my ufw status output: I'll look into Github. I don't have an account there, may set one up later.

Yes, it is reachable from the Internet. Netcat from another IP on a different hosting company shows it's reachable. I've also been monitoring the node closely and it's working fine. No, it's not Hetzner.

That gives identical output as without DEBUG=1

dashmate status core and dashmate status platform report ports 443, 9999 and 26656 as closed. Had me worried for a bit although my node seemed to chug along just fine. I checked with lsof that the server is listening on those ports: and also used a netcat port scan to confirm from another...

This doesn't work. Dashmate gives "Invalid format". The keys generated this way including your own example are 64 characters long and always start with "MC4CAQAwBQYDK2VwBCIEI". Dashmate rejects them. The keys generated by the MNOwatch site are 88 characters long and do not have repeating...

OK, what are the Platform Node ID and the private key internally used for? Or - what is the risk if I use a generated private key from a third-party website, which could potentially save the key? Could someone hijack my node or bring it down using that key? And this really needs to be named...

I'm trying to set up an Evo node and Dashmate is asking for a Ed25519 node key. I think it's from this part in the docu? https://docs.dash.org/en/stable/docs/user/masternodes/setup-evonode.html#generate-a-platform-node-id I tried both ways - using Docker and using open SSL - and copy the...

I'm a bit lost with the different masternode setup tools mentioned in different guides: Dashman (I understand this is obsolete) Dashmate Dash Masternode Tool Dash Zeus ... plus various guides to do it all manually. I asked in the Zeus thread about differences, but only got the response that...

Thanks for the response! If you don't mind, could you also explain the first part of my earlier post regarding Zeus versus Dash Masternode Tool?

Sorry, I need some more fundamental understanding of this tool. Is it basically a replacement for the Dash Masternode Tool mentioned in the documentation? https://docs.dash.org/en/stable/docs/user/masternodes/setup.html If so, what's the advantage of using this and is there any downside...

Any news on this?

update_service is ProUpServTx, right? This: https://docs.dash.org/en/stable/docs/user/masternodes/maintenance.html#proupservtx It doesn't say anything there about changing the payout address, only the operatorPayoutAddress. But for that to work a split has to be previously defined, which...

Is this going to work for Evo nodes once Platform is live? Some people have doubts https://www.dash.org/forum/index.php?threads/pose-banned-evo-node-is-not-a-regular.54882/post-238474

It's at over 90,000 now: 2024-05-15T09:24:43Z ThreadSocketHandler -- removing node: peer=90118 nRefCount=1 fInbound=1 m_masternode_connection=1 m_masternode_iqr_connection=0 My version is 20.1.0. I see there is a 20.1.1 point release where the release notes say: Work Queue RPC Fix / Deadlock...

Thanks! The documentation doesn't explain this: Is the documentation a community effort? Can I help update it somehow?

I got an Evo node POSE banned by a hard restart of the VPS. This node had payouts before, so I know the setup, pro reg tx IDs, BLS keys etc. was correct before. When it relaunched, some database was corrupt (can't this be prevented?): 2024-05-14T08:51:16Z cl-schdlr thread start...

I used this setup, but how do I properly trigger a reindex? Normally I'd call dashd with the -reindex option, but now I use sudo systemctl start/stop dashd which doesn't allow for options.