Full API node update - (7/6/2018)
2018-06-06T18:00:03 - 2018-06-07T18:00:02)
@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 utopian-io, 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 30 seconds.
| node | hours with failure | percentage |
|---|---|---|
| wss://rpc.steemviz.com | 1/23 | 4.3 % |
| https://rpc.steemviz.com | 1/23 | 4.3 % |
| https://gtg.steem.house:8090 | 1/23 | 4.3 % |
| https://rpc.curiesteem.com | 2/23 | 8.7 % |
| https://steemd.steemgigs.org | 23/23 | 100.0 % |
| wss://steemd.steemgigs.org | 23/23 | 100.0 % |
| https://seed.bitcoiner.me | 23/23 | 100.0 % |
| wss://seed.bitcoiner.me | 23/23 | 100.0 % |
| wss://rpc.steemliberator.com | 23/23 | 100.0 % |
| https://rpc.steemliberator.com | 23/23 | 100.0 % |
| https://api.steemitdev.com | 3/23 | 13.0 % |
| https://appbasetest.timcliff.com | 23/23 | 100.0 % |
| https://steemd.privex.io | 12/23 | 52.2 % |
| wss://appbasetest.timcliff.com | 23/23 | 100.0 % |
List of working nodes (At least once in the last 24h)
| node | min. time [s] | max. time [s] | version |
|---|---|---|---|
| wss://rpc.steemviz.com | 0.19 | 1.01 | 0.19.3 |
| wss://steemd.minnowsupportproject.org | 0.23 | 2.24 | 0.19.3 |
| wss://steemd.pevo.science | 0.25 | 7.63 | 0.19.2 |
| wss://steemd.privex.io | 0.31 | 63.00 | 0.19.2 |
| wss://rpc.buildteam.io | 0.33 | 1.26 | 0.19.3 |
| https://api.steemit.com | 1.63 | 1.82 | 0.19.4 |
| https://rpc.buildteam.io | 1.11 | 33.95 | 0.19.3 |
| wss://gtg.steem.house:8090 | 0.57 | 100.89 | 0.19.3 |
| https://api.steem.house | 2.81 | 3.78 | 0.19.4 |
| https://rpc.steemviz.com | 4.56 | 13.69 | 0.19.3 |
| https://steemd.minnowsupportproject.org | 9.07 | 9.60 | 0.19.3 |
| https://steemd.pevo.science | 3.48 | 14.90 | 0.19.2 |
| https://gtg.steem.house:8090 | 6.58 | 103.55 | 0.19.3 |
| https://rpc.curiesteem.com | 8.28 | 111.42 | 0.19.3 |
| https://api.steemitdev.com | 1.73 | 6.82 | 0.19.4 |
| https://steemd.privex.io | 12.09 | 118.63 | 0.19.3 |
Streaming blocks
In this test, it is measured how many blocks a node can stream in 30 seconds.
List of working nodes - block streaming
This table includes all nodes which were able to stream at least one block within 30 seconds.
The achieved minimum and the maximum blocks per seconds values are shown.
| node | min. block/s | max. block/s |
|---|---|---|
| wss://rpc.steemviz.com | 7.6 | 15.8 |
| wss://steemd.minnowsupportproject.org | 12.4 | 15.8 |
| wss://steemd.pevo.science | 9.3 | 15.6 |
| wss://steemd.privex.io | 3.4 | 15.4 |
| wss://rpc.buildteam.io | 7.0 | 12.6 |
| https://api.steemit.com | 2.8 | 3.1 |
| https://rpc.buildteam.io | 0.2 | 1.6 |
| wss://gtg.steem.house:8090 | 0.1 | 4.2 |
| https://api.steem.house | 0.9 | 1.0 |
| https://rpc.steemviz.com | 0.4 | 0.5 |
| https://steemd.minnowsupportproject.org | 0.2 | 0.2 |
| https://steemd.pevo.science | 0.1 | 0.2 |
| https://gtg.steem.house:8090 | 0.0 | 0.6 |
| https://rpc.curiesteem.com | 0.0 | 0.2 |
| https://api.steemitdev.com | 2.3 | 3.1 |
| https://steemd.privex.io | 0.0 | 0.0 |
Account history
In this test, it is measured how many account operation a node can stream in 30 seconds.
List of working nodes - account history
This table includes all nodes which were able to stream at least one account history operation within 30 seconds.
The achieved minimum and the maximum account transaction per seconds values are shown.
| node | min. hist/s | max. hist/s |
|---|---|---|
| wss://rpc.steemviz.com | 389.6 | 631.7 |
| wss://steemd.minnowsupportproject.org | 382.4 | 916.8 |
| wss://steemd.pevo.science | 179.7 | 619.4 |
| wss://steemd.privex.io | 269.4 | 811.8 |
| wss://rpc.buildteam.io | 307.8 | 779.0 |
| https://api.steemit.com | 186.3 | 301.2 |
| https://rpc.buildteam.io | 21.1 | 451.3 |
| wss://gtg.steem.house:8090 | 30.4 | 335.7 |
| https://api.steem.house | 109.3 | 132.1 |
| https://rpc.steemviz.com | 133.6 | 167.5 |
| https://steemd.minnowsupportproject.org | 46.8 | 71.3 |
| https://steemd.pevo.science | 30.5 | 54.8 |
| https://gtg.steem.house:8090 | 0.0 | 75.5 |
| https://rpc.curiesteem.com | 3.6 | 65.8 |
| https://api.steemitdev.com | 206.7 | 317.6 |
| https://steemd.privex.io | 4.0 | 12.2 |
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 30 seconds.
The achieved minimum and the maximum mean time durctions are shown.
| node | Min. time [s] | Max. time [s] |
|---|---|---|
| wss://rpc.steemviz.com | 0.034 | 0.163 |
| wss://steemd.minnowsupportproject.org | 0.045 | 0.295 |
| wss://steemd.pevo.science | 0.039 | 0.269 |
| wss://steemd.privex.io | 0.036 | 0.137 |
| wss://rpc.buildteam.io | 0.049 | 0.215 |
| https://api.steemit.com | 0.401 | 0.506 |
| https://rpc.buildteam.io | 0.367 | 1.074 |
| wss://gtg.steem.house:8090 | 0.160 | 3.976 |
| https://api.steem.house | 1.046 | 1.540 |
| https://rpc.steemviz.com | 1.804 | 2.599 |
| https://steemd.minnowsupportproject.org | 3.600 | 4.115 |
| https://steemd.pevo.science | 1.930 | 5.222 |
| https://gtg.steem.house:8090 | 1.241 | 23.445 |
| https://rpc.curiesteem.com | 3.620 | 40.480 |
| https://api.steemitdev.com | 0.408 | 0.477 |
| https://steemd.privex.io | 3.856 | 24.818 |
Summary of working nodes
A node is working, when it could fullfil at least once in the last 24h the following conditions:
- returned data within 30 seconds,
- blocks could be streamed,
- account history was possible,
- votes, a comment, an account could successfully be fetched and were 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 | score |
|---|---|---|---|---|
| wss://rpc.steemviz.com | 3 | 1 | 2 | 152.5 |
| wss://steemd.minnowsupportproject.org | 1 | 2 | 4 | 147.5 |
| wss://steemd.pevo.science | 4 | 3 | 3 | 135.0 |
| wss://rpc.buildteam.io | 2 | 5 | 5 | 132.5 |
| wss://steemd.privex.io | 5 | 4 | 1 | 115.0 |
| https://api.steemit.com | 6 | 6 | 8 | 107.5 |
| https://rpc.buildteam.io | 8 | 7 | 9 | 90.0 |
| https://api.steemitdev.com | 7 | 15 | 6 | 85.0 |
| https://api.steem.house | 9 | 9 | 10 | 82.5 |
| wss://gtg.steem.house:8090 | 12 | 8 | 7 | 70.0 |
| https://rpc.steemviz.com | 10 | 10 | 11 | 70.0 |
| https://steemd.minnowsupportproject.org | 13 | 11 | 13 | 50.0 |
| https://steemd.pevo.science | 14 | 12 | 12 | 50.0 |
| https://gtg.steem.house:8090 | 11 | 13 | 14 | 40.0 |
| https://rpc.curiesteem.com | 15 | 14 | 15 | 22.5 |
| https://steemd.privex.io | 16 | 16 | 16 | 10.0 |
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://steemd.pevo.science', 'wss://rpc.buildteam.io', 'wss://steemd.privex.io', 'https://api.steemit.com', 'https://rpc.buildteam.io', 'https://api.steem.house', 'wss://gtg.steem.house:8090', 'https://rpc.steemviz.com', 'https://steemd.minnowsupportproject.org', 'https://steemd.pevo.science', 'https://gtg.steem.house:8090', 'https://rpc.curiesteem.com', 'https://steemd.privex.io']"
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.failing_nodes- list of nodes that did not answer theget_configcall.report- test results.parameter- usedbeemand test parameter.
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)
If you like what I'm doing, please consider @holger80 as one of your witnesses.You can use steemconnect.com for approve your vote or go to https://steemit.com/~witnesses and enter my name into the vote field:
