Node economics

The full numbers behind MeterCall's open-source RPC layer. Every value on this page is the single source of truth — the on-chain contracts, the calculator on /node-operator.html, and the reference implementation in /node/index.js all reference these exact values.

Reward formula

daily_pcp = calls_served × 0.0001 × tier_mult × uptime_mult × operator_share

Base reward 0.0001 PCP per call is fixed in 0.1.0. The two multipliers scale output; operator_share is 0.20 (20% to the operator, 80% flows to delegators pro-rata).

Stake tier table

TierStake range (PCP)MultiplierExtras
T110,000 – 99,9991.0xBaseline. Any serious home operator.
T2100,000 – 999,9991.3xTypical $5 VPS operator after accumulating.
T31,000,000 – 9,999,9991.6xSerious pro operator, paid upstream RPCs.
T410,000,000+2.0xPriority routing: coordinator sends traffic to T4 first when healthy.

Stake floor to operate at all: 10,000 PCP (~$500 at $0.05/PCP).

Why location matters

Every L4 call is a race. The coordinator hands a request to the closest healthy node, and the network also runs parallel-of-5 races for high-value traffic — first response wins. Latency decides. A Raspberry Pi in Brooklyn serving users in Manhattan beats AWS us-east-1 at full load, because one hop inside a borough is < 5 ms and a trip to Ashburn is ~50 ms. The reward curve below makes that real: the fastest responder earns the most.

Latency multiplier

p50 serve latencyMultiplierWho typically hits it
< 10 ms2.5xSame-LAN/ISP nodes. Home Pi, phone, NAS, router serving local users.
< 25 ms2.0xSame-metro nodes. Desktop in your city's fiber range.
< 50 ms1.5xSame-region nodes. Home server or small VPS.
< 100 ms1.0xBaseline — cross-country / neighbouring region.
< 250 ms0.7xCross-continent. Soft penalty.
≥ 250 ms0.4xBad placement or overloaded. Hard penalty.

Residential bonus

When a node with hw_class of pi, phone, console, nas, or router wins a latency race, it earns +20% on top of its reward. We want Joe Schmoe's Pi in the basement to beat AWS us-east-1 — not because we subsidize it, but because it's actually closer to real users.

Density penalty

If more than 5 nodes crowd into the same ~20 km geohash-4 cell, the rewards pool splits among them — mult = 5 / count. Prevents "stack 50 VPSes in Ashburn" from winning. Forces geographic distribution.

Full L4 reward formula

daily_pcp = calls_served × 0.0001 × tier_mult × uptime_mult × latency_mult × residential_bonus × density_penalty × operator_share

Race winners also earn a 2x region leader multiplier on /api/node/leaderboard/latency. Live coverage + PCP earnings visible at /node-coverage.html.

Uptime multiplier

30-day uptimeMultiplierNote
≥ 99.5%1.2xBonus — rare air, routed more calls.
≥ 99.0%1.0xTarget. Standard multiplier.
95.0% – 98.9%0.7xSoft penalty.
< 95.0%0.5xHard penalty. Also risks downtime slash if any single incident > 1 hr.

Slashing

OffensePenaltyDetection
Verified dishonest answer1% of self-stake burned1% receipt sampling re-run against canonical source.
Downtime incident > 1 hour10% burnedCoordinator heartbeat timeout.
Provable fraud (double-sign, key theft, sybil)100% burned + banOn-chain challenge via NodeRegistry.challengeReceipt().

Only operator self-stake is slashable. Delegator stake is never directly burned — but a slashed operator earns less going forward, so delegator yield drops until they re-delegate elsewhere. Unbond period: 14 days.

Delegation

Don't want to run hardware? Delegate to a trusted operator and earn 80% of their reward flow, pro-rata against all delegators.

The split is Cosmos-style: operator keeps 20%, delegators share 80%. You can re-delegate anytime (14-day unbond still applies to delegated stake to prevent whiplash).

The delegator UI lives at /nodes.html — click any node row to open its delegation sheet.

100M PCP, 4-year emission curve

100,000,000 PCP is set aside from the 30% Community & Builders allocation, distributed linearly to node operators over 48 months based on proof-of-served calls.

M1M12M24M36M48

Monthly budget: ~2.083M PCP (100M ÷ 48). Distributed pro-rata across the set of honest nodes weighted by their tier/uptime-adjusted call count for that epoch.

vs Pokt Network — the stack advantage

Pokt pays in POKT for chain-specific relays (mostly EVM RPC). MeterCall pays for three stacked revenue streams on a single node runtime:

  • L4 chain calls — the same relay market Pokt owns.
  • Real-world API calls — 20M+ APIs, a market Pokt doesn't serve.
  • Bridge attestations — every cross-chain message signed by an L4 node pays out.

Same stake, same machine, three revenue lines. See full side-by-side.

Taxes

PCP rewards are likely earned income at the moment of receipt in most jurisdictions (USA, UK, EU). We do not issue 1099s or equivalents — this is a decentralized, permissionless network.

Keep your own records. Consult a crypto-aware accountant. Nothing on this page is tax or legal advice.