Errors

Every program returns custom error codes via Anchor's #[error_code] macro. The codes start at 6000 and are assigned in declaration order; meanings are documented here. The error variants are append-only across versions, so existing codes are stable.

entros-anchor errors

The Receipt* family (6015–6021) only fires on the first-verification path. Re-verification (update_anchor) binds via the verifier-program VerificationResult PDA, not via the validator-signed mint receipt.

entros-verifier errors

entros-registry errors

entros-voter-weight errors

SDK and HTTP errors

@entros/pulse-sdk returns a SubmissionResult from every submission helper:

type SubmissionResult = {
  success: boolean;
  txSignature?: string;
  attestationTx?: string;
  error?: string;
};

On success, txSignature is the verification transaction signature. attestationTx, when present, is the SAS attestation write. On failure, error carries the user-surfaceable message; the underlying program error code, when one exists, is included in that string and can be matched on.

Chain-side transaction failures

Since 1.5.0, the SDK throws when an on-chain transaction reverts. Earlier versions silently returned success: true for transactions that were included on chain but failed during execution—an easy way to ship a "verified!" UI for a tx that mutated nothing. The thrown error preserves the JSON InstructionError shape so callers can extract the Custom code:

const result = await session.complete(wallet, connection);
if (!result.success) {
  // result.error is one of:
  //   "Transaction failed on chain: {\"InstructionError\":[0,{\"Custom\":6011}]} (sig=...)"  // PrevCommitmentMismatch
  //   "Transaction failed on chain: {\"InstructionError\":[1,{\"Custom\":6015}]} (sig=...)"  // MissingValidatorReceipt
  //   "Transaction failed on chain: {\"InstructionError\":[0,\"InsufficientFundsForRent\"]}"
  //   ...or a non-chain failure (network, wallet rejected, etc.)
  const customMatch = result.error?.match(/"Custom":(\d+)/);
  if (customMatch) {
    const code = Number(customMatch[1]);
    if (code === 6012) showCooldownMessage();
    else if (code === 6011) showStaleBaselinePrompt();
    else showGenericError(`Program error ${code}`);
  } else {
    showGenericError(result.error);
  }
}

/attest requires wallet ownership proof

A request to the executor's /attest endpoint now requires wallet_address, nonce, signature, and message together on every call. Missing any of those returns:

{ "error": "wallet_ownership_required" }

with HTTP 400. The signed message format is Entros-ATTEST:{wallet_address}:{timestamp_secs}. The walletless attestation path was removed—wallets that cannot sign should not call /attest at all.

Response padding

Authenticated executor responses include an opaque _padding field of repeated ASCII characters that pads the JSON to a fixed byte length. Treat it as forward-compatible noise: ignore it on parse, do not surface it to users, do not assert on its content or length. It exists to defeat byte-length analysis of response classes.

Where to look next

• Reference: Programs—instruction documentation that defines when each error fires
• Reference: SDK—submission helper signatures
• Reference: Changelog—when each error variant was introduced