BitShares Forum
Main => Stakeholder Proposals => Topic started by: Digital Lucifer on February 21, 2020, 10:44:52 pm
-
Dear BitShares,
Since I was personally told and explained that there is no need for classic API's and previous worker I've had (Exotic infra) nodes were turned off 4 months ago - in the meantime we noticed increased need for stable ES/Kibana hosts for various reasons.
We (APAsia.tech) would like to provide, under our own review and collaborative management, the nodes and elastic search APIs that have been deployed with the soon expiring infrastructure worker by BPBV (https://www.bitshares.foundation/workers/2019-02-infrastructure).
Read the full details here: https://www.bitshares.foundation/workers/2020-02-infrastructure (https://www.bitshares.foundation/workers/2020-02-infrastructure)
Voting for worker proposals: Votes can be done via the reference wallet. Visit Menu -> Votes -> Workers or enter your account name in the link https://wallet.bitshares.org/#/voting
This worker proposal has id 1.14.253 and 202002-infrastructure.
We kindly ask for any comments and feedback.
Best Regards,
Collaboration infra worker teams.
Chee®s
-
Super, and thank you! The ElasticSearch databases are essential for proper statistic aggregation.
Both services (testing version) run on it:
- http://88.198.69.93:1234 (voting stats)
- http://88.198.69.93:1235/docs (statistics for cryptoranking websites)
-
+5%
-
For those who have interest, the stats page https://stats.bitshares.ws/ has some data and charts about usage.
-
Total budget:
30,600 USD (215,179 CNY)
Waiting for the worker to be created so I can vote.
-
Commercial use is an important aspect, which can lower the worker costs or completely remove it.
-
Commercial use is an important aspect, which can lower the worker costs or completely remove it.
Commercial-use have different definition in this worker. There is no such need that private owned for-profit companies such as gateways are listing nodes for public access.
We don't have actual "commercial" product apart from our users through wallet.bitshares.org, btspp and dexbot, hence "no commercial (ab)use".
Chee®s
-
Total budget:
30,600 USD (215,179 CNY)
Please quote additional budget requirements for the same worker, except no restrictions on gateways providers: GDEX, RUDEX, XBTSX, DEEX, etc.
There is no such need that private owned for-profit companies such as gateways are listing nodes for public access.
The nature of the argument: "gateways should be self funded because they keep all their profits", is no longer relevant with BSIP86.
These are no longer "independent for profit entities"; they are now taxed subjects of state.
(https://imgur.com/8QcW6LT.png)
If there is to be taxation; a qualification of the inherent power to do so, is that the proceeds of such levy, should provide for the general welfare of the taxed parties. This should include both listing on the reference UI and access worker-funded public API nodes.
As revenue raised - for the chain - by gateways will increase with their increased traffic. I propose explicitly excluding gateways from "commercial use". While current traffic is low, perhaps this means this worker should include a budget for "potential" increase in load handling of gateway traffic; to be return to chain in the event it is not needed.
-
Total budget:
30,600 USD (215,179 CNY)
Please quote additional budget requirements for the same worker, except no restrictions on gateways providers: GDEX, RUDEX, XBTSX, DEEX, etc.
There is no such need that private owned for-profit companies such as gateways are listing nodes for public access.
The nature of the argument: "gateways should be self funded because they keep all their profits", is no longer relevant with BSIP86.
These are no longer "independent for profit entities"; they are now taxed subjects of state.
(https://imgur.com/8QcW6LT.png)
If there is to be taxation; a qualification of the inherent power to do so, is that the proceeds of such levy, should provide for the general welfare of the taxed parties. This should include both listing on the reference UI and access worker-funded public API nodes.
As revenue raised - for the chain - by gateways will increase with their increased traffic. I propose explicitly excluding gateways from "commercial use". While current traffic is low, perhaps this means this worker should include a budget for "potential" increase in load handling of gateway traffic; to be return to chain in the event it is not needed.
As BSIP86 is not implemented yet, and new core worker still to go on chain/approved, hence worker will keep the "commercial limits" until BSIP86 is part of bitshares-core software mainnet release.
Best regards,
Ross Walker
APAsia.tech
-
The worker has been posted to the blockchain.
Read the full details here: https://www.bitshares.foundation/workers/2020-02-infrastructure (https://www.bitshares.foundation/workers/2020-02-infrastructure)
Voting for worker proposals: Votes can be done via the reference wallet. Visit Menu -> Votes -> Workers or enter your account name in the link https://wallet.bitshares.org/#/voting (https://wallet.bitshares.org/#/voting)
This worker proposal has id 1.14.253 and 202002-infrastructure.
Chee®s
-
+5%
-
I am a supporter for your great work DL...
-
I am a supporter for your great work DL...
Much appreciated, but this is all done by Stefan and Xeroc, I'm just being supportive and collaborative since we really have no other options.
Despite 20+ active witnesses, 3 operational gateways and God knows how many community ventures, but I'm able today to reach just 4 API nodes from wallet.bitshares.org.
This worker is a must or some chaotic rules applied at least on witnesses when it comes to API availability.
Chee®s