VPX Token Economy

2.1 Vesting & Lock-ups

All team and contributor tokens are subject to a 12-month cliff followed by 36-month linear vesting from t=0 (mainnet genesis). No team tokens are liquid at launch. Strategic partner tokens have a 6-month cliff and 24-month vest. These lock-ups are enforced by smart contract and cannot be overridden.

Private round investors (Seed and Series A) are subject to 6-month cliffs followed by linear vesting (Seed: 24 months; Series A: 18 months) per the §2.2 table, ensuring alignment with long-term network success. All investor vesting schedules are enforced by smart contract and publicly verifiable on-chain.

Node Operator Rewards follow a declining emission schedule: Year 1 emits 15% of the reward pool, Year 2 emits 13%, declining to Year 10 at 4%. This front-loads rewards during the critical network bootstrap phase while ensuring long-term sustainability. The full per-year schedule plus the 6% DAO Reserve Buffer is in Section 8 and sums to 100% of the pool.

Milestone-Accelerated Vesting (Team and Investor): Vesting may be accelerated against documented milestones in three classes: (1) quantitative on-chain milestones (cumulative fee volume, active Node count, cumulative burn) auto-certified by on-chain oracle; (2) quantitative off-chain milestones (carrier count, B2B revenue threshold) certified by annual auditor sign-off; (3) qualitative milestones (regulatory clearance achieved, 90-day production stability) requiring 4-of-6 vote of the VPX Foundation board with non-team majority and team representatives recused. If the Foundation board cannot be stood up before TGE with a qualifying non-team majority, milestone-accelerated vesting falls back to strict calendar vesting. Hybrid acceleration (some milestones gameable by the team) is explicitly excluded.

2.2 Private Fundraising Rounds

VPX will raise capital through phased private rounds to sophisticated investors, strategic carriers, and institutional funds. No public retail token sale is planned at mainnet launch. This phased approach allows the network to prove technical functionality and revenue generation before broader token distribution.

Seed Round: The initial fundraising round targets £2.5M from telecom-focused venture capital firms, strategic carriers, and infrastructure investors. Seed pricing (£0.05 per VPXN, £50M fully diluted valuation) reflects early-stage risk and provides sufficient upside for investors taking pre-revenue protocol risk. Funds will be used for mainnet development, smart contract audits, legal/compliance structure, initial DEX liquidity, and 6-month operational runway.

Series A: Following 12 months of mainnet operation and demonstrated carrier adoption (target: 25+ wholesale carriers processing 100K+ transactions/day), VPX will raise an additional £3-5M from growth-stage investors. Series A pricing will be set by reference to the then-current market trading price, with a discount-to-spot reflecting the 18-month vesting lock-up and the size of the institutional allocation (illustrative discount bands of 5-15% to volume-weighted spot are modelled in §11.1.1; final terms are subject to DAO ratification and market conditions at the time of the round). Funds will be used for Tier 2 centralised exchange listings, carrier acquisition scaling, team expansion, and security infrastructure.

Rationale for Phased Approach: A comparable telecom-blockchain project reached a peak token price in 2025 but declined roughly 88% within months despite having launched a working product (source: public market price data). VPX avoids this mistake by: (1) selling only to sophisticated investors at fair early-stage prices (£0.05, not inflated public sale pricing), (2) proving network utility and revenue generation for 12 months before broader access, (3) letting the market discover natural price levels via DEX trading rather than forcing an arbitrary public sale price.

2.3 Community Allocation

The Community Allocation (20M VPXN, 2.0% of supply) is the residual that closes the seven-bucket allocation table to 100%. It is reserved for future distribution programs governed by DAO vote. This allocation is NOT sold at launch - it provides flexibility for post-launch community initiatives as the network matures:

• Liquidity mining programs: Incentivise third-party liquidity providers on DEXs to deepen VPXN trading markets beyond treasury-provided liquidity.
• Exchange market making: Provide inventory to professional market makers for CEX listings, improving institutional trader access.
• Ecosystem airdrops: Distribute tokens to VoicePro Mobile users, early carrier partners, or community contributors as reward for participation.
• DAO-governed initiatives: Fund community-proposed programs via governance vote (e.g., developer bounties, hackathon prizes, regional growth campaigns).

All Community Allocation disbursements require DAO approval via weighted governance vote. A real-time transparency dashboard tracks all distributions, recipient addresses, amounts, and stated purposes. Undistributed tokens remain locked in the Community Treasury multi-sig wallet until DAO authorisation.

2.4 Token Unlock Schedule & Circulating Supply Projection

The following table projects circulating supply growth over the first 48 months, accounting for all vesting schedules, emission curves, and lock-up periods. Circulating supply represents tokens that are liquid and tradeable - excluding locked team/contributor tokens and unvested investor allocations.

Major Unlock Events (Price Risk Dates): Month 6 represents the largest proportional unlock as Seed investors complete their 6-month cliff. Month 12 marks the team cliff - but zero tokens unlock because the cliff only ends the waiting period before vesting begins. First material team unlock is Month 13 (~4.2M VPXN, then monthly). These dates represent potential selling pressure and should be monitored by market participants.

Circulating supply projections assume zero burn (conservative estimate). With the 40% fee burn active, actual circulating supply will track below these figures from Month 18 onward as cumulative burn begins offsetting emissions. The model transitions from net inflationary in early years to net deflationary as fee volume scales (see Section 4).

2.5 Ecosystem Development Allocation Breakdown

The Ecosystem Development allocation (200M VPXN, 20% of total supply) is subdivided into four ring-fenced categories that sum to the 20% parent allocation. Each sub-pool has independent vesting and governance requirements:

Each sub-pool has independent multi-sig control with distinct signer sets to prevent conflicts of interest. Consumer Rewards are managed by VoicePro Mobile product team. Grant Program is managed by VPX Foundation (independent entity). Strategic Partnerships require joint approval from VoicePro Plus board and DAO governance. Marketing budget is proposed monthly by the marketing team and approved by DAO vote.

All disbursements from Ecosystem Development sub-pools are published on-chain with recipient addresses, amounts, and stated purposes. A real-time transparency dashboard is available at vpx.network/ecosystem-transparency.

2.6 Treasury Reserve Sub-split

The Treasury Reserve (15.0% of total supply, 150M VPXN) is split into two ring-fenced sub-pools:

The Insurance Fund is inside Treasury Reserve, not a sixth top-level bucket. Its operating rules - payout triggers, claims process (2-of-3 multisig sign-off including DAO-elected representative), 20%-per-year payout cap, and 1%-of-fee-burn replenishment until 50M floor - are defined in the Protocol document.

Subsidy Fail-Safe: If projected Treasury Operations subsidy outflow during Phase 1 exceeds the Treasury Operations balance, the subsidy programme is the lever that flexes (reduce subsidy %, shorten the window, or cap Carrier participation count) - not the Treasury balance. The subsidy is not, under any circumstance, funded by reallocation from the Insurance Fund or Community pools, or by emergency token issuance.

3.1 Staking

Operating any Node type on the VPX Network requires a minimum VPXN stake. The stake serves two purposes: economic commitment (skin in the game) and slashing collateral (penalty for dishonest behaviour). Staked tokens are locked for the duration of Node operation plus a 7-day unbonding period.

Minimum stake requirements vary by Node type and are set by governance vote. Higher stakes earn proportionally higher rewards and greater governance weight.

3.2 Fee Payment

Network service fees - routing lookups, fraud score queries, CDR recording, settlement processing - are denominated and paid in VPXN. Carriers acquire VPXN through decentralised exchanges (DEXs), centralised exchanges (CEXs), or authorised third-party liquidity providers. VoicePro Plus does not sell VPXN directly to carriers post-mainnet launch - all token acquisition occurs through open market mechanisms. This creates organic demand for VPXN proportional to network usage while maintaining regulatory compliance and market integrity.

3.3 Governance

VPXN holders can vote on protocol parameter changes: consensus thresholds, fee structures, reward distributions, slashing conditions and new feature activation. Voting weight is proportional to staked VPXN (not total holdings), ensuring that only participants with economic commitment to the network influence its governance.

3.4 Node Operator Rewards

Honest, high-quality network participation earns VPXN rewards from the Node Operator Rewards pool and from fee redistribution. Rewards are distributed per epoch (1 hour) based on uptime, accuracy (Fraud Nodes), routing quality contribution (Routing Nodes), processing throughput (Analytics Nodes) and traffic volume (Gateway Nodes).

3.5 Consumer Rewards

VoicePro Mobile app users earn VPXN through everyday platform usage - making and receiving calls, purchasing top-up credits, sending and receiving transfers - subject to tiered monthly caps with dual VPXN-and-£ ceilings (12/45/120 VPXN with £1.20/£4.50/£12.00 sterling caps depending on user profile) and a 25/75 vesting split (25% immediately liquid, 75% vesting linearly over 12 months). Earned tokens accumulate in the users VPX Wallet and can be spent on SIM top-ups, merchandise from the VoicePro Shop, gift card exchanges, staking for participation rewards, or fiat cashout. Per-epoch reward rates are dynamically adjusted to ensure the programme never exceeds its allocated budget. This consumer rewards loop is detailed in Section 11.

4.1 Burn-Emission Equilibrium Modelling

The equilibrium circulating supply is the level where annual burn equals annual emission, creating zero net supply change. The relationship is:

Equilibrium Formula: Annual Burn (VPXN) = Annual Emission (VPXN), where Annual Burn = 0.40 × Annual Fee Volume (VPXN) and Annual Emission = Per-Epoch Emission × 8,760 epochs.

The equilibrium point depends on three variables: (i) fee volume in £, (ii) token price, and (iii) circulating stake base. We do not assert a specific "X% supply reduction by Year N" headline because the answer is materially price-dependent: at lower realised token prices, more VPXN is burnt per unit of fee revenue, and the supply contraction is steeper; at higher realised prices, less. The model surfaces this as a price sensitivity rather than a guaranteed outcome.

Token Velocity (note on terminology). Velocity in this paper is defined narrowly as `annual_fee_VPXN_flow / circulating_supply` - the number of times each circulating token is used for fee payment per year. This is a different quantity than the textbook equation-of-exchange velocity V = (P·Q)/M, which counts *all* on-chain transaction flow including transfers, DEX swaps and staking-pool rebalances. The narrow definition isolates fee-driven token-sink demand from speculative and transfer flow; readers applying the textbook definition will compute a higher number. We use the narrow definition because protocol fees are the only flow that drives the 40% burn, and the burn is what couples token economics to network usage. The model computes velocity as an output, not as an input assumption. At base case (£25M mature fees, £0.10 illustrative token price, 1B fixed supply with the modelled vesting and emission curves), computed narrow-velocity rises from approximately 1× in early years to 3-6× at maturity as circulating supply contracts under net deflation.

Sensitivity Analysis: A 50% reduction in network usage delays equilibrium by approximately 1-2 years. A 50% increase in burn rate (from 40% to 60% via DAO vote) accelerates equilibrium by approximately 1 year. The model reaches equilibrium across realistic growth scenarios within a 2-6 year window.

Physical Burn Cap: The protocol implements a physical-sustainability cap on annual burn at 30% of prior-year circulating supply. This cap recognises that tokens cannot be burnt faster than they can be acquired and used in fee payment. At asserted fee volumes that exceed this cap (which would be the case only in unlikely combinations of low token price and high fee volume), the cap binds and excess fee revenue is redistributed rather than burnt. The model surfaces a "burn-pressure ratio" diagnostic: any year in which raw burn exceeds the physical cap is flagged for governance review.

5.1 Yield Composition

Staking reward comprises two components: base rewards (from the Node Operator Rewards pool emission schedule) and fee redistribution (from network service fees after burn). In the early network, base rewards dominate. As network usage grows and fee volume increases, fee redistribution becomes the primary reward component - creating a sustainable long-term model independent of emission schedules.

5.2 Slashing Conditions

Stake slashing is triggered by demonstrably dishonest behaviour at the Operator level (an Operator may run multiple Nodes; slashing applies to the Operator and is borne pro-rata across their Nodes and delegators). VPX uses a three-tier penalty schedule: 25% on a first correctable offence, 75% on a severe offence (repeated breaches, deliberate fraud-detection bypass, double-signing), and 100% plus permanent deregistration on a terminal offence (coordinated attack, identity fraud, governance manipulation). Slashed tokens are burned, not redistributed - preventing perverse incentives around slashing events. Full schedule and trigger criteria are in Section 10.

6.1 Stage 1 - Eligibility Filtering

Only Nodes that were registered, staked above the minimum threshold and online for at least 90% of the epoch duration (54 of 60 minutes) are eligible for rewards. Nodes that deregistered mid-epoch, were slashed during the epoch or fell below the uptime threshold are excluded entirely. The eligibility set is published on-chain at epoch close.

6.2 Stage 2 - Performance Scoring

Each eligible Node receives a Performance Score (PS) between 0.00 and 1.00 calculated from node-type-specific metrics (detailed in Section 7). The score is a weighted composite: no single metric can produce a maximum score alone. Nodes that meet all thresholds at baseline receive PS = 0.50. Exceptional performance across all dimensions approaches PS = 1.00. The scoring function is continuous - there are no cliff thresholds that create discontinuous jumps in reward.

6.3 Stage 3 - Reward Calculation

The epoch reward pool is the sum of two components: the base emission allocation (from the Node Operator Rewards pool for this epoch) and the fee redistribution allocation (60% of all protocol fees collected during the epoch in Years 1-6; 55% from Year 7 onward, with 5% diverted to the Consumer Rewards Fund per Section 11.7). The total pool is divided among eligible Nodes using stake-weighted performance scoring.

For each eligible Node i, its epoch reward R_i is calculated as: R_i = Pool × (S_i × PS_i) / Σ(S_j × PS_j) for all eligible Nodes j - where S_i is the staked VPXN amount and PS_i is the Performance Score. This means reward is proportional to both stake size and performance quality. A Node with twice the stake but half the performance score earns the same as a Node with the base stake and perfect performance.

6.4 Stage 4 - Distribution & Vesting

Calculated rewards are credited to each Operator's reward balance at epoch close. Rewards are not immediately liquid - they enter a 24-hour maturation window during which they can be clawed back if post-epoch audit reveals fraudulent performance reporting. After maturation, rewards are claimable on-chain via a standard withdrawal transaction.

Unclaimed rewards accumulate in the Operator's reward balance indefinitely. There is no expiry. However, unclaimed rewards do not earn compound rewards and do not contribute to governance voting weight until explicitly staked.

7.1 Fraud Node Scoring

Fraud Nodes are scored on four dimensions:

• Detection Accuracy (weight: 0.35) - ratio of fraud reports submitted by this node that achieved consensus confirmation versus total reports submitted. Measures signal quality. Target: ≥ 92% confirmation rate.
• Detection Speed (weight: 0.25) - median time from first suspicious pattern emergence (as measured by network-wide traffic anomaly) to fraud report submission. Faster detection earns higher scores. Target: ≤ 45 seconds median.
• Consensus Participation (weight: 0.25) - percentage of consensus rounds in which this node participated by submitting a validation vote within the required window. Measures reliability. Target: ≥ 95% participation.
• Coverage Breadth (weight: 0.15) - number of distinct destination countries and fraud type categories (IRSF, Wangiri, AIT, CLI spoofing, grey route) for which this node submitted at least one confirmed report during the epoch. Rewards geographic and typological diversity.

7.2 Routing Node Scoring

Routing Nodes are scored on four dimensions:

• Routing Accuracy (weight: 0.30) - percentage of routing decisions where the selected route's actual quality (post-call ASR, ACD, PDD) fell within the predicted quality bounds at decision time. Measures model calibration. Target: ≥ 88% accuracy.
• Decision Latency (weight: 0.25) - P95 routing decision time measured from request receipt to signed route response. Real-time telecom requires sub-50ms decisions. Target: ≤ 30ms P95.
• Quality Table Freshness (weight: 0.25) - age of the quality intelligence table maintained by this node, measured as the median staleness of per-route quality scores relative to the most recent network-wide consensus update. Stale data degrades routing quality. Target: ≤ 120 seconds median staleness.
• Throughput Contribution (weight: 0.20) - total routing decisions processed during the epoch as a proportion of the node's declared capacity. Measures utilisation efficiency. Nodes that declare high capacity but process few requests are penalised.

7.3 Analytics Node Scoring

Analytics Nodes are scored on four dimensions:

• Processing Throughput (weight: 0.30) - total CDRs ingested, enriched and published during the epoch. Measured against the node's declared capacity. Target: ≥ 85% of declared capacity utilised.
• Processing Latency (weight: 0.25) - P95 time from raw CDR ingestion to enriched CDR availability via API. The network promise is sub-2-second enrichment. Target: ≤ 1.5 seconds P95.
• Anomaly Signal Quality (weight: 0.25) - ratio of anomaly signals raised by this node that were subsequently corroborated by Fraud Node consensus or confirmed by independent traffic analysis. False-positive anomaly signals degrade network trust. Target: ≥ 78% corroboration rate.
• Intelligence Contribution (weight: 0.20) - whether this node successfully computed and committed network-wide intelligence aggregates (route quality benchmarks, destination rankings, traffic volume trends) to the Protocol during the epoch. Binary per-aggregate with proportional scoring.

7.4 Gateway Node Scoring

Gateway Nodes are scored on four dimensions:

• Traffic Volume (weight: 0.30) - total call minutes and SMS messages transited through this Gateway during the epoch. Higher volume gateways contribute more network intelligence and earn proportionally higher volume scores.
• Translation Fidelity (weight: 0.25) - percentage of protocol translations (SIP/H.323 to VPX routing request and back) completed without signalling errors, codec mismatches or header corruption. Target: ≥ 99.5% fidelity.
• Uptime & Availability (weight: 0.25) - percentage of the epoch during which the Gateway was accepting inbound connections and processing traffic. Measured by peer heartbeat monitoring. Target: ≥ 99.0% availability.
• CDR Submission Completeness (weight: 0.20) - percentage of transited calls for which complete, correctly formatted CDR data was submitted to the Analytics Node layer within the required window. Missing or malformed CDRs degrade network intelligence. Target: ≥ 98% completeness.

7.5 Score Normalisation

Raw metric scores are normalised to the 0.00-1.00 range using a sigmoid function centred on the target threshold. Performance at the target earns 0.50. Performance 20% above target asymptotically approaches 1.00. Performance 30% below target asymptotically approaches 0.00. This sigmoid normalisation prevents extreme outliers from dominating the reward pool and ensures that consistent, reliable performance is rewarded more than occasional spikes of exceptional output.

8.1 Emission Halving Dynamics

The per-epoch emission in Year 10 is approximately 27% of the Year 1 rate. This decline is designed to mirror the expected growth in fee-based rewards: as the network scales from hundreds to thousands of nodes and processes increasing traffic volume, fee redistribution replaces base emission as the primary reward component. By Year 5 in the base case scenario (2,000 nodes), fee redistribution is projected to exceed base emission - making the declining emission schedule economically irrelevant to node operator yield.

8.2 DAO Reserve Buffer

The 6% reserve (21,000,000 VPXN) is not scheduled for automatic emission. It is held in a DAO-governed multi-sig wallet and can be deployed by governance vote for purposes including: extending emission beyond Year 10 if the network has not yet reached fee-sustainability, funding targeted incentive programmes for underserved node types or geographies, or one-time grants for ecosystem development. If the reserve is not deployed by Year 15, a governance proposal to burn the remaining balance is automatically submitted.

8.3 Interaction with Burn Mechanism

The emission schedule and the 40% fee burn operate as opposing forces on circulating supply. In Years 1-3, gross emission exceeds gross burn (net inflationary). Between Years 3-5 (depending on network growth trajectory), the burn rate surpasses emission rate (net deflationary). This inflection point is critical: it marks the transition from token supply expansion to contraction, fundamentally altering supply-demand dynamics.

9.1 Delegation Mechanics

A token holder delegates by submitting an on-chain delegation transaction specifying the target Operator address and the VPXN amount. Delegated tokens are locked with the same unbonding period as directly staked tokens (7 days). A delegator can split their holdings across multiple Operators to diversify risk. There is no minimum delegation amount, but gas costs make delegations below 100 VPXN economically impractical.

Delegated stake contributes to the Operator's total stake weight for reward calculation purposes. A Node with 500,000 directly staked VPXN and 300,000 delegated VPXN has an effective stake of 800,000 VPXN for the reward formula in Section 6.3.

Per-Operator Delegation Cap: No single Operator may control more than 5% of total network stake (own stake + delegated). New delegations to an Operator at or above the 5% cap are rejected at the protocol level; the cap is enforced on-chain at delegation time, not after the fact.

HHI Threshold Schedule (numeric): The cap is reviewed annually by DAO governance against the observed Herfindahl-Hirschman Index of stake concentration (HHI = Σ(s_i)² × 10,000 where s_i is each Operator's share of total stake). Three numeric thresholds govern action: (i) HHI < 1,000 - concentration low; no action. (ii) 1,000 ≤ HHI < 1,800 - concentration moderate; DAO must table a review proposal at the next annual review. (iii) HHI ≥ 1,800 - concentration high; the cap automatically tightens by one step (e.g. 5% → 4%) at the next epoch boundary unless the DAO ratifies an alternative remediation by super-majority within 30 days. These thresholds are aligned with the US DOJ Horizontal Merger Guidelines bands and provide an objective trigger rather than a discretionary "DAO decides" review. Tightening the cap below the auto-step requires a simple-majority DAO vote; loosening the cap requires a super-majority DAO vote. This asymmetry makes the cap a credible commitment.

Passive Overshoot Policy (5% cap, shrinking total stake): An Operator may passively exceed the 5% cap if total network stake shrinks (e.g. delegators elsewhere unbond). The policy is: (i) no forced redistribution and no slashing - passive overshoot is not an offence; (ii) the Operator is flagged on-chain as "over-cap (passive)" and is blocked from accepting new delegations until the share returns below 5%; (iii) the Operator continues to earn rewards on stake up to the 5% cap only - reward distribution above the cap is redirected to the DAO Treasury per epoch until the breach is cured; (iv) if the breach persists for more than 90 consecutive days, the Operator is required to submit a remediation plan to DAO governance (voluntary partial unbonding, commission-rate change to encourage delegator redistribution, or split into a second registered Operator entity). Forced unbonding is explicitly excluded as a remedy - it would penalise delegators who took no action.

9.2 Commission Rates

Node operators set a commission rate between 0% and 50% (inclusive). The commission is the percentage of delegator rewards retained by the operator. For example, if a delegator earns 100 VPXN in an epoch and the operator's commission is 10%, the delegator receives 90 VPXN and the operator retains 10 VPXN.

Commission rates are declared on-chain and are publicly visible. Operators can change their commission rate at any time, but changes take effect only after a 7-day notice period - giving delegators time to redelegate if the new rate is unfavourable. This prevents bait-and-switch commission changes.

9.3 Delegator Protections

Delegated tokens are subject to the same slashing conditions as directly staked tokens. If an Operator is slashed, delegators lose a proportional share of their delegation. This is by design: delegators must perform due diligence on Operator reliability and honesty before delegating.

To mitigate delegation risk, the Protocol publishes on-chain Operator scorecards showing: historical Performance Scores, slashing history, uptime percentage, total stake (direct + delegated), commission rate, commission rate change history and time since registration. These scorecards are available via API and are surfaced in the VPX Network dashboard.

9.4 Governance Weight for Delegators

Delegated tokens retain governance voting weight with the delegator - not the Operator. A delegator with 10,000 VPXN delegated to an Operator votes with 10,000 weight on governance proposals. The Operator does not inherit delegator voting weight. This separation ensures that delegation is an economic decision and governance remains an independent decision (protocol direction).

Delegators may optionally assign governance voting weight to their Operator via a separate on-chain delegation-of-governance transaction. This is distinct from stake delegation and can be revoked independently at any time with no unbonding period.

10.1 Slashable Offences

The Protocol defines four categories of slashable offence, each with distinct evidence requirements:

• Fraudulent Reporting (Fraud Nodes) - submitting a fraud report with fabricated evidence or a deliberately incorrect fraud classification. Evidence: the fraud report hash does not match any observed traffic pattern across ≥ 3 independent peer Nodes. This is the most serious offence as it undermines the integrity of the shared fraud intelligence layer.
• Data Falsification (Routing/Analytics Nodes) - providing quality scores, CDR data or routing metrics that contradict on-chain evidence or peer-validated observations. Evidence: ≥ 3 independent peer attestations contradicting the submitted data with cryptographic proof of the correct values.
• Consensus Manipulation - attempting to influence consensus outcomes by submitting conflicting votes to different peers, withholding votes strategically or coordinating with other nodes to produce a predetermined outcome. Evidence: signed messages from the offending node that are mutually contradictory within the same consensus round.
• Extended Unannounced Downtime - being offline for more than 6 consecutive hours without submitting a deregistration or maintenance announcement transaction. This is the lightest offence - it penalises unreliability rather than dishonesty.

10.2 Three-Tier Penalty Schedule

The canonical slashing schedule is three tiers, applied at the Operator level:

• Tier 1 (Correctable): 25% of stake slashed. Trigger class: first-time uptime breach, transient ML-flag, recoverable misconfiguration. Operator receives a formal on-chain warning and remains operational.
• Tier 2 (Severe): 75% of remaining stake slashed. Trigger class: repeated breaches, deliberate fraud-detection bypass, double-signing. Operator suspended for 30 days; all delegators receive an automatic redelegate prompt; Operator must resubmit a registration application reviewed by DAO governance to resume operations.
• Tier 3 (Terminal): 100% of remaining stake slashed; permanent deregistration; Operator address blacklisted from future registration. Trigger class: coordinated attack, identity fraud, governance manipulation. Irreversible and not subject to governance override.
• The 3× documented-damages multiplier. A 3× multiplier on slashed stake, applied where a false fraud report causes documented carrier financial loss, activates once the damages-oracle (§16.6) is deployed and DAO-ratified. It is not active at mainnet genesis: until the damages-oracle is live, the slashing schedule is the three-tier 25 / 75 / 100% schedule above only, with no documented-damages multiplier in effect.

10.2.1 Comparison with Other Networks

VPX slashing rates are calibrated by reference to established proof-of-stake networks (Cosmos Hub, Polkadot, Ethereum) so that penalties are proportional and credible relative to comparable systems:

VPX slashing is more aggressive than Ethereum and Polkadot for first offences, comparable to Cosmos for severe offences. This reflects the higher trust requirements of telecom fraud consensus - a single false fraud report can cause material financial harm to carriers, justifying stronger deterrence. The compressed three-tier structure (eliminating intermediate "second-offence" leniency) reflects the principle that an Operator's first severe offence is already a structural failure of their internal controls.

10.3 Slashing Arithmetic

Slashing percentages apply to total stake at the time of the slash event - not the original stake amount. Progressive slashing compounds: an Operator who starts with 1,000,000 VPXN staked and commits successive offences loses 25% (250,000), then 75% of 750,000 (562,500), then the remaining 187,500. Total loss: 1,000,000 VPXN.

For Operators with delegated stake, slashing is applied proportionally. If an Operator has 600,000 directly staked and 400,000 delegated, a 25% slash removes 150,000 from direct stake and 100,000 from delegated stake. Each delegator's loss is proportional to their share of total delegated stake.

10.4 Slash Destination (and the slash-vs-fee distinction)

Slashed tokens (this section). All slashed tokens are permanently burned - sent to an unrecoverable zero address. Slashed tokens are never redistributed to other Nodes, to the reporter of the offence, to the Consumer Rewards Pool, or to the DAO treasury. This design decision prevents three perverse incentives specific to enforcement: Nodes filing false slash reports to earn redistributed tokens, coordinated slashing attacks to concentrate rewards among fewer Nodes, and governance capture through accumulated slash revenue.

Fee tokens (distinct mechanism, §11.3). This 100%-burn principle applies to slashing only. Protocol fees and cashout fees are governed by a separate published split (40% burn / 55% Node redistribution / 5% Consumer Rewards Fund from Year 7; cashout-fee split 50% burn / 50% Consumer Rewards Pool per §11.3). The perverse-incentive logic does not apply to fee flows because fee payment is voluntary user behaviour, not adversarial behaviour requiring punishment. Fee splits are DAO-governable; slash destination is not.

A small fixed bounty of 1,000 VPXN is paid to the Operator filing an upheld slashing report, drawn from the Treasury Operations sub-pool (not from slashed tokens). This bounty addresses the free-rider problem on enforcement (monitoring is costly; without compensation, undetected misconduct persists) without creating the perverse incentives of redistribution. Frivolous reports continue to carry the 1,000 VPXN deposit forfeit (Section 10.5).

Slash burn events are recorded on-chain alongside the standard fee burn and contribute to the same deflationary supply dynamics described in Section 4.

10.5 Dispute Resolution (layered)

Dispute resolution is layered by slash tier, combining the 11-node jury and the DAO-reapply mechanisms as components of a single process.

Tier 1 disputes (correctable, 25% slash) - 11-node jury, fast fact-finding. An Operator who believes a Tier-1 slash was triggered in error can submit a Slash Dispute within 48 hours. The dispute is reviewed by a randomly selected jury of 11 Nodes (sampled via the VRF used for validator selection per Protocol §6.2, weighted by stake, and excluding any Nodes involved in the original offence report). The jury votes within 72 hours. If 7 or more jury members vote to overturn, the slash is reversed and the slashed tokens are restored. Dispute submission requires a non-refundable deposit of 1,000 VPXN. If the dispute is upheld, the deposit is returned. If denied, it is burned. The realised overturn rate will be reported once mainnet dispute data accumulates.

Tier 2 / Tier 3 disputes (severe / terminal, 75% / 100% slash) - DAO reapply. Tier 2 and Tier 3 events automatically suspend the Operator (Tier 2) or permanently terminate registration (Tier 3) per WP-03 §3.4. Resumption from a Tier 2 suspension requires the Operator to submit a remediation case to DAO governance and obtain a super-majority vote to reinstate. Tier 3 terminations are not subject to reapply; the affected Operator may, at DAO discretion, register a new Operator entity subject to fresh diligence. The 11-node jury mechanism is not the dispute path for Tier 2/3 events - that path is governed by DAO governance, consistent with WP-03 §3.4.

The fast 11-node jury is structurally appropriate for the high-volume / low-stake-impact Tier-1 surface; the slower DAO reapply path is structurally appropriate for the rare / high-stake-impact Tier-2/3 surface. The two mechanisms operate at different tiers and are not in conflict.

10.6 Anti-MEV Provisions

Maximal Extractable Value (MEV) is the value a Validator can extract by reordering, inserting or censoring transactions within a block. On general-purpose smart-contract chains MEV is a structural problem (frontrunning, sandwich attacks, oracle latency arbitrage). On a telecom-routing protocol the surface is narrower but non-trivial: a Validator that controls routing-lookup ordering can preferentially route higher-fee minutes to its own Operator, frontrun fraud-blacklist propagation against a competing carrier, or sandwich oracle price updates that drive VPXN-denominated fee settlement. The VPX Protocol treats MEV as an explicit governance concern and applies the following provisions:

• Deterministic intra-block ordering. Within each block, transactions are sorted by (priority class, deterministic hash of transaction body, account nonce). Validators cannot reorder transactions within a block - the order is computed from on-chain inputs, not Validator choice. This eliminates the proposer-discretion vector that produces MEV on general-purpose L1s.
• Encrypted mempool for fraud-blacklist propagation. Pending fraud-blacklist updates are submitted as commitments (hash + threshold-encrypted payload) and revealed only after the block containing them is finalised. A Validator cannot read the contents of a pending blacklist update and therefore cannot frontrun it against an affected carrier.
• Oracle price-update commit-reveal. VPXN-denominated fee oracle updates use a two-phase commit-reveal: at block N a Validator commits hash(price, salt); at block N+1 the price is revealed. Sandwich attacks against the reveal are blocked because the price is fixed by the prior block hash, and the salt is rotated per-update so commitments cannot be replayed.
• Routing-fairness rule. A Validator that is also an Operator may not select its own routing path for any minute where an alternative path scored within 2% of its own path on the published least-cost-route algorithm. Violations are detectable from the on-chain routing decision log and are a Tier-2 slashable offence under §10.2.
• MEV revenue redistribution. Any provable MEV extraction (e.g. demonstrated frontrunning, demonstrated sandwich, demonstrated self-routing in violation of the fairness rule) is treated as a slashable offence under §10.1. The slashed stake is burned per §10.4 and not redistributed - removing the incentive for other Validators to collude with or tolerate MEV behaviour.
• DAO review. The DAO reviews realised on-chain MEV indicators (intra-block ordering anomalies, oracle reveal-reorderings, routing-fairness deviations) at each annual review. Material findings trigger a protocol-parameter update proposal under standard governance rules.

These provisions do not claim that MEV is structurally impossible on VPX - no public protocol can credibly make that claim. They constrain the most economically significant MEV vectors that arise specifically from the telecom-routing and fraud-consensus workloads, and they make the residual surface enforceable rather than discretionary.

11.1 Earning VPXN Through Platform Usage

VoicePro Mobile users earn VPXN through five categories of platform activity. Each category has a defined reward rate calibrated to encourage sustained engagement without creating unsustainable emission pressure:

• Making Calls - outbound voice calls on VoicePro Mobile earn VPXN per minute of connected call time. The rate is tiered: domestic UK calls earn the base rate, EU calls earn 1.5× base and international calls earn 2× base. Reward is credited at call completion and reflects the actual connected duration, not the dialled duration.
• Receiving Calls - inbound calls earn VPXN at 50% of the outbound base rate per connected minute. This rewards users for maintaining an active, reachable number on the VoicePro network and ensures that both parties in a conversation generate token activity.
• Purchasing Top-Up Credits - every top-up purchase (via card, bank transfer or VPX Wallet balance) earns a percentage-based VPXN reward. The reward rate is 3% of the top-up value denominated in VPXN at the prevailing exchange rate. Larger top-ups earn the same percentage - there is no tiering advantage to frequent small top-ups.
• Sending Transfers - peer-to-peer credit transfers between VoicePro users earn the sender a flat VPXN reward per transaction. The reward is fixed regardless of transfer amount to prevent wash-trading incentives.
• Receiving Transfers - the recipient of a peer-to-peer transfer earns 50% of the sender's flat reward. This encourages network effects: users have an incentive to bring friends and family onto the VoicePro platform because both parties earn when credits move between them.

Per-action rates (VPXN per minute, VPXN per transfer) are not asserted - they are derived by solving a three-equation system from the per-tier monthly cap and the canonical activity bundle for each tier. The full per-action rate table at low / base / high illustrative prices is published in `VPXN_Tokenomics_Model.xlsx` (Outputs sheet, Table O2).

11.1.1 Example Earning Scenarios

The following scenarios illustrate VPXN earning potential for different user profiles, based on launch-era reward rates (Year 1) and an illustrative VPXN price of £0.10 for modelling purposes only. Each tier carries a dual VPXN-and-£ ceiling: the user earns the lesser of the VPXN cap and (£ cap ÷ token price). This dual cap protects the consumer rewards pool from over-distribution at low token prices and protects user earning value at high token prices. Actual earnings depend on usage volume and are subject to the dynamic rate adjustment mechanism described in Section 11.6.1. All consumer rewards follow a 25/75 vesting split: 25% of earned VPXN is immediately liquid, while 75% vests linearly over 12 months (see Section 11.8).

The 4.6% / 9.6% / 13.3% effective-discount progression is computed from the cap-times-profile system at the £-denominated ARPU values shown above; it is not asserted independently of the model.

Value Proposition for Users: For Power users, VPXN rewards offset approximately 13% of monthly telecom costs when fully-vested tokens are converted back to calling credit. This creates a meaningful incentive to consolidate telecom spending on VoicePro Mobile rather than splitting usage across multiple carriers. The vesting mechanism creates a "savings account" effect - users who remain active for 12+ months accumulate a growing VPXN balance as vesting tranches unlock.

Impact on Customer LTV (Lifetime Value): Internal projections estimate that users who actively earn and spend VPXN will have approximately 2x higher retention rates and 30-40% higher ARPU compared to non-rewards users. The vesting schedule is central to this: users who leave the platform forfeit unvested token balances (which return to the consumer rewards pool), creating a meaningful switching cost.

Reward Rate Adjustments: The earning scenarios above reflect Year 1 caps when the consumer rewards pool emission is highest. Caps may be adjusted downward approximately 15-20% year-over-year as the emission schedule steps down (see Section 11.6). Per-epoch reward rates are dynamically adjusted based on (monthly budget / active eligible users) - see Section 11.6.1 - ensuring the programme never exceeds its allocated budget regardless of user growth.

Price Sensitivity (with dual-cap design): At £0.05/VPXN, the VPXN cap binds: a Power user earns 120 VPXN = £6 (~6.7% of ARPU). At £0.10 (base case): both caps coincide, user earns 120 VPXN = £12 (~13.3% of ARPU). At £0.20: the £-cap binds, user earns 60 VPXN = £12 (~13.3% of ARPU; same £-value, half the tokens, pool stretches twice as far). At £0.50: still £12 sterling, 24 VPXN (pool stretches five times further). The dual-cap holds the discount percentage approximately constant at and above base price; below base price, user takes the hit (less £-value but more tokens). The pool is mathematically incapable of being over-drawn from price appreciation.

11.2 The VPX Wallet

Earned VPXN tokens accumulate in the user's VPX Wallet - an integrated wallet within the VoicePro Mobile app designed to hold both fiat-denominated calling credit and VPXN token balance. The VPX Wallet provides a unified view of both balances and supports in-app conversion between them at the prevailing rate (fiat balance is custodial under the licensed payment partner; VPXN balance is non-custodial under the user's own keys - see WP-07 Business Plan §13). Users can hold VPXN indefinitely, spend it immediately or convert to calling credit at the current exchange rate.

The VPX Wallet is non-custodial for VPXN holdings: tokens are held in a user-controlled wallet with a private key derived from the user's account credentials and secured by device-level biometric authentication. VoicePro Plus cannot access, freeze or confiscate user VPXN balances. Fiat calling credit remains custodial and subject to standard regulatory requirements.

11.3 Spending VPXN

VPXN earned through platform usage can be spent across five categories within the VoicePro ecosystem:

• SIM Top-Ups - VPXN can be converted directly to calling credit at the prevailing exchange rate. This creates a closed loop: usage earns tokens, tokens fund further usage. For high-volume users, the effective discount on calling credit can be significant - particularly on international routes where per-minute rates are higher and VPXN earning rates are elevated.
• Merchandise - the VoicePro Shop accepts VPXN for devices, accessories and branded merchandise. Prices are denominated in GBP with a VPXN equivalent calculated at checkout using a 15-minute rolling average exchange rate. This prevents price manipulation through momentary exchange rate spikes.
• Gift Cards - VPXN can be exchanged for third-party gift cards from a rotating selection of retail partners. Gift card redemption uses a fixed monthly exchange rate published on the first day of each calendar month to provide price certainty for users planning redemptions.
• Staking - users can stake VPXN earned through consumer rewards in exactly the same staking infrastructure used by Operators and delegators. Consumer-staked tokens earn delegation rewards (see Section 9) and gain governance voting weight. This pathway allows engaged consumers to transition from casual platform users to active ecosystem participants.
• Fiat Cashout - VPXN can be withdrawn to fiat currency (GBP, EUR or USD) via the VPX Wallet. Cashout is processed through a licensed exchange partner with settlement to the user's linked bank account within 2-3 business days. A smooth cashout fee curve applies: 2.0% floor at prices below £0.10, rising linearly to 5.0% cap at prices of £1.00 and above (e.g. £0.20 → 2.5%; £0.50 → 3.5%; £0.80 → 4.4%). The smooth curve replaces an earlier step function (2% / 3.5% / 5% at price boundaries) that created arbitrage incentives at the boundaries. In all tiers, half the fee is burned and half funds the consumer rewards pool - creating a self-reinforcing cycle that also acts as a natural brake on extraction pressure during sustained price rises.

11.4 The Consumer Flywheel

The consumer rewards loop creates a self-reinforcing flywheel with four stages: users make calls and top-ups on VoicePro Mobile, earning VPXN with each transaction. Earned VPXN can be spent on further top-ups (extending usage), merchandise (driving platform revenue), staking (deepening ecosystem commitment) or cashout (providing liquidity). Platform revenue from consumer spending funds network operations and Operator rewards, which in turn sustain the infrastructure that delivers call quality and fraud protection. Better infrastructure attracts more users, who generate more transactions, who earn more VPXN.

The flywheel is designed to be sustainable at scale. Consumer reward emission rates are calibrated so that the VPXN earned per user per month remains a genuine incentive without exceeding the economic value the user's activity generates for the network. The programme operates around a Hybrid Vesting Model with dynamic rate adjustment: Year 1 budget of 10.8M VPXN supports approximately 20,000 active users at an average of 45 VPXN/month at target. As the user base scales beyond 20,000, per-epoch reward rates automatically adjust downward to stay within budget. By Year 4, the fee-funded supplement begins contributing, and by Year 6 the programme transitions fully to fee-funded rewards (Section 11.7) that scale sustainably with network usage.

Programme Kill Switch: The DAO retains authority, by simple-majority vote, to pause all consumer-rewards emissions for up to 30 days in response to a systemic exploit. During pause: no new rewards are issued, vested balances continue to vest on schedule, all earned-but-unvested balances are preserved. Pause may be extended to 90 days by super-majority vote. After 90 days, the programme re-opens with revised rules (also by DAO vote) or is wound down (token-holder vote, super-majority).

11.5 Anti-Abuse Measures

Consumer reward systems are inherently vulnerable to farming, wash-trading and bot exploitation. The VPX consumer rewards framework implements five layers of abuse prevention:

• KYC-Gated Enrolment - consumer rewards are only available to KYC-verified VoicePro Mobile accounts. Each individual can hold one rewards-eligible account. Duplicate accounts identified through document verification, device fingerprinting or behavioural analysis are permanently excluded.
• Velocity Limits - per-account monthly VPXN earning caps with concurrent £-ceilings (Bronze: 12 VPXN / £1.20 monthly · Silver: 45 VPXN / £4.50 monthly · Gold: 120 VPXN / £12.00 monthly) prevent bot-driven high-frequency farming and ensure budget sustainability. Tier assignment is determined by account age, KYC verification level and rolling 90-day usage history. All caps are DAO-governable. Daily sub-caps of 50% of the monthly cap prevent front-loading.
• Transfer Cooling - peer-to-peer transfer rewards are subject to a 24-hour cooling period and a maximum of 10 reward-eligible transfers per account per day. Transfers between accounts that share device fingerprints, IP addresses or payment methods earn zero rewards.
• Minimum Call Duration - call-based rewards require a minimum connected duration of 30 seconds. Calls terminated before 30 seconds earn no VPXN. This eliminates flash-call farming where bots place thousands of sub-second calls to accumulate per-call rewards.
• ML Anomaly Detection - the same ML scoring infrastructure used for carrier fraud detection (see Whitepaper 03: Blockchain Fraud Consensus) monitors consumer reward patterns. Accounts exhibiting anomalous earning behaviour - unusual call timing patterns, repetitive transfer loops, geographic impossibilities - are flagged for manual review and suspended from rewards pending investigation.

11.6 Consumer Rewards Emission Schedule

The 60M VPXN consumer rewards sub-allocation is distributed on a declining schedule with a labelled residual. Sum: 100% of pool. The Adoption-Overshoot Buffer is a labelled, single-purpose reserve drawn down by the dynamic-rate mechanism (Section 11.6.1) if Year-1 user adoption exceeds the 20,000-user target by 50% or more. The Buffer is also replenished by churn forfeitures from Section 11.8's 25/75 vesting. The schedule sums to 100% by construction:

• Year 1: 18% of pool (10.8M VPXN) - aggressive launch incentives to drive adoption.
• Year 2: 16% of pool (9.6M VPXN) - sustained high rewards as user base grows.
• Year 3: 14% of pool (8.4M VPXN) - gradual reduction as organic platform value increases.
• Year 4: 12% of pool (7.2M VPXN) - reward rates normalise as user behaviour embeds.
• Year 5: 10% of pool (6.0M VPXN) - fee-funded rewards begin supplementing emission.
• Year 6: 8% of pool (4.8M VPXN) - final emission year before full transition to fee-funded model.
• Adoption-Overshoot Buffer: 22% of pool (13.2M VPXN) - residual reserve.

11.6.1 Dynamic Rate Adjustment Mechanism

To prevent the consumer rewards programme from exceeding its allocated budget regardless of user growth, per-epoch reward rates are dynamically adjusted using the following formula:

Per-Epoch Rate Formula: Available VPXN per epoch = (Annual Budget ÷ 8,760 epochs). Per-user-per-epoch allocation = Available VPXN per epoch ÷ Active Eligible Users in epoch.

This mechanism is the critical safety valve of the consumer rewards programme. If Year 1 targets 20,000 active users but actual adoption reaches 50,000, per-user reward rates automatically scale downward - ensuring the 10.8M VPXN Year 1 budget is never exceeded. Conversely, if adoption is slower than projected (e.g. 10,000 users), per-user rates increase but remain capped at the monthly maximums (12 / 45 / 120 VPXN with £1.20 / £4.50 / £12.00 sterling caps) to prevent windfall concentration. Excess unspent budget carries to the Adoption-Overshoot Buffer for use in subsequent years.

The dynamic rate mechanism ensures three properties: (1) the programme is mathematically incapable of bankruptcy - total distribution can never exceed the allocated pool; (2) early users are rewarded with higher per-user rates during the bootstrap phase when adoption risk is highest; (3) the transition to fee-funded rewards is automatically accelerated if user growth outpaces emission capacity. All rate adjustments are computed on-chain per epoch and are publicly auditable.

Per-Cohort Rate Table - Fee-Funded Steady State (Year 7+): The figures below show how the dynamic rate mechanism scales per-user rewards across cohort sizes, assuming a £25M annual protocol fee base (see §13.2) and 5% Consumer Rewards Fund allocation = £1.25M/yr ≈ 12.5M VPXN at the £0.10 reference price. Per-user-per-month figures are computed as (annual VPXN budget ÷ 12 ÷ active users) and are bounded by the §11.6.1 tier caps (12 / 45 / 120 VPXN).

- 25,000 active users (~baseline): £1.25M / 25k ≈ £50/user/yr ≈ ~42 VPXN/user/month avg. Regular-tier (45) and Power-tier (120) caps still binding for active users.

- 50,000 active users: £1.25M / 50k ≈ £25/user/yr ≈ ~21 VPXN/user/month avg. Power-tier cap no longer binding; Regular-tier partially binding; rates auto-reduce per §11.6.1.

- 100,000 active users: £1.25M / 100k ≈ £12.50/user/yr ≈ ~10 VPXN/user/month avg. All tier caps non-binding; rates uniformly compressed; programme still solvent.

- 250,000 active users: £1.25M / 250k ≈ £5/user/yr ≈ ~4 VPXN/user/month avg. Minimum-viable reward level; expected to coincide with materially higher protocol fee volume (above £25M) which would lift the 5% allocation proportionately.

The per-cohort scaling is mechanical and on-chain; no DAO vote or operating-company action is required to enforce it. Above the 25,000-user baseline the programme remains solvent at every cohort size shown - reward rates compress, the programme does not break. If protocol fee volume scales above the £25M base case, the 5% allocation scales linearly and per-user rates recover. See §16.2 (Standard Reward Disclaimer).

11.7 Transition to Fee-Funded Consumer Rewards

After the 6-year emission schedule completes, consumer rewards transition to a fee-funded model. From Year 7 onward, 5% of protocol fees (the residual after the 40/55/5 fee split - see §10.4) is allocated to the Consumer Rewards Fund. This allocation is the sole ongoing funding source for the consumer rewards programme from Year 7 onwards. Any additional buyback contribution is explicitly excluded from the sustainability calculation in this paper.

At base-case projected network scale (£25M annual protocol fees - see §13.2 for the derivation), 5% allocation ≈ £1.25M/yr equivalent in VPXN (~12.5M VPXN at the £0.10 reference unit price used throughout this paper). At Year-1 per-user cap levels this supports approximately 25,000 active users on a sustained basis, funded entirely from protocol fees with no reliance on emission, buyback, or operating-company subsidy.

The programme is sized to be sustainable at this conservative ~25,000-user level. Two follow-on dynamics extend capacity above this baseline without changing the fee-only assumption: (i) the §11.6.1 dynamic rate mechanism scales per-user reward rates inversely with active-user count, so cohorts above 25,000 still receive meaningful rewards at lower per-user rates; (ii) protocol-fee volume above the £25M base case directly increases the 5% allocation. Both effects are mechanical, not contingent on any board decision.

A separate, conditional buyback programme is described in §16.5 of this paper. That programme is not ratified, not assumed in the Year-7+ sustainability calculation, and not required for the consumer rewards programme to remain solvent. The conditional buyback and the fee-funded transition are independent, and only the fee-funded component is load-bearing.

The transition is gradual: from Year 4 onward, an increasing proportion of consumer rewards is sourced from protocol fees rather than from emission. By Year 6 the emission component reaches zero and the fee-funded component fully sustains the programme. Users experience no discontinuity - reward rates adjust smoothly each epoch based on the pool available, per the §11.6.1 dynamic rate mechanism. See §16.2 (Standard Reward Disclaimer) - reward rates are not guaranteed.

11.8 Consumer Reward Vesting

All VPXN earned through consumer rewards is subject to a 25/75 vesting split designed to prevent rapid extraction, discourage farming and drive long-term platform retention:

• Immediate Liquidity (25%) - one quarter of each reward credit is immediately available in the user's VPX Wallet for spending, staking or cashout. This ensures users experience tangible, instant value from their mobile usage.
• Vesting Portion (75%) - three quarters of each reward credit enters a 12-month linear vesting schedule. Each month, 1/12th of the vesting portion unlocks and becomes liquid. A user who earns 45 VPXN in a given month receives 11.25 VPXN immediately and 2.8125 VPXN per month over the following 12 months.
• Vesting Accelerators - users who maintain an unbroken active streak of 6+ consecutive months (defined as at least one qualifying transaction per month) unlock vesting at 1.5× speed. Users with 12+ consecutive active months unlock at 2× speed. This recognises genuine, sustained platform engagement rather than one-time farming bursts.
• Forfeiture Conditions - if a user closes their VoicePro Mobile account, is permanently banned for anti-abuse violations or remains inactive (zero qualifying transactions) for 90 consecutive days, all unvested VPXN is forfeited and returned to the Adoption-Overshoot Buffer (Section 11.6). This protects the programme from dormant accounts accumulating unlocked value without contributing to platform activity.
• Staking Bonus - users who immediately stake their vesting portion (rather than waiting for linear unlock) receive a 1.5× staking weight multiplier on the vested tokens. This achieves the same cash-flow spreading effect as time-locked vesting but frames it as a user choice ("stake for more") rather than a restriction. Staked vesting tokens earn delegation rewards and governance voting weight while remaining in the vesting schedule.

Why Vesting is Essential: Without vesting, the consumer rewards programme would be vulnerable to rapid extraction - users could earn tokens, immediately convert at market price and churn, taking maximum value with zero long-term platform commitment. The 25/75 split balances immediate gratification with long-term alignment.

Impact on Budget Sustainability: The vesting mechanism spreads liquid token distribution across a 12-month window for each earning event. For Year 1 with a 10.8M VPXN budget and 20,000 active users: immediate liquid distribution is approximately 2.7M VPXN (25%), with the remaining 8.1M VPXN vesting linearly into Year 2. This means Year 1 liquid emission is well within the allocated budget, and Year 2 liquid supply includes both Year 2 emission and Year 1 vesting unlocks - already accounted for in the 6-year emission schedule.

12.1 Example Governance Proposals

The following illustrative examples show how the DAO voting process is designed to function:

Proposal 001 (illustrative): Despite 42% support, the proposal fails for want of a simple majority. The 19% quorum triggers the extended timelock, but quorum alone is insufficient - actual majority consensus is required.

Proposal 002 (illustrative): Strong quorum (31%) and decisive support (71%) reflect broad stakeholder alignment on security priorities. A higher minimum stake is the kind of change that deters low-quality Fraud Node registrations.

Proposal 004 (illustrative): An emergency multi-sig action can bypass normal governance during a critical oracle failure (see Whitepaper 01, Section 3.4), with a post-facto community ratification vote as the accountability mechanism that keeps the multi-sig authority subject to community oversight.

These examples illustrate the intended governance dynamics: some proposals pass decisively, others fail despite minority support, and emergency mechanisms exist for time-critical situations while remaining accountable to community oversight.

13.1 Conservative (500 nodes by Year 5)

At 500 active Nodes processing 2 billion minutes annually, the model projects: annual fee generation of approximately £8M equivalent in VPXN, annual burn of £3.2M equivalent (post physical-cap), net deflationary from Year 5+ depending on token price, and projected staking reward bands of 4-7% across Node types from fee redistribution alone (independent of emission rewards).

13.2 Base Case (2,000 nodes by Year 5)

At 2,000 active Nodes processing 15 billion minutes annually, the model projects: annual fee generation of approximately £25M equivalent, annual burn of £10M equivalent (post physical-cap), net deflationary from Year 4+ depending on token price, and projected staking reward bands of 6-10% across Node types. This scenario represents roughly the annual traffic of a single mid-tier wholesale carrier (about 6% of the international wholesale-voice market) routed through VPX.

Derivation of the £25M base-case figure. The £25M is built up from minute volume × VPX-eligible share × per-minute fee captured by the protocol. We use external market sources (TeleGeography Global Voice Traffic reports; BICS / iBASIS public wholesale-voice commentary) for the underlying global minute volume; the share and per-minute fee assumptions are VPX-internal modelling. The mechanical build-up is shown below; the figure is anchored to the traffic of a single mid-tier carrier rather than an aspirational market share.

Sensitivity: a ±20% move in either VPX share or blended take-per-minute produces approximately £20M-£30M annual fees, all of which keep the §11.7 fee-funded consumer rewards programme solvent at the ~25,000-user baseline. The figure is not load-bearing on a single assumption. Source attribution is required reading for any quantitative use of this paper: VPX does not own the underlying minute-volume data and cites third-party sources without endorsement.

13.3 Aggressive (10,000 nodes by Year 5)

At 10,000 active Nodes processing 80 billion minutes annually, the model projects: annual fee generation of approximately £80M equivalent, annual burn of £24M equivalent (post physical-cap), net deflationary from Year 2+ depending on token price, and projected staking reward bands of 8-14% across Node types. This scenario represents the combined volume of several major wholesale carriers - a high-share stress case, not a forecast.

We do not state a specific "X% supply reduction by Year N" headline because the answer is materially price-dependent. The model surfaces this as a price sensitivity rather than a guaranteed outcome.

14.1 Decentralised Exchange (DEX) Liquidity

Architecture note (revised). Per Protocol §3.4 and §21 (Glossary), VPXN is a native token on the purpose-built VPX chain and the chain gas token at mainnet genesis. There is no ERC-20 representation of VPXN at genesis and consequently no Ethereum-based DEX liquidity at Day 1. The Ethereum L2 bridge that enables an EVM-compatible representation of VPXN is a Phase 3 deliverable (Months 13-18). The DEX-venue plan below is Phase-3-dependent and is presented here as forward-looking liquidity strategy, not as a Day-1 commitment. Day-1 trading of VPXN occurs on the native VPX chain via a native AMM (specification to follow in WP-01 update) and via OTC venues. The section below is retained as forward guidance and is explicitly contingent on Phase 3 bridge delivery and audit clearance.

Phase 3 (Months 13-18) bridge-dependent DEX liquidity plan, funded from Seed Round proceeds ($200-300K allocation) and Treasury Reserve:

• Day-1 (genesis) - native VPX-chain AMM: Initial liquidity provided by VPX Treasury on the native VPX-chain AMM (specification in WP-01 update). VPXN/USDC-equivalent stable-pair depth at the £150-200K-equivalent band, managed by VPX Treasury with automated rebalancing.
• Phase 3 (Months 13-18) - Uniswap V3 [bridge-dependent, forward guidance]: Primary Ethereum-side liquidity pool VPXN/USDC with concentrated range, initial depth $150-200K USDC equivalent. Contingent on Ethereum L2 bridge delivery and audit clearance per Protocol §17 Phase 3 plan.
• Phase 3+ - Curve Finance [bridge-dependent, forward guidance]: Secondary VPXN/USDT stable-swap pool optimised for low-slippage large trades (carrier acquisition use case). Deployed only after Uniswap-side Phase 3 launch demonstrates volume justifying the additional venue.
• Additional DEX venues (Day-1 native or Phase 3 Ethereum-side): Evaluated based on organic trading volume and community demand. VPX will not fragment liquidity across multiple low-volume pools.

Initial DEX liquidity depth is conservative ($150-250K) reflecting early-stage market conditions and Seed Round capital constraints. This depth supports price discovery and small-to-medium trades during bootstrap phase. As network usage scales and Series A capital is deployed, additional liquidity will be added to support institutional-size trades ($50K-250K) with reduced slippage.

All DEX pools may be incentivised with VPXN rewards (from Marketing & Community sub-pool, subject to DAO approval) to attract third-party liquidity providers and deepen markets beyond treasury-provided depth. Liquidity mining programs will be evaluated based on capital efficiency vs. direct treasury liquidity provision.

14.2 Centralised Exchange (CEX) Listings

Centralised exchange listings will be pursued following 12-18 months of mainnet operation, demonstrated network adoption, and sufficient organic trading volume on DEXs. CEX listings are a post-launch growth strategy, not a day-one requirement. Target timeline and exchanges:

• Month 12-18 (Post-Mainnet): Apply to Tier 2 exchanges (Kraken, OKX, Bybit, KuCoin) following proven network traction (25+ Carriers, 100K+ daily transactions). Tier 2 listing fees range from $50K-150K per exchange.
• Month 24-36 (Maturity Phase): Pursue Tier 1 exchanges (Binance, Coinbase) if network metrics justify institutional interest. Tier 1 listings require meeting strict compliance, custody, and audit standards. Listing fees can exceed $250K-500K.
• Listing Readiness: All CEX applications require: (1) 6+ months of DEX trading history, (2) $500K+ monthly trading volume, (3) third-party smart contract audits, (4) registered legal entity with clear compliance framework, (5) demonstrated real-world utility (Carrier usage, transaction volume).

CEX listings are not guaranteed and VPX cannot control exchange listing timelines or approval decisions. DEX liquidity ensures that VPXN is tradeable from genesis regardless of CEX status. Series A capital (Month 12-18) will fund Tier 2 CEX listing fees and market making inventory. Tier 1 listings (if pursued) will require additional capital raise or allocation from Treasury Reserve subject to DAO approval.

VPX will NOT pay for "guaranteed listings" from unregulated or low-tier exchanges. All CEX listing decisions prioritise legitimate, compliance-focused venues with institutional-grade custody and audit standards.

14.3 Fiat On-Ramps & Off-Ramps

Direct fiat-to-VPXN purchase and VPXN-to-fiat cashout is enabled through partnerships with licensed fiat gateway providers:

• Card and bank on-ramp: Integrated into the VPX Wallet for GBP, EUR, USD purchases via card or bank transfer. Supports buy amounts from £10 to £10,000 per transaction. KYC required for purchases >£500.
• A second fiat gateway: broader geographic coverage (150+ countries). Integrated into VPX Network dashboard for node operator token acquisition.
• Fiat off-ramp: VPXN-to-GBP cashout (see Section 11.3). Settlement to user bank account in 2-3 business days. Tiered cashout fees apply (2-5% depending on VPXN price - see Section 11.3). Half of each fee is burned, half funds the consumer rewards pool.

Fiat gateways enable non-crypto-native users (VoicePro Mobile consumers, small carriers) to participate in the token economy without needing to navigate DEXs or manage self-custody wallets. All fiat gateway providers are licensed and regulated in their respective jurisdictions.

14.4 Professional Market Making

VPX intends to engage a quantitative trading firm (to be announced ahead of launch) to provide professional market making services for VPXN across DEX and CEX venues. Target market-making terms:

• Spread target: ≤1% bid-ask spread for trades up to $50K equivalent, ≤2% for trades up to $250K.
• Uptime commitment: Market maker maintains two-sided quotes 99% of trading hours (24/7 for DEX, exchange hours for CEX).
• Inventory commitment: Market maker maintains ≥$500K equivalent inventory ($250K VPXN, $250K stables/BTC) to ensure large order absorption.
• Fee structure: Monthly retainer + volume-based performance bonus. Market maker does not receive VPXN token allocation - all inventory is purchased or borrowed.

Professional market making ensures that large VPXN buyers (Carriers acquiring tokens for fee payment, institutions accumulating for staking) and sellers (Operators liquidating rewards, early investors taking profits) can execute trades without excessive slippage or waiting for organic order flow. This is critical for institutional adoption - Carriers require predictable execution when acquiring $100K+ of VPXN for network fee payment.

14.5 Oracle Price Feeds

Architecture note (revised). At mainnet genesis VPXN is native to the VPX chain and the chain gas token (Protocol §3.4); the native chain runs its own on-chain VPXN-fee oracle sourced from native AMM TWAP and OTC settlement reports. Chainlink VPXN/USD feeds and any other Ethereum-side oracle are Phase 3 (Months 13-18) bridge-dependent and not available at Day 1. The Chainlink-based plan described below is forward guidance, contingent on Phase 3 bridge delivery, and is retained for transparency on the long-run integration roadmap. Accurate, manipulation-resistant VPXN price data is required for fee pricing (Section 3.4 of Whitepaper 01), consumer reward calculations and accounting. The Phase-3 Chainlink integration plan:

• Day-1 (genesis) feed - native chain: 7-day TWAP computed natively on the VPX chain from the native VPX-chain AMM pool(s) plus aggregated OTC settlement reports submitted by registered counterparties. Update frequency: on-chain price update every 24 hours, or if price deviates >2.5% from last update. Manipulation resistance: TWAP smoothing prevents flash-trade and wash-trading price manipulation.
• Phase 3 (Months 13-18) feed - bridge-dependent, forward guidance: 7-day TWAP aggregated from Ethereum-side VPXN pools (Uniswap V3, Curve, Balancer) once the Phase 3 Ethereum L2 bridge is delivered and audited. This Phase-3 plan supplements - and does not replace - the native-chain feed at Day 1.
• Update frequency: On-chain price update every 24 hours, or if price deviates >2.5% from last update.
• Manipulation resistance: TWAP smoothing prevents flash-loan attacks and wash-trading price manipulation.

A Chainlink VPXN/USD feed is not live at mainnet genesis. The native VPX-chain price oracle described above is the canonical price-data source at Day 1 and is the feed used by Protocol §3.4 fee pricing and consumer reward calculations. A Chainlink VPXN/USD feed becomes feasible only after the Phase 3 (Months 13-18) Ethereum L2 bridge is delivered and audited - at that point the Chainlink feed will be evaluated as a redundancy oracle alongside the native feed. Third-party applications (wallets, portfolio trackers, tax software) at Day 1 should integrate against the native VPX-chain price oracle; Phase-3 Chainlink integration will be documented in a subsequent draft.

16.1 Glossary (Canonical)

The following terms are used with their defined meanings throughout the VPX document suite. They are not interchangeable; cross-document references are linted against this glossary:

16.2 Standard Reward Disclaimer

The following disclaimer applies to every consumer-facing or Operator-facing reward disclosure across VoicePro and VPX materials:

*VPXN rewards are utility tokens earned through participation in the VoicePro Mobile platform or operation of VPX infrastructure. They are denominated in VPXN and convertible within the VoicePro ecosystem. Reward rates are not guaranteed; they are subject to network conditions, DAO governance changes, and the dynamic adjustment mechanisms described elsewhere in this paper. The value of unredeemed VPXN balances may fluctuate. VoicePro does not solicit purchases of VPXN as an investment. VPXN is not a security, share, or claim on revenue.*

16.3 Standard Tax Notice

The following notice applies to every consumer-facing reward and staking-reward section across VoicePro and VPX materials:

*VPXN rewards may constitute taxable income or a benefit in kind in the recipient's jurisdiction. UK recipients should be aware that HMRC has indicated that crypto rewards from platform engagement may be treated as miscellaneous income or, in some circumstances, as a benefit in kind. Recipients are responsible for their own tax compliance. VoicePro does not provide tax advice; recipients should consult a qualified adviser. This notice is general in nature and does not constitute legal or tax advice.*

16.4 Securities-Framing Principles

This paper observes the following framing principles, applied across every section. They are stricter than legally required because the cost of error is fatal:

• No "yield" without immediate context. "Staking rewards" is acceptable; "yield" alone is not. Where yield-like figures appear, they appear as bands with stake-base scenarios explicit.
• No "expectation of profit", "expected returns", "investment", "appreciation". Replaced with utility-function language.
• No comparative claims to investment products.
• Consumer rewards are framed as service credit reducing a telecom bill, not as financial return.
• No "guaranteed", "promised", or "ensured" anywhere near reward figures. Use "scheduled", "designed to", "subject to network conditions".
• DAO-governable parameters are flagged as such on first mention.

16.5 What This Paper Explicitly Does Not Promise

For absolute clarity, this paper does not promise any of the following:

• A specific Year-20 supply-reduction percentage. The answer is materially price-dependent; the model surfaces the dependency rather than asserting a point estimate.
• Specific yield numbers. Bands replace point claims throughout.
• Post-Year-20 dynamics. The 20-year horizon is the model's commitment surface; beyond that, DAO governance has full latitude to revise emission, burn, and reward parameters.
• A guaranteed 5% B2B gross-profit buyback. The commitment requires a board resolution at VoicePro Plus Ltd; absent ratification, the programme operates as discretionary with a stated 5% target rather than a binding obligation.
• Specific Insurance Fund payouts. The Fund operates by process (Whitepaper 01, Section 19.5); specific payouts require multisig and DAO-elected-representative sign-off.

16.6 Detailed Design Specifications

This section specifies the detailed design for each protocol-mechanic area, at the level an auditor or integrating team needs. Parameters stated here are the design as adopted; those that are contract-deployment parameters are confirmed at deployment and in the independent security audit.

• Consumer activity attestation oracle. ConsumerRewards (§11) depends on knowing that a call happened, lasted ≥30 seconds, was UK / EU / International, and was between identified VoicePro accounts. The attestation oracle that bridges off-chain VoicePro Mobile usage to on-chain reward credits works as follows: per-epoch Merkle-root attestation signed by a threshold-multisig of VoicePro-operated reporter nodes (initial threshold 3-of-5, migrating to DAO-elected reporters by Year 2); per-user usage events committed off-chain, aggregated to a per-epoch Merkle root submitted on-chain; individual reward claims redeemed via Merkle-proof inclusion against the published root. The 30-second floor and tier classification (UK / EU / International) are enforced inside the aggregator before the root is committed.
• Fraud-consensus N-of-M threshold. The numeric quorum required for a fraud-blacklist commitment to finalise is 2/3 of active Fraud Nodes weighted by stake, with a minimum of 7 Nodes voting: M = max(7, ceil(2/3 × active_fraud_nodes)). The full fraud-consensus mechanics are set out in Whitepaper 03.
• VPX chain architecture. VPXN is a native token on the purpose-built VPX chain and is the chain gas token. Authoritative sources: Protocol §3.4 (native token / gas) and Protocol §21 (Glossary). At mainnet genesis there is no ERC-20 form, no IERC20 interface inside VPX-chain contracts, and no token bridge. The Ethereum mainnet checkpoint anchor (Protocol §13.4) is a one-way Merkle-root write for long-range-attack defence and is explicitly not a token bridge. An Ethereum L2 bridge for VPXN representation on EVM venues is a Phase 3 (Months 13-18) post-genesis deliverable scoped as a separate design problem with its own audit and insurance allocation. Any ERC-20 VPXN representation, or Uniswap / Curve / Chainlink VPXN-USD oracle usage, pertains to that Phase 3 bridged representation, not the native genesis token, and is Phase-3-dependent.
• Validator-selection randomness. Per Protocol §6.2: a deterministic geographic-merit shortlist of 2N nodes (top by stake × performance after regional / AS / datacentre filters), followed by a VRF-driven stake-weighted random sample of N validators from that shortlist. VRF seed: `keccak256(prev_block_hash, prev_epoch_hash, beacon_round)` with beacon_round drawn from drand or equivalent distributed-randomness beacon. The hybrid preserves geographic-diversity guarantees while introducing per-epoch unpredictability against long-horizon adversary planning.
• Foundation-board enforcement of "non-team majority + team recusal". The 4-of-6 Foundation-board multi-sig requirement is not a simple signer-count check. The contract must (i) hold an on-chain role registry tagging each authorised signer as `team` or `non-team`; (ii) validate that any approved transaction has at least 3 signers tagged `non-team` and at most 2 signers tagged `team`; (iii) for transactions where team members are recused, require zero `team` signatures. The role-tagged signer registry is updated on-chain, governed by a separate super-majority DAO vote.
• Emergency 7-of-9 multi-sig post-facto ratification window. The ratification window for emergency actions taken by the 7-of-9 multi-sig is 14 calendar days from the on-chain action; if the DAO has not ratified by simple majority within that window, the emergency action is automatically reverted at the next epoch boundary (or, where revert is technically impossible, the multi-sig is suspended pending DAO re-authorisation). This parameter is set at deployment.
• VPXN token decimals. VPXN uses 18 decimals. All VPXN-denominated amounts in this paper and in `VPXN_Tokenomics_Model.xlsx` assume 18 decimals. This is set explicitly in the deployed contract and confirmed in audit; it is not a free parameter post-launch.
• Damage-multiplier slashing requires an off-chain damages oracle. Protocol §8 specifies a 3× documented-damages multiplier for false fraud reports that cause carrier financial loss. The damages figure cannot be computed on-chain: it requires off-chain documentation of carrier termination losses, dispute correspondence, and (where contested) third-party arbitration. This uses a registered damages-oracle multisig with role-tagged signers, a 14-day evidence-submission window, and a counter-evidence period mirroring the fraud-consensus structure. The damages-oracle multisig is 5-of-9 (3 DAO-elected Operators, 3 DAO-elected non-Operators, 3 independent arbitrators); damages claims are capped at the lesser of demonstrated loss or 3× slashed-stake to prevent runaway multipliers.
• Custom routing-contract permissioning (Protocol §5.1). Carriers may deploy custom routing contracts in Move. Published custom routing contracts require (i) Operator-level stake equal to or greater than the Routing Node minimum, (ii) a passing automated Move Prover property suite covering loop-freedom and termination guarantees, (iii) a 14-day public-review window before activation, and (iv) explicit per-carrier opt-in. Contracts that do not meet these requirements are default-denied, and the deployer is the only Operator permitted to invoke a contract it publishes.
• Insurance Fund operating spec (TE §2.6 / WP-01 §19.5). The Fund is sized at 5% of total VPXN supply and is DAO-governed, and its operating spec is: (i) scope - covers Delegator losses from protocol-bug-induced slashing and bridge-contract failures (Phase 3+); explicitly excludes losses from disputed but lawful slashing, market price movements, exchange failures, and user key compromise; (ii) payout cap - per-claim cap of 1% of Fund balance; per-epoch aggregate cap of 5% of Fund balance; (iii) claim flow - claimant files on-chain with evidence package; 14-day review by DAO-elected Insurance Council (5 members, staggered terms); simple-majority approval triggers payout; super-majority required for any single claim above the per-claim cap; (iv) replenishment - DAO may direct a portion of fee burn (up to 5% of weekly burn) to Fund top-up if balance falls below 80% of target. Payouts are subject to DAO ratification.
• Encrypted CDRs and GDPR Article 17 (cryptographic erasure). Protocol §11.1-§11.2 specifies AES-256 per-record encryption of CDRs with keys held off-chain in a KMS. The Article-17 "right to erasure" is satisfied by destroying the per-record key (cryptographic erasure) rather than rewriting the chain. This pattern introduces a hard off-chain dependency on KMS availability and key-destruction integrity. The KMS will be a dedicated VoicePro-controlled HSM cluster at launch, with documented per-key destruction audit logs; key-destruction events are committed to chain as Merkle inclusions so an erasure request is publicly verifiable as having been honoured. This dependency is documented in the Encrypted Communications (WP-05) and Risk Disclosures (WP-09) papers as an operational risk surface.

These specifications are confirmed at contract deployment and validated in the independent security audit.

16.7 Provenance

Every numerical claim in this paper is traceable to a named cell in the internal tokenomics workbook (`VPXN_Tokenomics_Model.xlsx`, Inputs/Formulas/Outputs sheets), the single source of record for the figures presented here. The workbook is held by VoicePro Plus Ltd and is made available to qualified investors and nominated auditors under NDA; the filename identifies the source of record for audit purposes and is not an external URL.