namera execution status

Read the state of an existing transaction submission.

UsageCopy Anchor Link

namera execution status 0199dfe1-0000-7000-8000-000000000003

OutputCopy Anchor Link

-> Status: Pending confirmation
-> UserOp Hash: 0x1111111111111111111111111111111111111111111111111111111111111111

Not confirmed yet. Check again with:
  namera execution status 0199dfe1-0000-7000-8000-000000000003

Example output uses fixture accounts and hashes, captured with the CLI's output formatters. Plain-text output is shown without terminal colors; your values and relative expiry dates will differ.

With --output json:

{
  "namespace": "eip155",
  "submissionId": "0199dfe1-0000-7000-8000-000000000003",
  "status": "submitted",
  "userOperationHash": "0x1111111111111111111111111111111111111111111111111111111111111111"
}

ArgumentsCopy Anchor Link

submission-idCopy Anchor Link

• Type: string (UUID)
• Required: yes

Use the submissionId returned by execution, not a transaction hash, UserOp hash, or confirmed execution ID. The command checks once; repeat the read to poll.

OptionsCopy Anchor Link

--profileCopy Anchor Link

• Type: string
• Default: personal

Choose the saved CLI connection for this command. Pass the same name used at login. If NAMERA_API_KEY is set, ordinary API commands use that key instead of the profile's OAuth credentials.

namera wallet list --profile work

The command also accepts global options: --output pretty|json, --quiet, and --help.

StatusesCopy Anchor Link

Confirmed JSON includes execution; failed JSON has no fabricated reason or hash. See Get Submission Status for complete response variants. Human confirmed output makes an additional execution-details read to show account and actor names.

ErrorsCopy Anchor Link

Failures exit nonzero and are written to stderr. With --output json, inspect error.code and error.nextStep. See Output and Errors.