[Thailand] Proposal for RPC Active Nodes additional status page

[oxarbitrage]

the problem right now is that most nodes are "private" nodes created by third parties to do their stuff. they don't want/need to be fully public because they only want to host traffic for their business, not for all the businesses running in the chain.

i understand your concern and the bitshares foundation is after this with a new worker proposal , very close to be approved at this moment that actually want to create a public network of public api nodes between other things, read the full thing at http://www.bitshares.foundation/workers/2017-12-infrastructure

[Digital Lucifer]

Great, you are also looking for our passwords and RSA keys?

don't forget to add your social numbers and name/address

 

Fav, as admin, you should be able to process this request instantly, without making pesty comments.

You should be well aware, that there is no request made for any access at all. We still can do all of this without your consent, by picking one by one from all lists, and doing it without communication.

Since we have Load Balancers proposal with more "independent" bitshares network, my suggestions is simply to polish current one and apply nginx load balancers with CDN network for utilizing js,css and media files and decentralizing it more, doing GEOIP for media only, not by Balancers. Balancers can load between 5 nodes in asia 20% each, already on existing infrastructure.

And i disagree that only official Bitshares RPC should be utilizied, as long as we are still listing in wallets other ones. We should stay aware that all of those private businesses are presenting, at the end of the day, Bitshares Network itself, by just being built and run on top of it.

[fav]

Great, you are also looking for our passwords and RSA keys?

don't forget to add your social numbers and name/address

 

[sahkan]

Great, you are also looking for our passwords and RSA keys?

[Digital Lucifer]

We would like to create a page/link (locked by password), to provide detailed specs about each and every RPC Bitshares node running world wide.

Each and every faucet are showing different nodes. There is no available real list or statuses on owner of them, availability or what they are actually running.

More and more users are, more and more often, facing Transaction Broadcast Error, Failed to Confirm, etc. As soon as the node list is being swiped by user (which should be not doing ti manually and many of them don't even understand where and what is the problem), and one normal Node is found, it's all good and working.

There is something seriously wrong with infrastructure, and since recently there was proposal about Load Balancers and making Bitshares network more stable, can we first get an info on where are we at this moment ?

Requirement:

1.) All owners of the nodes running official Bitshares, please deliver details in order to populate the page and list.

-Location
-IP (RPC only)
-RPC port
-Domain Name (RPC only)
-Server Configuration
-OS/Firewall Configuration (OS, services running such as Nginx, redis, mysql and their versions, ports, security details - fail2ban, csf/lfd...)
-Bandwidth Test
-Docker or Source

ETA:

- 3 Business Days to do Stress Tests by sending/simulating a lot of requests to each node.
- 6 Business Days to do Ethical Penetration Tests on all nodes.
- 1 Business Days to deliver the page url with the dataaccess visible to selected members of Bitshares Community, so we can track all decentralized individual servers are that are representing Bitshares, getting more knowledge and data where the actual problems are.
- 2 Business Days to provide Full Reports on results of Availability/Penetration testing.

When we are well aware of the STATE OF THE NETWORK itself, we can support more.

There is no cost for this, just reason, logic and focus from the community is needed.

Many thanks

Bitshares Thailand

on behalf of
@apasia.tech