Connected DeFi Operations: Proceeds, Wallets and Partial Completion

Understand how supported financial steps connect, what a saved plan contains and how to recover after partial completion.

Begin with an exact source and destination

A useful financial plan identifies the starting wallet, network, asset and available amount, then the intended destination. “Move USDC into a supported vault” becomes a concrete sequence only after the source funds, target market and required transactions are known. A product appearing in the builder does not establish that every asset or market is compatible.

Carry confirmed proceeds into the next step

Bitpont’s connected-operation builder verifies each supported action before adding it to a draft. A later action can reference the proceeds of an earlier one rather than assuming a displayed balance is available. For liquidity workflows with more than one token output, each output retains its own budget and identity. Never add both a receipt token and the underlying asset as though they were independent copies of the same capital.

Understand the boundary between steps

Consider a withdrawal, bridge and deposit. If the withdrawal completes and the bridge cannot proceed, the withdrawal does not reverse automatically. If the bridge has been submitted, the destination deposit must wait for the supported delivery checks. Separate networks and margin accounts do not become atomic merely because their steps are displayed in one plan.

The final deposit amount can differ from an early estimate because of costs, price changes and actual execution. Review a fresh quote, available balance, permissions and simulation at each signing step. Keep enough native gas where the chosen route requires it.

A recovery checklist

1. Reconnect the owner wallet recorded on the plan and select the correct network.
2. Read the last transaction identifier and distinguish submitted, confirmed and completed states.
3. Check which asset is now spendable and whether a request is still pending.
4. Continue from the next eligible step. Do not recreate completed steps to make the screen appear consistent.

Keep a usable record

Save or export a verified draft before leaving when you need to retain its structure. Device-local records are not a hosted automation service and are not proof of execution. Imported drafts require review and cannot sign on their own. Linking positions helps organize a strategy but does not merge their collateral or liquidation rules.