# Redeem Without the App

> Exit a leveraged position by calling the Facility directly — from Etherscan, a wallet that accepts raw calldata, or Foundry's cast. Find and verify an open redemption intent, approve and deposit your Position Manager shares, and claim USDC once the intent resolves.



You can exit a 3F position without the 3F app by calling the Facility directly — from Etherscan, a wallet that accepts raw calldata, or Foundry's `cast`. Under the hood this is the [withdrawal flow](/protocol/flows/withdrawal/): you deposit your Position Manager shares into a Facility **redemption intent**, receive ERC-6909 LP tokens 1:1, and once the position has been unwound and the intent resolved you burn them to claim USDC.

The steps mirror [Deposit Without the App](/protocol/guides/manual-deposit/) with the two assets swapped. Read that page first for [how to send the calls](/protocol/guides/manual-deposit/#how-to-send-the-calls) in each format; this page focuses on what differs for redemptions.

1. `approve` — let the Facility pull your Position Manager shares
2. `deposit` — send the shares into the redemption intent
3. *(wait for the intent to resolve)*
4. `claim` — burn your LP tokens and receive USDC

## Before You Start

You need:

- **A wallet that can sign transactions** on Ethereum mainnet, holding the Position Manager shares you want to redeem and some ETH for gas.
- **An allowed address.** Position Manager shares can only move between addresses their [TransferGuard](/protocol/transfer-guard/) allows. If your address is not onboarded, `deposit` reverts with `TransferBlocked`.
- **An intent ID confirmed by the 3F team** — see [step 1](#1-find-an-open-redemption-intent).

| Contract | Address |
| --- | --- |
| Facility | [`0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F`](https://etherscan.io/address/0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F) |
| USDC | [`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`](https://etherscan.io/address/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48) |
| Position Managers | One per asset and leverage tier — see [Deployments](/protocol/deployments/) |

:::caution[Position Manager shares have 18 decimals]
Every amount on this page is in Position Manager shares, which have **18 decimals** — not 6 like USDC. Redeeming 1,000 shares means `1000000000000000000000` (1,000 × 10¹⁸). The builder below does the conversion for you.
:::

## Fill In Your Values

Enter your values once and every call below is filled in for you, in all three formats.

The calls below use these placeholders — replace them with your own values:

- `<intent-id>` — the intent ID from step 1
- `<amount>` — the amount in shares, in 18-decimal units
- `<your-address>` — your address
- `<position-manager>` — the Position Manager whose shares you hold (see the Deployments page)

To redeem your whole position, read your exact share balance and use it as the amount:

Call `balanceOf(address)` (selector `0x70a08231`) on the Position Manager, `<position-manager>`.

- **Etherscan:** Read as Proxy → `balanceOf` (#4)

| Field | Value |
| --- | --- |
| owner (address) | `<your-address>` |

```sh
cast call <position-manager> \
  "balanceOf(address)(uint256)" <your-address> \
  --rpc-url "$ETH_RPC_URL"
```

## 1. Find an Open Redemption Intent

Redemptions go into a dedicated intent whose deposit asset is the Position Manager you hold. There is usually one open redemption intent per Position Manager.

- **Ask the 3F team** for the intent ID to use, or
- **Use the 3F LP API.** `GET https://lp.3f.xyz/v1/intents/{asset}?state=created&vault=<position manager address>` lists the open intents for that Position Manager. Keep the item with `"type": "withdraw"`; the intent ID is `onChainId`. The `{asset}` slugs are listed on the [deposit guide](/protocol/guides/manual-deposit/#1-find-an-open-intent), and the full API reference is at [lp.3f.xyz/docs](https://lp.3f.xyz/docs).

:::danger[Confirm the intent with 3F]
Whichever way you find an intent, confirm with the 3F team that it is the right one for your redemption before sending shares. The facilitator can close an intent's deposit window early, and caps change over time.
:::

## 2. Verify the Intent

Read the intent's configuration with `getIntent`:

Call `getIntent(uint256)` (selector `0x906e277b`) on the Facility, `0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F`.

- **Etherscan:** Read as Proxy → `getIntent` (#6): https://etherscan.io/address/0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F#readContract#F6

| Field | Value |
| --- | --- |
| id (uint256) | `<intent-id>` |

![getIntent result on Etherscan for a FALCONX-5X redemption intent](/images/guides/etherscan/redeem-get-intent.webp)

```sh
cast call 0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F \
  "getIntent(uint256)(((address,bool),(address,bool),uint256,address,uint40,uint8,bool),address,address,bool)" <intent-id> \
  --rpc-url "$ETH_RPC_URL"
```

A redemption intent is the mirror image of a deposit intent (see [how to read the `cast` output](/protocol/guides/manual-deposit/#2-verify-the-intent)). Check every field; if anything does not match, do not deposit — contact the 3F team.

| Field | Expected for a redemption intent |
| --- | --- |
| `depositAsset.asset` | **The Position Manager whose shares you hold** — the one you selected above. Cross-check it on [Deployments](/protocol/deployments/) |
| `depositAsset.isPositionManager` | `true` |
| `targetAsset.asset` | **USDC** — `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48` |
| `targetAsset.isPositionManager` | `false` |
| `depositCap` | Leaves room for your shares (18 decimals) — see [the cap check](#check-the-remaining-cap) below |
| `guardKey` | The same address as `depositAsset.asset` |
| `resolveStart` | **In the future**, with a comfortable margin (Unix timestamp in seconds) |
| `quorum` | **At least `1`** |
| `resolved` | **`false`** |

:::caution[Check the target asset]
When only the deposit side of an intent is a Position Manager, the contract does not restrict what the target asset can be. Make sure `targetAsset.asset` is USDC and `targetAsset.isPositionManager` is `false` — otherwise the intent is not a redemption into USDC.
:::

In the example above, intent `12147` takes FALCONX-5X shares (`0x7495…da93`) and targets USDC, accepts up to about 2.79M shares, closes deposits at `1793333580` (2026-10-30 04:13 UTC), requires one guardian signature and is not resolved — a valid redemption intent at the time of the screenshot.

### Check the Remaining Cap

`totalSupply` returns how many shares have already been deposited into the intent:

Call `totalSupply(uint256)` (selector `0xbd85b039`) on the Facility, `0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F`.

- **Etherscan:** Read as Proxy → `totalSupply` (#19): https://etherscan.io/address/0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F#readContract#F19

| Field | Value |
| --- | --- |
| id (uint256) | `<intent-id>` |

![totalSupply on Etherscan for the redemption intent](/images/guides/etherscan/redeem-total-supply.webp)

```sh
cast call 0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F \
  "totalSupply(uint256)(uint256)" <intent-id> \
  --rpc-url "$ETH_RPC_URL"
```

The most you can redeem through this intent is `depositCap − totalSupply`, both in 18-decimal share units.

## 3. Approve the Position Manager Shares

Position Manager shares are an ERC-20 token, so the approval is made on the Position Manager itself, with the Facility as spender:

Call `approve(address,uint256)` (selector `0x095ea7b3`) on the Position Manager, `<position-manager>`.

- **Etherscan:** Write as Proxy → `approve` (#2)

| Field | Value |
| --- | --- |
| spender (address) | `0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F` |
| amount (uint256) | `<amount>` |

![Position Manager approve on Etherscan with the Facility as spender](/images/guides/etherscan/redeem-approve.webp)

```sh
cast send <position-manager> \
  "approve(address,uint256)" \
  0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F <amount> \
  --rpc-url "$ETH_RPC_URL" --interactive
```

## 4. Deposit Your Shares

Call `deposit` on the Facility with the redemption intent ID and the number of shares you approved:

Call `deposit(uint256,uint256)` (selector `0xe2bbb158`) on the Facility, `0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F`.

- **Etherscan:** Write as Proxy → `deposit` (#10): https://etherscan.io/address/0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F#writeContract#F10

| Field | Value |
| --- | --- |
| id (uint256) | `<intent-id>` |
| amount (uint256) | `<amount>` |

![deposit of 1,000 FALCONX-5X shares into intent 12147 on Etherscan](/images/guides/etherscan/redeem-deposit.webp)

```sh
cast send 0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F \
  "deposit(uint256,uint256)" \
  <intent-id> <amount> \
  --rpc-url "$ETH_RPC_URL" --interactive
```

The Facility pulls your shares and mints you the same amount of LP tokens for that intent. Simulating first catches a missing approval, an exceeded cap or a closed deposit window before you send.

## 5. Wait for the Intent to Resolve

After deposits close, the facilitator unwinds the position: it takes a bridge loan to repay the Position Manager's debt, withdraws the freed collateral, redeems it with the fund and repays the bridge loan from the proceeds (see the [withdrawal flow](/protocol/flows/withdrawal/)). The fund's redemption schedule sets the pace — expect anywhere from days to weeks depending on the asset.

Until deposits close, `withdraw` gives you your shares back 1:1:

Call `withdraw(uint256,address,address,uint256)` (selector `0xa318c1a4`) on the Facility, `0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F`.

- **Etherscan:** Write as Proxy → `withdraw` (#36): https://etherscan.io/address/0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F#writeContract#F36

| Field | Value |
| --- | --- |
| id (uint256) | `<intent-id>` |
| from (address) | `<your-address>` |
| receiver (address) | `<your-address>` |
| amount (uint256) | `<amount>` |

```sh
cast send 0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F \
  "withdraw(uint256,address,address,uint256)" \
  <intent-id> <your-address> <your-address> <amount> \
  --rpc-url "$ETH_RPC_URL" --interactive
```

The intent is ready to claim when [`getIntent`](#2-verify-the-intent) shows `resolved: true`.

## 6. Claim Your USDC

A claim pays out your pro-rata share of everything the intent holds: mostly USDC — the proceeds of the unwound position net of the bridge loan's cost — plus any Position Manager shares that were not unwound. To see exactly which tokens and amounts the intent holds:

Call `intentBalances(uint256)` (selector `0xa43bb77d`) on the Facility, `0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F`.

- **Etherscan:** Read as Proxy → `intentBalances` (#10): https://etherscan.io/address/0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F#readContract#F10

| Field | Value |
| --- | --- |
| id (uint256) | `<intent-id>` |

```sh
cast call 0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F \
  "intentBalances(uint256)(address[],uint256[])" <intent-id> \
  --rpc-url "$ETH_RPC_URL"
```

Then call `claim` with your address as both `from` and `receiver`, and the number of LP tokens to burn as `shares` — the total number of Position Manager shares you deposited, still in **18-decimal** units:

Call `claim(uint256,address,address,uint256)` (selector `0xd6e3413e`) on the Facility, `0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F`.

- **Etherscan:** Write as Proxy → `claim` (#5): https://etherscan.io/address/0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F#writeContract#F5

| Field | Value |
| --- | --- |
| id (uint256) | `<intent-id>` |
| from (address) | `<your-address>` |
| receiver (address) | `<your-address>` |
| shares (uint256) | `<amount>` |

![claim for intent 12147 on Etherscan](/images/guides/etherscan/redeem-claim.webp)

```sh
cast send 0x4e013ca8fF612a58F53C822904cDD0eC538a4A4F \
  "claim(uint256,address,address,uint256)" \
  <intent-id> <your-address> <your-address> <amount> \
  --rpc-url "$ETH_RPC_URL" --interactive
```