EcoPylon documentation

Introduction

EcoPylon is a DePIN aggregation layer. The DePIN space — Decentralized Physical Infrastructure Networks — is fragmented across dozens of isolated protocols, each with its own token, SDK, pricing model and onboarding. To use three of them you integrate three times.

EcoPylon collapses that. You connect once and reach every provider on the grid across six categories — compute, storage, bandwidth, wireless, sensors and energy — through a single API, a single balance denominated in PYLON, and a single settlement layer on Robinhood Chain. The grid handles discovery, price/region/reliability routing, metering and payment; you handle your workload.

Quickstart

Rent a GPU from the grid in four steps.

1. Create an account and generate an API key in the Grid Console.
2. Fund your balance with PYLON on Robinhood Chain.
3. Send a deploy request naming a category, a spec and a max price.
4. Receive an endpoint; usage is metered per second and settled from your balance.

curl -X POST https://api.ecopylon.com/v1/deploy \
  -H "Authorization: Bearer $PYLON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "compute",
    "spec":     { "gpu": "H100", "count": 2 },
    "region":   "eu-west",
    "maxPrice": "0.90"
  }'

{
  "session":  "sess_9f2a…",
  "provider": "HeliosGPU",
  "endpoint": "ssh://sess_9f2a@eu-west.grid.ecopylon.com",
  "price":    "0.86",        // PYLON / hr
  "region":   "eu-west",
  "status":   "running"
}

Core concepts

• Grid — the aggregated pool of all provider capacity across the six categories.
• Provider — anyone listing hardware or capacity: a DePIN network, a data center, or an individual operator.
• Category — one of the six resource types the grid routes across.
• Routing — matching each request to the best provider by price, region, spec and reliability score.
• Session — a metered rental of capacity, billed per second and settled in PYLON.
• Settlement — on-chain payment on Robinhood Chain; providers are paid, a share of fees is burned.
• Staking — locking PYLON for priority routing, better rates and (for providers) a reliability bond.
• Reliability score — a rolling measure of a provider’s uptime and SLA compliance that weights routing.

Resource categories

Renting capacity

A deploy request describes what you need, not who serves it. The grid resolves the provider. You can constrain the match with region, maxPrice and minUptime, and pin a specific provider with provider if you want to bypass routing.

POST /v1/deploy
{
  "category":  "storage",
  "spec":      { "size": "40TB", "encryption": "aes-256" },
  "region":    "us-east",
  "minUptime": 99.9,
  "maxPrice":  "2.50"       // PYLON / TB / month
}

Stop a session with DELETE /v1/sessions/{id}. Billing halts at the second the session ends; unused prepaid balance stays in your account.

API reference

Base URL https://api.ecopylon.com/v1. All requests are authenticated with a bearer API key. Responses are JSON; timestamps are RFC 3339; prices are PYLON strings.

Rate limits: 60 requests/minute per key. Errors return an error.code and human-readable error.message. Idempotency is supported via the Idempotency-Key header on POST /deploy.

Becoming a provider

If you run any kind of infrastructure — GPUs, storage, bandwidth, wireless coverage, sensors or energy storage — you can list it on the grid and earn PYLON as demand is routed to you. Providers post a PYLON stake as a reliability bond; higher stake and uptime raise your routing priority.

pylon provider register \
  --category storage \
  --capacity 40TB \
  --price 2.10 \
  --region us-east \
  --stake 25000

pylon provider status      # health, reliability score, earnings
pylon provider withdraw    # claim accrued PYLON

Earnings accrue per settled session and can be claimed at any time. Failing an SLA slashes a portion of your bond and lowers your reliability score, which reduces the share of demand routed to you until it recovers.

Staking & routing

Staking PYLON serves two roles. Renters stake for priority routing, discounted rates and higher rate limits. Providers stake as a reliability bond that backs their SLA. The router scores each candidate provider on price, region match and reliability, and biases toward staked participants on both sides.

PYLON token

PYLON is the settlement, staking and governance asset of the grid. Fixed supply of 1,000,000,000, a low 1% / 1% buy/sell tax, and a fee-burn tied to network usage. Every session is paid in PYLON; a share of protocol fees buys back and burns PYLON, linking real usage to supply. Holders govern new categories, provider standards and treasury spend. See the Token page for allocation and mechanics.

Network & contracts

EcoPylon runs on Robinhood Chain — an Arbitrum Orbit network with native ETH. Sub-cent settlement makes per-second metering of infrastructure viable. Contract addresses are published here once deployed and audited.

Security & audits

• The PYLON token and grid contracts will be audited by an independent firm before mainnet launch; reports link here.
• Liquidity is locked at launch; the lock reference will be published on the Token page.
• Provider bonds and slashing are enforced on-chain — the router cannot pay a provider that failed settlement conditions.
• API keys are scoped and revocable; never embed a key in client-side code.
• Found an issue? Responsible disclosure to security@ecopylon.com.

Developer FAQ

Do I need to hold PYLON to test? Testnet PYLON is available from the faucet once the network is live; use chain ID 46630.

Can I pin a specific provider? Yes — pass provider in the deploy body to bypass routing.

How is usage metered? Per second for compute/energy, per GB for bandwidth, per TB/month for storage, per node/month for wireless, per feed for sensors.

What happens if a provider goes down mid-session? The grid fails the session over to another provider in the same category/region where possible, and you are only billed for capacity actually delivered.

More general questions are answered on the FAQs page.