Swagger

Architecture

The path from intent to execution, node by node. What each service along it owns is on the services page.

System architecture

A coordinated path from intent to execution

UGTP keeps client signing explicit while coordinating rails, fees, routing, and network execution behind one gateway.

01

Client

Builds the intent, holds the account key, and signs whatever the prepare response returns.

02

UGTP Gateway

Authenticates public requests, resolves the project's fee terms, decides which rail carries the operation, and orchestrates the account, swap, fee, private-token, and transaction APIs.

03

UGTP Engine

Builds the operation for its rail, relays or broadcasts it, and tracks it to a terminal status.

04

UGTP Paymaster

Sponsors gas through EntryPoint v0.9 and collects the fee from the transferred asset on the UserOperation rail.

05

Avalanche executor

Executes an account-signed EIP-712 request on Avalanche C-Chain and pulls its fee against a one-time allowance.

06

LI.FI routing

Returns same-chain swap and cross-chain route execution data.

07

Chainlink price feeds

Prices the fee's dollar-denominated parts in the fee token, read on chain by the fee-collecting contracts.

08

Blockchain network

Executes the submitted operation or the routed transfer.

client gateway: API request, then the signaturegateway routing: discover a routegateway engine: prepare and submitengine paymaster: sponsor the UserOperationengine executor: relay the signed requestengine network: broadcast and trackpaymaster network: execute gaslesslyexecutor network: execute gaslesslyrouting network: execute the routepaymaster price-feeds: price the fee in USDexecutor price-feeds: price the fee in USD