Gonka mainnet · Always on · Completely free

Fast, reliable RPC
for Gonka apps.

A community-operated, open-access gateway to the Gonka blockchain. No API key required. Full chain history, CosmWasm, indexed data — backed by multiple independent nodes.

Get started — it's free See docs
INDEX // CHAIN DATA VOLUME
Loading…
API // WHAT YOU CAN QUERY See docs
[RPC] Chain JSON-RPC Blocks, validators, ABCI
[REST] Cosmos REST API Bank, staking, tx broadcast
[TX] Transaction lookup By hash, instant
[BLOCK] Block explorer feed All txs in a height
[ADDR] Address history Full paginated tx feed
[SLASH] Slashing events Filterable by validator
[HW] Hardware registry Node registrations & snapshots
[EPOCH] Epoch performance Per-epoch counters by participant

How traffic flows

YOUR REQUEST rpc.gonka.gg health checks smart caching auto failover CosmWasm routing WebSocket proxy status scrubbing Feather RPC #2 gonkalabs/feather · archive Hyperfusion gonka.spv.re · community 6block gonka04.6block.com · community Feather RPC #1 gonkalabs/feather · archive node1.gonka.ai public · CosmWasm fallback

Powered by

Loading…

Why teams choose gonka RPC

Completely free — no catch

No API key required. No credit card. No rate-limit surprises. Just point at rpc.gonka.gg and go. Optional account registration lets you track usage if you need it.

Multi-node, high availability

Requests are load-balanced across 2 dedicated Feather RPC nodes, the Hyperfusion community node, and public fallbacks — with automatic health-checking and failover.

Full history, not just the tip

Archive nodes with pre-indexed transactions, addresses, hardware stats, and epoch metrics. Sub-50ms on complex queries that would take seconds on a raw node.

One endpoint for everything

Chain RPC, REST API, CosmWasm, and indexed data behind one base URL. Change a single config line and your whole app is on gonka RPC.

Built for every use case

Try the API — indexed lookups

Real queries against the live index. No API key needed — just copy any command into a terminal and run it. Response times shown are typical for warm queries.

Transaction by hash

~125ms

Full transaction details by hash — ideal for explorers and support.


        

        

          

            
All transactions in a block

            ~110ms
          

          
Every transfer in a block height, ordered as they appeared on chain.

          

        

        

          

            
Address transaction history

            ~0.5s
          

          
Full paginated history for any wallet — sent and received, newest first.

          

        

        

          

            
Slashing events

            ~130ms
          

          
Slash records across the chain — filter by validator and height range.

          

        

        

          

            
Hardware node registry

            ~100ms
          

          
Current hardware registrations for a participant — GPU models, status, timestamps.

          

        

        

          

            
Hardware snapshots

            ~120ms
          

          
Per-epoch hardware history — scope by epoch for fast results.

          

        

        

          

            
Epoch performance

            ~150ms
          

          
Per-epoch inference and rewards counters by participant, with optional epoch range filter.

          

        

      

      

        Full endpoint reference with parameters and examples: API documentation →
      

    


    

      
Get started instantly

      

        Optionally create an account to track usage in the portal.
        See all endpoints →