BITPONT / HELP/OPERATIONS

Connected Operations Help — Funding, Refinancing & Recovery

Review supported financial sequences and continue from the last verified step after an interruption.

On this page

Updated 8 November 2026

10 min read
BITPONT PRODUCT GUIDEOpen Operations →All guides

Start with a supported path

Operations connects compatible actions exposed by Bitpont’s adapters. Select an available operation, its source position or asset, the wallet and destination. This is not universal composition: incompatible protocols, assets, markets or networks cannot be combined just because they appear elsewhere on Bitpont.

Open connected operations →

Before approving a sequence

  1. Check the whole plan. Review source and destination assets, account ownership, approvals, expected outputs, minimums and available cost estimates.
  2. Distinguish atomic and separate steps. A supported same-chain bundle may revert as one transaction. Bridges and many funding or migration flows complete in separate transactions.
  3. Keep enough gas for the exit. An initial quote does not guarantee later liquidity, bridge delivery or available fees.
  4. Review fresh requests. Changes to wallet, account, network or financial inputs require fresh preparation. Do not reuse an older review for a changed operation.

Resume without repeating completed actions

Open the saved operation and inspect each step’s status and transaction reference. Confirm source execution and destination delivery separately. Resume only the next eligible step after checking the current onchain state. An unknown result needs reconciliation before resubmission; never infer failure from a timeout alone.

Local records and account boundaries

Recovery records on this device help reconnect the steps; they are not a universal chain-history ledger or an unattended execution service. Clearing browser storage can remove those records. Keep important transaction references independently. A rule or plan does not authorize automatic transfers without the required permissions.

Transaction status help →

Compare the cost of moving a yield position

In a cross-chain migration or Yield Explorer, open Is the move worth its costs? Enter a starting value, total one-time costs, both annual-rate assumptions, your holding period and APR or APY. Use the same valuation currency for all amounts.

The comparison deducts costs before redeposit and shows the difference between staying and moving, plus the time to recover switching costs under those assumptions. A higher rate may still leave you worse off over a short period. The calculator uses no live execution quote and does not submit or authorize a transaction.

Rates, prices, incentives, borrowing costs and exit availability can change. Compare product risks separately. Current composed USDC migrations support the eligible Aave and Morpho routes shown between Ethereum and Base, with separate wallet approvals and verified delivery. This does not enable automatic entry into every listed vault.

Compare switching costs →Prepare a supported migration →

What an operation authorizes

The plan review shows the minimum number of transaction confirmations and the participating networks. Additional token allowances or protocol permissions may require more prompts. The composition API reports the same execution model so an integrating application can explain it before handing you the plan.

A sequence is not one cross-chain atomic transaction. Current composed bridge steps use verified EVM delivery. The separate SOL → Pendle tool can prepare a single-signature funding route when this installation has enabled Relay execution and an eligible direct PT quote exists. Source payment and destination delivery remain separate chain events. Selected same-chain protocol bundles can combine actions, while the overall sequence retains separate reviews.

Scheduled orders and automated collateral are different

Supported accepted venue TWAP and trigger orders can continue when this page is closed. A saved connected operation does not authorize an unattended executor. Cross-chain collateral rescue is not enabled: withdrawing an LP and bridging can take longer than a position remains solvent.

Use the venue’s supported position and margin controls to review exposure. Treat thresholds as warnings, not guarantees. Any future automation needs explicit asset and amount limits, permitted contracts, expiry, revocation, execution costs and recovery rules.

Manage supported scheduled orders →

Start with a financial outcome

Open Operations and choose an outcome: buy an eligible Pendle PT, move into supported USDC lending, fund Boros margin, fund a Velocity subaccount or enter Marinade liquid staking. The selector builds compatible steps using the existing transaction review and recovery system.

  1. Select the source. Choose the owner wallet, network, wallet asset or supported lending deposit, and an exact amount. The outcome keeps the same owner across its steps. EVM inputs can use an exact token address; the Solana selector accepts SOL, USDC and USDT wallet inputs.
  2. Choose the destination. For Pendle, browse active maturities or enter the exact market address. Load its accepted funding assets. A PT is a claim in the market’s redemption asset, not a guarantee of dollar value. Margin funding creates available collateral, not an open derivative trade.
  3. Inspect the prepared route. Bitpont adds an eligible withdrawal, conversion or EVM bridge only where required. The summary lists transaction reviews, destination and exit path. Balances, withdrawal liquidity, gas and complete arrival amounts are not quoted by preparation.
  4. Open and save the operation. Review its exact assets, owner, networks and steps in the builder. Opening a new outcome replaces unsaved builder steps only; saved drafts and recovery records remain available.
  5. Review each transaction. Obtain fresh balances, quotes and simulation before signing. Extra approvals can require additional prompts. Keep native gas on each participating network.

Set a final PT floor

The optional minimum is expressed in PT units. The final purchase must have a reviewed, router-enforced minimum at least as high as this floor. A floor that cannot be met stops the purchase. Earlier withdrawals, swaps or bridges remain completed; their proceeds stay at the completed step’s destination.

Coverage and recovery

These are separately reviewed sequences, not single-signature intents. The simple selector supports eligible EVM-to-EVM funding and Solana-only funding; it does not prepare Solana-to-Pendle routes. Bridge continuations require finalized destination evidence. Unknown results block the next step and resubmission. Saved plans require this browser’s recovery records; exported drafts contain no execution proof.

Prepare an outcome → Check saved progress →

Migrate selected portfolio capital

Portfolio migration groups up to 24 selected wallet balances or supported lending deposits under one supported lending or Pendle PT destination. It is designed for reviewing several moves together while retaining separate transaction records for every source.

  1. Choose the owner and destination. Select one connected EVM wallet, Ethereum or Base, and the supported Aave USDC product or Morpho USDC Prime vault.
  2. Add your sources. Choose exact wallet assets on supported EVM networks, or supported Aave/Morpho USDC deposits on Ethereum or Base. Enter an amount for each source. Use exact contract addresses when symbols are ambiguous. The same source cannot appear twice in one group.
  3. Check and save. Bitpont checks each selected balance, network and owner, then prepares separate withdrawal, swap, bridge and deposit steps as required. A debt warning on an Aave source must be evaluated before withdrawing collateral. These checks do not establish that a withdrawal is liquid or that a bridge quote exists for the amount.
  4. Review a source. Saving a group does not move funds. Choose Review source, let Bitpont refresh its balance, and save the reviewed action plan. Follow its existing transaction reviews. Allowances, costs and simulations are checked by the product before signing.
  5. Resume from saved progress. Return to Portfolio migration in the same browser. Confirmed steps stay complete. Check a pending transaction before another submission. Completed groups link to the destination portfolio.

Discover balances and choose a maturity

Open Portfolio migration and scan one source network. Token scans are paginated; load additional pages or add a token by exact address. You can select 25%, 50%, 75% or 100% of verified non-native balances. Native gas assets require a manual amount. Scanned allocations expire after one minute and are checked again before preparation.

For Pendle, choose the destination network and browse active maturities. Select the exact market, load its accepted funding tokens and choose a PT purchase slippage limit. The preview estimates funding-token arrival, not the final PT purchase. A matured or changed market must be reviewed again. Principal redemption follows the accounting asset and underlying protocol conditions.

The switching-cost calculator compares user-entered constant-APY scenarios. It deducts the entered switching cost from deployed capital. It is not a live rate recommendation or guarantee.

Compare current routes before moving

After preparing a migration, or selecting a saved group that has not started, choose Check current routes. Bitpont rechecks the exact selected source balances, requests available swap or bridge quotes, and reads native gas balances on the participating networks. Routes are sorted by exact token output. Missing costs remain unknown.

The comparison uses 0.5% slippage for estimates only. It does not select or reserve an execution route, set the later signed minimum, or authorize a transaction. The estimated funding-token amount is before destination-entry costs. A Pendle migration still requires a fresh PT purchase quote. Known gas covers quoted conversion legs only; withdrawals, approvals and deposits are not included. Native funds present does not establish that enough gas is available.

When any source or quote is unavailable or expired, the complete-group output is unavailable. Source and quote expiry remove stale estimates. Cancel stops read-only checks. Once the migration has pending or completed execution activity, use its saved steps for current quotes rather than estimating its original full amount again.

What this migration does not combine

Cross-chain migration is not a single atomic transaction and does not share rollback across networks. One source can complete while another remains unfinished. There is no whole-portfolio quote, reserved balance, guaranteed arrival time or promised slippage saving. Keep gas on every participating network, especially when selecting native assets. Large positions may exceed available route or withdrawal liquidity.

This version covers selected EVM wallet assets and the supported USDC lending deposits. It does not migrate an arbitrary LP, debt, derivative account or Solana position. It stores up to ten migration groups locally and does not silently discard older groups. Saved groups contain public asset, wallet and plan information, never private keys.

Open portfolio migration → Inspect lending positions →

Use SOL to buy eligible Pendle PT

  1. Connect your Solana wallet and the EVM wallet that will receive PT.
  2. Open SOL → Pendle, choose Ethereum or Arbitrum, load a market and select a direct input asset.
  3. Enter the amount to invest on the destination and the maximum SOL payment. Keep extra SOL for source fees.
  4. Prepare and review the exact SOL payment, minimum PT and recipient, then sign the one Solana funding transaction.
  5. Use Purchase activity to track source finality and destination delivery, and export the recovery record.

Relay executes the committed destination calls. An unsuccessful purchase can leave the destination input token instead of PT, and the quoted refund has no guaranteed minimum. A provider success report alone is insufficient: Bitpont checks the finalized PT receipt and matching purchase calldata. The association between source and destination is supplied by Relay. Never repeat a pending funding payment.

Open SOL → Pendle →

Restore a signed SOL-to-Pendle purchase

Purchase activity can restore an exported signed purchase for its original Solana wallet. Bitpont checks the hash against the original reviewed message and queries chain evidence without submitting it again. A missing transaction alone does not clear a pending payment. Expiry requires a finalized block-height boundary, an invalid blockhash and repeated history checks. RPC availability and completeness remain trust assumptions. Keep the recovery export and do not pay again while the source or destination result is unresolved.