Align executeContract behavior across account types

[iamalwaysuncomfortable]

Stacked on #54. Addresses the three behavioral-predictability issues raised in review of that PR.

Summary

1. RPC path now matches local path return shape. Today the RPC branch casts the wallet's { transactionId } response to RawExecuteResult — transitions is undefined and outputs is whatever the wallet happened to put in that field. After this PR, the RPC path polls getConfirmedTransaction itself and runs extractTransitions on the confirmed tx. The SDK does not broker decryption on behalf of the wallet: record outputs come back as raw record1... ciphertexts on the RPC path. Plaintext outputs come through verbatim. Local-account semantics are unchanged.

2. executeTransaction aligned with the Aleo wallet adapter spec. Previously the wallet client method executeTransaction was bound to the heavy executeContract action, while the action-level alias inside writeContract.ts pointed executeTransaction to writeContract — three sites disagreed. Now executeTransaction is consistently aliased to writeContract (light, returns tx id) everywhere: wallet client, top-level package export, action layer. The full-lifecycle action is exposed as executeContract on the wallet client and under its own name as a top-level export.

3. outputs is the called function's transition only on both paths. The raw layer no longer flattens all transition outputs into one array; transitions[] carries the per-transition data. RawExecuteResult.outputs is the called function's transition's outputs (always the last element of execution.transitions[] per Aleo execution semantics, where inner cross-program transitions are recorded before their callers).

Refactoring side-effects

• waitForConfirmation and extractTransitions moved from packages/provable/src/index.ts closures to shared utilities under packages/core/src/utils/. Both reachable via @veil/core exports.
• extractTransitions takes an optional Decryptor parameter: (ciphertext: string) => string | null. The local path passes a view-key decryptor (self-custodied); the RPC path passes none (permission boundary).
• Position-based top-level identification replaces name matching — Aleo execution semantics guarantee the called function's transition is the last in execution.transitions[].

Files changed

• packages/core/src/actions/wallet/executeContract.ts — RPC path rewritten (submit → poll → extract)
• packages/core/src/clients/decorators/wallet.ts — `executeTransaction` → `writeContract`; expose `executeContract`
• packages/core/src/contract/getContract.ts — proxy calls `executeContract`; outputs derivation simplified
• packages/core/src/index.ts — exports realigned; export new utilities
• packages/core/src/types/proving.ts — `outputs` docstring updated
• packages/core/src/utils/extractTransitions.ts — new shared utility
• packages/core/src/utils/waitForConfirmation.ts — new shared utility
• packages/provable/src/index.ts — drop local closures; use shared utilities with a view-key decryptor

Test plan

• All existing tests pass.
• New tests in executeContract.test.ts:
  • `RPC: submits via wallet, polls for confirmation, returns RawExecuteResult`
  • `RPC: forwards wallet-adapter param shape (privateFee + imports as string[], no fee/programSource)`
  • `RPC: record ciphertexts pass through as raw strings (no decryption)`
• New tests in createWalletClient.test.ts:
  • `executeTransaction and writeContract produce identical requests` (behavioral, not just type)
  • `top-level executeTransaction export === writeContract`
• New test in getContract.test.ts: `outputs is empty when no transition matches the called program/function`.
• `pnpm vitest run` — 691 passing, 0 failing.
• `pnpm --filter @veil/core exec tsc --noEmit` — 0 errors.
• `pnpm --filter @veil/loyalty-dapp exec tsc --noEmit` — clean.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
veil-loyalty-dapp	Ready	Preview, Comment	May 13, 2026 4:11am

[marshacb]

LGTM!