Nano Public Nodes

Public and free-to-use API to access the Nano network without hosting your own Nano node.

Nano is a decentralized, secure, fast, and feeless cryptocurrency network. This site queries each of the below Public Nano Node APIs (from your browser) to give you a real-time view of the node's availability.

If you want a simple wallet to receive and send Nano, see the Unofficial Nano Wallets Guide.

If you want more information on running your own Nano node (public or private) as well as more resources on building with Nano, check the Official Nano Website.

If you want your node added to this list, email me or find me on Twitter @SomeNanoTweets.

This data is current and updates on every page refresh.

Sponsored by Nanswap Nodes - Nano Node API with free plan available
Name Tests Comments
Node Version Block Counts API Supports
"process"		 API Supports
"receivable"		 API Supports
"work_generate"		 Token Limited WebSocket
Setup		 WebSocket
Ping		 WebSocket
Subscribe
All		 WebSocket
Subscribe
Addresses

See lots of failed tests? Check your browser antivirus for a block of certain top level domains (TLDs) like ".cc"

You can also view more data on each test in your browser's console.

More Information

Node Version: Queries the node with action: version and compares against latest version of the Nano Node.

Block Counts: Queries the node with action: block_count and checks for uncomfirmed blocks. If there are a lot of unconfirmed blocks (see node_tests.js for specifics) the test fails. If there are only a few unconfirmed, the test is a partial success.

API Supports "process": Queries the node with action: process and checks that the node returns an error message indicating it attempted to process the block. I am not attempting to broadcast legitimate blocks for these tests.

API Supports "receivable": Queries the node with action: receivable and checks for valid return. In Nano Node v23.0, the "pending" terminology became deprecated and replaced with "receivable". Although Nano Nodes may have updated to or beyond V23.0, some have proxies that must be updated. This test shows which APIs support the new "receivable" action.

API Supports "work_generate": Queries the node with action: work_generate and checks for a returned work value. Many public nodes won't support this action because of the processing power costs. Some that allow limit requests via tokens/time will charge more than for a work_generate call than any other.

Token Limited: Queries the node with an arbitrary action and looks to see if a known token system is in use. Some public nodes use tokens (likely those that have implemented the NanoRPCProxy to prevent abuse of their free-to-use public node. In this test I check for the response data to include a value for requestsLimit.

WebSocket Setup: Attempts to connect to the WebSocket provided.

WebSocket Ping: Messages the WebSocket with a ping message as defined in the Nano docs. Watches for pong message back with corresponding id.

WebSocket Subscribe All: Messages the WebSocket with a a request to subscribe to confirmations (confirmation_type=active) without specifying any particular addresses, as shown in in the Nano docs. Watches for "ack" message back with corresponding id.

WebSocket Subscribe Addresses: Messages the WebSocket with a subscribe to confirmations (confirmation_type=active) for one specific address, as shown in in the Nano docs. Watches for "ack" message back with corresponding id.

Please note all tests error out after 10 seconds of no response.

First I'd like to point you to a "Getting Started" series of articles I wrote and published. They are a great place to start if you are just getting to know Nano.

And here are some additional resources that will help you BUIDL/develop/code with Nano, many of which I cite and rely on heavily in the above articles. This is certainly not a comprehensive list. It is mainly resources/tools that I have personally used and think provide the most value for people just getting into developing with Nano.

  • Official nano.org: Developer resources from the Nano Foundation.
  • Nano Documentation: If you are interacting with a Nano node, this is the documentation you need to be reading.
  • Nano Tools: A phenomenal list of tools (many of which are on this list) that will help you integrate Nano in whatever environment you are developing.
  • Nano on Github: All official releases of nodes/work servers/etc are found on the Github.
  • KeyTools: A wide variety of tools that are useful for learning about how the Nano protocol works. These tools can be used offline as well.
  • nanoo.tools: Another wide variety of tools that are useful for learning about how the Nano protocol works. Includes an RPC Playground that will let you query a public node (similar to how tests on this page are run).
  • Pippin Nano Wallet: Advertised as a "production-ready, high-performance developer wallet", this service can be used to as middleware to interact with your node or a public node. It provides wallet features such as send/receive and account management. While a Nano node allows you to interact with the network, a wallet is what maintains the state of your accounts.
  • Nano DPoW: Nano uses a hashing/proof of work system to combat spam in the network. While the POW is minimal compared to other cryptocurrencies, if you are developing on a minimum specs VPS/RPI/etc, you may not want to waste time calculating proof of work on your own. DPoW is a service that is free for non-commercial use, integrates seamlessly into Pippin, and provides a pool of GPU workers to give near instant POW actions. Great for hobby or just getting started.

If you have resources you think I should add, email me or find me on Twitter @SomeNanoTweets

Aww, thanks for the kind words.

I will gratefully allow you to buy me a beer. If you are so inclined, please donate here: nano_1somenanerzdzdbyr4y6x996qbo764ifxk8beuhphydmwn1agpzkwquqqick

So many side projects, and this is one of them. Here are some of the "todo" items for this site...

  • Make it prettier (help?)
  • Add an RPC Playground
  • Expand the number of actions tested
  • Integrate a faucet to enable testing with funds
  • Provide better "benchmark" testing