uvd-x402-sdk 2.69.0 → 2.71.0

package/README.md

@@ -927,6 +927,86 @@ const result = await erc8004.submitFeedback({
 await erc8004.appendResponse('ethereum', 42, 1, 'Thank you for your feedback!');
 ```
 
+### Ratings the chain attributes to the rater
+
+`submitFeedback()` above works, but the registry records `msg.sender` as the
+author -- and on that route `msg.sender` is the **facilitator**. It is why 87,2%
+of the reputation on Base (1.384 of 1.587 feedbacks) is attributed to one
+wallet, which can also revoke it.
+
+EIP-7702 fixes it without touching the registry: the rater delegates their own
+EOA to a `FeedbackDelegate`, and the transaction is sent **to the rater's
+address**, so the registry sees the rater while the facilitator still pays the
+gas.
+
+```typescript
+import { Erc8004Client, supportsRelayedFeedback } from 'uvd-x402-sdk/backend';
+
+const erc8004 = new Erc8004Client();
+
+if (!supportsRelayedFeedback('base')) {
+  // fall back to submitFeedback(); the facilitator is the author there
+}
+
+const prep = await erc8004.prepareRelayedFeedback({
+  x402Version: 1,
+  network: 'base',
+  feedback: {
+    agentId: 18896,
+    value: 95,
+    tag1: 'quality',
+    rater: raterAddress, // who the chain will record as the author
+  },
+});
+
+// 1. Sign with the RATER's key. WHICH value you sign depends on HOW you sign
+//    it — get this wrong and you produce a well-formed signature that
+//    authorises nobody, and the only symptom is `relay_bad_signature`.
+//
+//    `prep.digest` already carries the EIP-191 envelope. A raw key signs it as
+//    a prehash; a wallet's personal_sign would add the envelope a SECOND time,
+//    so wallets sign `prep.signingPayload` instead.
+const signature = await account.sign({ hash: prep.digest! });   // raw key
+// ...or, from a browser wallet:
+//   const signature = await walletClient.signMessage({
+//     account, message: { raw: prep.signingPayload! },
+//   });
+
+// 2. Only the first time this rater rates: point their EOA at the delegate.
+const authorization = prep.delegated
+  ? undefined
+  : {
+      chainId: prep.chainId, // 0 is EIP-7702's wildcard: valid on every chain
+      address: prep.delegate!,
+      nonce: prep.accountNonce!,
+      ...(await signAuthorization(prep.chainId, prep.delegate!, prep.accountNonce!)),
+    };
+
+const result = await erc8004.submitRelayedFeedback({
+  x402Version: 1,
+  network: 'base',
+  feedback: { agentId: 18896, value: 95, tag1: 'quality', rater: raterAddress },
+  deadline: prep.deadline!, // short by design; past it, refused
+  nonce: prep.nonce!,
+  signature,
+  authorization,
+});
+```
+
+Pass the **same** feedback parameters, `deadline` and `nonce` back to
+`submitRelayedFeedback()`. They are not redundant: the facilitator rebuilds the
+registry calldata from them and refuses to relay anything the rater's signature
+does not cover.
+
+Available on the nine networks in `RELAYED_FEEDBACK_NETWORKS` -- the eight
+mainnets with a deployed `FeedbackDelegate` (base, ethereum, polygon, arbitrum,
+optimism, celo, bsc, monad) plus base-sepolia. **Avalanche is not one of them
+and is not waiting to become one**: its C-Chain rejects the transaction type
+itself (`-32000 transaction type not supported`), so anchor the rating on a
+chain that supports EIP-7702 -- the payment stays where it was made.
+
+Requires facilitator v1.93.0+ for the mainnets; base-sepolia since v1.74.0.
+
 ## `/accepts` Negotiation
 
 Discover what the facilitator can settle before constructing payment authorizations. Used by Faremeter middleware and clients.

package/dist/backend/index.d.mts

@@ -1385,6 +1385,152 @@ declare function wireNetwork(network: string): string;
  * reaches the wire. Use 'base'.
  */
 type Erc8004Network = 'ethereum' | 'base' | 'polygon' | 'arbitrum' | 'optimism' | 'celo' | 'bsc' | 'monad' | 'avalanche' | 'scroll' | 'skale-base' | 'base-mainnet' | 'ethereum-sepolia' | 'base-sepolia' | 'polygon-amoy' | 'arbitrum-sepolia' | 'optimism-sepolia' | 'celo-sepolia' | 'avalanche-fuji' | 'skale-base-sepolia' | 'solana' | 'solana-devnet';
+/**
+ * Networks where the facilitator serves the RELAYED feedback rail, i.e. where
+ * Execution Market has deployed a `FeedbackDelegate` and the facilitator
+ * verified it on-chain (code present, and its `REPUTATION_REGISTRY()` reads
+ * back that network's registry).
+ *
+ * Anywhere else `POST /feedback/evm/prepare` answers 400 — and it should. An
+ * invented delegate address would send a type-4 transaction to an account with
+ * no code behind it, and in the EVM a `.call()` to an address with no code
+ * RETURNS SUCCESS. The failure would look exactly like a rating that rated
+ * nobody.
+ *
+ * `avalanche` is absent and is not waiting to join: the C-Chain rejects the
+ * transaction type itself (`-32000 transaction type not supported`), so there
+ * is nothing to deploy against. Anchor the rating on a chain that supports
+ * EIP-7702; the payment stays where it was made.
+ */
+declare const RELAYED_FEEDBACK_NETWORKS: readonly Erc8004Network[];
+/**
+ * Whether `network` serves the rater-authored feedback rail.
+ *
+ * Lets a caller route without paying a round trip for a 400. The facilitator
+ * re-checks the delegate on-chain on every request regardless — this list is a
+ * routing hint, never the authority.
+ */
+declare function supportsRelayedFeedback(network: string): boolean;
+/**
+ * An EIP-7702 authorization, as a wallet produces it.
+ *
+ * Needed only the first time a rater rates: it points their EOA at the
+ * `FeedbackDelegate`. Once delegated, `prepare` answers `delegated: true` and
+ * the submission carries no authorization at all.
+ */
+interface RelayAuthorizationParams {
+    /**
+     * Chain the authorization is for.
+     *
+     * `0` is EIP-7702's wildcard and is valid on EVERY chain — a far broader
+     * grant than pinning this one. Send the chain id `prepare` returned.
+     */
+    chainId: number;
+    /**
+     * The delegate the account is pointed at. Must be the address `prepare`
+     * offered; the facilitator refuses anything else before it pays for a
+     * transaction.
+     */
+    address: string;
+    /** The rater account's nonce at the moment the authorization executes */
+    nonce: number;
+    yParity: number;
+    r: string;
+    s: string;
+}
+/**
+ * Request body for `POST /feedback/evm/prepare`.
+ *
+ * `rater` is the address that will appear on-chain as the author, which is the
+ * whole point of this rail.
+ */
+interface PrepareRelayFeedbackRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    feedback: FeedbackParams & {
+        rater: string;
+    };
+}
+/**
+ * Response from `POST /feedback/evm/prepare`.
+ *
+ * Everything the rater has to sign so the CHAIN records them as the author
+ * while the facilitator pays the gas.
+ */
+interface PrepareRelayFeedbackResponse {
+    success: boolean;
+    /** The `FeedbackDelegate` the rater's EOA must be delegated to */
+    delegate?: string;
+    /** Registry calldata the rater is authorising, hex-encoded */
+    data?: string;
+    /**
+     * The value the rater's signature must recover against.
+     *
+     * **The EIP-191 envelope is already applied here.** A holder of a raw key
+     * signs this directly as a prehash (viem's `sign({ hash })`, ethers'
+     * `signingKey.sign`). A WALLET must not be handed this value: `personal_sign`
+     * applies the envelope itself, so it gets wrapped twice and recovers an
+     * address that is not the rater. Wallets sign {@link signingPayload}.
+     */
+    digest?: string;
+    /**
+     * The same hash with the envelope still OFF — what a wallet signs.
+     *
+     * `keccak256('\x19Ethereum Signed Message:\n32' || signingPayload)` is
+     * exactly {@link digest}, so a client can check the two against each other
+     * rather than rebuilding the preimage from `data`.
+     *
+     * Requires facilitator v1.95.0+. Older facilitators omit it; a client that
+     * needs it should fail loudly rather than fall back to signing `digest`
+     * through a wallet, which produces a well-formed signature that authorises
+     * nobody.
+     */
+    signingPayload?: string;
+    /**
+     * Unix seconds after which the authorisation is void. Short on purpose:
+     * relaying is permissionless, so a signed authorisation is live in the wild
+     * until it expires.
+     */
+    deadline?: number;
+    /** Single-use value binding this authorisation. Echo it back on submit */
+    nonce?: string;
+    /**
+     * Whether the account is already delegated. When `false` the submission MUST
+     * carry an `authorization`.
+     */
+    delegated: boolean;
+    /** The account nonce to put in the EIP-7702 authorization, when needed */
+    accountNonce?: number;
+    chainId: number;
+    error?: string;
+    network: Erc8004Network;
+}
+/**
+ * Request body for `POST /feedback/evm/submit`.
+ *
+ * The feedback parameters are not redundant with `prepare`: the facilitator
+ * rebuilds the registry calldata from them and requires the rater's signature
+ * to cover exactly that. It does not relay calldata it was handed.
+ */
+interface SubmitRelayFeedbackRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    feedback: FeedbackParams & {
+        rater: string;
+    };
+    /** The deadline `prepare` returned */
+    deadline: number;
+    /** The single-use nonce `prepare` returned */
+    nonce: string;
+    /**
+     * The rater's signature. It must recover to `rater` over `digest` — so
+     * either a raw-key prehash signature over `digest`, or a wallet
+     * `personal_sign` over `signingPayload`. Not `personal_sign` over `digest`.
+     */
+    signature: string;
+    /** Required only when `prepare` answered `delegated: false` */
+    authorization?: RelayAuthorizationParams;
+}
 /**
  * Proof of payment returned when settling with ERC-8004 extension
  */
@@ -1871,6 +2017,14 @@ declare class Erc8004Client {
      *
      * Requires proof of payment for authorized feedback submission.
      *
+     * @deprecated On this route the facilitator is the AUTHOR: the registry
+     * records `msg.sender`, and that is the facilitator's wallet — which can also
+     * revoke what it wrote. On the networks in {@link RELAYED_FEEDBACK_NETWORKS}
+     * use {@link Erc8004Client.prepareRelayedFeedback} +
+     * {@link Erc8004Client.submitRelayedFeedback} instead, which record the RATER
+     * as author. This route still works and is not going away without notice: it
+     * is the only one available where no `FeedbackDelegate` is deployed.
+     *
      * @param request - Feedback request with agent ID, value, and proof
      * @returns Feedback response with transaction hash
      *
@@ -1898,6 +2052,71 @@ declare class Erc8004Client {
      * ```
      */
     submitFeedback(request: FeedbackRequest): Promise<FeedbackResponse>;
+    /**
+     * Ask the facilitator what the rater must sign to author a rating.
+     *
+     * Step 1 of the rater-authored rail. Writes nothing on-chain and costs
+     * nothing: it reads the delegate, the rater's delegation state and their
+     * account nonce, then hands back a digest, a deadline and a single-use nonce.
+     *
+     * Why this exists: the ERC-8004 Reputation Registry records `msg.sender` as
+     * the author, and the deployed implementation has no delegation path — no
+     * `giveFeedbackWithSignature`, no ERC-2771 forwarder. So a rating the
+     * facilitator relays the ordinary way is a rating attributed to the
+     * FACILITATOR. EIP-7702 fixes it without touching the registry: the rater
+     * delegates their own EOA to the `FeedbackDelegate` and the transaction is
+     * sent TO THE RATER'S ADDRESS, so the registry sees the rater while the
+     * facilitator pays.
+     *
+     * What to do with the answer:
+     * 1. Produce the rater's signature. **Which value you sign depends on how you
+     *    sign it**, and getting it wrong yields a well-formed signature that
+     *    authorises nobody:
+     *    - raw key: sign `digest` as a **prehash**. It already carries the
+     *      EIP-191 envelope.
+     *    - 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`.
+     * 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
+     *    parameters, `deadline` and `nonce`.
+     *
+     * @param request - Network, rater address and feedback parameters
+     * @returns Everything needed to sign, including whether an EIP-7702
+     * authorization is still required
+     *
+     * @example
+     * ```ts
+     * const prep = await erc8004.prepareRelayedFeedback({
+     *   x402Version: 1,
+     *   network: 'base',
+     *   feedback: { agentId: 18896, value: 95, tag1: 'quality', rater: raterAddress },
+     * });
+     * // prep.delegated === false -> an EIP-7702 authorization is required
+     * ```
+     */
+    prepareRelayedFeedback(request: PrepareRelayFeedbackRequest): Promise<PrepareRelayFeedbackResponse>;
+    /**
+     * Relay a rater-authored rating; the facilitator pays the gas.
+     *
+     * Step 2 of the rater-authored rail. The on-chain record that comes out of it
+     * has the RATER as `msg.sender`, so `getClients(agentId)` shows the rater
+     * rather than the facilitator.
+     *
+     * Pass back the same feedback parameters, `deadline` and `nonce` that
+     * {@link prepareRelayedFeedback} returned. They are not redundant: the
+     * facilitator rebuilds the registry calldata from them and requires the
+     * rater's signature to cover exactly that.
+     *
+     * `authorization` is required only when `prepare` answered
+     * `delegated: false`. One that names a different delegate than the one
+     * `prepare` offered is refused before any gas is spent.
+     *
+     * @param request - Feedback parameters plus the rater's signature
+     * @returns Feedback response with the transaction hash
+     */
+    submitRelayedFeedback(request: SubmitRelayFeedbackRequest): Promise<FeedbackResponse>;
     /**
      * Revoke previously submitted feedback
      *
@@ -2528,4 +2747,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 ProofOfPayment, type RefundRequest, type RefundStatus, type RegisterAgentRequest, type RegisterAgentResponse, type RegisterJobResponse, type RegisterJobStatus, RegistrationPendingError, type ReputationResponse, type ReputationSummary, type RequestRefundOptions, type ResourceInfoV2, type SettleRequest, type SettleRequestV2, type SettleResponse, type SettleResponseWithProof, 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, 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 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 };

package/dist/backend/index.d.ts

@@ -1385,6 +1385,152 @@ declare function wireNetwork(network: string): string;
  * reaches the wire. Use 'base'.
  */
 type Erc8004Network = 'ethereum' | 'base' | 'polygon' | 'arbitrum' | 'optimism' | 'celo' | 'bsc' | 'monad' | 'avalanche' | 'scroll' | 'skale-base' | 'base-mainnet' | 'ethereum-sepolia' | 'base-sepolia' | 'polygon-amoy' | 'arbitrum-sepolia' | 'optimism-sepolia' | 'celo-sepolia' | 'avalanche-fuji' | 'skale-base-sepolia' | 'solana' | 'solana-devnet';
+/**
+ * Networks where the facilitator serves the RELAYED feedback rail, i.e. where
+ * Execution Market has deployed a `FeedbackDelegate` and the facilitator
+ * verified it on-chain (code present, and its `REPUTATION_REGISTRY()` reads
+ * back that network's registry).
+ *
+ * Anywhere else `POST /feedback/evm/prepare` answers 400 — and it should. An
+ * invented delegate address would send a type-4 transaction to an account with
+ * no code behind it, and in the EVM a `.call()` to an address with no code
+ * RETURNS SUCCESS. The failure would look exactly like a rating that rated
+ * nobody.
+ *
+ * `avalanche` is absent and is not waiting to join: the C-Chain rejects the
+ * transaction type itself (`-32000 transaction type not supported`), so there
+ * is nothing to deploy against. Anchor the rating on a chain that supports
+ * EIP-7702; the payment stays where it was made.
+ */
+declare const RELAYED_FEEDBACK_NETWORKS: readonly Erc8004Network[];
+/**
+ * Whether `network` serves the rater-authored feedback rail.
+ *
+ * Lets a caller route without paying a round trip for a 400. The facilitator
+ * re-checks the delegate on-chain on every request regardless — this list is a
+ * routing hint, never the authority.
+ */
+declare function supportsRelayedFeedback(network: string): boolean;
+/**
+ * An EIP-7702 authorization, as a wallet produces it.
+ *
+ * Needed only the first time a rater rates: it points their EOA at the
+ * `FeedbackDelegate`. Once delegated, `prepare` answers `delegated: true` and
+ * the submission carries no authorization at all.
+ */
+interface RelayAuthorizationParams {
+    /**
+     * Chain the authorization is for.
+     *
+     * `0` is EIP-7702's wildcard and is valid on EVERY chain — a far broader
+     * grant than pinning this one. Send the chain id `prepare` returned.
+     */
+    chainId: number;
+    /**
+     * The delegate the account is pointed at. Must be the address `prepare`
+     * offered; the facilitator refuses anything else before it pays for a
+     * transaction.
+     */
+    address: string;
+    /** The rater account's nonce at the moment the authorization executes */
+    nonce: number;
+    yParity: number;
+    r: string;
+    s: string;
+}
+/**
+ * Request body for `POST /feedback/evm/prepare`.
+ *
+ * `rater` is the address that will appear on-chain as the author, which is the
+ * whole point of this rail.
+ */
+interface PrepareRelayFeedbackRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    feedback: FeedbackParams & {
+        rater: string;
+    };
+}
+/**
+ * Response from `POST /feedback/evm/prepare`.
+ *
+ * Everything the rater has to sign so the CHAIN records them as the author
+ * while the facilitator pays the gas.
+ */
+interface PrepareRelayFeedbackResponse {
+    success: boolean;
+    /** The `FeedbackDelegate` the rater's EOA must be delegated to */
+    delegate?: string;
+    /** Registry calldata the rater is authorising, hex-encoded */
+    data?: string;
+    /**
+     * The value the rater's signature must recover against.
+     *
+     * **The EIP-191 envelope is already applied here.** A holder of a raw key
+     * signs this directly as a prehash (viem's `sign({ hash })`, ethers'
+     * `signingKey.sign`). A WALLET must not be handed this value: `personal_sign`
+     * applies the envelope itself, so it gets wrapped twice and recovers an
+     * address that is not the rater. Wallets sign {@link signingPayload}.
+     */
+    digest?: string;
+    /**
+     * The same hash with the envelope still OFF — what a wallet signs.
+     *
+     * `keccak256('\x19Ethereum Signed Message:\n32' || signingPayload)` is
+     * exactly {@link digest}, so a client can check the two against each other
+     * rather than rebuilding the preimage from `data`.
+     *
+     * Requires facilitator v1.95.0+. Older facilitators omit it; a client that
+     * needs it should fail loudly rather than fall back to signing `digest`
+     * through a wallet, which produces a well-formed signature that authorises
+     * nobody.
+     */
+    signingPayload?: string;
+    /**
+     * Unix seconds after which the authorisation is void. Short on purpose:
+     * relaying is permissionless, so a signed authorisation is live in the wild
+     * until it expires.
+     */
+    deadline?: number;
+    /** Single-use value binding this authorisation. Echo it back on submit */
+    nonce?: string;
+    /**
+     * Whether the account is already delegated. When `false` the submission MUST
+     * carry an `authorization`.
+     */
+    delegated: boolean;
+    /** The account nonce to put in the EIP-7702 authorization, when needed */
+    accountNonce?: number;
+    chainId: number;
+    error?: string;
+    network: Erc8004Network;
+}
+/**
+ * Request body for `POST /feedback/evm/submit`.
+ *
+ * The feedback parameters are not redundant with `prepare`: the facilitator
+ * rebuilds the registry calldata from them and requires the rater's signature
+ * to cover exactly that. It does not relay calldata it was handed.
+ */
+interface SubmitRelayFeedbackRequest {
+    x402Version: 1 | 2;
+    network: Erc8004Network;
+    feedback: FeedbackParams & {
+        rater: string;
+    };
+    /** The deadline `prepare` returned */
+    deadline: number;
+    /** The single-use nonce `prepare` returned */
+    nonce: string;
+    /**
+     * The rater's signature. It must recover to `rater` over `digest` — so
+     * either a raw-key prehash signature over `digest`, or a wallet
+     * `personal_sign` over `signingPayload`. Not `personal_sign` over `digest`.
+     */
+    signature: string;
+    /** Required only when `prepare` answered `delegated: false` */
+    authorization?: RelayAuthorizationParams;
+}
 /**
  * Proof of payment returned when settling with ERC-8004 extension
  */
@@ -1871,6 +2017,14 @@ declare class Erc8004Client {
      *
      * Requires proof of payment for authorized feedback submission.
      *
+     * @deprecated On this route the facilitator is the AUTHOR: the registry
+     * records `msg.sender`, and that is the facilitator's wallet — which can also
+     * revoke what it wrote. On the networks in {@link RELAYED_FEEDBACK_NETWORKS}
+     * use {@link Erc8004Client.prepareRelayedFeedback} +
+     * {@link Erc8004Client.submitRelayedFeedback} instead, which record the RATER
+     * as author. This route still works and is not going away without notice: it
+     * is the only one available where no `FeedbackDelegate` is deployed.
+     *
      * @param request - Feedback request with agent ID, value, and proof
      * @returns Feedback response with transaction hash
      *
@@ -1898,6 +2052,71 @@ declare class Erc8004Client {
      * ```
      */
     submitFeedback(request: FeedbackRequest): Promise<FeedbackResponse>;
+    /**
+     * Ask the facilitator what the rater must sign to author a rating.
+     *
+     * Step 1 of the rater-authored rail. Writes nothing on-chain and costs
+     * nothing: it reads the delegate, the rater's delegation state and their
+     * account nonce, then hands back a digest, a deadline and a single-use nonce.
+     *
+     * Why this exists: the ERC-8004 Reputation Registry records `msg.sender` as
+     * the author, and the deployed implementation has no delegation path — no
+     * `giveFeedbackWithSignature`, no ERC-2771 forwarder. So a rating the
+     * facilitator relays the ordinary way is a rating attributed to the
+     * FACILITATOR. EIP-7702 fixes it without touching the registry: the rater
+     * delegates their own EOA to the `FeedbackDelegate` and the transaction is
+     * sent TO THE RATER'S ADDRESS, so the registry sees the rater while the
+     * facilitator pays.
+     *
+     * What to do with the answer:
+     * 1. Produce the rater's signature. **Which value you sign depends on how you
+     *    sign it**, and getting it wrong yields a well-formed signature that
+     *    authorises nobody:
+     *    - raw key: sign `digest` as a **prehash**. It already carries the
+     *      EIP-191 envelope.
+     *    - 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`.
+     * 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
+     *    parameters, `deadline` and `nonce`.
+     *
+     * @param request - Network, rater address and feedback parameters
+     * @returns Everything needed to sign, including whether an EIP-7702
+     * authorization is still required
+     *
+     * @example
+     * ```ts
+     * const prep = await erc8004.prepareRelayedFeedback({
+     *   x402Version: 1,
+     *   network: 'base',
+     *   feedback: { agentId: 18896, value: 95, tag1: 'quality', rater: raterAddress },
+     * });
+     * // prep.delegated === false -> an EIP-7702 authorization is required
+     * ```
+     */
+    prepareRelayedFeedback(request: PrepareRelayFeedbackRequest): Promise<PrepareRelayFeedbackResponse>;
+    /**
+     * Relay a rater-authored rating; the facilitator pays the gas.
+     *
+     * Step 2 of the rater-authored rail. The on-chain record that comes out of it
+     * has the RATER as `msg.sender`, so `getClients(agentId)` shows the rater
+     * rather than the facilitator.
+     *
+     * Pass back the same feedback parameters, `deadline` and `nonce` that
+     * {@link prepareRelayedFeedback} returned. They are not redundant: the
+     * facilitator rebuilds the registry calldata from them and requires the
+     * rater's signature to cover exactly that.
+     *
+     * `authorization` is required only when `prepare` answered
+     * `delegated: false`. One that names a different delegate than the one
+     * `prepare` offered is refused before any gas is spent.
+     *
+     * @param request - Feedback parameters plus the rater's signature
+     * @returns Feedback response with the transaction hash
+     */
+    submitRelayedFeedback(request: SubmitRelayFeedbackRequest): Promise<FeedbackResponse>;
     /**
      * Revoke previously submitted feedback
      *
@@ -2528,4 +2747,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 ProofOfPayment, type RefundRequest, type RefundStatus, type RegisterAgentRequest, type RegisterAgentResponse, type RegisterJobResponse, type RegisterJobStatus, RegistrationPendingError, type ReputationResponse, type ReputationSummary, type RequestRefundOptions, type ResourceInfoV2, type SettleRequest, type SettleRequestV2, type SettleResponse, type SettleResponseWithProof, 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, 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 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 };