uvd-x402-sdk 2.72.0 → 2.74.0

package/dist/backend/index.d.mts

@@ -1486,6 +1486,22 @@ interface PrepareRelayFeedbackResponse {
      * nobody.
      */
     signingPayload?: string;
+    /**
+     * The full `eth_signTypedData_v4` payload. **v4 delegates only.**
+     *
+     * Present exactly when the delegate deployed on that chain is v4, which the
+     * facilitator reads from the chain per request rather than assuming from a
+     * release. **When it is present, sign IT** — the wallet renders the agent, the
+     * score, the tags and the deadline as named fields, so the rater sees what
+     * they authorise instead of a hex blob.
+     *
+     * v4 carries no {@link signingPayload} and needs none: `signTypedData` has no
+     * envelope to apply twice, which is the entire class of bug that kept the v3
+     * rail at zero signatures for days.
+     *
+     * Requires facilitator v1.96.0+.
+     */
+    typedData?: Record<string, unknown>;
     /**
      * Unix seconds after which the authorisation is void. Short on purpose:
      * relaying is permissionless, so a signed authorisation is live in the wild
@@ -1531,6 +1547,39 @@ interface SubmitRelayFeedbackRequest {
     /** Required only when `prepare` answered `delegated: false` */
     authorization?: RelayAuthorizationParams;
 }
+/**
+ * Request body for `POST /feedback/response/evm/prepare`.
+ *
+ * `responder` is the address the chain will record as the author.
+ */
+interface PrepareRelayResponseRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    responder: string;
+    agentId: number | string;
+    /** WHOSE feedback is being answered — inside the signed struct. */
+    clientAddress: string;
+    /** Which feedback (1-indexed) — also inside the struct. */
+    feedbackIndex: number;
+    responseUri: string;
+    responseHash?: string;
+}
+/** Request body for `POST /feedback/response/evm/submit`. */
+interface SubmitRelayResponseRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    responder: string;
+    agentId: number | string;
+    clientAddress: string;
+    feedbackIndex: number;
+    responseUri: string;
+    responseHash?: string;
+    deadline: number;
+    nonce: string;
+    /** The responder's signature over the typed data. */
+    signature: string;
+    authorization?: RelayAuthorizationParams;
+}
 /**
  * Proof of payment returned when settling with ERC-8004 extension
  */
@@ -2077,6 +2126,9 @@ declare class Erc8004Client {
      *    - wallet: `personal_sign` over `signingPayload`. `personal_sign` adds the
      *      envelope itself, so signing `digest` with it wraps the value TWICE and
      *      recovers a stranger — the only symptom is `relay_bad_signature`.
+     *    - **unless `typedData` came back** — that chain runs a v4 delegate. Then
+     *      sign THAT with `eth_signTypedData_v4` and ignore the other two: it is
+     *      the only form the rater can read, and it has no envelope ambiguity.
      * 2. If `delegated` is `false`, also produce an EIP-7702 authorization over
      *    `(chainId, delegate, accountNonce)`.
      * 3. Hand both to {@link submitRelayedFeedback} with the SAME feedback
@@ -2155,11 +2207,50 @@ declare class Erc8004Client {
         supportedNetworks: Erc8004Network[];
         version: string;
     }>;
+    /**
+     * Ask what the RESPONDER must sign to author a response on-chain.
+     *
+     * The mirror of {@link prepareRelayedFeedback}, for the other write the
+     * registry accepts from anybody. `appendResponse` is not agent-only — the
+     * registry takes it from any address — so on the plain {@link appendResponse}
+     * route the `responder` recorded on-chain is the FACILITATOR. That does not
+     * destroy anyone's reputation the way a revoke would; it ties the
+     * facilitator's on-chain identity to a third party's content, which is its own
+     * kind of wrong.
+     *
+     * **v4 delegates only.** The v3 delegate accepts exactly two selectors and
+     * `appendResponse` is not one of them, so a v3 network answers 400
+     * `relay_response_needs_v4` rather than silently falling back to the route
+     * this replaces.
+     *
+     * `clientAddress` and `feedbackIndex` are inside the signed struct: without
+     * them one signature would answer any client's rating, or any rating at that
+     * index.
+     */
+    prepareRelayedResponse(request: PrepareRelayResponseRequest): Promise<PrepareRelayFeedbackResponse>;
+    /**
+     * Relay a responder-authored response; the facilitator pays the gas.
+     *
+     * Pass back the same parameters, `deadline` and `nonce` that
+     * {@link prepareRelayedResponse} returned: the facilitator rebuilds the struct
+     * from them and refuses to relay anything the signature does not cover.
+     */
+    submitRelayedResponse(request: SubmitRelayResponseRequest): Promise<FeedbackResponse>;
+    /** Shared POST for the relay routes: a refusal is data, never a throw. */
+    private postRelay;
     /**
      * Append a response to existing feedback
      *
-     * Allows agents to respond to feedback they received.
-     * Only the agent (identity owner) can append responses.
+     * @deprecated On this route the facilitator is the AUTHOR: the registry
+     * records `msg.sender` as the `responder`, and that is the facilitator's
+     * wallet. Where the delegate is **v4**, use {@link prepareRelayedResponse} +
+     * {@link submitRelayedResponse} instead. This route still works and is the
+     * only one available where the delegate is still v3.
+     *
+     * **This is NOT agent-only**, despite what this comment claimed until
+     * 2026-08-25. Verified on-chain on 2026-08-18: the registry accepts
+     * `appendResponse` from ANY address. There is no identity-owner check, here or
+     * in the contract.
      *
      * @param network - Network where feedback was submitted
      * @param agentId - Agent ID
@@ -2747,4 +2838,4 @@ declare class AdvancedEscrowClient {
     private sendViaAdapter;
 }
 
-export { type AdvancedAuthorizationResult, AdvancedEscrowClient, type AdvancedEscrowClientOptions, type AdvancedEscrowContracts, type AdvancedEscrowTaskTier, type AdvancedPaymentInfo, type AdvancedTransactionResult, type AgentId, type AgentIdentity, type AgentRegistration, type AgentRegistrationFile, type AgentService, type AtomStats, BASE_MAINNET_CONTRACTS, BazaarClient, type BazaarClientOptions, type BazaarDiscoverOptions, type BazaarDiscoverResponse, type BazaarRegisterOptions, type BazaarResource, type CreateEscrowOptions, DEPOSIT_LIMIT_USDC, type DiscoveryAccepts, type DiscoveryCuration, type DiscoveryHealth, type DiscoveryHealthStatus, type DiscoveryListOptions, type DiscoveryPagination, type DiscoveryRegisterOptions, type DiscoveryResource, type DiscoveryResponse, type DiscoverySource, type DiscoveryStats, type DiscoveryTier, type Dispute, type DisputeOutcome, ERC8004_CONTRACTS, ERC8004_EXTENSION_ID, ESCROW_CONTRACTS, ESCROW_TIMEOUT_MS, Erc8004Client, type Erc8004ClientOptions, Erc8004LookupError, type Erc8004Network, EscrowClient, type EscrowClientOptions, type EscrowPayment, type EscrowStateResponse, type EscrowStatus, FacilitatorClient, type FacilitatorClientOptions, type FeedbackEntry, type FeedbackParams, type FeedbackRequest, type FeedbackResponse, HEALTH_FILTERS, type HonoMiddlewareOptions, type IdentityByOwnerResponse, type IdentityMetadataResponse, type IdentityTotalSupplyResponse, MAX_SEARCH_LEN, type MetadataEntryParam, OPERATOR_ABI, OPERATOR_ABI_CREATE3, PAYMENT_INFO_TYPEHASH, type PaymentAcceptance, type PaymentMiddlewareOptions, type PaymentPayloadV2, type PaymentRequirementResolver, type PaymentRequirements, type PaymentRequirementsOptions, type PaymentRequirementsV2, type PrepareRelayFeedbackRequest, type PrepareRelayFeedbackResponse, type ProofOfPayment, RELAYED_FEEDBACK_NETWORKS, type RefundRequest, type RefundStatus, type RegisterAgentRequest, type RegisterAgentResponse, type RegisterJobResponse, type RegisterJobStatus, RegistrationPendingError, type RelayAuthorizationParams, type ReputationResponse, type ReputationSummary, type RequestRefundOptions, type ResourceInfoV2, type SettleRequest, type SettleRequestV2, type SettleResponse, type SettleResponseWithProof, type SubmitRelayFeedbackRequest, TIER_FILTERS, TIER_TIMINGS, USDC_DOMAIN_NAME, type VerifiedPaymentState, type VerifyRequest, type VerifyRequestV2, type VerifyResponse, X402_CORS_HEADERS, X402_HEADER_NAMES, ZERO_ADDRESS, buildErc8004PaymentRequirements, buildPaymentRequirements, buildSettleRequest, buildSettleRequestV2, buildVerifyRequest, buildVerifyRequestV2, canRefundEscrow, canReleaseEscrow, create402Response, createHonoMiddleware, createPaymentMiddleware, epochToDate, escrowTimeRemaining, extractPaymentFromHeaders, getCorsHeaders, getEscrowContractsByChainId, getEscrowSupportedChainIds, isAlive, isEscrowExpired, isEscrowSupportedOnChain, isRegisterJobTerminal, parsePaymentHeader, supportsRelayedFeedback, wireNetwork };
+export { type AdvancedAuthorizationResult, AdvancedEscrowClient, type AdvancedEscrowClientOptions, type AdvancedEscrowContracts, type AdvancedEscrowTaskTier, type AdvancedPaymentInfo, type AdvancedTransactionResult, type AgentId, type AgentIdentity, type AgentRegistration, type AgentRegistrationFile, type AgentService, type AtomStats, BASE_MAINNET_CONTRACTS, BazaarClient, type BazaarClientOptions, type BazaarDiscoverOptions, type BazaarDiscoverResponse, type BazaarRegisterOptions, type BazaarResource, type CreateEscrowOptions, DEPOSIT_LIMIT_USDC, type DiscoveryAccepts, type DiscoveryCuration, type DiscoveryHealth, type DiscoveryHealthStatus, type DiscoveryListOptions, type DiscoveryPagination, type DiscoveryRegisterOptions, type DiscoveryResource, type DiscoveryResponse, type DiscoverySource, type DiscoveryStats, type DiscoveryTier, type Dispute, type DisputeOutcome, ERC8004_CONTRACTS, ERC8004_EXTENSION_ID, ESCROW_CONTRACTS, ESCROW_TIMEOUT_MS, Erc8004Client, type Erc8004ClientOptions, Erc8004LookupError, type Erc8004Network, EscrowClient, type EscrowClientOptions, type EscrowPayment, type EscrowStateResponse, type EscrowStatus, FacilitatorClient, type FacilitatorClientOptions, type FeedbackEntry, type FeedbackParams, type FeedbackRequest, type FeedbackResponse, HEALTH_FILTERS, type HonoMiddlewareOptions, type IdentityByOwnerResponse, type IdentityMetadataResponse, type IdentityTotalSupplyResponse, MAX_SEARCH_LEN, type MetadataEntryParam, OPERATOR_ABI, OPERATOR_ABI_CREATE3, PAYMENT_INFO_TYPEHASH, type PaymentAcceptance, type PaymentMiddlewareOptions, type PaymentPayloadV2, type PaymentRequirementResolver, type PaymentRequirements, type PaymentRequirementsOptions, type PaymentRequirementsV2, type PrepareRelayFeedbackRequest, type PrepareRelayFeedbackResponse, type PrepareRelayResponseRequest, type ProofOfPayment, RELAYED_FEEDBACK_NETWORKS, type RefundRequest, type RefundStatus, type RegisterAgentRequest, type RegisterAgentResponse, type RegisterJobResponse, type RegisterJobStatus, RegistrationPendingError, type RelayAuthorizationParams, type ReputationResponse, type ReputationSummary, type RequestRefundOptions, type ResourceInfoV2, type SettleRequest, type SettleRequestV2, type SettleResponse, type SettleResponseWithProof, type SubmitRelayFeedbackRequest, type SubmitRelayResponseRequest, TIER_FILTERS, TIER_TIMINGS, USDC_DOMAIN_NAME, type VerifiedPaymentState, type VerifyRequest, type VerifyRequestV2, type VerifyResponse, X402_CORS_HEADERS, X402_HEADER_NAMES, ZERO_ADDRESS, buildErc8004PaymentRequirements, buildPaymentRequirements, buildSettleRequest, buildSettleRequestV2, buildVerifyRequest, buildVerifyRequestV2, canRefundEscrow, canReleaseEscrow, create402Response, createHonoMiddleware, createPaymentMiddleware, epochToDate, escrowTimeRemaining, extractPaymentFromHeaders, getCorsHeaders, getEscrowContractsByChainId, getEscrowSupportedChainIds, isAlive, isEscrowExpired, isEscrowSupportedOnChain, isRegisterJobTerminal, parsePaymentHeader, supportsRelayedFeedback, wireNetwork };

package/dist/backend/index.d.ts

@@ -1486,6 +1486,22 @@ interface PrepareRelayFeedbackResponse {
      * nobody.
      */
     signingPayload?: string;
+    /**
+     * The full `eth_signTypedData_v4` payload. **v4 delegates only.**
+     *
+     * Present exactly when the delegate deployed on that chain is v4, which the
+     * facilitator reads from the chain per request rather than assuming from a
+     * release. **When it is present, sign IT** — the wallet renders the agent, the
+     * score, the tags and the deadline as named fields, so the rater sees what
+     * they authorise instead of a hex blob.
+     *
+     * v4 carries no {@link signingPayload} and needs none: `signTypedData` has no
+     * envelope to apply twice, which is the entire class of bug that kept the v3
+     * rail at zero signatures for days.
+     *
+     * Requires facilitator v1.96.0+.
+     */
+    typedData?: Record<string, unknown>;
     /**
      * Unix seconds after which the authorisation is void. Short on purpose:
      * relaying is permissionless, so a signed authorisation is live in the wild
@@ -1531,6 +1547,39 @@ interface SubmitRelayFeedbackRequest {
     /** Required only when `prepare` answered `delegated: false` */
     authorization?: RelayAuthorizationParams;
 }
+/**
+ * Request body for `POST /feedback/response/evm/prepare`.
+ *
+ * `responder` is the address the chain will record as the author.
+ */
+interface PrepareRelayResponseRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    responder: string;
+    agentId: number | string;
+    /** WHOSE feedback is being answered — inside the signed struct. */
+    clientAddress: string;
+    /** Which feedback (1-indexed) — also inside the struct. */
+    feedbackIndex: number;
+    responseUri: string;
+    responseHash?: string;
+}
+/** Request body for `POST /feedback/response/evm/submit`. */
+interface SubmitRelayResponseRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    responder: string;
+    agentId: number | string;
+    clientAddress: string;
+    feedbackIndex: number;
+    responseUri: string;
+    responseHash?: string;
+    deadline: number;
+    nonce: string;
+    /** The responder's signature over the typed data. */
+    signature: string;
+    authorization?: RelayAuthorizationParams;
+}
 /**
  * Proof of payment returned when settling with ERC-8004 extension
  */
@@ -2077,6 +2126,9 @@ declare class Erc8004Client {
      *    - wallet: `personal_sign` over `signingPayload`. `personal_sign` adds the
      *      envelope itself, so signing `digest` with it wraps the value TWICE and
      *      recovers a stranger — the only symptom is `relay_bad_signature`.
+     *    - **unless `typedData` came back** — that chain runs a v4 delegate. Then
+     *      sign THAT with `eth_signTypedData_v4` and ignore the other two: it is
+     *      the only form the rater can read, and it has no envelope ambiguity.
      * 2. If `delegated` is `false`, also produce an EIP-7702 authorization over
      *    `(chainId, delegate, accountNonce)`.
      * 3. Hand both to {@link submitRelayedFeedback} with the SAME feedback
@@ -2155,11 +2207,50 @@ declare class Erc8004Client {
         supportedNetworks: Erc8004Network[];
         version: string;
     }>;
+    /**
+     * Ask what the RESPONDER must sign to author a response on-chain.
+     *
+     * The mirror of {@link prepareRelayedFeedback}, for the other write the
+     * registry accepts from anybody. `appendResponse` is not agent-only — the
+     * registry takes it from any address — so on the plain {@link appendResponse}
+     * route the `responder` recorded on-chain is the FACILITATOR. That does not
+     * destroy anyone's reputation the way a revoke would; it ties the
+     * facilitator's on-chain identity to a third party's content, which is its own
+     * kind of wrong.
+     *
+     * **v4 delegates only.** The v3 delegate accepts exactly two selectors and
+     * `appendResponse` is not one of them, so a v3 network answers 400
+     * `relay_response_needs_v4` rather than silently falling back to the route
+     * this replaces.
+     *
+     * `clientAddress` and `feedbackIndex` are inside the signed struct: without
+     * them one signature would answer any client's rating, or any rating at that
+     * index.
+     */
+    prepareRelayedResponse(request: PrepareRelayResponseRequest): Promise<PrepareRelayFeedbackResponse>;
+    /**
+     * Relay a responder-authored response; the facilitator pays the gas.
+     *
+     * Pass back the same parameters, `deadline` and `nonce` that
+     * {@link prepareRelayedResponse} returned: the facilitator rebuilds the struct
+     * from them and refuses to relay anything the signature does not cover.
+     */
+    submitRelayedResponse(request: SubmitRelayResponseRequest): Promise<FeedbackResponse>;
+    /** Shared POST for the relay routes: a refusal is data, never a throw. */
+    private postRelay;
     /**
      * Append a response to existing feedback
      *
-     * Allows agents to respond to feedback they received.
-     * Only the agent (identity owner) can append responses.
+     * @deprecated On this route the facilitator is the AUTHOR: the registry
+     * records `msg.sender` as the `responder`, and that is the facilitator's
+     * wallet. Where the delegate is **v4**, use {@link prepareRelayedResponse} +
+     * {@link submitRelayedResponse} instead. This route still works and is the
+     * only one available where the delegate is still v3.
+     *
+     * **This is NOT agent-only**, despite what this comment claimed until
+     * 2026-08-25. Verified on-chain on 2026-08-18: the registry accepts
+     * `appendResponse` from ANY address. There is no identity-owner check, here or
+     * in the contract.
      *
      * @param network - Network where feedback was submitted
      * @param agentId - Agent ID
@@ -2747,4 +2838,4 @@ declare class AdvancedEscrowClient {
     private sendViaAdapter;
 }
 
-export { type AdvancedAuthorizationResult, AdvancedEscrowClient, type AdvancedEscrowClientOptions, type AdvancedEscrowContracts, type AdvancedEscrowTaskTier, type AdvancedPaymentInfo, type AdvancedTransactionResult, type AgentId, type AgentIdentity, type AgentRegistration, type AgentRegistrationFile, type AgentService, type AtomStats, BASE_MAINNET_CONTRACTS, BazaarClient, type BazaarClientOptions, type BazaarDiscoverOptions, type BazaarDiscoverResponse, type BazaarRegisterOptions, type BazaarResource, type CreateEscrowOptions, DEPOSIT_LIMIT_USDC, type DiscoveryAccepts, type DiscoveryCuration, type DiscoveryHealth, type DiscoveryHealthStatus, type DiscoveryListOptions, type DiscoveryPagination, type DiscoveryRegisterOptions, type DiscoveryResource, type DiscoveryResponse, type DiscoverySource, type DiscoveryStats, type DiscoveryTier, type Dispute, type DisputeOutcome, ERC8004_CONTRACTS, ERC8004_EXTENSION_ID, ESCROW_CONTRACTS, ESCROW_TIMEOUT_MS, Erc8004Client, type Erc8004ClientOptions, Erc8004LookupError, type Erc8004Network, EscrowClient, type EscrowClientOptions, type EscrowPayment, type EscrowStateResponse, type EscrowStatus, FacilitatorClient, type FacilitatorClientOptions, type FeedbackEntry, type FeedbackParams, type FeedbackRequest, type FeedbackResponse, HEALTH_FILTERS, type HonoMiddlewareOptions, type IdentityByOwnerResponse, type IdentityMetadataResponse, type IdentityTotalSupplyResponse, MAX_SEARCH_LEN, type MetadataEntryParam, OPERATOR_ABI, OPERATOR_ABI_CREATE3, PAYMENT_INFO_TYPEHASH, type PaymentAcceptance, type PaymentMiddlewareOptions, type PaymentPayloadV2, type PaymentRequirementResolver, type PaymentRequirements, type PaymentRequirementsOptions, type PaymentRequirementsV2, type PrepareRelayFeedbackRequest, type PrepareRelayFeedbackResponse, type ProofOfPayment, RELAYED_FEEDBACK_NETWORKS, type RefundRequest, type RefundStatus, type RegisterAgentRequest, type RegisterAgentResponse, type RegisterJobResponse, type RegisterJobStatus, RegistrationPendingError, type RelayAuthorizationParams, type ReputationResponse, type ReputationSummary, type RequestRefundOptions, type ResourceInfoV2, type SettleRequest, type SettleRequestV2, type SettleResponse, type SettleResponseWithProof, type SubmitRelayFeedbackRequest, TIER_FILTERS, TIER_TIMINGS, USDC_DOMAIN_NAME, type VerifiedPaymentState, type VerifyRequest, type VerifyRequestV2, type VerifyResponse, X402_CORS_HEADERS, X402_HEADER_NAMES, ZERO_ADDRESS, buildErc8004PaymentRequirements, buildPaymentRequirements, buildSettleRequest, buildSettleRequestV2, buildVerifyRequest, buildVerifyRequestV2, canRefundEscrow, canReleaseEscrow, create402Response, createHonoMiddleware, createPaymentMiddleware, epochToDate, escrowTimeRemaining, extractPaymentFromHeaders, getCorsHeaders, getEscrowContractsByChainId, getEscrowSupportedChainIds, isAlive, isEscrowExpired, isEscrowSupportedOnChain, isRegisterJobTerminal, parsePaymentHeader, supportsRelayedFeedback, wireNetwork };
+export { type AdvancedAuthorizationResult, AdvancedEscrowClient, type AdvancedEscrowClientOptions, type AdvancedEscrowContracts, type AdvancedEscrowTaskTier, type AdvancedPaymentInfo, type AdvancedTransactionResult, type AgentId, type AgentIdentity, type AgentRegistration, type AgentRegistrationFile, type AgentService, type AtomStats, BASE_MAINNET_CONTRACTS, BazaarClient, type BazaarClientOptions, type BazaarDiscoverOptions, type BazaarDiscoverResponse, type BazaarRegisterOptions, type BazaarResource, type CreateEscrowOptions, DEPOSIT_LIMIT_USDC, type DiscoveryAccepts, type DiscoveryCuration, type DiscoveryHealth, type DiscoveryHealthStatus, type DiscoveryListOptions, type DiscoveryPagination, type DiscoveryRegisterOptions, type DiscoveryResource, type DiscoveryResponse, type DiscoverySource, type DiscoveryStats, type DiscoveryTier, type Dispute, type DisputeOutcome, ERC8004_CONTRACTS, ERC8004_EXTENSION_ID, ESCROW_CONTRACTS, ESCROW_TIMEOUT_MS, Erc8004Client, type Erc8004ClientOptions, Erc8004LookupError, type Erc8004Network, EscrowClient, type EscrowClientOptions, type EscrowPayment, type EscrowStateResponse, type EscrowStatus, FacilitatorClient, type FacilitatorClientOptions, type FeedbackEntry, type FeedbackParams, type FeedbackRequest, type FeedbackResponse, HEALTH_FILTERS, type HonoMiddlewareOptions, type IdentityByOwnerResponse, type IdentityMetadataResponse, type IdentityTotalSupplyResponse, MAX_SEARCH_LEN, type MetadataEntryParam, OPERATOR_ABI, OPERATOR_ABI_CREATE3, PAYMENT_INFO_TYPEHASH, type PaymentAcceptance, type PaymentMiddlewareOptions, type PaymentPayloadV2, type PaymentRequirementResolver, type PaymentRequirements, type PaymentRequirementsOptions, type PaymentRequirementsV2, type PrepareRelayFeedbackRequest, type PrepareRelayFeedbackResponse, type PrepareRelayResponseRequest, type ProofOfPayment, RELAYED_FEEDBACK_NETWORKS, type RefundRequest, type RefundStatus, type RegisterAgentRequest, type RegisterAgentResponse, type RegisterJobResponse, type RegisterJobStatus, RegistrationPendingError, type RelayAuthorizationParams, type ReputationResponse, type ReputationSummary, type RequestRefundOptions, type ResourceInfoV2, type SettleRequest, type SettleRequestV2, type SettleResponse, type SettleResponseWithProof, type SubmitRelayFeedbackRequest, type SubmitRelayResponseRequest, TIER_FILTERS, TIER_TIMINGS, USDC_DOMAIN_NAME, type VerifiedPaymentState, type VerifyRequest, type VerifyRequestV2, type VerifyResponse, X402_CORS_HEADERS, X402_HEADER_NAMES, ZERO_ADDRESS, buildErc8004PaymentRequirements, buildPaymentRequirements, buildSettleRequest, buildSettleRequestV2, buildVerifyRequest, buildVerifyRequestV2, canRefundEscrow, canReleaseEscrow, create402Response, createHonoMiddleware, createPaymentMiddleware, epochToDate, escrowTimeRemaining, extractPaymentFromHeaders, getCorsHeaders, getEscrowContractsByChainId, getEscrowSupportedChainIds, isAlive, isEscrowExpired, isEscrowSupportedOnChain, isRegisterJobTerminal, parsePaymentHeader, supportsRelayedFeedback, wireNetwork };

package/dist/backend/index.js

@@ -2911,6 +2911,9 @@ var Erc8004Client = class {
    *    - wallet: `personal_sign` over `signingPayload`. `personal_sign` adds the
    *      envelope itself, so signing `digest` with it wraps the value TWICE and
    *      recovers a stranger — the only symptom is `relay_bad_signature`.
+   *    - **unless `typedData` came back** — that chain runs a v4 delegate. Then
+   *      sign THAT with `eth_signTypedData_v4` and ignore the other two: it is
+   *      the only form the rater can read, and it has no envelope ambiguity.
    * 2. If `delegated` is `false`, also produce an EIP-7702 authorization over
    *    `(chainId, delegate, accountNonce)`.
    * 3. Hand both to {@link submitRelayedFeedback} with the SAME feedback
@@ -3116,11 +3119,82 @@ var Erc8004Client = class {
       throw error;
     }
   }
+  /**
+   * Ask what the RESPONDER must sign to author a response on-chain.
+   *
+   * The mirror of {@link prepareRelayedFeedback}, for the other write the
+   * registry accepts from anybody. `appendResponse` is not agent-only — the
+   * registry takes it from any address — so on the plain {@link appendResponse}
+   * route the `responder` recorded on-chain is the FACILITATOR. That does not
+   * destroy anyone's reputation the way a revoke would; it ties the
+   * facilitator's on-chain identity to a third party's content, which is its own
+   * kind of wrong.
+   *
+   * **v4 delegates only.** The v3 delegate accepts exactly two selectors and
+   * `appendResponse` is not one of them, so a v3 network answers 400
+   * `relay_response_needs_v4` rather than silently falling back to the route
+   * this replaces.
+   *
+   * `clientAddress` and `feedbackIndex` are inside the signed struct: without
+   * them one signature would answer any client's rating, or any rating at that
+   * index.
+   */
+  async prepareRelayedResponse(request) {
+    return this.postRelay("/feedback/response/evm/prepare", request, {
+      success: false,
+      delegated: false,
+      chainId: 0,
+      network: request.network
+    });
+  }
+  /**
+   * Relay a responder-authored response; the facilitator pays the gas.
+   *
+   * Pass back the same parameters, `deadline` and `nonce` that
+   * {@link prepareRelayedResponse} returned: the facilitator rebuilds the struct
+   * from them and refuses to relay anything the signature does not cover.
+   */
+  async submitRelayedResponse(request) {
+    return this.postRelay("/feedback/response/evm/submit", request, {
+      success: false,
+      network: request.network
+    });
+  }
+  /** Shared POST for the relay routes: a refusal is data, never a throw. */
+  async postRelay(path, request, onError) {
+    const controller = new AbortController();
+    const timeoutId = setTimeout(() => controller.abort(), this.timeout);
+    try {
+      const response = await fetch(`${this.baseUrl}${path}`, {
+        method: "POST",
+        headers: { "Content-Type": "application/json", "Accept": "application/json" },
+        body: JSON.stringify({ ...request, network: wireNetwork(request.network) }),
+        signal: controller.signal
+      });
+      clearTimeout(timeoutId);
+      if (!response.ok) {
+        const errorText = await response.text();
+        return { ...onError, error: `Facilitator error: ${response.status} - ${errorText}` };
+      }
+      return await response.json();
+    } catch (error) {
+      clearTimeout(timeoutId);
+      return { ...onError, error: error instanceof Error ? error.message : "Unknown error" };
+    }
+  }
   /**
    * Append a response to existing feedback
    *
-   * Allows agents to respond to feedback they received.
-   * Only the agent (identity owner) can append responses.
+   * @deprecated On this route the facilitator is the AUTHOR: the registry
+   * records `msg.sender` as the `responder`, and that is the facilitator's
+   * wallet. Where the delegate is **v4**, use {@link prepareRelayedResponse} +
+   * {@link submitRelayedResponse} instead. This route still works and is the
+   * only one available where the delegate is still v3.
+   *
+   * **This is NOT agent-only**, despite what this comment claimed until
+   * 2026-08-25. Verified on-chain on 2026-08-18: the registry accepts
+   * `appendResponse` from ANY address. There is no identity-owner check, here or
+   * in the contract.
    *
    * @param network - Network where feedback was submitted
    * @param agentId - Agent ID