Mysterium Network Integration: Decentralized VPN, SDK, API

Integration with Mysterium Network

A specific scenario: you are building an application that needs a decentralized VPN or residential proxy — without a single provider, without KYC on users, with crypto payment. For example, you need to scrape data from sites that block datacenter IPs, or ensure privacy for mobile app users without collecting personal data. Mysterium Network is a p2p network of ~13,000 nodes, operating on Proof-of-Traffic. Each participant can sell unused traffic for MYST tokens. For a developer, the task is not just "connect to a VPN", but to embed Mysterium into your application as a programmable transport layer.

We have been integrating decentralized networks for over five years and have completed more than 50 projects, several specifically on Mysterium. In one case, a client saved up to 90% compared to standard residential proxy rates.

How Mysterium Handles Payments

Mysterium uses payment channels via the Hermes contract on Polygon. This is off-chain micropayments with periodic settlement. Programmatic top-up is a direct MYST transfer via ethers.js. Below is an example of creating a payment channel:

const channelAddress = await api.paymentOrderGetChannelAddress(identity.id);
const order = await api.paymentOrderCreate(identity.id, {
  mystAmount: "10.0",
  payCurrency: "USD",
  gateway: "coingate",
  country: "US",
  callerData: "{}",
});
console.log("Payment URL:", order.publicGatewayData.paymentUrl);

Wireguard is the transport protocol on which the Mysterium network is built. It provides minimal latency and high throughput.

Mysterium Architecture: Under the Hood

Mysterium operates on top of several protocols. Here is their comparison:

The key component for developers is the SDK mysterium-vpn-js (TypeScript) and the node REST API (tequilapi).

How to Connect via SDK

The SDK allows you to manage the node and sessions programmatically. Example of basic startup:

import { TequilapiClientFactory, NodeHttpTransport } from "mysterium-vpn-js";

const factory = new TequilapiClientFactory(
  "http://127.0.0.1:4050",
  5000
);

const api = factory.build(NodeHttpTransport());

const nodeInfo = await api.healthCheck();
console.log("Node version:", nodeInfo.version);

const proposals = await api.findProposals({
  serviceType: "wireguard",
  qualityMin: 0.9,
  locationCountry: "DE",
});

Session Creation, Management, and Monitoring

const identities = await api.identityList();
if (identities.length === 0) {
  const identity = await api.identityCreate("your_passphrase");
  await api.identityRegister(identity.id, { token: undefined });
}

const identity = identities[0];
const status = await api.identityStatus(identity.id);
if (status.registrationStatus !== "Registered") {
  throw new Error("Identity not registered");
}

const connection = await api.connectionCreate({
  consumerId: identity.id,
  providerId: proposals[0].providerId,
  serviceType: "wireguard",
  connectOptions: { dnsOption: "auto" }
});

console.log("Session ID:", connection.sessionId);

const stats = await api.connectionStatistics();
console.log({ bytesSent: stats.bytesSent, bytesReceived: stats.bytesReceived, tokensSpent: stats.tokensSpent, duration: stats.duration });

const location = await api.connectionLocation();
console.log("Exit IP:", location.ip, "Country:", location.country);

await api.connectionCancel();

Why Use a Custom Discovery?

By default, a Mysterium node uses the centralized Discovery service of Mysterium Foundation. For enterprise or private networks, you need self-hosted NATS:

version: '3.8'
services:
  nats:
    image: nats:2.9-alpine
    ports:
      - "4222:4222"
      - "8222:8222"
    command: "--jetstream --cluster_name mysterium-private"
  discovery:
    image: mysteriumnetwork/discovery:latest
    environment:
      - NATS_URL=nats://nats:4222
      - BROKER_ADDRESS=nats://nats:4222
    depends_on:
      - nats

Nodes are configured with --discovery.address pointing to your NATS. This gives you full control over the provider list and connection quality.

Common Mistake: Lack of Fallback

Mysterium does not guarantee stable bandwidth. For critical applications, incorporate a fallback provider. We implement switching logic based on response time and errors. Testing during integration reveals up to 30% of nodes with poor performance — we exclude them from the pool.

Cost Comparison: Mysterium vs. Traditional Residential Proxies

Mysterium is significantly cheaper than traditional residential proxies, providing substantial savings for large-scale scraping.

Typical Use Cases

• Decentralized proxy for web scraping — Replace rotating residential proxies with Mysterium. Reliability varies, so we incorporate fallback.
• Privacy-preserving API calls — A mobile application hides the user's IP through Mysterium.
• Geo-distributed testing — Test from different geolocations without renting VPS.

Limitations: Mysterium does not guarantee bandwidth or uptime. For latency-sensitive applications, a fallback is required. Our integration includes provider switching logic.

What We Deliver in the Integration: Deliverables

• SDK integration module for Mysterium into your code (TypeScript/JavaScript).
• Setup and launch of a test node with a payment channel on Polygon.
• Implementation of self-hosted Discovery on NATS (optional).
• Automatic MYST balance top-up and cost monitoring.
• Documentation for API, configuration, and troubleshooting.
• Team training (2–3 hour workshop).
• One month of post-release support.

How We Help with Integration: Step-by-Step Algorithm

1. Analyze your scenario and architecture.
2. Set up and launch a test Mysterium node.
3. Integrate the SDK into your application.
4. Implement the payment layer via Polygon (MYST balance, top-up, monitoring).
5. Optionally: deploy a custom Discovery service (NATS).
6. Prepare operational documentation and troubleshooting.
7. Provide post-release support.

A typical integration takes from 2 weeks; full custom work up to 10 weeks. Get a consultation — contact us to discuss your project and get a free estimate of the work scope.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.