Which masternodes voted and what exactly voted on various proposals (v2)

[vazaki3]

New feature of mnowatch. All your votes revealed!

For example lets reveal all the votes of the below IPhash that belongs to a 24whale which today has a history of 492 reports.

638275126495143352507001456593990486195668035868

We know your votes, dear masternodes voters, so the day of judgement is near....


Also....Comming .... soon (?) ....Charts.

DASH Voters' History

mnowatch.org

 

[vazaki3]

Now mnowatch.sh can connect to a remote dash-cli

GitHub - dundemo/mnowatch: watch mno

watch mno. Contribute to dundemo/mnowatch development by creating an account on GitHub.

github.com

 

[vazaki3]

Now mnowatch.sh can connect to a remote dash-cli

GitHub - dundemo/mnowatch: watch mno

watch mno. Contribute to dundemo/mnowatch development by creating an account on GitHub.

github.com

Mnowatch is out of order due to the new remote dash-cli feature, that is not compatible to our provider which considers remote procedure calls (rpc) as DDOS!

We have an issue with the F/W of the VPS provider of mnowatch. It seems the provider blocks the access from the webserver to the dashd for a while, intermittent . We enquired with the VPS provider, they said it is the fault of their DDOS protection system . We are now looking at tunneling the dashd rpc via stunnel or similar.

So in case you know how we can do an stunnel or smth similar, please help.
Or alternatively tip us , for mnowatch to move to a better provider (that accepts crypto as payment).

 

[vazaki3]

Mnowatch is out of order due to the new remote dash-cli feature, that is not compatible to our provider which considers remote procedure calls (rpc) as DDOS!

We have an issue with the F/W of the VPS provider of mnowatch. It seems the provider blocks the access from the webserver to the dashd for a while, intermittent . We enquired with the VPS provider, they said it is the fault of their DDOS protection system . We are now looking at tunneling the dashd rpc via stunnel or similar.

So in case you know how we can do an stunnel or smth similar, please help.
Or alternatively tip us , for mnowatch to move to a better provider (that accepts crypto as payment).

The issue was resolved.
Mnowatch is up and running again.

 

[GrandMasterDash]

Why are you complicating things with stunnel? Can't you just do the data gathering on the node and write an API to fetch it?

 

[vazaki3]

Why are you complicating things with stunnel? Can't you just do the data gathering on the node and write an API to fetch it?

The issue was resolved without using stunnel. We used secure rpc (remote procedure call).

We have the mnowatch web server in a computer, and by using rpc calls we connect to another computer which has the dashd, in order to receive the dash data and form the reports.
This is because we want the mnowatch web server to be as light as possible. Also another reason is because if we put into the same machine both the mnowatch web server and the dashd server, then we need a powerfull machine, and powerfull machines are not cheap.

By the way, have a look at the new work of @xkcd --->

1. DASH DAO Summary (mnowatch.org)
2. DASH Proposal Owners (mnowatch.org)

 

[GrandMasterDash]

The issue was resolved without using stunnel. We used secure rpc (remote procedure call).

We have the mnowatch web server in a computer, and by using rpc calls we connect to another computer which has the dashd, in order to receive the dash data and form the reports.
This is because we want the mnowatch web server to be as light as possible. Also another reason is because if we put into the same machine both the mnowatch web server and the dashd server, then we need a powerfull machine, and powerfull machines are not cheap.

By the way, have a look at the new work of @xkcd --->

1. DASH DAO Summary (mnowatch.org)
2. DASH Proposal Owners (mnowatch.org)

I guess I didn't explain that well. I meant, you collect and format the data locally (on the node) and then make a private API that only you can remotely access. But yeah, I guess your solution also works. Are you getting a lot of web traffic?

 

[vazaki3]

I guess I didn't explain that well. I meant, you collect and format the data locally (on the node) and then make a private API that only you can remotely access.

The overhead and bottleneck is mainly when collecting and formating the data. Another overhead is dashd itself. We need to make things as light as possible, and as cheap as possible. Because a big server is more expensive than two small ones, we choosed the two servers solution, one for the dashd and another for collecting and formating the data.

We rely on bash scripts and on an rdbms, when collecting and formating the data. The web API is an http technology. Why add another overhead (a webserver) on all this?
I feel sorry because we use bash scripts (or rdbms calls), instead of using pure assembly, machine code or at least c++ when creating the reports.
But my skills are limited, I cannot talk directly to the machine. So unfortunately I rely on the code libraries others created, and thus my reports are not created as fast as they possibly could be.

But yeah, I guess your solution also works. Are you getting a lot of web traffic?

I dont know. @xkcd may answer this. But I assume https://apogee.dynu.net has no big traffic.

 

[GrandMasterDash]

I'm not entirely convinced but okay, understood.

Depending which database you're using, I wouldn't be surprised if it used more resources than a web server. There's almost nothing you can't do with sqlite and by orders of magnitude far easier to manage and backup than your typical rdbms. sqlite forces you to to design more efficiently.

Nginx is light and very fast serving static files and not that slow with scripting. I don't have much experience with bash scripts, it's a bit ugly.

 

[vazaki3]

I'm not entirely convinced but okay, understood.

Depending which database you're using, I wouldn't be surprised if it used more resources than a web server. There's almost nothing you can't do with sqlite and by orders of magnitude far easier to manage and backup than your typical rdbms. sqlite forces you to to design more efficiently.

Nginx is light and very fast serving static files and not that slow with scripting. I don't have much experience with bash scripts, it's a bit ugly.

We are already using sqlite3, this is our rdbms. But in order to have a web API, it requires both sqlite3 and a webserver. So why adding the webserver overhead and security hole?
I think connecting via rpc is faster and more secure than connecting through nginx or anyother webserver. Isnt it?

 

[GrandMasterDash]

We are already using sqlite3, this is our rdbms. But in order to have a web API, it requires both sqlite3 and a webserver. So why adding the webserver overhead and security hole?
I think connecting via rpc is faster and more secure than connecting through nginx or anyother webserver. Isnt it?

If you're using sqlite3 then there is no background service, most of the load is when inserting new rows. As for security holes, I don't know. If you're allowing random node commands, albeit secured, then it might be argued that a wrapped https call is more secure as you get to control which commands can or can not be called and from which IP. But honestly, you could be right.

 

[xkcd]

I dont know. @xkcd may answer this. But I assume https://apogee.dynu.net has no big traffic.

Not commenting on traffic, but of course we suggest everyone in the Dash community and beyond to access the reports and services on mnowatch.org to learn as much as possible about Dash and the Dash DAO. Demo is right about the hosting of two servers being cheaper than 1 big one and also, we can provide the right amount of resources to each, the dashd did waste a bunch of cycles we would have preferred to allocate to hosting pages and generating the content. The solution we have now is working for us.

 

[vazaki3]

New classifications added to mnowatch.

Classifications (mnowatch.org)

Can you see your own individuality in the above classifications? If not, dont worry. Sooner or later, we will catch you!

 

[vazaki3]

There are a lot of it. So you may choose any you like

What do you mean? Are you a human or a bot?

 

[vazaki3]

New classifications added to mnowatch.

Classifications (mnowatch.org)

Can you see your own individuality in the above classifications? If not, dont worry. Sooner or later, we will catch you!

We have spotted 56 individuals in mnowatch. https://mnowatch.org/Types/index.html

If someone realizes that his individuality is wrongly displayed in mnowatch, please inform (you dont have to reveal your individuality, just inform us that there is an error)

 

[vazaki3]

Apogee News: Mnowatch/Apogee admins have (until now) classified 84 individuals who control 1779 masternodes!!!

Among them, 68 individuals who vote in the budget by using 888 mno votes ! (crowdnode is included to the calculation with 31 votes)

If someone realizes that his individuality is wrongly displayed in mnowatch, please inform (you dont have to reveal your individuality, just inform us that there is an error)

 

[GrandMasterDash]

Wow, dash really becoming centralized now. This needs top priority over Dash Platform, the network can not function correctly without decentralization. And no, I do not listen to people whom say Crowdnode are "honest people". We didn't build a network for human trust, we built it for coded uncheatable trust.

Fact: There are more people looking for no-work-passive-income than there are do-work-operate-a-masternode-income. When the NWPI group have the largest voting power with the least skin in the game, then we may as well call this Proof of Stake.

We need to drop all collateral requirements ASAP and put more effort into enforcing paid Proof of Service. Hopefully we can also add the Proof of Useful Work to the equation.

 

[vazaki3]

Just to remind a usefull service of mnowatch.org, for those who are not aware of it.
MNO Notifications (mnowatch.org)

Remind? I mean announce ...Althouth notifications is the second oldest service of mnowatch, this is the first time I announce it here in the mnowatch thread of dashtalk.