DEVELOPER API

Build with VargaMesh

Versioned, readable JSON endpoints for explorers, dashboards, monitoring and integrations.

OpenAPI JSON Health endpoint

REFERENCE

Public API reference

Base URL: https://vargamesh.com/api/v1

GET/health

Service health

GET/config

Mainnet parameters

GET/status

Node and chain status

GET/blocks

Recent blocks

GET/block/{id}

Block by height or hash

GET/tx/{txid}

Transaction detail

GET/address/{address}

Address summary and UTXOs

GET/utxos/{address}

Spendable/unspent outputs

GET/pool

Public mining telemetry

GET/pool/blocks

Recent tagged pool blocks

GET/supply

Issuance and mature supply

GET/supply/circulating

Plain-text mature circulating supply

GET/supply/total

Plain-text total issued supply

GET/releases

Canonical software release manifest

GET/wallet-standard

VMESH-HD-1 machine-readable wallet standard

GET/fee

Transaction fee information

GET/proof/status

VargaProof service and index status

GET/proof/lookup/{sha256}

Verify an on-chain proof by SHA-256

GET/proof/recent

Recent confirmed VPF1 anchors

GET/proof/openapi.json

VargaProof OpenAPI specification

VARGAPROOF API

Digests only, never files

POST /api/v1/proof/anchor accepts JSON containing exactly one 64-character SHA-256 digest. The public page hashes files locally in the browser.

fetch('/api/v1/proof/anchor', {
  method: 'POST',
  headers: {'Content-Type': 'application/json'},
  body: JSON.stringify({sha256: '…'})
})

VPF1

36 bytes on-chain

56504631 (ASCII “VPF1”) + 32 bytes of SHA-256 are committed in an OP_RETURN output. No file or filename is stored on-chain.

Open VargaProof →

CORS

Readable integration

Public read endpoints are intended for web integrations. Core RPC credentials remain private.

fetch('https://vargamesh.com/api/v1/status')
  .then(r => r.json())
  .then(console.log)

MINING

Public VMESH SOLO telemetry & policy

/api/v1/pool describes the main public VMESH SOLO pool. Its documented payout policy is 99% miner / 1% operations. Merged SOLO and Home Mining / PPLNS use separate infrastructure and accounting.

Mining documentation →

VNS API · VNS1

VargaMesh Name Service

Public resolver and transaction-payload endpoints for name.vmesh. VNS is an application-layer namespace indexed from VargaMesh OP_RETURN records; Core consensus is unchanged.

Open VNS WebWallet →

StatusGET /api/vns/v1/status

AvailabilityGET /api/vns/v1/availability/{name}

ResolveGET /api/vns/v1/resolve/{name}

Name + historyGET /api/vns/v1/name/{name}

Names by addressGET /api/vns/v1/address/{address}

Encode commitPOST /api/vns/v1/encode/commit

Encode registerPOST /api/vns/v1/encode/register

Encode transferPOST /api/vns/v1/encode/transfer

Encode renewPOST /api/vns/v1/encode/renew

Registration fee: 10 VMESH per registration/renewal year, paid on-chain to vm1qmh7cnjshtxyrqdfefzs2k7g6r7pd7ma9ntrleg. Commit transactions pay only the normal network fee.

TREASURY API

Ecosystem Treasury transparency endpoints

Public balance reconciliation, verified contributor leaderboard, ledger and pseudonymous contribution attribution.

OpenAPI/api/treasury/openapi.json

Status/api/treasury/status

Contributors/api/treasury/contributors

Ledger/api/treasury/ledger

Treasury page →OpenAPI JSON →

MESHPROOF API · v0.3

Public node contribution & reward transparency

MeshProof exposes its verifier state without exposing VargaMesh Core RPC. Registration and claim verification affect only the off-consensus MeshProof registry.

MeshProof page →

StatusGET /api/meshproof/status

NodesGET /api/meshproof/nodes

ReceiptsGET /api/meshproof/receipts?limit=100

Reward previewGET /api/meshproof/rewards/preview

EpochsGET /api/meshproof/epochs?limit=30

Claim detailsGET /api/meshproof/claim/{id}

Verify claimPOST /api/meshproof/claim/verify

VMT-1 · TOKEN API

Fungible-token directory endpoints

VMT-1 is an application-layer protocol indexed from confirmed VargaMesh mainnet transactions. Token state is chain-derived; issuer logos and descriptive metadata are off-chain and appear publicly only after issuer proof and manual review.

Token Directory →

Method	Endpoint	Purpose
GET	`/api/v1/vmt/status`	VMT indexer, activation and replica status
GET	`/api/v1/vmt/stats`	Token, holder and event totals
GET	`/api/v1/tokens`	Search/list VMT-1 tokens
GET	`/api/v1/tokens/<token_id>`	Token detail, issuer, supply and reviewed metadata
GET	`/api/v1/tokens/<token_id>/holders`	Positive token balances by address
GET	`/api/v1/tokens/<token_id>/events`	CREATE/MINT/TRANSFER/BURN history
GET	`/api/v1/addresses/<vm1...>/tokens`	Token balances, issuer role and mintability for an address
GET	`/api/v1/addresses/<vm1...>/events`	Confirmed VMT activity involving an address
POST	`/api/v1/vmt/preflight`	Read-only exact signed-transaction validation; never broadcasts
POST	`/api/v1/tokens/<token_id>/metadata/challenge`	Issuer ownership challenge for metadata
POST	`/api/v1/tokens/<token_id>/metadata/submissions`	Issuer-signed metadata/logo submission for manual review

WebWallet safety: CREATE, TRANSFER, BURN and MINT are built and signed locally in the browser. /api/v1/vmt/preflight validates the exact signed transaction against VMT state, the live CREATE-fee policy and VargaMesh Core mempool rules without broadcasting it. Private keys are never submitted to the API.

Metadata: pending PNG files are never served by the public API. Only manually approved metadata is exposed. Read replicas verify the authority's signed Ed25519 metadata manifest.

VMESH/USDT · API

Exchange reference and machine-readable market links

NestEx, FynEx, FiloDex: /markets.html

VargaMesh exchange directory JSON: /data/exchange-directory.json · optional refreshed snapshots: /data/market-venues.json

FynEx ticker: GET /api/v2/public/markets/vmeshusdt/ticker. FiloDex market-data REST base: https://api.filodex.xyz (ticker route not yet verified). These market APIs are independent from VargaMesh Core RPC.