TESTNET
Ecosystem tokens · SOMA.finance · Ethereum ⇄ XRP Ledger
Fund your SOMA purchase from your XRP wallet. LiquidAcre and LiquidManzana are Reg S / Reg D security tokens sold through a FINRA broker-dealer and settled in USDC. They are not stablecoins, and LiquidLabs does not sell or hold them. What we do: quote the funding leg from your XRP wallet, track it on-chain, and show the tokens SOMA delivers to an Ethereum address only you control.
Securities offered through Tritaurian Capital, Incorporated — Member FINRA | SIPC (BrokerCheck #45500). Facts below as of 2026-09-04, from SOMA Starter and the verified contract on Etherscan.
LQDA and LQDM are regulated security tokens sold by a broker-dealer, not stablecoins. The safe way to buy them from an XRP wallet keeps the broker of record where it is and keeps the token in an address only you control.
Your XRPL wallet funds USDC on Ethereum through a ranked bridge route; SOMA delivers the ERC-20 to your Ethereum address; LiquidLabs reads that balance. An XRPL twin would be an XLS-33 MPT with RequireAuth so only transfer-agent-authorised holders can hold it.
No wrapped security, no custody of securities, no second venue — and a credible path to native XRPL issuance the day the issuer decides it.
USDC (XRPL native)CCTP / Wormhole / AxelarERC-20 balanceOfMPT RequireAuthLand as a liquid, programmable, universally accessible financial asset through legally enforceable digital tokens.
0x4d89167b844eAfF93319775aD1E9daEA4815f118Real-estate tokenization for the Spanish-speaking Americas — the LiquidAcre model, one hemisphere south.
The two ways
One way works today; the other is the native future. Walk each one step by step — click a step, use the arrow keys, or press play.
The security stays an ERC-20 on Ethereum, delivered to an address only you control. LiquidLabs funds and tracks the purchase; it never holds the token.
Open a SOMA.finance account and pass the broker-dealer's KYC / AML and eligibility checks — Reg S outside the United States, Reg D for accredited investors inside it. Your documents go to SOMA and its broker-dealer. LiquidLabs never sees them.
Send USDC from your XRP wallet over Circle's CCTP: it is burned on the XRP Ledger and minted on Ethereum, attested by Circle, with no third-party bridge holding it in between. The funding job here advances only on on-chain evidence — a burn you can see, a mint you can see.
Pay in USDC at SOMA's checkout. The broker-dealer books the trade and the ERC-20 security is delivered to the Ethereum address you gave SOMA — not to LiquidLabs, not to a pool.
Attach that Ethereum address here — a hardware wallet, MetaMask, or the address your vault wallet derives from the same seed. We store the public address and nothing else: no key, no token, no power to move it.
Your ecosystem holdings show beside your XRPL assets through a read-only balanceOf() call on the verified contract. No wrapped token, no custody, no second venue — a mirror, not a vault.
The issuer locks the Ethereum token and issues an XLS-33 Multi-Purpose Token on the XRP Ledger that only authorised accounts may hold. One cap table, two ledgers, one transfer agent.
The tokens to be twinned move into an issuer-controlled vault contract. What is locked there is exactly what may exist on the XRP Ledger — one security, never two supplies.
A registered transfer agent keeps the single cap table and publishes a daily attestation: locked on Ethereum equals issued on XRPL. When the two numbers disagree, issuance pauses until they agree again.
Issuance is a governance decision with a second approver and a reason on record — a ceremony, never a deploy. The Platform Studio holds both approvals and the why, in the audit trail.
The XLS-33 Multi-Purpose Token is issued with RequireAuth, CanTransfer, CanLock and CanClawback set: only accounts the issuer authorises after their own KYC can receive it, transfers can be frozen, and a lawful order can be honoured. CanTrade stays off — no open market until the transfer agent says so.
An authorised XRPL account holds the twin like any other asset — in Xaman or a vault wallet. Redemption burns it on the XRP Ledger and unlocks the Ethereum token; the cap table stays one.
Way A is what this page does today. Way B is a specification until the issuer, a transfer agent and the two-person governance ceremony say otherwise.
Sign in to attach the address SOMA delivers your tokens to. We store the public address and nothing else — no key, no seed, no signing.
Sign in| Route | Trust | Fee | Finality | |
|---|---|---|---|---|
| Circle CCTP Circle burns and re-mints the same USDC. No third party ever custodies it. ★ Recommended. |
Issuer-operated burn & mint | $0 | ~900s | Sign in |
| Axelar General message passing, secured by Axelar's staked validator set. The canonical bridge for the XRPL EVM Sidechain. |
Proof-of-stake validator set | $0.40 | ~18s | Sign in |
| Wormhole A signed VAA from a 13-of-19 guardian quorum authorises the mint. |
19 guardians · 13-of-19 quorum | $0.45 | ~120s | Sign in |
| LayerZero Fast and cheap. Security equals the weakest verifier in the configured DVN set — read the config before trusting it with size. |
Configurable DVN set | $0.28 | ~4s | Sign in |
| XRPL path payment XRPL → XRPL only. For another chain, choose a bridge below. |
Atomic · single ledger | — | — |
USDC exists natively on the XRP Ledger. Circle's CCTP burns it there and mints the same USDC on Ethereum — no third party ever holds it, which is why it ranks first. A funding job hands you deposit instructions and advances only on on-chain evidence; the platform does not execute the bridge for you.
Why stop at funding? The ecosystem issuer can issue the same security natively on the XRP Ledger as an XLS-33 Multi-Purpose Token. The flags below are what make that legally defensible — and the transfer agent is what makes it true.
LQDAT · LiquidAcre (XRPL twin · testnet)| Flag | Set | Why |
|---|---|---|
RequireAuth |
on | Only accounts the transfer agent authorises can hold units — this is how Reg S / Reg D eligibility is enforced at the unit. |
CanClawback |
on | Court orders, erroneous transfers and sanctions require the issuer to recover units. |
CanLock |
on | Corporate actions and lock-up periods (Reg D: one year) need a freeze the ledger enforces. |
CanTransfer |
on | Holder-to-holder transfers between authorised accounts are the point of a secondary market. |
CanTrade |
off | XRPL does not yet implement MPT trading on the DEX (XLS-82 is a draft). Setting it would promise a venue that does not exist. |
Cap-table sync. The transfer agent keeps one cap table across both chains: a unit issued on XRPL is a unit burned or locked on Ethereum, and vice versa. Without that agent the twin is a promise, which is why mainnet needs a decision, not a deploy.
LQDMT · LiquidManzana (XRPL twin · testnet)| Flag | Set | Why |
|---|---|---|
RequireAuth |
on | Only accounts the transfer agent authorises can hold units — this is how Reg S / Reg D eligibility is enforced at the unit. |
CanClawback |
on | Court orders, erroneous transfers and sanctions require the issuer to recover units. |
CanLock |
on | Corporate actions and lock-up periods (Reg D: one year) need a freeze the ledger enforces. |
CanTransfer |
on | Holder-to-holder transfers between authorised accounts are the point of a secondary market. |
CanTrade |
off | XRPL does not yet implement MPT trading on the DEX (XLS-82 is a draft). Setting it would promise a venue that does not exist. |
Cap-table sync. The transfer agent keeps one cap table across both chains: a unit issued on XRPL is a unit burned or locked on Ethereum, and vice versa. Without that agent the twin is a promise, which is why mainnet needs a decision, not a deploy.
A twin on mainnet is a legal decision (transfer agent, issuer approval, two-person ceremony) — never a deploy. A testnet twin can be minted by an operator once the decision says so; until then this section is a specification, not a token.
Nothing on this page is an offer or solicitation of securities by LiquidLabs. LQDA and LQDM are offered exclusively through SOMA.finance and its broker-dealer, subject to their eligibility and disclosure requirements. Facts are stated as of 2026-09-04 and may change.