bitpontPick up where
your capital left off.
Keep recovery references together. Check what completed, understand your history and follow the next action.
Your private recovery workspace
Synchronize action plans and transaction references from Swap, Earn, Bridge and Treasury. Keep your recovery code somewhere private: it contains both the access token and decryption key. Bitpont cannot recover a lost code. Anyone with the code can read or replace this workspace.
Local activity stays on this device until you choose Save. No signing keys or wallet permissions are synchronized.
Restored records reopen as unresolved. Check each transaction in its original product before continuing a plan. A successful source transaction alone does not prove a bridge delivery, Safe execution or venue fill. Synchronization is manual; save after important progress. Safe proposals and Safe/Solana payment-run lists are included. Imported completion is never accepted as authorization or execution evidence.
Delete stored data
This removes the server copy for this code, including notification subscriptions. Keep a local export if you need the records.
Follow the money, in its own units.
Read finalized ERC-20 transfers, vault deposit and withdrawal events, and source-network costs. Historical USD prices and missing protocol costs remain unknown. Transfers and deposits do not count as investment income.
Select an account. No wallet signature is needed for these public-chain reads.
What is missing from the result?
- Native-only transfers, rebases, off-chain fills and events outside the selected range.
- Protocol borrowing interest, perpetual funding and trading or bridge charges unless separately reconciled.
- Historical valuations and opening cost basis. Incomplete history cannot establish total performance.
Vault events describe flows. Receipt-token transfers and their underlying deposits are separate representations of the same exposure and must not be added together.
Follow a position. Know the next step.
Use your recovery code for a private inbox. Background monitoring reads the wallet and position references you explicitly save here. These monitoring references are stored on the server separately from your encrypted recovery archive. Optional webhooks receive signed messages.
Create or enter a recovery code to manage notifications.
Monitoring is best effort. Checks can be delayed by provider outages and workload; the last successful check and delivery state remain visible. Keep independent oversight of liquidation risk.