Latch: C-Address Onboarding Infrastructure

<aside> 🧩

Submission: Stellar Community Fund (SCF)

Track: RFP — C-Address Tooling & Onboarding

Focus: Bridge, Wallet, and SDK for Soroban Smart Accounts

</aside>

The Problem

Users and wallets cannot reliably fund Soroban Smart Accounts (C-addresses) from the places money actually comes from:

CEXs and fiat on-ramps only support G-address deposits
Memo mistakes are common and lead to lost deposits or long support loops
Smart account deployment is a chicken-and-egg problem: the account may not exist yet, but the user needs an address now
Fee bootstrapping: first-time users often have 0 XLM to deploy or pay for actions

Result: Smart Accounts are harder to adopt, even when they are the better security and UX model.

The Solution: Latch

A C-address onboarding infrastructure layer that bridges legacy Stellar funding rails (G-address deposits) to Soroban Smart Accounts (C-addresses).

Feature	Benefit
Memo-based routing	Works with existing CEX + on-ramp deposit flows without protocol changes
Deterministic smart account addresses	Users can share a C-address before deployment (predictable onboarding)
Fee sponsorship / abstraction	New users can receive funds and deploy even with 0 XLM
Reference wallet + SDK	Gives the ecosystem a pattern to copy and integrate quickly

Latch brings “send from Coinbase/Binance to your smart account” to Soroban — safely and with a copy-paste UX.

Key Features

Latch is a production-grade onboarding stack for Soroban smart accounts:

3 components: Bridge, Wallet, SDK
Memo router: versioned memo format with checksum validation
Relay/indexer service: detects deposits and forwards to the correct C-address
Smart account factory: deterministic deployment to make “pre-deployment addresses” real