@opendatalabs/vana-sdk 2.3.0 → 3.0.1

package/dist/types/permissions.js

@@ -1 +0,0 @@
-//# sourceMappingURL=permissions.js.map

package/dist/types/permissions.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}

package/dist/types/personal.cjs

@@ -1,17 +0,0 @@
-"use strict";
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __copyProps = (to, from, except, desc) => {
-  if (from && typeof from === "object" || typeof from === "function") {
-    for (let key of __getOwnPropNames(from))
-      if (!__hasOwnProp.call(to, key) && key !== except)
-        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
-  }
-  return to;
-};
-var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
-var personal_exports = {};
-module.exports = __toCommonJS(personal_exports);
-//# sourceMappingURL=personal.cjs.map

package/dist/types/personal.cjs.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../../src/types/personal.ts"],"sourcesContent":["/**\n * Defines parameters for posting data requests to personal servers.\n *\n * @remarks\n * Used to initiate data access requests that require user permission.\n * The permission ID references a previously granted permission that\n * authorizes the requester to access specific user data.\n *\n * @example\n * ```typescript\n * const params: PostRequestParams = {\n *   permissionId: 123\n * };\n *\n * const response = await vana.personal.postRequest(params);\n * console.log('Request posted:', response.requestId);\n * ```\n *\n * @category Personal Server\n */\nexport interface PostRequestParams {\n  /**\n   * References a granted permission authorizing data access.\n   * Obtain via permission granting flow or query existing permissions.\n   * @throws {PermissionNotFoundError} If permission ID is invalid.\n   */\n  permissionId: number;\n}\n\n/**\n * Defines parameters for creating server-side operations.\n *\n * @remarks\n * Initiates asynchronous operations on the personal server that\n * process user data according to granted permissions. Operations\n * run in the background and can be monitored via their operation ID.\n *\n * @example\n * ```typescript\n * const params: CreateOperationParams = {\n *   permissionId: 456\n * };\n *\n * const operation = await vana.server.createOperation(params);\n * // Monitor operation status\n * const status = await vana.server.getOperationStatus(operation.id);\n * ```\n *\n * @category Personal Server\n */\nexport interface CreateOperationParams {\n  /**\n   * References the permission scope for this operation.\n   * Determines what data and actions are allowed.\n   * @throws {InsufficientPermissionsError} If permission scope is inadequate.\n   */\n  permissionId: number;\n}\n\n/**\n * Parameters for downloading an artifact from a server operation.\n *\n * @remarks\n * Artifacts are files generated during operations like Gemini agent analysis.\n * The download requires authentication using the application's signature.\n *\n * @category Personal Server\n */\nexport interface DownloadArtifactParams {\n  /**\n   * The operation ID that generated the artifact.\n   */\n  operationId: string;\n  /**\n   * The path to the artifact file to download.\n   */\n  artifactPath: string;\n}\n\n/**\n * Defines parameters for initializing personal server connections.\n *\n * @remarks\n * Establishes secure communication channels with a user's personal\n * data server. The server manages encrypted user data and enforces\n * permission-based access control. Initialization includes key exchange\n * and session establishment.\n *\n * @example\n * ```typescript\n * const params: InitPersonalServerParams = {\n *   userAddress: '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36'\n * };\n *\n * const server = await vana.personal.initServer(params);\n * console.log('Connected to server:', server.baseUrl);\n * ```\n *\n * @category Personal Server\n */\nexport interface InitPersonalServerParams {\n  /**\n   * Identifies the user whose personal server to connect to.\n   * Must be a valid Ethereum address in hex format.\n   * @example '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36'\n   */\n  userAddress: string;\n}\n\n/**\n * Represents comprehensive personal server identity and connection information.\n *\n * @remarks\n * Combines core server identity with connection metadata required for\n * establishing secure communication. Personal servers are user-controlled\n * nodes that store and serve encrypted personal data according to\n * user-defined permissions. This interface provides all necessary\n * information to connect to and interact with a personal server.\n *\n * @example\n * ```typescript\n * const identity: PersonalServerIdentity = {\n *   kind: 'PersonalServer',\n *   address: '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36',\n *   publicKey: '0x04...', // 65-byte uncompressed public key\n *   baseUrl: 'https://ps.user.vana.com',\n *   name: 'User Personal Server #1'\n * };\n *\n * // Use identity to establish encrypted connection\n * const encrypted = await crypto.encrypt(data, identity.publicKey);\n * const response = await fetch(`${identity.baseUrl}/api/data`, {\n *   method: 'POST',\n *   body: encrypted\n * });\n * ```\n *\n * @category Personal Server\n */\nexport interface PersonalServerIdentity {\n  /**\n   * Identifies the resource type for API disambiguation.\n   * Always 'PersonalServer' for personal server instances.\n   */\n  kind: string;\n\n  /**\n   * Uniquely identifies the server on the blockchain.\n   * Used for permission verification and identity proofs.\n   * @example '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36'\n   */\n  address: string;\n\n  /**\n   * Enables end-to-end encryption for data transmission.\n   * Must be in uncompressed format (65 bytes with 0x04 prefix).\n   * @example '0x04...' (130 hex characters)\n   */\n  publicKey: string;\n\n  /**\n   * Provides the HTTPS endpoint for server API requests.\n   * Should not include trailing slashes or API paths.\n   * @example 'https://ps.user.vana.com'\n   */\n  baseUrl: string;\n\n  /**\n   * Displays a user-friendly identifier for the server.\n   * Used in UI components and logging for clarity.\n   * @example 'Primary Data Server'\n   */\n  name: string;\n}\n\n/**\n * @remarks\n * Additional server response types are auto-generated from the OpenAPI\n * specification and available in the server-exports module. Import those\n * types directly when working with server API responses.\n *\n * @see {@link ../types/server-exports | Server Export Types}\n */\n"],"mappings":";;;;;;;;;;;;;;AAAA;AAAA;","names":[]}

package/dist/types/personal.d.ts

@@ -1,174 +0,0 @@
-/**
- * Defines parameters for posting data requests to personal servers.
- *
- * @remarks
- * Used to initiate data access requests that require user permission.
- * The permission ID references a previously granted permission that
- * authorizes the requester to access specific user data.
- *
- * @example
- * ```typescript
- * const params: PostRequestParams = {
- *   permissionId: 123
- * };
- *
- * const response = await vana.personal.postRequest(params);
- * console.log('Request posted:', response.requestId);
- * ```
- *
- * @category Personal Server
- */
-export interface PostRequestParams {
-    /**
-     * References a granted permission authorizing data access.
-     * Obtain via permission granting flow or query existing permissions.
-     * @throws {PermissionNotFoundError} If permission ID is invalid.
-     */
-    permissionId: number;
-}
-/**
- * Defines parameters for creating server-side operations.
- *
- * @remarks
- * Initiates asynchronous operations on the personal server that
- * process user data according to granted permissions. Operations
- * run in the background and can be monitored via their operation ID.
- *
- * @example
- * ```typescript
- * const params: CreateOperationParams = {
- *   permissionId: 456
- * };
- *
- * const operation = await vana.server.createOperation(params);
- * // Monitor operation status
- * const status = await vana.server.getOperationStatus(operation.id);
- * ```
- *
- * @category Personal Server
- */
-export interface CreateOperationParams {
-    /**
-     * References the permission scope for this operation.
-     * Determines what data and actions are allowed.
-     * @throws {InsufficientPermissionsError} If permission scope is inadequate.
-     */
-    permissionId: number;
-}
-/**
- * Parameters for downloading an artifact from a server operation.
- *
- * @remarks
- * Artifacts are files generated during operations like Gemini agent analysis.
- * The download requires authentication using the application's signature.
- *
- * @category Personal Server
- */
-export interface DownloadArtifactParams {
-    /**
-     * The operation ID that generated the artifact.
-     */
-    operationId: string;
-    /**
-     * The path to the artifact file to download.
-     */
-    artifactPath: string;
-}
-/**
- * Defines parameters for initializing personal server connections.
- *
- * @remarks
- * Establishes secure communication channels with a user's personal
- * data server. The server manages encrypted user data and enforces
- * permission-based access control. Initialization includes key exchange
- * and session establishment.
- *
- * @example
- * ```typescript
- * const params: InitPersonalServerParams = {
- *   userAddress: '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36'
- * };
- *
- * const server = await vana.personal.initServer(params);
- * console.log('Connected to server:', server.baseUrl);
- * ```
- *
- * @category Personal Server
- */
-export interface InitPersonalServerParams {
-    /**
-     * Identifies the user whose personal server to connect to.
-     * Must be a valid Ethereum address in hex format.
-     * @example '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36'
-     */
-    userAddress: string;
-}
-/**
- * Represents comprehensive personal server identity and connection information.
- *
- * @remarks
- * Combines core server identity with connection metadata required for
- * establishing secure communication. Personal servers are user-controlled
- * nodes that store and serve encrypted personal data according to
- * user-defined permissions. This interface provides all necessary
- * information to connect to and interact with a personal server.
- *
- * @example
- * ```typescript
- * const identity: PersonalServerIdentity = {
- *   kind: 'PersonalServer',
- *   address: '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36',
- *   publicKey: '0x04...', // 65-byte uncompressed public key
- *   baseUrl: 'https://ps.user.vana.com',
- *   name: 'User Personal Server #1'
- * };
- *
- * // Use identity to establish encrypted connection
- * const encrypted = await crypto.encrypt(data, identity.publicKey);
- * const response = await fetch(`${identity.baseUrl}/api/data`, {
- *   method: 'POST',
- *   body: encrypted
- * });
- * ```
- *
- * @category Personal Server
- */
-export interface PersonalServerIdentity {
-    /**
-     * Identifies the resource type for API disambiguation.
-     * Always 'PersonalServer' for personal server instances.
-     */
-    kind: string;
-    /**
-     * Uniquely identifies the server on the blockchain.
-     * Used for permission verification and identity proofs.
-     * @example '0x742d35Cc6558Fd4D9e9E0E888F0462ef6919Bd36'
-     */
-    address: string;
-    /**
-     * Enables end-to-end encryption for data transmission.
-     * Must be in uncompressed format (65 bytes with 0x04 prefix).
-     * @example '0x04...' (130 hex characters)
-     */
-    publicKey: string;
-    /**
-     * Provides the HTTPS endpoint for server API requests.
-     * Should not include trailing slashes or API paths.
-     * @example 'https://ps.user.vana.com'
-     */
-    baseUrl: string;
-    /**
-     * Displays a user-friendly identifier for the server.
-     * Used in UI components and logging for clarity.
-     * @example 'Primary Data Server'
-     */
-    name: string;
-}
-/**
- * @remarks
- * Additional server response types are auto-generated from the OpenAPI
- * specification and available in the server-exports module. Import those
- * types directly when working with server API responses.
- *
- * @see {@link ../types/server-exports | Server Export Types}
- */

package/dist/types/personal.js

@@ -1 +0,0 @@
-//# sourceMappingURL=personal.js.map

package/dist/types/personal.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}

package/dist/types/relayer.cjs

@@ -1,17 +0,0 @@
-"use strict";
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __copyProps = (to, from, except, desc) => {
-  if (from && typeof from === "object" || typeof from === "function") {
-    for (let key of __getOwnPropNames(from))
-      if (!__hasOwnProp.call(to, key) && key !== except)
-        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
-  }
-  return to;
-};
-var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
-var relayer_exports = {};
-module.exports = __toCommonJS(relayer_exports);
-//# sourceMappingURL=relayer.cjs.map

package/dist/types/relayer.cjs.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../../src/types/relayer.ts"],"sourcesContent":["/**\n * Defines types for gasless transaction relayers and server operations.\n *\n * @remarks\n * This module provides comprehensive type definitions for interacting with\n * relayer services that enable gasless transactions and auxiliary operations.\n * It includes both legacy v1 types and the simplified v2 unified interface.\n *\n * @category Types\n * @module types/relayer\n */\n\nimport type { Hash, Address, TransactionReceipt } from \"viem\";\nimport type {\n  GrantFile,\n  PermissionGrantTypedData,\n  GenericTypedData,\n} from \"./permissions\";\nimport type { Contract, Fn } from \"../generated/event-types\";\n\n/**\n * Represents the response from storing grant files via relayer.\n *\n * @remarks\n * Contains storage location, metadata, and error information for\n * grant file upload operations.\n *\n * @category Advanced\n */\nexport interface RelayerStorageResponse {\n  /** The IPFS URL where the grant file is stored */\n  grantUrl: string;\n  /** Success status */\n  success: boolean;\n  /** Optional error message */\n  error?: string;\n  /** Storage metadata */\n  metadata?: {\n    /** IPFS hash */\n    ipfsHash: string;\n    /** File size in bytes */\n    size: number;\n    /** Upload timestamp */\n    timestamp: number;\n  };\n}\n\n/**\n * Represents the response from submitting transactions via relayer.\n *\n * @remarks\n * Contains transaction hash, status, and metadata for gasless\n * transaction submissions.\n *\n * @category Advanced\n */\nexport interface RelayerTransactionResponse {\n  /** The transaction hash of the submitted transaction */\n  transactionHash: Hash;\n  /** Success status */\n  success: boolean;\n  /** Optional error message */\n  error?: string;\n  /** Transaction metadata */\n  metadata?: {\n    /** Gas used */\n    gasUsed?: bigint;\n    /** Gas price */\n    gasPrice?: bigint;\n    /** Block number */\n    blockNumber?: bigint;\n    /** Transaction status */\n    status?: \"pending\" | \"confirmed\" | \"failed\";\n  };\n}\n\n/**\n * Specifies parameters for storing grant files via relayer.\n *\n * @remarks\n * Includes the grant file and optional storage configuration\n * such as encryption and pinning duration.\n *\n * @category Advanced\n */\nexport interface RelayerStoreParams {\n  /** The grant file to store */\n  grantFile: GrantFile;\n  /** Optional storage options */\n  options?: {\n    /** IPFS pin duration in seconds */\n    pinDuration?: number;\n    /** Whether to use encryption */\n    encrypt?: boolean;\n    /** Custom metadata */\n    metadata?: Record<string, unknown>;\n  };\n}\n\n/**\n * Specifies parameters for submitting gasless transactions.\n *\n * @remarks\n * Contains signed typed data and transaction configuration options\n * for relayer submission.\n *\n * @category Advanced\n */\nexport interface RelayerSubmitParams {\n  /** The signed typed data */\n  typedData: PermissionGrantTypedData;\n  /** The signature */\n  signature: string;\n  /** Optional transaction options */\n  options?: {\n    /** Gas limit */\n    gasLimit?: bigint;\n    /** Priority level */\n    priority?: \"low\" | \"medium\" | \"high\";\n    /** Whether to wait for confirmation */\n    waitForConfirmation?: boolean;\n  };\n}\n\n/**\n * Represents the current status and capabilities of a relayer service.\n *\n * @remarks\n * Provides information about supported chains, rate limits, and\n * current operational status for monitoring and decision-making.\n *\n * @category Advanced\n */\nexport interface RelayerStatus {\n  /** Whether the relayer is online */\n  online: boolean;\n  /** Service version */\n  version: string;\n  /** Supported chains */\n  supportedChains: number[];\n  /** Current chain status */\n  chainStatus: Record<\n    number,\n    {\n      /** Whether the chain is supported */\n      supported: boolean;\n      /** Current block number */\n      currentBlock: bigint;\n      /** Gas price estimation */\n      gasPrice: bigint;\n      /** Queue size */\n      queueSize: number;\n    }\n  >;\n  /** Rate limit information */\n  rateLimits: {\n    /** Requests per minute */\n    requestsPerMinute: number;\n    /** Storage requests per hour */\n    storageRequestsPerHour: number;\n    /** Transaction requests per hour */\n    transactionRequestsPerHour: number;\n  };\n}\n\n/**\n * Configures behavior for relayer requests.\n *\n * @remarks\n * Controls timeout, retry logic, headers, and priority for\n * relayer operation requests.\n *\n * @category Advanced\n */\nexport interface RelayerRequestOptions {\n  /** Request timeout in milliseconds */\n  timeout?: number;\n  /** Whether to retry on failure */\n  retry?: boolean;\n  /** Custom headers */\n  headers?: Record<string, string>;\n  /** Request priority */\n  priority?: \"low\" | \"medium\" | \"high\";\n}\n\n/**\n * Represents an error response from the relayer service.\n *\n * @remarks\n * Provides structured error information including codes, messages,\n * and debugging details for error handling and recovery.\n *\n * @category Advanced\n */\nexport interface RelayerErrorResponse {\n  /** Error code */\n  code: string;\n  /** Error message */\n  message: string;\n  /** Additional error details */\n  details?: Record<string, unknown>;\n  /** Request ID for debugging */\n  requestId?: string;\n  /** Timestamp of error */\n  timestamp: number;\n}\n\n/**\n * Provides information about the relayer's processing queue.\n *\n * @remarks\n * Includes queue size, position, estimated processing time, and\n * performance statistics for queue monitoring.\n *\n * @category Advanced\n */\nexport interface RelayerQueueInfo {\n  /** Current queue size */\n  size: number;\n  /** Estimated processing time in seconds */\n  estimatedProcessingTime: number;\n  /** Queue position for a specific request */\n  position?: number;\n  /** Processing statistics */\n  stats: {\n    /** Average processing time in seconds */\n    averageProcessingTime: number;\n    /** Requests processed in last hour */\n    requestsProcessedHour: number;\n    /** Success rate percentage */\n    successRate: number;\n  };\n}\n\n/**\n * Tracks the status of a transaction submitted via relayer.\n *\n * @remarks\n * Provides detailed tracking information including confirmation status,\n * gas usage, and historical status checks.\n *\n * @category Advanced\n */\nexport interface RelayerTransactionStatus {\n  /** Transaction hash */\n  transactionHash: Hash;\n  /** Current status */\n  status: \"pending\" | \"confirmed\" | \"failed\";\n  /** Block number if confirmed */\n  blockNumber?: bigint;\n  /** Gas used */\n  gasUsed?: bigint;\n  /** Error message if failed */\n  error?: string;\n  /** Status checks performed */\n  checks: Array<{\n    /** Check timestamp */\n    timestamp: number;\n    /** Status at time of check */\n    status: string;\n    /** Block number at time of check */\n    blockNumber: bigint;\n  }>;\n}\n\n/**\n * Provides performance metrics for the relayer service.\n *\n * @remarks\n * Includes transaction statistics, success rates, processing times,\n * and uptime information for monitoring and optimization.\n *\n * @category Advanced\n */\nexport interface RelayerMetrics {\n  /** Total transactions processed */\n  totalTransactions: number;\n  /** Successful transactions */\n  successfulTransactions: number;\n  /** Failed transactions */\n  failedTransactions: number;\n  /** Average processing time in seconds */\n  averageProcessingTime: number;\n  /** Current queue size */\n  queueSize: number;\n  /** Uptime percentage */\n  uptime: number;\n  /** Last 24 hour statistics */\n  last24Hours: {\n    /** Transactions processed */\n    transactions: number;\n    /** Success rate */\n    successRate: number;\n    /** Average response time */\n    averageResponseTime: number;\n  };\n}\n\n/**\n * Configures webhook notifications for relayer events.\n *\n * @remarks\n * Enables asynchronous notifications for transaction confirmations,\n * failures, and storage completions.\n *\n * @category Advanced\n */\nexport interface RelayerWebhookConfig {\n  /** Webhook URL */\n  url: string;\n  /** Events to subscribe to */\n  events: Array<\n    \"transaction_confirmed\" | \"transaction_failed\" | \"storage_complete\"\n  >;\n  /** Webhook secret for signature verification */\n  secret?: string;\n  /** Whether webhook is active */\n  active: boolean;\n}\n\n/**\n * Represents a webhook event payload from the relayer.\n *\n * @remarks\n * Contains event data, timestamp, and signature for verification\n * of webhook authenticity.\n *\n * @category Advanced\n */\nexport interface RelayerWebhookPayload {\n  /** Event type */\n  event: string;\n  /** Event data */\n  data: Record<string, unknown>;\n  /** Timestamp */\n  timestamp: number;\n  /** Webhook ID */\n  webhookId: string;\n  /** Signature for verification */\n  signature: string;\n}\n\n// ===== NEW SIMPLIFIED RELAYER TYPES (v2) =====\n\n/**\n * Handles both EIP-712 signed operations and direct server operations through a single interface.\n *\n * @remarks\n * This discriminated union provides type safety through TypeScript's narrowing.\n * The `type` field determines which operation variant is being used.\n * Signed operations require blockchain transactions, while direct operations\n * handle auxiliary tasks like file storage.\n *\n * @category Relayer\n * @see {@link https://docs.vana.org/docs/gasless-transactions | Gasless Transactions Guide}\n */\nexport type UnifiedRelayerRequest =\n  | SignedRelayerRequest\n  | DirectRelayerRequest\n  | {\n      type: \"status_check\";\n      operationId: string;\n    };\n\n/**\n * Represents an EIP-712 signed operation for gasless transaction submission.\n *\n * @remarks\n * Signed requests contain typed data and signatures that are verified\n * on-chain by smart contracts. The relayer pays gas fees on behalf of users.\n *\n * @category Relayer\n */\nexport interface SignedRelayerRequest {\n  /** Discriminator field identifying this as a signed operation */\n  type: \"signed\";\n  /** Operation identifier for routing (e.g., 'submitAddPermission') */\n  operation: SignedOperationType;\n  /** EIP-712 typed data structure for the operation */\n  typedData: GenericTypedData;\n  /** User's signature of the typed data */\n  signature: Hash;\n  /** Optional address for additional signer verification */\n  expectedUserAddress?: Address;\n}\n\n/**\n * Enumerates supported EIP-712 signed operation types.\n *\n * @remarks\n * Each operation type corresponds to a specific smart contract\n * function that accepts gasless transactions.\n *\n * @category Relayer\n */\nexport type SignedOperationType =\n  | \"submitAddPermission\"\n  | \"submitPermissionRevoke\"\n  | \"submitTrustServer\"\n  | \"submitAddAndTrustServer\"\n  | \"submitUntrustServer\"\n  | \"submitAddServerFilesAndPermissions\";\n// | \"submitRegisterGrantee\"; // TODO: Add when contract supports registerGranteeWithSignature\n\n/**\n * Represents direct server operations that don't require blockchain signatures.\n *\n * @remarks\n * Direct requests handle auxiliary operations like file uploads and grant storage.\n * These operations may still result in blockchain transactions but don't require\n * user signatures for gasless submission.\n *\n * @category Relayer\n */\nexport type DirectRelayerRequest =\n  | {\n      type: \"direct\";\n      operation: \"submitFileAddition\";\n      params: {\n        url: string;\n        userAddress: Address;\n      };\n    }\n  | {\n      type: \"direct\";\n      operation: \"submitFileAdditionWithPermissions\";\n      params: {\n        url: string;\n        userAddress: Address;\n        permissions: Array<{ account: Address; key: string }>;\n      };\n    }\n  | {\n      type: \"direct\";\n      operation: \"submitFileAdditionComplete\";\n      params: {\n        url: string;\n        userAddress: Address;\n        permissions: Array<{ account: Address; key: string }>;\n        schemaId: number;\n        ownerAddress?: Address;\n      };\n    }\n  | {\n      type: \"direct\";\n      operation: \"storeGrantFile\";\n      params: GrantFile;\n    }\n  | {\n      type: \"direct\";\n      operation: \"submitRegisterGrantee\";\n      params: {\n        owner: Address;\n        granteeAddress: Address;\n        publicKey: string;\n      };\n    };\n\n/**\n * Context for transaction operations to enable proper event parsing.\n *\n * @remarks\n * This context is preserved in relayer responses to enable client-side\n * event parsing without requiring manual reconstruction of transaction details.\n *\n * @category Relayer\n */\nexport interface TransactionContext {\n  /** The contract that was called */\n  contract: Contract;\n  /** The function that was called on the contract */\n  fn: Fn<Contract>;\n  /** The address that initiated the transaction */\n  from: Address;\n}\n\n/**\n * Provides type-safe responses for all relayer operations.\n *\n * @remarks\n * The discriminated union ensures proper error handling and result typing.\n * Check the `type` field to determine success or failure before accessing results.\n * The new async pattern returns pending operations with operationIds for polling.\n *\n * Transaction responses include optional context to enable client-side event parsing\n * through the enhanced response pattern.\n *\n * @category Relayer\n */\nexport type UnifiedRelayerResponse =\n  | {\n      type: \"pending\";\n      operationId: string;\n    }\n  | {\n      type: \"submitted\";\n      hash: Hash;\n      /** Optional context for client-side event parsing and enhanced responses */\n      context?: TransactionContext;\n    }\n  | {\n      type: \"confirmed\";\n      hash: Hash;\n      // Receipt is optional; a performance hint for the client SDK's polling logic.\n      receipt?: TransactionReceipt;\n    }\n  | {\n      type: \"signed\";\n      hash: Hash;\n      /** Optional context for client-side event parsing and enhanced responses */\n      context?: TransactionContext;\n    }\n  | {\n      /** Non-transactional operations that complete immediately (e.g., IPFS uploads, file info) */\n      type: \"direct\";\n      /** The result data from the operation, structure depends on the specific operation */\n      result: unknown;\n    }\n  | {\n      type: \"error\";\n      error: string;\n    };\n\n/**\n * Simplified relayer configuration.\n * Can be a URL string for convenience, or a callback for full control.\n *\n * @category Configuration\n * @example\n * ```typescript\n * // Option 1: Simple URL (SDK handles the transport)\n * const vana = Vana({\n *   walletClient,\n *   relayer: '/api/relay'\n * });\n *\n * // Option 2: Full control with callback\n * const vana = Vana({\n *   walletClient,\n *   relayer: async (request) => {\n *     const response = await fetch('/api/relay', {\n *       method: 'POST',\n *       body: JSON.stringify(request)\n *     });\n *     return response.json();\n *   }\n * });\n * ```\n */\nexport type RelayerConfig =\n  | string\n  | ((request: UnifiedRelayerRequest) => Promise<UnifiedRelayerResponse>);\n\n/**\n * Simplified relayer callbacks interface (v2).\n * A single callback handles all relayer operations.\n *\n * @category Configuration\n * @example\n * ```typescript\n * const relayerCallbacks: RelayerCallbacksV2 = {\n *   submit: async (request) => {\n *     // Send to your server endpoint\n *     const response = await fetch('/api/relay', {\n *       method: 'POST',\n *       headers: { 'Content-Type': 'application/json' },\n *       body: JSON.stringify(request)\n *     });\n *     return response.json();\n *   }\n * };\n * ```\n */\nexport interface RelayerCallbacksV2 {\n  /**\n   * Submits any relayer operation to the server.\n   *\n   * @remarks\n   * This single callback handles all operations:\n   * - EIP-712 signed operations (permissions, server trust, etc.)\n   * - Direct operations (file additions, grant storage)\n   *\n   * On your server, pass the entire request object to the SDK's\n   * `handleRelayerOperation` helper function.\n   *\n   * @param request - The unified request object.\n   *   Check `type` field to determine operation variant.\n   * @returns Promise resolving to operation-specific response\n   *\n   * @example\n   * ```typescript\n   * async submit(request) {\n   *   const response = await fetch('/api/relay', {\n   *     method: 'POST',\n   *     body: JSON.stringify(request)\n   *   });\n   *   return response.json();\n   * }\n   * ```\n   */\n  submit: (request: UnifiedRelayerRequest) => Promise<UnifiedRelayerResponse>;\n}\n"],"mappings":";;;;;;;;;;;;;;AAAA;AAAA;","names":[]}