Client
Builds the intent, shows the operation for review and requests the required signature from the account wallet or signer.
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.
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.
UGTP Engine
Builds the operation for its rail, relays or broadcasts it, and tracks it to a terminal status.
UGTP Paymaster
Pays the network through EntryPoint v0.9 and collects gas plus the fee from the transferred asset on the UserOperation rail.
Avalanche executor
Executes an account-signed EIP-712 request on Avalanche C-Chain and pulls its fee against sufficient ERC-20 allowance.
LI.FI routing
Returns same-chain swap and cross-chain route execution data.
Chainlink price feeds
Prices the fee's dollar-denominated parts in the fee token, read on chain by the fee-collecting contracts.
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: settle gas in the tokenexecutor → network: settle gas in the fee tokenrouting → network: execute the routepaymaster → price-feeds: price the fee in USDexecutor → price-feeds: price the fee in USD