Back to Documentation

Transaction Lifecycle

How transactions flow through Setu's cross-chain infrastructure

On This Page

Overview

Setu's transaction lifecycle is designed for security, speed, and reliability across diverse blockchain networks. Each transaction follows a standardized path from initiation to completion.

3-8s
End-to-End Speed
Non-Custodial
Security Model
100%
Transaction Transparency

Transaction Flow

👤

User initiates transfer

User connects wallet and sends stablecoins to the Lock Contract on the source chain

Fee Structure

0.3%
99.7%

Protocol Fee

0.3%

Sent to the Revenue Address for protocol maintenance and development

User Transfer

99.7%

Sent to the Admin Address which handles transfers to destination chains

Cross-Chain Example: Stellar → Arbitrum

✨

Stellar

non-evm
User Address:G...
Lock Contract:XLM_Lock
Token:USDC
âš¡

Arbitrum

evm
User Address:0x...
Release Contract:0xARB_Release
Token:USDC.e

Technical Implementation

Signature Generation

Setu uses a threshold signature scheme (TSS) to securely generate signatures for destination chain transactions. This approach eliminates the single point of failure present in traditional multisig setups.

// Simplified threshold signature process
1. Multiple signers generate key shares
2. Transaction data is distributed to signers
3. Each signer creates a partial signature
4. Partial signatures are combined on-chain
5. Final signature is generated and validated

Status Monitoring

Every transaction is monitored throughout its lifecycle, from initiation on the source chain to confirmation on the destination chain.

Real-time confirmations across different chains
Optimized gas price strategies for timely inclusion
Chain-specific finality guarantees (e.g., 12 blocks on EVM)

Error Handling

Transaction Failure
High Severity

Transaction reverts or fails on destination chain

Resolution:

Automatic retry with transaction simulation pre-check and parameter adjustments

Network Congestion
Medium Severity

High gas prices or network congestion on destination chain

Resolution:

Automatic retry with increased gas price and optimized gas limit

RPC Failure
High Severity

RPC endpoint unresponsive or returning errors

Resolution:

Automatic failover to redundant RPC providers with different infrastructure