UGTP v2 — the Universal Gasless Transaction Platform — is a B2B API that abstracts chains, gas, bridges, and blockchain security into a single intelligent execution layer. Not a wallet, not a bridge — infrastructure any wallet, dApp, or fintech app integrates in one call.
“The first secure intelligent execution layer for consumer cross-chain finance.”
UGTP v1 required a separate integration layer for every network it supported — each with its own adapter, its own maintenance, its own attack surface. UGTP v2 collapses that into a single common platform serving all EVM-compatible chains through one unified execution gateway.
A modular stack where each layer is independently auditable and replaceable. Requests flow down through integration, orchestration, and capability providers, and settle on Avalanche C-Chain.
Every UGTP v2 capability is exposed through the same authenticated gateway — and every one of them runs behind the security gate.
Programmable Kernel accounts that replace seed phrases and gas tokens with code.
Automated bridging and DEX aggregation across 60+ chains — any token to any token.
Pre-execution threat analysis on every transaction — a protocol gate, not a plugin.
Avalanche C-Chain provides the execution environment for all UGTP v2 smart account operations.
What happens inside the gateway between a client’s
POST /transactions call and final settlement — ten steps, with the security
firewall as a mandatory gate.
POST /api/v1/transactions with an X-API-Key
header and the transaction body.api_keys table. Invalid or disabled → 401.GET /transactions/:id through pending → submitted → confirmed.Cross-chain operations are asynchronous: the client requests a quote, executes a route, and polls for completion. LI.FI selects and aggregates the bridge and DEX path; the security gate runs before any value moves.
Security is not an optional plugin. Transactions and cross-chain transfers all
pass through a SecurityProvider before execution. The interface is pluggable: a mock
provider runs today, and the real Check Point provider activates automatically the moment
CHECKPOINT_API_URL and CHECKPOINT_API_KEY are set — with zero changes to
routes or services.
A single contract every provider implements:
This makes UGTP v2 a mandatory security gate — every integrating wallet gets Check Point protection by default.
All endpoints live under /api/v1/ and ship with an
OpenAPI 3.0 specification rendered at doc.ugtp.io. Seven endpoint groups cover the whole platform.
X-API-Key header except /health and /admin/login. API keys
are stored only as SHA-256 hashes. Admin endpoints additionally require an
Authorization: Bearer <JWT> token issued by /admin/login.
State lives in a serverless PostgreSQL database (Neon). The schema auto-initializes on the first request — no migration step to run.
UGTP v2 settles on Avalanche C-Chain, leveraging its mature ERC-4337 ecosystem, sub-second finality, and low transaction fees for gasless smart account operations.
C-Chain provides production-grade infrastructure with full ERC-4337 support, enabling smart accounts, bundlers, and gasless operations out of the box.
UGTP v2 monetizes at several points along a single transaction through the API and settlement infrastructure.
UGTP v2 is engineered to sit where infrastructure, security, and consumer distribution meet — making each partner stronger than they are alone.
UGTP v2 is delivered as five Next.js + TypeScript applications deployed on Vercel, sharing one PostgreSQL database on Neon.
Next.js · TypeScript · Tailwind · viem
| Data — PostgreSQL / Neon | Hosting — Vercel
| Settlement — Avalanche C-Chain