Full API node update - 1/6/2018

@fullnodeupdate provides daily updates about the state of all available full API node server.

What is a full RPC node and why it is necessary

A full RPC node contains all STEEM blocks and several databases, in which e.g. account-related transactions, followers for an account, all posts of a blog from an account, .... are stored.
Without nodes, the steemit site would be down, there would be no bid-bots and services as steemauto.com or GINAbot would not work.

Complete RPC node list

All nodes have support for https://. For nodes with websocket support (WSS is yes), wss:// has to put in front. All which have websocket support are checked twice (1x https and 1x wss).
The node version was read out from the server itself, and when this was not possible (node did not respond) a question mark is shown instead.

Server	WSS	Ran By	Info
steemd.privex.io	yes	privex	post
steemd.pevo.science	yes	pharesim	post
rpc.steemliberator.com	yes	netuoso	post
rpc.buildteam.io	yes	themarkymark	post
gtg.steem.house:8090	yes	gtg	post
api.steem.house	no	gtg	post
rpc.steemviz.com	yes	ausbitbank	post
seed.bitcoiner.me	yes	bitcoiner	link
steemd.steemgigs.org	yes	steemgigs	post
steemd.minnowsupportproject.org	yes	followbtcnews	post
rpc.curiesteem.com	no	curie	post
appbasetest.timcliff.com	yes	timcliff	post
api.steemit.com	no	Steemit Inc.	-
api.steemitstage.com	no	Steemit Inc.	-
api.steemitdev.com	no	Steemit Inc.	-

api.steemitstage.com and api.steemitdev.com may contain newer node versions and should be used only with care.

get_config API call

This API call is available on 0.19.3 and 0.19.4 nodes.

List of failing nodes

This table includes a list of all nodes which were not able to answer to a get_config api call within 300 seconds.

node	error
https://steemd.steemgigs.org	NumRetriesReached
wss://steemd.steemgigs.org	NumRetriesReached
https://seed.bitcoiner.me	NumRetriesReached
wss://seed.bitcoiner.me	NumRetriesReached
wss://rpc.steemliberator.com	NumRetriesReached
https://rpc.steemliberator.com	NumRetriesReached

List of working nodes

node	duration [s]	version
wss://steemd.pevo.science	0.23	0.19.2
wss://steemd.minnowsupportproject.org	0.24	0.19.3
wss://rpc.buildteam.io	0.34	0.19.3
wss://rpc.steemviz.com	0.73	0.19.3
wss://appbasetest.timcliff.com	1.34	0.19.4
wss://steemd.privex.io	1.35	0.19.2
https://api.steemit.com	1.66	0.19.4
https://api.steemitdev.com	1.75	0.19.4
https://steemd.pevo.science	1.79	0.19.2
https://api.steemitstage.com	1.80	0.19.4
https://api.steem.house	2.89	0.19.4
wss://gtg.steem.house:8090	3.97	0.19.3
https://rpc.buildteam.io	5.78	0.19.3
https://gtg.steem.house:8090	8.58	0.19.3
https://steemd.minnowsupportproject.org	9.09	0.19.3
https://rpc.steemviz.com	9.80	0.19.3
https://rpc.curiesteem.com	11.96	0.19.3
https://appbasetest.timcliff.com	12.11	0.19.4
https://steemd.privex.io	69.77	0.19.3

Streaming blocks

In this test, it is measured how many blocks a node can stream in 300 seconds.

List of working nodes - block streaming

This table includes all nodes which were able to stream at least one block within 300 seconds.

node	N blocks	Duration [s]
wss://rpc.steemviz.com	4502	300.2
wss://steemd.minnowsupportproject.org	4455	302.2
wss://steemd.pevo.science	4329	300.3
wss://steemd.privex.io	3861	300.3
wss://rpc.buildteam.io	3302	300.4
https://api.steemit.com	980	301.6
https://api.steemitstage.com	939	301.8
https://api.steemitdev.com	937	301.9
wss://gtg.steem.house:8090	439	341.6
https://rpc.buildteam.io	426	301.7
https://rpc.steemviz.com	192	305.0
https://steemd.minnowsupportproject.org	99	309.9
https://gtg.steem.house:8090	61	467.0
https://rpc.curiesteem.com	38	350.4

Account history

In this test, it is measured how many account operation a node can stream in 300 seconds.

List of working nodes - account history

This table includes all nodes which were able to stream at least one account history operation within 300 seconds.

node	N acc hist	Duration [s]
wss://steemd.privex.io	236240	361.0
wss://steemd.minnowsupportproject.org	127766	303.0
wss://rpc.steemviz.com	127362	300.8
wss://rpc.buildteam.io	109485	300.3
wss://steemd.pevo.science	87366	300.4
https://api.steemitdev.com	66257	301.1
https://api.steemitstage.com	65853	301.2
https://api.steemit.com	60601	300.9
https://rpc.buildteam.io	59793	300.7
wss://gtg.steem.house:8090	50804	303.9
https://rpc.steemviz.com	45855	301.6
https://api.steem.house	38179	301.2
https://steemd.minnowsupportproject.org	26059	301.6
https://rpc.curiesteem.com	11818	304.9
https://gtg.steem.house:8090	8586	312.5
wss://appbasetest.timcliff.com	573	9.0

Receiving a vote, a comment, and an account

In this test, the mean duration to receive an account, a comment, and a vote is measured.

List of working nodes - api calls

This table includes all nodes which were able to answer all three api calls within 300 seconds.

node	Duration [s]
wss://rpc.steemviz.com	0.061
wss://steemd.minnowsupportproject.org	0.061
wss://rpc.buildteam.io	0.075
wss://gtg.steem.house:8090	0.124
https://api.steemitdev.com	0.138
https://api.steemitstage.com	0.140
https://api.steemit.com	0.152
https://api.steem.house	0.324
https://rpc.buildteam.io	0.363
https://gtg.steem.house:8090	0.553
https://rpc.steemviz.com	0.733
https://steemd.minnowsupportproject.org	1.008
https://rpc.curiesteem.com	1.172

Summary of working nodes

A node is working, when:

• returns data within 300 seconds,
• blocks can be streamed,
• account history is possible,
• votes, a comment, an account can successfully be fetched and are not empty.
  The nodes in the following table are ranked by the mean rank of all three node tables shown above.
  This table includes only nodes which were passing all three tests sucessfully.

node	block rank	hist rank	call rank
wss://rpc.steemviz.com	1	3	1
wss://steemd.minnowsupportproject.org	2	2	2
wss://rpc.buildteam.io	5	4	3
https://api.steemit.com	6	6	5
wss://gtg.steem.house:8090	7	8	4
https://rpc.buildteam.io	8	7	7
https://rpc.steemviz.com	9	9	9
https://steemd.minnowsupportproject.org	10	11	10
https://gtg.steem.house:8090	11	13	8
https://rpc.curiesteem.com	12	12	11

Set fully working nodes with beempy

https://api.steemitstage.com, https://api.steemitdev.com and nodes with not working results were excluded.

beempy set nodes "['wss://rpc.steemviz.com', 'wss://steemd.minnowsupportproject.org', 'wss://rpc.buildteam.io', 'https://api.steemit.com', 'wss://gtg.steem.house:8090', 'https://rpc.buildteam.io', 'https://rpc.steemviz.com', 'https://steemd.minnowsupportproject.org', 'https://gtg.steem.house:8090', 'https://rpc.curiesteem.com']"

Receive fully working nodes from json_metadata of the @fullnodeupdate account

The nodes are also stored in the json_metadata variable of the @fullnodeupdate account.
The nodes inside the account metadata are updated every hour.
The json_metadata includes the following data:

• nodes - list of nodes that passed all tests.
• node_version - node version of all nodes that answered the get_config break.
• failing_nodes - list of nodes that did not answer the get_config call.
• block_test - test results of the block streaming test.
• acc_hist_test - test results of the account history streaming test.
• api_call_test - test results of the three api calls.
• parameter - used beem and test parameter.

https://api.steemitstage.com, https://api.steemitdev.com and nodes with not working results were excluded.
Example code for python:

from beem.account import Account
import json
acc = Account("fullnodeupdate")
nodes = json.loads(acc["json_metadata"])["nodes"]
acc.steem.set_default_nodes(nodes)

image source