# Using a Self-Custody Wallet as Your Main DeFi Account: Where Your Assets Actually Sit

*Where your assets actually sit when you use a self-custody wallet to swap, earn, bridge, and trade, and the check to run before you sign.*

**Source URL:** https://degate.com/playbook/self-custody-wallet-defi-account/
**Updated:** 2026-07-02
**Published:** 2026-07-02
**Categories:** self-custody
**Primary entity:** Where a self-custody wallet's assets sit across active DeFi activities such as swaps, earning, bridging, and trading
**Author:** DeGate Editorial Team

**Questions this reference answers:**
- What changes when a self-custody wallet becomes your active DeFi account?
- Where do your assets actually sit when you swap, earn, bridge, and trade?
- Does a balance shown in your wallet mean the underlying assets are at your address?
- How is active DeFi use different from cold storage?
- What should you check before signing a DeFi transaction?

---

**TL;DR:**

Using a self-custody wallet as your everyday DeFi account does not work the way cold storage does. In a simple cold-storage setup, your assets usually sit at an address you control and are not actively interacting with protocols. In active use (swapping, earning, bridging, trading), your key stays with you the whole time, but your assets do not always stay at your address. Many actions hand the underlying assets to a protocol, and what your wallet shows afterward may be a receipt, an LP token, a position, or an account balance rather than the assets themselves.

One line holds the whole picture together: **your key control is the constant; where your assets sit is the variable.** So before you sign anything, it is worth asking three questions: where will the asset sit after this, what will my wallet actually hold, and what can happen before I can exit. This reference maps the states your assets move through and points to deeper references for each. It is not investment advice.

## "Active DeFi account" is not the same as "safe storage"

Most self-custody advice is about storage: not your keys not your coins, hardware wallets, cold storage, keeping assets untouched and safe. That advice answers one question: who controls the key. In self-custody, the answer is you.

But an active DeFi user is not trying to lock assets away. They are swapping, bridging, earning, and trading, often daily. For them, "is my key safe?" is necessary but not sufficient, because self-custody of the key does not automatically govern what happens to assets once they are working inside a protocol. Holding your own key settles who can *initiate* an action. It does not, by itself, settle what a protocol's rules can do to your assets *after* you have signed.

This is the shift worth naming clearly. Moving off a centralized exchange changes where your custody risk lives; it does not remove it. On a CEX, the exchange holds your assets and you carry exchange risk. In active self-custody, you hold the key, but each action you take can expose you to a different set of risks: approvals you granted, the contracts you interact with, the bridges you cross, the positions you hold. The rest of this reference is a map of those states, written for using a wallet, not just holding one.

## What your wallet shows is not always where your assets sit

Here is the idea most active DeFi risk traces back to: **a wallet balance display is not always the same thing as the underlying assets sitting at your address.** Your wallet may show a token, an LP token, a staked token, a position, a receipt, or an account balance. That display does not always mean the underlying assets are at your address and movable by your key alone. Depending on what you did, your assets fall into one of three states.

**1. Wallet-held token.** The asset is a token (an ERC-20 or the chain's equivalent) sitting at your address. What the wallet shows is what you hold. In the simplest case, moving it requires your signature or a permission you previously granted. This is the cold-storage state, and it is the one where "in my wallet" and "at my address" line up most cleanly.

**2. In-transit protocol flow.** The asset is passing through a contract or route: a swap, a bridge crossing, an aggregator or intent-based path. For simple on-chain swaps this can complete or fail as a single transaction, with assets landing back at an address you control. But wallet-based flows can also route through aggregators, intents, or bridges, so the questions that matter are what approval you granted and which contracts or routes touch the assets on the way.

**3. Protocol-held position or account state.** The asset has entered a protocol and is working there: an LP position, a staking deposit, a lending supply, a perps margin account. Your wallet may hold a claim, a receipt token, an LP token, a position representation, or nothing at all beyond an internal account balance shown by a front-end. Either way, the underlying assets are now governed by the protocol's rules. Exiting generally requires your signature, but the amount, timing, or conditions of exit may be set by the protocol: impermanent loss on an LP, a lending pool's utilization, or a liquidation engine on a perp can change what you are able to withdraw, without any further signature from you.

The constant across all three is your key: you usually control initiation, and exits generally require your signature. The variable is location: whether the underlying asset is at your address, in transit, or held inside a protocol changes with every action. Keep those two apart and the specific activities below become easy to place.

## Swaps

A swap exchanges one asset for another. In many simple on-chain swaps, the transaction completes or fails as one transaction, and you end up holding the new token at your address: briefly state (2), then back to state (1). The detail worth watching is the approval: to swap a token, you typically grant a contract permission to move it, and that permission can persist after the swap is done. A standing approval means the approved contract can move that token again later, which is why leftover approvals to compromised or malicious contracts are a common way wallets get drained, and why reviewing and revoking old approvals matters. Wallet-based swaps can also route through aggregators, intents, or bridges rather than a single pool, so the practical question is not "did the swap work" but "what did I approve, and which contracts or routes touched the assets." A cross-chain swap, in particular, is part swap and part bridge; see below.

## Earning (LP, staking, lending)

Earning is where the wallet display most often diverges from where the assets are. Providing liquidity, staking, or supplying to a lending pool means handing the underlying assets to a protocol or strategy, where they are governed by that system while the position is open. This is state (3): your wallet may show an LP token, a staked-token receipt, or a supplied balance, but the underlying assets are in the protocol, subject to its rules, and some systems route deposited assets onward into further contracts or strategies. Earning is not "your assets sit in your wallet and generate yield on the side." It is a position inside a protocol, exposed to that protocol's smart-contract risk, to conditions like impermanent loss on a liquidity position, and to whatever exit terms (delays, fees, unbonding periods) the protocol imposes. What you can withdraw at the end is set by the protocol's state, not only by what you deposited.

## Bridging

Bridging moves assets between chains, and it is worth treating as its own risk layer rather than a longer swap. Bridge is not one custody model. Some bridges are short-lived transfer routes; others leave the source asset locked on one chain while a mapped or wrapped representation exists on another, so what you hold on the destination chain may be a claim on locked collateral rather than the native asset. The trust assumption also varies: some bridges are trust-minimized, relying on the underlying chains' security, while others depend on an operator, validators, or relayers you are trusting not to fail or collude. Bridges have historically been a major source of crypto exploits. The point is not to memorize bridge designs, but to treat any bridge crossing as a distinct step with its own risk, and to know whether what you receive on the far side is the native asset or a representation of it.

## Perpetuals and other leveraged trading

Trading perps from a wallet is a clear case of state (3). To open a position, you fund a margin account inside the protocol; the collateral is credited to the protocol, not held as a token at your address. You sign to enter and to withdraw, but while a position is open the protocol's liquidation engine can close it and consume your margin if the market moves against you, with no additional signature required. Your key still governs entry and exit; your deployed margin does not sit in your wallet.

**For the full mechanics (the three custody models, funding, region limits, and fees), see [Can You Trade Perpetuals From a Self-Custody Wallet?](/playbook/perpetuals-self-custody-wallet/).**

## What the wallet actually does across all of this

It helps to be precise about the wallet's role, because "do DeFi from your wallet" makes it sound like the wallet is doing the swapping, earning, bridging, and trading. It is not. Across every activity above, the wallet is one thing: the entry and signing layer, and the one constant that stays with you. It holds your key, it signs your transactions, and it can connect you to third-party protocols, often by opening a protocol's own front-end in the wallet's in-app browser, increasingly from a phone. Smoother entry, including on mobile, does not change where the assets sit; it only changes how you reach the protocol.

A self-custody wallet such as DeGate can sit at that entry layer: holding assets, signing transactions, and connecting users to third-party dApps, such as through an in-app browser. The wallet is not the swap route, the yield protocol, the bridge, or the liquidation engine. Those roles belong to the protocols and routes you choose, and the risks that come with each belong there too.

## A check to run before you sign

The map matters less than the habit it supports. Before you confirm any DeFi action, ask three questions:

1. **Where will the asset sit after this action?** At my address, in transit through a route, or inside a protocol?
2. **What will my wallet actually hold afterward?** The original token, or a receipt, LP token, position, or account balance that represents assets held elsewhere?
3. **What can happen before I can exit?** What can the protocol's rules do to my assets between now and withdrawal: slippage, impermanent loss, a bridge's trust assumptions, withdrawal delays, liquidation?

If you can answer those three, you understand your exposure for that action. If you cannot answer the second or third, that is the signal to slow down before signing.

## FAQ

**Can a self-custody wallet be my main DeFi account?**
Yes. A self-custody wallet can be the entry and signing layer for swapping, earning, bridging, and trading. What it does not do is change where your assets sit once they enter a protocol. Your key stays with you throughout; the underlying assets may not stay at your address.

**If my wallet shows a balance or position, does that mean the underlying assets are still in my wallet?**
Not always. Your wallet may display a token, an LP token, a staked token, a position, a receipt, or an account balance. That display does not always mean the underlying assets are sitting at your address; often they are held inside a protocol, and what you hold is a claim or representation governed by the protocol's rules.

**Is using a wallet for DeFi the same as keeping crypto in cold storage?**
No. A simple cold-storage setup is usually designed to keep assets at an address you control, untouched by active protocol interactions. Active DeFi use puts assets to work inside protocols, where your key still controls initiation and exit but the protocol's rules govern the assets in between. They are different goals with different risk profiles.

**Does self-custody remove the risks I had on a centralized exchange?**
It changes them rather than removing them. You no longer carry the exchange's custody risk, but active use exposes you to approvals, smart-contract risk, bridge risk, and position risk like liquidation or impermanent loss. The key question shifts from "do I trust the exchange" to "do I understand what each action does to my assets."

**What should I check before signing a DeFi transaction?**
Ask three things: where the asset will sit after the action, what your wallet will actually hold afterward, and what can happen before you exit. If you cannot answer the last two, slow down before signing.

---

## Sources

### Protocol & technical documentation

- [Ethereum.org — Ethereum wallets](https://ethereum.org/wallets/)
- [Revoke.cash — What Are Token Approvals?](https://revoke.cash/learn/approvals/what-are-token-approvals)
- [Ethereum.org — Introduction to blockchain bridges (trusted vs trustless, trust assumptions, bridge risks)](https://ethereum.org/bridges/)

---

*This reference maps where assets sit across common DeFi activities when a self-custody wallet is used as an active account. It is not investment advice. Protocol behaviour, approvals, and asset availability depend on the specific protocol, chain, and route you use, and can change; confirm specifics before you sign, and consult a qualified adviser where relevant.*
