A high-available public GRIN API cluster for the Grin community.
Please consider the API as “beta” as of now, I am also working on the implementation of API v2 for the upcoming hard fork in January 2020.
- Wallets which need a full node
I have tested it with some of the available GRIN wallets:
grin-wallet 2.1.0 - can be used, no known problems
grin-wallet 3.0.0-beta.1 - can be used, no known problems
grin++ - not tested
Wallet 713 - not tested
Wimble - not tested
- Add grinnode.live to your Grin node for a fast sync
To Connect your GRIN Node use:
_$ cat grin-server.toml […] peers_preferred = [“184.108.40.206:3414”]
or use FQDN
_$ cat grin-server.toml […] peers_preferred = [“grinnode.live:3414”]
When hosting a Blockexplorer you can query the grinnode.live cluster using the documented GRIN API. (some commands are restricted to allowed users only, not allowed due to high load on the cluster or rate limited)
Public API querys
An HTTP(s) possibility to query the GRIN API
query first GRIN Block
We try to keep all nodes which are part of the cluster as archive-nodes.
Other query methods like “curl” or Python can also be used.
CORS is disabled as of December 2019 so you can also start using it for your Frontend or some other GRIN applications.
Public: One request per 10 seconds (no hard rate limit set yet)
If you need more requests per second of a white listing please contact me directly.
How is the High-Availability archived at grinnode.live?
We are using multiple Grin nodes across different data centers which are always synced to the Grin mainnet. All nodes are connected to a central configuration management to keep all servers updated and make the administration of such a cluster easy. We also added a private Meshnet between the nodes in order to access and transfer data in a secure way. Furthermore we are running an HAProxy in front of the HA-IP “220.127.116.11” address and grinnode.live domain in order to load balance all traffic accordingly to our reverse-proxies which then send the requests to a free Grinnode Server.
Please try to use the FQDN “grinnode.live” instead of the Ha-IP address if possible. This makes it easy for us to switch to new infrastructure if needed.
As of now we are not providing any GRIN floonet nodes or APIs.
Please report problems or features you want using the Github page or here.