BitShares Forum

Main => Stakeholder Proposals => Topic started by: fav on December 01, 2017, 09:35:53 am

Title: Every witness providing a public API node gets my vote.
Post by: fav on December 01, 2017, 09:35:53 am
with a growing user base the struggle on the very few nodes is getting out of hand.

Witnesses, please provide public nodes to the reference wallet.

Post here if you do, I'll vote for you & do promo.
Title: Re: Every witness providing a public API node gets my vote.
Post by: xeroc on December 01, 2017, 11:10:31 am
Just a few more votes missing:
http://www.bitshares.foundation/workers/2017-12-infrastructure
Title: Re: Every witness providing a public API node gets my vote.
Post by: netdragonx on December 01, 2017, 05:10:19 pm
Yeah, it sounds like a solid proposal. Let's do it.
Title: Re: Every witness providing a public API node gets my vote.
Post by: sahkan on December 01, 2017, 08:04:44 pm
I am glad you are bringing this up. [member=120]xeroc[/member] 's worker needs votes ASAP. Most witnesses that run gateways provide public nodes. But that's not enough! My Public API node now runs at 66GB RAM and doubled the average open connections from last month. This is becoming the true cost of the infrastructure vs. running the witness node which can be now tweaked to run under 2GB RAM. I know [member=42801]startail[/member] also provides the API node but is not voted in. There was some talk among the devs about reducing the RAM requirement for the full nodes and that would help lower the cost of the full nodes because right now we are looking at 96GB minimum, 128GB recommended and 256GB to be safe and we need several of them to handle the traffic.
Title: Re: Every witness providing a public API node gets my vote.
Post by: Xeldal on December 01, 2017, 08:32:37 pm
I'm looking into maintaining a dedicated API node to add to the list.  Are there any basic guides or points to consider for optimizing the node beyond the most basic configuration?  It's easy enough to just turn one one but I'd like to know I'm getting the most out of it.
Title: Re: Every witness providing a public API node gets my vote.
Post by: leo-87 on December 02, 2017, 02:20:46 am
Hi!, i was doing some investigation about create a witness and a seed node, I have some doubts about the seed node and full node, is the full node used for a public API ?

This seeds node are just only for blockchain download and not for public API : http://status.bitsharesnodes.com ?
I hope grab some servers this weeks and get all the stuffs working, after that i will anounce my intentions to help the bitshares network, now i have a steem witness node and i really like the graphene ecosystem, would like to help all the dpos chains, hehe.


Thanks!

Title: Re: Every witness providing a public API node gets my vote.
Post by: rnglab on December 02, 2017, 06:12:20 am
Fair enough fav.

Although I don't agree to weigh just one single factor when voting; with the Infrastructure Worker proposal being delayed and the Elastic Search plugin under development, I appreciate any active action to fix a high priority bottleneck.

I'm going to work on this early next week, and will try bring Ansible playbooks as soon as possible to make full node deployments easier for everyone.
Title: Re: Every witness providing a public API node gets my vote.
Post by: ivandev on December 04, 2017, 09:50:15 am
Absolutely support Fav's initiative for making entry point more decentralized. Our team is always ready to assist and consult anyone, going to deploy public node. Just pm me or connect with our team in any of tm channels.

In any case, everyone always may rely on infrastructure of public nodes built by OpenLedger without any limitations. Feel free to use any of our aliases with or without adding "/ws" (for web sockets):
bitshares.openledger.info (http://bitshares.openledger.info)
dex.openledger.info (http://dex.openledger.info)
eu.openledger.info (http://eu.openledger.info)
openledger.co (http://openledger.co)
openledger.io (http://openledger.io)
openledger.hk (http://openledger.hk)

Current total load is around 20% of whole capacity. Most of nodes are located in EU.
Title: Re: Every witness providing a public API node gets my vote.
Post by: fav on December 05, 2017, 02:10:28 pm
Absolutely support Fav's initiative for making entry point more decentralized. Our team is always ready to assist and consult anyone, going to deploy public node. Just pm me or connect with our team in any of tm channels.

In any case, everyone always may rely on infrastructure of public nodes built by OpenLedger without any limitations. Feel free to use any of our aliases with or without adding "/ws" (for web sockets):
bitshares.openledger.info (http://bitshares.openledger.info)
dex.openledger.info (http://dex.openledger.info)
eu.openledger.info (http://eu.openledger.info)
openledger.co (http://openledger.co)
openledger.io (http://openledger.io)
openledger.hk (http://openledger.hk)

Current total load is around 20% of whole capacity. Most of nodes are located in EU.

voted for openledger witness.
Title: Re: Every witness providing a public API node gets my vote.
Post by: Fox on December 08, 2017, 02:28:55 am
API server now live: wss://api.vativ.io  (ws://52.179.155.209)

As load demands, I will add node(s) to a load balancer and publish the endpoint.
Title: Re: Every witness providing a public API node gets my vote.
Post by: sahkan on December 08, 2017, 04:13:05 am
API server now live: ws://52.179.155.209

As load demands, I will add node(s) to a load balancer and publish the endpoint.
Do you also provide a secure websocket on this ip?
Title: Re: Every witness providing a public API node gets my vote.
Post by: Xeldal on December 10, 2017, 09:43:24 pm
I've got a new API server up and running.

wss://kc-us-dex.xeldal.com/ws
Location: Kansas City Missouri, USA
2x E5-2670 128GB
Title: Re: Every witness providing a public API node gets my vote.
Post by: Fox on December 11, 2017, 08:10:04 pm
[member=43537]sahkan[/member] Yes, I have added a TLS cert for: wss://api.vativ.io

Please reach out if you encounter any issues.

I appreciate your votes.
Title: Re: Every witness providing a public API node gets my vote.
Post by: fav on December 11, 2017, 09:16:40 pm
[member=43537]sahkan[/member] Yes, I have added a TLS cert for: wss://api.vativ.io

Please reach out if you encounter any issues.

I appreciate your votes.

where's it located?
Title: Re: Every witness providing a public API node gets my vote.
Post by: Fox on December 12, 2017, 02:30:15 am
Currently the node is locat in East US. However, it can easily be migrated to a region most in need. May I receive your suggestion?
Title: Re: Every witness providing a public API node gets my vote.
Post by: sahkan on December 12, 2017, 03:35:44 am
Currently the node is locat in East US. However, it can easily be migrated to a region most in need. May I receive your suggestion?

That is great. Looks like it's in Boydton, Virginia USA. We finally have a strong API Nodes network in the USA. I counted 6 USA nodes now.
Title: Re: Every witness providing a public API node gets my vote.
Post by: fav on December 12, 2017, 08:09:14 am
please make sure to add a request to github to get your nodes listed
Title: Re: Every witness providing a public API node gets my vote.
Post by: startail on February 05, 2018, 05:20:47 pm
I am glad you are bringing this up. [member=120]xeroc[/member] 's worker needs votes ASAP. Most witnesses that run gateways provide public nodes. But that's not enough! My Public API node now runs at 66GB RAM and doubled the average open connections from last month. This is becoming the true cost of the infrastructure vs. running the witness node which can be now tweaked to run under 2GB RAM. I know [member=42801]startail[/member] also provides the API node but is not voted in. There was some talk among the devs about reducing the RAM requirement for the full nodes and that would help lower the cost of the full nodes because right now we are looking at 96GB minimum, 128GB recommended and 256GB to be safe and we need several of them to handle the traffic.

Thanks for the mention, I do indeed run an access node on wss://bitshares.crypto.fans, located in Munich Germany, and has been in the clients access node list since its start. Since I'm still not an active witness, but found the lack of accessible nodes for the clients to few, it's just a connection node running with a little less memory and capabilities than a full API node.

I put it online at the time there wheren't that many access nodes available on the network, and it's been running stable since then.

It's running on an optimized server with ~20GB memory usage at the moment, and is heavly used by the community.
I'm looking at expanding towards a public API and faster access node, but so far I've haven't had the money to put out a bigger server(s) for this as I'm not gaining anything back for it.

However, I intend to start up a full featured node on a dedicated instance with full memory usage for the community in the soon future.
Title: Re: Every witness providing a public API node gets my vote.
Post by: Bangzi on May 15, 2018, 02:58:43 pm
bangzi

API Node:
wss://btsfullnode.bangzi.info/ws (Germany)
Title: Re: Every witness providing a public API node gets my vote.
Post by: btspp on April 11, 2019, 11:18:32 am
btspp-witness

wss://api.weaccount.cn  (China)
Title: Re: Every witness providing a public API node gets my vote.
Post by: vianull on July 10, 2019, 09:50:50 am
witness.hiblockchain

wss://api.bts.ai (China)
Title: Re: Every witness providing a public API node gets my vote.
Post by: abit on July 11, 2019, 06:41:17 pm
btspp-witness

wss://api.weaccount.cn  (China)
Please create a pull request to https://github.com/dls-cipher/bitshares-ui/blob/develop/app/api/apiConfig.js
Title: Re: Every witness providing a public API node gets my vote.
Post by: btspp on July 12, 2019, 01:56:47 am
btspp-witness

wss://api.weaccount.cn  (China)
Please create a pull request to https://github.com/dls-cipher/bitshares-ui/blob/develop/app/api/apiConfig.js

Already submitted, the new version of ui should already be included.