bitpontOperations / Enso routing / Base
ERC20 & receipt-token routing
Enso routing · Base
Inspect both exact token contracts and request a supported same-chain route.
Your source and destination
Route details
Activity & recovery
One supported move on one network.
Enso can find eligible paths that redeem a tokenized position, exchange its underlying asset and deposit into another tokenized position. Bitpont accepts only ordinary ERC20 input and output for this first integration.
Each review binds your wallet, network, exact spend, output contract and minimum amount. The router must deliver at least that amount to your wallet or the complete same-chain route reverts. A prior approval remains a separate transaction.
How do I choose a source or destination?
Use a token or vault-share contract from an inspected Bitpont market. Paste the exact contracts, inspect their symbols, decimals and balances, then enter an amount. A listed asset is not a guarantee that a route is available.
What happens if a route fails?
Same-chain route execution reverts if its output protection is not met. Network gas can still be spent, and earlier approvals remain. Use the saved transaction record to establish finality before retrying.
Can this move an entire cross-chain portfolio?
This adapter executes one source-to-destination token route on the same network. Cross-chain delivery and multi-position recovery use the separate migration planner; neither is advertised as universally atomic.
THIS ROUTE
ERC20 & receipt-token routing
Source and output tokens can be vault shares. Minimum output must use the actual output token units.
Contract identity & reference data
- Network
- Base
- Token scope
- ERC20 and eligible tokenized positions
- Output protection
- Explicit minimum received
- Provider access
- Server configuration required
Configured route identity. Current balances, liquidity and transaction permissions are checked before review on this page.