Recv

id is the stable identifier for this entry. Swap-backed SEND and RECV rows use the Lightning payment_hash. Credit-backed RECV rows use the credit operation id (see CreditReceive.operation_id); the payment_hash lives on recv progress/detail instead. EXIT rows use leave_job_id (or sweep txid); DEPOSIT rows use the boarding outpoint or txid.

kind is the user-visible category.

status is the coarse user-facing outcome: PENDING, COMPLETE, or FAILED. It mirrors the backing source's durable state and should not be reinterpreted by display clients.

amount_sat is signed: positive values are incoming to the wallet, negative values are outgoing.

fee_sat is the absolute fee paid (or pending) for this operation.

counterparty is a short, display-friendly identifier of the other side: a truncated invoice for Lightning, an ark peer address for OOR, a bech32 onchain address for exits, or "boarding" for deposits.

created_at_unix is the local creation timestamp in unix seconds.

updated_at_unix is the last persisted update timestamp in unix seconds. List ACTIVITY and SubscribeWallet sort by this field, descending.

note is the caller-supplied label captured at submit time, if any.

failure_reason is populated only when status is FAILED. It is a single human-readable string, never a coded enum tree.

request is the original payment request or destination associated with the entry, when the backing subsystem persists it. This is useful for expanded views and inspection; compact clients should not need to parse it to explain status or lifecycle.

progress carries lifecycle-specific metadata already normalized by the wallet service. Clients can render phase_label directly or switch on phase without inferring meaning from swap/ledger internals.

failure_code is a stable, machine-readable classification of why a FAILED entry failed. It is set ONLY on FAILED entries; a non-failed entry omits the field entirely (presence-tracked), so its absence is the canonical "no failure" signal and ENTRY_FAILURE_CODE_UNSPECIFIED is never sent on the wire. failure_reason remains the human-readable supplement.

lightning_invoice is populated for Lightning send and receive entries.

onchain_address is populated for deposit and exit entries.

ark_address is populated for direct Ark send or receive entries.

invoice is the BOLT-11 payment request.

payment_hash identifies the invoice and remains stable after the invoice itself is no longer convenient to display.

address is the bech32 onchain address originally issued or targeted.

address is the Ark address originally issued or targeted.

phase is the coarse lifecycle phase for this entry.

phase_label is a short lowercase label that clients can render as-is while they migrate to enum-based presentation.

payment_hash is populated for Lightning-backed send/recv entries.

txid is populated when the backing ledger row has an onchain txid.

confirmation_height is populated once the source records it.

vtxo_outpoint is populated when a swap observes the Ark vHTLC output.

preimage is the hex-encoded Lightning payment preimage once the swap revealed it. For a completed Lightning-backed send this is the proof of payment for the paid invoice (sha256(preimage) == payment_hash); it is empty until the preimage is durably known and for non-Lightning entries.

operation_id is the durable credit-subsystem operation id tracking this receive. It is the WalletEntry.id for credit RECV rows; the server-owned payment_hash is in payment_hash below.

amount_sat is the amount in satoshis the caller asked to receive, credited to the wallet account once the server-owned invoice settles.

payment_hash is the hex-encoded payment hash of the server-owned receive invoice.