Self-custodial wallets: your assets, your control

What is a self-custodial wallet?

A self-custodial wallet lets you authorize the transactions that move your digital assets. A custodial platform controls the keys and processes withdrawals on your behalf. Lex uses Turnkey as its wallet infrastructure provider, with a separate wallet for each user and authorization through the user’s passkey. That gives you control over your wallet while keeping everyday sending and receiving familiar.

The key distinction is who can approve a transaction. With a custodial service, the balance you see is typically the platform’s record of what it owes you. With self-custody, your wallet’s holdings are recorded on the blockchain. The wallet application lets you view and use that account; the assets do not sit inside the app itself.

Custodial platforms can offer convenient account recovery and internal transfers. Those benefits come with reliance on the operator’s controls, withdrawal availability, and handling of customer assets. Self-custody changes that relationship: moving assets held in your wallet starts with your authorization rather than a withdrawal request against a platform balance.

What control changes in practice

Control means choosing when to send, who receives, and which supported asset to use. You can receive into your wallet from a compatible external wallet and send to another compatible address. The other person does not need to use the same app. This makes a wallet useful beyond a single company’s customer network.

For someone paid in stablecoins, that flexibility matters. You might keep some funds, send part to family, and use an available conversion route for local expenses. A wallet transfer and a bank payout remain different operations. The recipient’s preferred outcome determines which route makes sense, including any conversion or withdrawal costs.

Self-custody does not eliminate practical dependencies. Apps, signing infrastructure, and blockchain networks can experience outages. A token may have issuer restrictions, and a bank partner may require eligibility checks. Your authority over the wallet is a meaningful benefit, but it is not a promise that every transaction will always be available or instant.

How are your assets kept separate?

In Lex, each user has a distinct wallet address and a separate authorization environment. Assets held at that address are not an entry in a shared Lex trading balance. You can inspect the address and transaction history with a blockchain explorer, giving you a way to verify holdings independently of the app’s display.

There are two useful forms of separation here: one user cannot authorize another user’s wallet, and wallet balances remain distinct from Lex’s operating funds. This reduces reliance on a platform’s internal accounting for assets held directly in your wallet. An explorer can show a token balance, although you must check the network and token contract to identify the actual asset.

That separation has limits. A stablecoin still depends on its issuer and reserves. A tokenized stock still has the rights and restrictions in its issuer documents. Depositing into a DeFi vault exposes funds to that protocol; holding the resulting position in your wallet does not isolate the underlying investment from losses. Self-custody is not deposit insurance or a guarantee about every legal or insolvency outcome.

How Lex uses Turnkey

Turnkey provides the infrastructure that secures Lex wallet keys and processes authorized signatures. Its non-custodial key design keeps stored keys encrypted and restricts their use to authenticated requests under the configured permissions. Lex’s normal transaction flow does not require exposing a raw private key to Lex’s servers.

Lex creates a separate Turnkey sub-organization for each user, with that user as the controlling account and their passkey as the initial authenticator. Lex prepares the transaction for review, then relays the authorization produced by your device. Lex cannot use its own administrative credentials to sign a transaction from that user wallet.

Turnkey performs key generation and signing in secure enclaves: computing environments isolated by hardware, with checks on the software running inside. This protects key operations while allowing a familiar approval experience. Your passkey authorizes access; it is not the blockchain private key itself.

The provider’s name alone does not establish self-custody. Turnkey supports different configurations, and its shared responsibility model makes permission choices the application’s responsibility. Lex’s user-controlled configuration is the relevant detail. Protecting your device, passkey, and recovery access remains part of keeping that control.

Sending and receiving across compatible wallets

To receive, choose the supported asset in Lex’s receive flow and share the wallet address or compatible request. Tell the sender the exact asset and network. An address alone may not communicate both. For supported wallet transfers in Lex, check that the sender is using Base and the intended token before they submit anything.

To send, use a compatible address or payment request and review the destination, asset, amount, and any displayed cost before authorizing. QR payment requests can reduce typing by carrying those details. A QR does not prove that the recipient is trustworthy or make an unsupported network compatible.

After submission, check the transaction status before trying again. Network confirmation and the receiving app’s display may update at different times. Receiving a token into a wallet also does not automatically convert it into bank money. If a recipient wants pesos, reais, or euros, compare the available conversion and payout route separately.

An example: receive 200 USDC and send 80

Imagine Ana receives 200 USDC on Base into her Lex wallet. She checks the incoming transaction and the token balance at her wallet address. The payment is now associated with her wallet, rather than remaining as a withdrawable balance at the sender’s platform. If the sender used a custodial exchange, that platform first had to complete its withdrawal.

Ana wants to send 80 USDC to a friend using a different compatible wallet. She confirms the friend’s Base address and USDC support, reviews the transfer, and authorizes it with her passkey. Once completed, the friend has the 80 USDC at their address and Ana has 120 USDC remaining before any applicable fees.

These numbers illustrate token quantities, not a live quote or a guarantee of dollar redemption. The useful change is who controls the next step: each person authorizes their own wallet’s transactions. Neither needs to join the other’s app just to receive a compatible transfer. Converting the tokens into local spending money may involve additional costs and checks.

Keeping control over time

Keep access to your passkey and protect the recovery email associated with your wallet. Lex’s security and recovery flow can help you replace a lost passkey through the supported verification process. Recovery is a security-sensitive capability, so protecting your email matters alongside protecting the device you use to approve transactions.

If key export is available for your account, use the in-app export flow and understand how the destination wallet protects the key. Export availability is a separate feature; do not assume every account or app version offers it. A private key gives transaction authority to whoever obtains it, so never share it with someone claiming to provide support.

Before choosing any wallet, understand who authorizes transactions, how recovery works, and how you can move supported assets elsewhere. Lex brings that control into an everyday interface with Turnkey underneath. Knowing the boundaries lets you benefit from self-custody while making informed decisions about the assets you hold.