Wallet Logs API.
Connect wallet intent with observed transaction state.

Keep interface actions distinct from chain evidence

A wallet connection, signing request, and submitted transaction are different events. Preserve that distinction in the application timeline. A user can cancel a prompt before any transaction exists, and a submitted request can remain unresolved after the interface times out. Use a workflow reference to connect the stages without turning each one into a generic success or failure.

Record the component that observed the event. The interface describes local interaction, the submission component describes request handling, and the chain collector describes network evidence. Keep retry attempts visible with their own identifiers so an operator can follow what happened when a response was delayed or unavailable.

Scope addresses and transaction references

Associate wallet and transaction references with their network context. Preserve relevant contract and participant roles separately. The wallet selected in an interface is not necessarily the emitting contract or every participant in a transaction. Use exact identifiers for investigation and human-readable labels only for display.

For chain observations, retain block context and collector observation time. Record how the application derives displayed state from receipts, relevant events, or state reads. The wallet and tokenized asset logging guide explains why submission acceptance, execution outcome, and application confirmation policy should remain separate concepts.

Build a recoverable and limited history

Plan for repeated observations, collection gaps, and changes to the chain view before finality. Maintain checkpoints, support deduplication, and preserve corrections instead of silently rewriting history. A reconciliation event should explain what state was checked and which network context supports the result.

Never include private keys, seed phrases, recovery material, or signing credentials in routine logs. Public addresses can also expose sensitive relationships when linked to account records, so limit those associations. Test cancellation, failed execution, timeouts, collector restarts, and corrections. The recommended fields below support the application layer of this model and can be extended with chain-specific evidence where needed.