In order for Steem apps and sites to work, they must connect to full nodes over an API.
Several witnesses including myself are providing such nodes.
Here are the ones I know of:
| Connection | Details |
|---|---|
| wss://steemd.steemit.com | Provider - @steemit |
| wss://steemd.steemitdev.com | Provider - @steemit |
| wss://node.steem.ws ws://node.steem.ws | Providers - @xeroc, @jesta Post - steem.ws - The public steem api cluster Status Page - https://steem.ws |
| wss://this.piston.rocks ws://this.piston.rocks | Provider - @xeroc Post - This.Piston.Rocks - Public Steem API for piston users and developers |
| wss://gtg.steem.house:8090 | Provider - @gtg Post - gtg.steem.house runs a full node with a public steem API |
| wss://seed.bitcoiner.me ws://seed.bitcoiner.me | Provider - @bitcoiner Post - bitcoiner - Witness Thread Status Page - https://bitcoiner.me |
Some nodes have an insecure option (ws) and may be ever slightly faster without the need to encrypt, but the secure option (wss) should be preferred.
I believe these have all common available plugins enabled, such as database_api, login_api, account_by_key_api, follow_api, and market_history_api.
As a note, there are plenty of seed nodes out there, but not all of them expose the RPC port for API calls over WebSockets, which is what frontends use.
Please let me know of any more I may be missing.
Example Usage
curl
To call an API function, say get_version from the login_api, you will use http(s) in place of ws(s):
curl --silent https://steemd.steemit.com --data '{"method": "call", "params": ["login_api", "get_version", []], "id": 0}' | jq
{
"id": 0,
"result": {
"blockchain_version": "0.16.3",
"steem_revision": "e21a808cb572330ed31ff159a031f3b32c156aeb",
"fc_revision": "5cfcb5c0d6ee6ba1acbb40d9de49effc25daf74f"
}
}
Note: jq is a very helpful utility to do queries on json and formats the output nicely.
piston
piston --node wss://steemd.steemit.com info
cli_wallet
cli_wallet -s wss://steemd.steemit.com
bitcoiner!