Give your users, wallets and contracts names people can recognise. Soran connects those names to on-chain addresses and payment instructions, under a namespace you control.
Explore illustrative app flows below. Names, amounts and confirmations are examples; no transactions are submitted. Try a live testnet lookup →
For DAOs
Give your community a shared identity.
Bring contributors, treasury accounts and governance contracts under your DAO’s namespace. Reserve official names and choose who can register, with rules enforced on chain.
●registration · invitation list · proof checked on chain
The owner reserves official names and configures an invitation list. Eligible members then claim their own names.
For wallets
Make every destination more familiar.
Let users enter a name when sending a payment and see elected display names in their transaction history. Read the destination directly from Soran’s Universal Lookup contract, including any required memo or muxed routing ID.
A supporting wallet resolves a name, includes the returned memo and lets the sender approve the payment. The wallet can show the recipient’s elected display name in history.
For exchanges
Give every customer a deposit name.
Turn a deposit address and its routing details into one name customers can share. Supporting wallets resolve the complete destination, helping users avoid copying an address and memo into separate fields.
One thing to share. Supporting wallets resolve the address and memo together.
→ GABFQI…LZJNL6 · memo 336114091
✓
Incoming deposit
●+500 USDCelected sender name · memo matchedCREDITED
A customer shares a deposit name. The sending wallet resolves the account and required memo; the exchange matches the incoming deposit using those routing details.
For apps built on Stellar
Your app. Your namespace. Your users.
Let users claim a branded username during signup or from their account settings. Build the experience with Soran’s SDKs, choose free or paid registration, and reserve the names your team needs. Users approve their own claims without the namespace owner manually signing each registration.
Your application checks availability and claim rules. The user reviews the name and signs the claim with their own wallet. The confirmed name resolves on chain.
For payments
A name worth putting on an invoice.
Give customers a recognisable destination for invoices, checkout and repeat payments. A Soran-enabled payment app looks up the receiving address and routing details before the sender approves.
Your payment app can display the sender’s elected name: alice.nova.
An invoice shows a payment name. A supporting wallet resolves the destination and required memo, then asks the sender to approve. The payment application records the receipt.
For anchors
Make the Stellar side of your service easier to use.
Add recognisable names to customer receiving accounts and supported deposit destinations. Integrate name resolution into your existing deposit and payout flows, so users can work with familiar names while your service handles the underlying payment details.
A customer provides a name. The anchor resolves the complete Stellar destination, submits its payout and records the result in its own customer history.
Others
Familiar names for everything you’re building.
From NFTs and games to AI agents, tokenized stocks and real-world assets, give the wallets and smart contracts behind your product names people can recognise. Apps can resolve those names directly on chain to find the address they need.
Think collection.yourbrand, player.yourgame or agent.yourapp.
NFT collection contracts, player accounts, AI-agent accounts and tokenized-asset contracts can each have a readable name that resolves to their address.
Build with names. Resolve on chain.
Start with a namespace for your product, or integrate lookup into an application you already run.