DECENTRALIZED RESIDENTIAL ACCESS · SOLANA

Fetch the web.
Prove the origin.

Proxinode routes requests through real residential nodes and returns every result with a signed record of where, when, and exactly what was retrieved. Origin, proven — not promised.

NODES ONLINE
4
REGIONS
FETCHES SERVED
$PRXN CArevealed at launch
HOW A FETCH SETTLES
escrow → proof → release
Published
Routed
Fetching
Validating
Settled
Proof-of-Fetch · verified
origin · timestamp · content hash · node signature
01 — THE PROBLEM

Access was solved. Provenance wasn't.

AI teams need fresh data from real residential IPs in specific regions. Today they pay for that access and take origin on faith.

DATACENTER IPs
Banned on sight

Fingerprinted, filtered, and served different content — or nothing at all.

access ✕ blocked
origin — irrelevant
RESIDENTIAL PROXIES
Access on faith

The request gets through — but nothing proves it ran where, when, or how the vendor claims.

access ✓ works
origin ✕ unprovable
PROXINODE
Access, with a manifest

Every fetch returns signed: origin coordinates, timestamp, content hash, node signature — verifiable by anyone.

access ✓ residential
origin ✓ proven
Proof-of-Fetch
VERIFIED · ed25519
TEE ATTESTED
ORIGINresidential IP · region · coordinates
TIMESTAMPwhen the response landed
CONTENT HASHsha256 of the exact bytes
NODE SIGNATUREsigned by the node’s registered key
02 — PROOF-OF-FETCH

A customs manifest for every byte.

Each fetch resolves into a compact, signed seal. Every layer is independently checkable against the node's on-chain identity. Nothing to trust, everything to verify.

01

The node signs origin, time, and content hash with its registered key the instant the response lands.

02

Validators check signature, geo-consistency, and freshness before escrow releases a single cent.

03

Premium orders add a TEE attestation: the fetch demonstrably ran inside untampered hardware.

03 — TWO SIDES OF THE NETWORK

Supply earns. Demand verifies.

SUPPLY

Run a node

Lend your home connection's idle capacity. Your node fetches, signs, and gets paid per verified result.

Earn per verified fetchUSDC, settled per epoch
Stake $PRXNunlocks premium orders
Rare geographyearns rarity multipliers
Misbehavestake is slashed — disclosed
Install the node client
DEMAND

Buy verified access

Publish an order — URL pattern, target geography, replica count, freshness. Escrow USDC. Receive data with proofs.

Target by regionpricing follows geo-rarity
Escrowed USDCreleases only on valid proof
Replicas & freshnessN nodes, bounded staleness
Premium tierTEE-attested, staked nodes only
Publish your first order
04 — THE $PRXN LOOP

Revenue in. Buybacks out.

Order fees and pump.fun creator fees fund $PRXN buybacks, distributed to stakers. Staked $PRXN gates premium orders — closing the loop between usage and the token.

Order fees
USDC · per fetch
Protocol treasury
on-chain · auditable
$PRXN buyback
open-market
Stakers
pro-rata distribution

STAKED $PRXN GATES PREMIUM ORDERS → MORE FEE REVENUE

05 — WHERE THINGS ACTUALLY STAND

Built, activating, planned.

Transparency is part of the product. Here is exactly what runs today, what switches on at token launch, and what is still roadmap.

LIVE NOW
Order escrow & settlement program
Proof-of-Fetch signatures (ed25519)
Node client — Chrome extension
Residential geo-routing & cross-check validation
AT TOKEN LAUNCH
USDC settlement
$PRXN staking & premium-order gating
Buybacks funded by protocol revenue
Reputation tiers & geo-rarity pricing
ROADMAP
TEE attestation for premium orders
Challenge-based slashing
External demand integrations (API)
Governance over fee & routing params