source
Full API node update - 31/5/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 foran 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 websocketsupport 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 nodes who did not answer
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://rpc.steemviz.com | 0.60 | 0.19.3 |
wss://steemd.pevo.science | 0.68 | 0.19.2 |
wss://rpc.buildteam.io | 0.69 | 0.19.3 |
wss://steemd.privex.io | 0.72 | 0.19.3 |
wss://steemd.minnowsupportproject.org | 0.72 | 0.19.3 |
wss://appbasetest.timcliff.com | 0.81 | 0.19.4 |
https://api.steemitdev.com | 1.74 | 0.19.4 |
https://rpc.buildteam.io | 1.77 | 0.19.3 |
https://api.steemitstage.com | 1.83 | 0.19.4 |
https://api.steemit.com | 2.21 | 0.19.4 |
https://api.steem.house | 2.75 | 0.19.4 |
https://rpc.steemviz.com | 4.59 | 0.19.3 |
https://steemd.pevo.science | 5.54 | 0.19.2 |
https://steemd.minnowsupportproject.org | 9.50 | 0.19.3 |
https://steemd.privex.io | 10.11 | 0.19.2 |
https://appbasetest.timcliff.com | 11.13 | 0.19.4 |
wss://gtg.steem.house:8090 | 47.17 | 0.19.3 |
https://gtg.steem.house:8090 | 82.13 | 0.19.3 |
https://rpc.curiesteem.com | 115.75 | 0.0.0 |
Streaming blocks
In this test, it is measured how many blocks a node can stream in 60 seconds.
List of working nodes - block streaming
node | N blocks | Duration [s] |
---|---|---|
wss://steemd.minnowsupportproject.org | 384 | 120.4 |
https://api.steemitstage.com | 186 | 122.7 |
https://api.steemitdev.com | 186 | 123.4 |
https://api.steemit.com | 181 | 123.1 |
wss://gtg.steem.house:8090 | 115 | 131.8 |
https://api.steem.house | 101 | 124.8 |
https://rpc.steemviz.com | 47 | 126.9 |
https://rpc.buildteam.io | 42 | 123.4 |
https://steemd.minnowsupportproject.org | 33 | 134.1 |
Account history
In this test, it is measured how many account operation a node can stream in 60 seconds.
List of working nodes - account history
node | N acc hist | Duration [s] |
---|---|---|
wss://rpc.steemviz.com | 56460 | 121.9 |
wss://steemd.minnowsupportproject.org | 49895 | 121.5 |
wss://steemd.privex.io | 48986 | 121.5 |
wss://rpc.buildteam.io | 47976 | 121.2 |
wss://steemd.pevo.science | 31311 | 121.1 |
https://api.steemitdev.com | 30099 | 121.6 |
https://api.steemitstage.com | 29190 | 121.6 |
https://api.steemit.com | 24140 | 121.4 |
https://rpc.steemviz.com | 16666 | 121.6 |
https://api.steem.house | 15050 | 121.1 |
wss://gtg.steem.house:8090 | 11919 | 126.8 |
https://steemd.minnowsupportproject.org | 10606 | 122.7 |
https://steemd.privex.io | 607 | 139.8 |
wss://appbasetest.timcliff.com | 566 | 7.3 |
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
node | Duration [s] |
---|---|
wss://appbasetest.timcliff.com | -1.000 |
https://steemd.pevo.science | -1.000 |
wss://steemd.pevo.science | -1.000 |
wss://steemd.privex.io | -1.000 |
https://appbasetest.timcliff.com | -1.000 |
wss://steemd.minnowsupportproject.org | 0.052 |
wss://rpc.steemviz.com | 0.068 |
wss://rpc.buildteam.io | 0.126 |
wss://gtg.steem.house:8090 | 0.137 |
https://rpc.buildteam.io | 0.189 |
https://api.steemitdev.com | 0.223 |
https://api.steemit.com | 0.223 |
https://api.steemitstage.com | 0.226 |
https://api.steem.house | 0.304 |
https://gtg.steem.house:8090 | 0.393 |
https://rpc.steemviz.com | 0.719 |
https://steemd.privex.io | 1.349 |
https://steemd.minnowsupportproject.org | 1.636 |
https://rpc.curiesteem.com | 3.411 |
Summary of working nodes
A node is working, when:
- returns data within 60 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
node | block rank | hist rank | call rank |
---|---|---|---|
wss://steemd.minnowsupportproject.org | 1 | 2 | 1 |
https://api.steemit.com | 2 | 6 | 6 |
wss://gtg.steem.house:8090 | 3 | 9 | 4 |
https://api.steem.house | 4 | 8 | 7 |
https://rpc.steemviz.com | 5 | 7 | 9 |
https://steemd.minnowsupportproject.org | 7 | 10 | 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://steemd.minnowsupportproject.org', 'https://api.steemit.com', 'wss://gtg.steem.house:8090', 'https://api.steem.house', 'https://rpc.steemviz.com', 'https://steemd.minnowsupportproject.org']
Receive fully working nodes from json_metadata
The nodes are also stored in the json_metadata
variable in each post from @fullnodeupdate.
Example code for python:
from beem.account import Account
acc = Account("fullnodeupdate")
latest_post = acc.get_blog(limit=1, raw_data=False)[0]
nodes = latest_post.json_metadata["nodes"]
acc.steem.set_default_nodes(nodes)
✅ @fullnodeupdate, I gave you an upvote on your first post! Please give me a follow and I will give you a follow in return!
Please also take a moment to read this post regarding bad behavior on Steemit.
Hi. Can you clarify what is tested for
List of working nodes - block streaming
? I don't seeappbasetest.timcliff.com
in the list.Also, can you clarify what the numbers for
appbasetest.timcliff.com
mean inList of working nodes - account history
compared to the other nodes?I will try to improve the script and be more informative.
List of working nodes - block streaming
is a list of all nodes who could stream at least one block in 60s.wss://appbasetest.timcliff.com was able to do this, https://appbasetest.timcliff.com was to slow.
List of working nodes - account history
is a list of all nodes who could stream at list one account operation in 60 s.The
-1
inList of working nodes - api calls
means that the node was needing to long or the output was empty.I will increase the timeout from 60 seconds to 120 seconds.
Do you like the general idea to automatically generate a node report in this place?
Yes, I see value in it.
are you sure the buildteam.io is not the cryptodrive , i didnt know the markymark got a node.
https://steemit.com/buildteam/@buildteam/buildteam-high-performance-rpc-full-node-cluster
Markymark operates it.