VargaMeshDEVELOPER HUB · MAINNET
CHECKING API
BUILD ON VMESH

Developer infrastructure for VargaMesh.

One place for the public mainnet API, integration patterns, wallet/payment flows, VargaProof, mining telemetry and reference SDKs.

Start building →Live OpenAPICore on GitHub ↗
PUBLIC APIAPI v1
NETWORKVMESH Mainnet
BASE URL/api/v1
OVERVIEW

Public building blocks

Use the public HTTPS layer for apps and dashboards. Keep Core RPC private. Wallet keys stay in the client.

GET

Public API

Chain, block, transaction, address, supply, fee and mining telemetry over versioned JSON endpoints.

SELF-CUSTODY

Wallet integrations

Read public UTXOs, construct and sign transactions locally, then submit only signed raw transaction hex.

VPF1

VargaProof

Hash files locally and anchor only a SHA-256 digest. Files and filenames do not need to leave the client.

5 MINUTES

Quickstart

1. Check the network

curl -fsS https://vargamesh.com/api/v1/health
curl -fsS https://vargamesh.com/api/v1/status
curl -fsS https://vargamesh.com/api/v1/supply

2. Read from JavaScript

const base = 'https://vargamesh.com/api/v1';
const r = await fetch(base + '/status');
if (!r.ok) throw new Error(`HTTP ${r.status}`);
console.log(await r.json());
No API key is required for the documented public endpoints. Treat the API as public infrastructure, not as a place to store secrets.
BOUNDARIES

Recommended architecture

Browser / Android / Desktop / Merchant integration
                    │
                    │ HTTPS JSON
                    ▼
        https://vargamesh.com/api/v1
                    │
          public integration layer
                    │
        ┌───────────┴───────────┐
        ▼                       ▼
  chain/index data        signed TX broadcast

Private infrastructure boundary
────────────────────────────────────────────────
VargaMesh Core RPC :29667  → localhost/service network only
wallet keys / WIF / seeds  → client-side only
READ-ONLY PLAYGROUND

Try the API

The explorer deliberately supports GET requests only. Write routes are documented separately.

Response
Choose an endpoint and run it.


REFERENCE
Endpoint map
GET/healthService health
GET/configMainnet parameters
GET/statusNode / chain status
GET/statsCombined network / pool stats
GET/blocks?limit=20Recent blocks
GET/block/{id}Height or hash
GET/tx/{txid}Transaction details
GET/address/{address}Address summary
GET/utxos/{address}Unspent outputs
GET/search?q=...Explorer search
GET/poolMining telemetry
GET/pool/minersMiner information
GET/pool/blocksPool block history
GET/supplyIssued / matured supply
GET/supply/circulatingPlain-text mature circulating supply
GET/supply/totalPlain-text total issued supply
GET/releasesCanonical software releases
GET/wallet-standardVMESH-HD-1 wallet standard
GET/feeFee information
GET/mining/address/{address}Coinbase payouts
POST/broadcastSigned raw transaction only
Live machine-readable specification: /api/v1/openapi.json ↗


CLIENTS
SDKs and starter clients
Wallet SDK
Reference wallet integration package published under the VargaMesh npm scope.
npm install @vargamesh/wallet-sdk
Reference API clients
This repository includes dependency-light JavaScript and Python clients for the public API.
sdk/javascript/
sdk/python/


PAYMENTS
VargaMesh Pay
A common URI lets browsers, QR codes and wallets describe the same VMESH payment request.
vargamesh:vm1q...?amount=12.5&label=Merchant&message=Invoice&reference=INV-4711
Merchant side
Generate a URI/QR using public address data only. A checkout must never need a WIF or private key.
Wallet side
Validate address and amount, show the exact payment, sign locally, then broadcast the signed transaction.
VargaMesh Pay repository ↗


PROOF OF EXISTENCE
VargaProof API
Verify
GET /api/v1/proof/lookup/{sha256}
GET /api/v1/proof/recent?limit=8
GET /api/v1/proof/status
Anchor
POST /api/v1/proof/anchor
Content-Type: application/json

{"sha256":"<64 hex characters>"}
Hash locally whenever possible. VPF1 stores the protocol marker plus the SHA-256 digest, not the original file.


MINING
Mining integrations
The public API exposes pool and payout telemetry. Miners connect separately through Stratum.
stratum+tcp://vargamesh.com:3933

GET /api/v1/pool
GET /api/v1/pool/miners
GET /api/v1/pool/blocks
GET /api/v1/mining/address/{address}?limit=100&scan=500


NODE OPERATORS
Core / RPC integration
Do not expose Core RPC directly to browsers or the public internet. Public apps should call the HTTPS API. Core RPC credentials remain server-side.
P2P
Public node networking uses the VargaMesh P2P service. P2P is not an application API.
TCP 29666
Core RPC
Administrative/node RPC should be bound to localhost or a protected service network.
127.0.0.1:29667


SECURITY MODEL
Integration checklist
AreaDoDo not
KeysSign locallySend WIF/private keys to an API
RPCKeep on localhost/service networkExpose arbitrary RPC publicly
BroadcastSubmit signed raw hexAsk server to sign user funds
ProofHash files locallyUpload files when only a digest is needed
WebUse HTTPS and validate inputsTrust payment parameters silently