Skip to main content

​
Trace a deposit

Open the Flagship USDC vault’s deposit history on Base. Search for intent 45cd8617-8e56-4891-8129-75592b4fdb26 and expand its row. This is a real same-asset deposit from Deposit CBAssets (3a3c). The production strategy has its own allocation and redemption-buffer policy. It is not an execution of the teaching 10%/7.5% reserve strategy.
  1. Row: confirm action DEPOSIT, state COMPLETED, and the intended strategy. Public Base USDC history searched for intent 45cd8617-8e56-4891-8129-75592b4fdb26, showing one completed Deposit CBAssets row.
  2. Detail: compare the execution ID and lifecycle timestamps. This intent was created at 2026-10-20T18:50:30.029113Z and completed at 2026-10-20T18:50:35.135081Z. Expanded Base deposit with completed lifecycle, matching intent and strategy identifiers, and execution 46bf87f4-cd8e-469a-8d7e-55caf27f7d06. UI times are localized.
  3. Fill: expand the fills section. One fill links to execution 46bf87f4-cd8e-469a-8d7e-55caf27f7d06 on chain 8453. The same deposit's single Base onchain fill, transaction link, raw amounts and gas used of 610847. This panel is not a transaction receipt.
  4. Transaction: open the Base transaction. Its successful receipt and source Deposit event confirm the transaction-local deposit.
The fill’s token_in is a zero-address placeholder; token identity here comes from the receipt’s USDC transfer and Deposit event, not that placeholder. Completion establishes this execution, not the current idle reserve or the behavior of a different strategy version.

​
Read the same record with public GET

No account, signature, or token is needed for these scoped reads:
This returns an intents array. Newer activity can move the example off the first page; use the exact detail and fills reads to locate it directly:
Search, detail, and fills returned HTTP 200 during verification. Detail identifies the strategy, execution, state, and fill count; the fills array contains the transaction hash above. Match IDs rather than assuming the first row is your execution. The host prefix is /api/strategy/api/v1, not bare /api/v1. The corresponding /events request returned HTTP 401 with no_session: full events are not an anonymous read. Use authorized access where needed; do not extract browser credentials.

​
Inspect a failed deposit

Search the same strategy for 69eb0ad1-f269-46e2-bf0b-a81db27da275, created on 16 October 2026. Its detail returned FAILED, FAIR_PRICE_TIMEOUT, and:
The price check timed out while assessing the whole plan. Try again.
Failed Base deposit 69eb0ad1-f269-46e2-bf0b-a81db27da275 showing FAIR PRICE TIMEOUT, the exact error message, matching strategy and zero fills. Its fills_count is zero and its fills response is empty. Read it directly:
Before another attempt, check pricing-service recovery and whether another intent is already in flight. Do not remove price checks or increase slippage to clear a timeout.

​
Decide by stage

  • No intent: inspect lifecycle, input freshness, rule, size, cooldown, and locks. History does not record every false evaluation.
  • Intent still in progress: compare timestamps and execution status before retrying.
  • Failed: retain the exact error and check fills before taking recovery action.
  • Completed: follow the fill to the transaction and verify the intended balance change.
See Strategy Troubleshooting for the blocked-stage checklist.