Continue with evidence.

Read the coverage before the total.

Portfolio scans supported accounts when you connect. Pendle discovery checks PT, YT and LP balances across the catalogue, including matured markets. Curve StableSwap-NG discovery checks registered pool and gauge balances. Balancer checks wallet-held V2/V3 pool receipts from its indexed catalogue.

Use Continue discovery to read up to twelve source pages per pass. Pause after the current read when needed, and continue until each source finishes. The coverage indicator separates finished sources, remaining reads and failures. An outage, changed catalogue or failed contract read remains incomplete. External staking, unsupported gauges and unclaimed rewards can require separate protocol inspection. Wallet receipts are not additional capital on top of their underlying position. There is no claim of complete reconciled net worth.

Start on one device. Verify on the next.

1. Open Account tools, create a recovery code and keep it privately. Copy it before saving your workspace.
2. Save your local transaction references and action plans. AES-GCM encryption happens in the browser. The server receives an access token and ciphertext, never the encryption key.
3. On the next device, enter the same code and load the archive. Review its references, then restore them.
4. Restored transactions remain unresolved until their original product checks them again. Reconnect the correct wallet and verify every completed step before continuing.
5. Save again after new progress. If two devices changed the same record, resolve the conflict before replacing either version.

A recovery code does not sign transactions or control funds. Losing it prevents decryption; sharing it gives access to the archived references. Exported JSON is unencrypted and contains public wallet and transaction details. Keep that file private. Deleting server data does not delete local records or blockchain transactions.

Treasury transaction references, validated Safe proposals and Safe/Solana payment lists are included. A restored Safe execution hash is retained for checking; fresh matching execution evidence is required before that batch is complete. Restored Solana runs without their source transaction evidence remain pending. Safe proposals and Safe/Solana payment-run lists are included. Imported completion is never accepted as authorization or execution evidence. For a missing record, inspect its transaction hash on the matching network. Source success does not by itself establish a delivered bridge, a completed Safe payment or a derivative fill.

Separate capital flows from performance.

Account history reads finalized token transfers and ERC-4626 deposit/withdraw event shapes over the block range you select. Continue up to twelve pages at a time, pause after a read and review gaps. Export JSON or CSV with exact atomic units, transaction identities, costs and missing reads. The visible event table is paginated without discarding loaded evidence. Each transaction contributes its network cost once, even if it emits many token events.

A token deposit, a receipt mint and a wallet transfer are not three sources of income. Actual performance requires opening value, deposits, withdrawals, closing value, attributable costs and a complete history. Missing prices, native transfers, rebases, borrowing interest or funding prevent a complete result. For a supported vault, select its protocol and exact contract to compare historical opening and closing assets with deposit and withdrawal flows. The gross result stays unavailable until the selected range is complete and transferred-share basis is resolved. Network fees and other charges remain separate, so this is not a net profit figure. Use the existing accounting import and export tools to supplement documented gaps.

Compare now accepts entry costs, both exit costs, borrowing APRs, entry delays, withdrawal waiting periods and estimated destination capacity. Borrowing costs continue during the withdrawal waiting period; this scenario adds no further yield during that wait. Optional lower and higher destination rates show how the same costs change the outcome. Export the assumptions and results for review. Its break-even is a scenario under your assumptions, not a forecast or quote. Inspect current limits on the exact product page.

Monitor the event you need to act on.

Choose a supported loan-health source, Pendle maturity, withdrawal request, deBridge delivery or failed source transaction. Save the exact network, wallet and position reference. Choose a Pendle maturity notice from one to ninety days, pause individual monitors and mark inbox events as read. Background checks continue while this server is running. The inbox shows stale or unavailable checks instead of treating an outage as a healthy position.

Monitoring references must be readable by the server and are separate from encrypted recovery data. For webhooks, configure a public HTTPS endpoint and secret. Validate the HMAC-SHA256 of timestamp + a period + the raw JSON body using the Bitpont-Signature header, check the timestamp, and deduplicate Bitpont-Event-Id. Use Test delivery to send a clearly labeled test without changing a position observation. Tests are limited to once per minute per workspace. Failed deliveries retry with backoff up to eight attempts.

Alerts can be late or unavailable. They never approve, repay, claim or close a position. Open the exact linked product and review fresh conditions.