@walletmesh/aztec-rpc-wallet 0.3.1 → 0.4.1

package/docs/type-aliases/AztecChainId.md

@@ -1,4 +1,4 @@
-[**@walletmesh/aztec-rpc-wallet v0.3.1**](../README.md)
+[**@walletmesh/aztec-rpc-wallet v0.4.1**](../README.md)
 
 ***
 
@@ -6,6 +6,19 @@
 
 # Type Alias: AztecChainId
 
-> **AztecChainId**: `` `aztec:${string}` ``
+> **AztecChainId** = `` `aztec:${string}` ``
 
-Defined in: [aztec/rpc-wallet/src/types.ts:296](https://github.com/WalletMesh/walletmesh-packages/blob/65bc501d5bed45d0e6d444f53e29595da551d59e/aztec/rpc-wallet/src/types.ts#L296)
+Defined in: [aztec/rpc-wallet/src/types.ts:64](https://github.com/WalletMesh/walletmesh-packages/blob/c22c9775e630bf48780e547c01c8f5442dc5b36c/aztec/rpc-wallet/src/types.ts#L64)
+
+Type-safe Aztec chain ID format following the CAIP-2 standard.
+
+Format: `aztec:{reference}` where reference is typically:
+- "mainnet" for the main Aztec network
+- A numeric chain ID for test networks (e.g., "31337" for local development)
+
+## Example
+
+```typescript
+const mainnetChainId: AztecChainId = "aztec:mainnet";
+const localChainId: AztecChainId = "aztec:31337";
+```

package/docs/variables/ALL_AZTEC_METHODS.md

@@ -0,0 +1,20 @@
+[**@walletmesh/aztec-rpc-wallet v0.4.1**](../README.md)
+
+***
+
+[@walletmesh/aztec-rpc-wallet](../globals.md) / ALL\_AZTEC\_METHODS
+
+# Variable: ALL\_AZTEC\_METHODS
+
+> `const` **ALL\_AZTEC\_METHODS**: readonly \[`"aztec_getAddress"`, `"aztec_getCompleteAddress"`, `"aztec_getChainId"`, `"aztec_getVersion"`, `"aztec_sendTx"`, `"aztec_getTxReceipt"`, `"aztec_simulateTx"`, `"aztec_getNodeInfo"`, `"aztec_getBlockNumber"`, `"aztec_getCurrentBaseFees"`, `"aztec_registerSender"`, `"aztec_getSenders"`, `"aztec_removeSender"`, `"aztec_registerContract"`, `"aztec_registerContractClass"`, `"aztec_getContractMetadata"`, `"aztec_getContractClassMetadata"`, `"aztec_proveTx"`, `"aztec_profileTx"`, `"aztec_simulateUtility"`, `"aztec_getPrivateEvents"`, `"aztec_getPublicEvents"`, `"aztec_getPXEInfo"`, `"aztec_getBlock"`, `"aztec_createAuthWit"`, `"aztec_wmDeployContract"`, `"aztec_wmExecuteTx"`, `"aztec_wmSimulateTx"`\]
+
+Defined in: [aztec/rpc-wallet/src/client/helpers.ts:17](https://github.com/WalletMesh/walletmesh-packages/blob/c22c9775e630bf48780e547c01c8f5442dc5b36c/aztec/rpc-wallet/src/client/helpers.ts#L17)
+
+A comprehensive list of all JSON-RPC methods supported by the Aztec RPC wallet.
+This array includes standard Aztec wallet methods as well as WalletMesh-specific extensions (prefixed with `wm_`).
+It can be used when establishing a connection to request permissions for all available functionalities.
+
+## See
+
+ - [AztecWalletMethodMap](../interfaces/AztecWalletMethodMap.md) for detailed type information on each method.
+ - [connectAztec](../functions/connectAztec.md) and connectAztecWithWallet which use this list by default.

package/docs/variables/AztecWalletErrorMap.md

@@ -1,4 +1,4 @@
-[**@walletmesh/aztec-rpc-wallet v0.3.1**](../README.md)
+[**@walletmesh/aztec-rpc-wallet v0.4.1**](../README.md)
 
 ***
 
@@ -6,8 +6,13 @@
 
 # Variable: AztecWalletErrorMap
 
-> `const` **AztecWalletErrorMap**: `Record`\<`AztecWalletErrorType`, \{ `code`: `number`; `message`: `string`; \}\>
+> `const` `readonly` **AztecWalletErrorMap**: `Record`\<`AztecWalletErrorType`, \{ `code`: `number`; `message`: `string`; \}\>
 
-Defined in: [aztec/rpc-wallet/src/errors.ts:37](https://github.com/WalletMesh/walletmesh-packages/blob/65bc501d5bed45d0e6d444f53e29595da551d59e/aztec/rpc-wallet/src/errors.ts#L37)
+Defined in: [aztec/rpc-wallet/src/errors.ts:59](https://github.com/WalletMesh/walletmesh-packages/blob/c22c9775e630bf48780e547c01c8f5442dc5b36c/aztec/rpc-wallet/src/errors.ts#L59)
 
-Map of error codes and messages for Aztec Wallet RPC errors.
+A map associating each AztecWalletErrorType with a specific JSON-RPC error code
+and a human-readable message. This map is used by the [AztecWalletError](../classes/AztecWalletError.md) class
+to construct standardized error objects.
+
+The error codes are chosen from the range typically reserved for server-defined errors
+in JSON-RPC (e.g., -32000 to -32099).

package/docs/variables/AztecWalletSerializer.md

@@ -0,0 +1,45 @@
+[**@walletmesh/aztec-rpc-wallet v0.4.1**](../README.md)
+
+***
+
+[@walletmesh/aztec-rpc-wallet](../globals.md) / AztecWalletSerializer
+
+# Variable: AztecWalletSerializer
+
+> `const` **AztecWalletSerializer**: [`JSONRPCSerializer`](https://github.com/WalletMesh/walletmesh-packages/tree/main/core/jsonrpc/docs/interfaces/JSONRPCSerializer.md)\<`JSONRPCParams`, `unknown`\>
+
+Defined in: [aztec/rpc-wallet/src/wallet/serializers.ts:265](https://github.com/WalletMesh/walletmesh-packages/blob/c22c9775e630bf48780e547c01c8f5442dc5b36c/aztec/rpc-wallet/src/wallet/serializers.ts#L265)
+
+A comprehensive [JSONRPCSerializer](https://github.com/WalletMesh/walletmesh-packages/tree/main/core/jsonrpc/docs/interfaces/JSONRPCSerializer.md) for all Aztec wallet methods.
+
+This serializer handles both parameters and results:
+
+**Parameters (`params`):**
+ - `serialize`: Currently uses a fallback mechanism (`createFallbackSerializer`) which
+   stringifies parameters using `jsonStringify`. This assumes the client-side
+   (e.g., [AztecDappWallet](../classes/AztecDappWallet.md) via [AztecRouterProvider](../classes/AztecRouterProvider.md)) sends parameters
+   already in a format that can be processed by the `deserialize` logic after
+   basic JSON parsing.
+ - `deserialize`: Contains detailed, method-specific logic to parse the JSON string
+   of incoming parameters and reconstruct them into their correct Aztec types
+   (e.g., `AztecAddress.fromString`, `TxExecutionRequest.schema.parse`). It uses
+   Zod schemas and helper functions (`ensureParam`, `getOptionalParam`) for
+   validation and type conversion.
+
+**Results (`result`):**
+ - `serialize`: For each method, it attempts to use a specific serializer defined in
+   `RESULT_SERIALIZERS`. These typically use `jsonStringify` with a Zod schema
+   for the specific result type (e.g., `AztecAddress.schema`, `TxHash.schema`).
+   If no specific serializer is found, it uses `createFallbackSerializer`.
+ - `deserialize`: Similar to result serialization, it uses `RESULT_SERIALIZERS`
+   to find a method-specific deserializer, often employing `jsonParseWithSchema`
+   with the appropriate Zod schema. If no specific deserializer exists, it may
+   return the raw data or attempt a simple JSON parse.
+
+This serializer is crucial for ensuring that complex Aztec objects maintain their
+type integrity and structure when transmitted over JSON-RPC.
+
+## See
+
+ - [AztecWalletMethodMap](../interfaces/AztecWalletMethodMap.md) for the definitions of methods, params, and results.
+ - [JSONRPCSerializer](https://github.com/WalletMesh/walletmesh-packages/tree/main/core/jsonrpc/docs/interfaces/JSONRPCSerializer.md) for the interface it implements.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@walletmesh/aztec-rpc-wallet",
-  "version": "0.3.1",
+  "version": "0.4.1",
   "description": "",
   "type": "module",
   "main": "dist/index.js",
@@ -17,16 +17,18 @@
   "author": "",
   "license": "Apache-2.0",
   "devDependencies": {
-    "typedoc": "^0.27.2",
-    "typedoc-plugin-markdown": "^4.3.1"
+    "typedoc": "^0.28.4",
+    "typedoc-plugin-markdown": "^4.6.3"
   },
   "dependencies": {
-    "@aztec/aztec.js": "0.76.2",
-    "@aztec/circuit-types": "0.76.2",
-    "@aztec/circuits.js": "0.76.2",
-    "@aztec/foundation": "0.76.2",
-    "@walletmesh/jsonrpc": "0.4.0",
-    "@walletmesh/router": "0.4.0"
+    "@aztec/aztec.js": "0.87.8",
+    "@aztec/blob-lib": "0.87.8",
+    "@aztec/entrypoints": "0.87.8",
+    "@aztec/foundation": "0.87.8",
+    "@aztec/stdlib": "0.87.8",
+    "zod": "^3.25.67",
+    "@walletmesh/router": "^0.5.0",
+    "@walletmesh/jsonrpc": "^0.5.0"
   },
   "scripts": {
     "build": "tsc --build tsconfig.build.json",