@mysten/docs 0.1.18 → 0.1.19

package/dist/dapp-kit/react/hooks/use-current-wallet.md

@@ -1,11 +1,11 @@
 # useCurrentWallet
 
-> React hook to get the current wallet connection
+> React hook to get the currently connected wallet in a Sui dApp.
 
 The `useCurrentWallet` hook provides access to the currently connected wallet.
 
 > **Warning:** All dApp Kit hooks must be used within components that are descendants of
-> [DAppKitProvider](../dapp-kit-provider). Using them outside will result in an error.
+> [`DAppKitProvider`](../dapp-kit-provider). Using them outside will result in an error.
 
 ## Usage
 
@@ -29,7 +29,7 @@ The `useCurrentWallet` hook provides access to the currently connected wallet.
 }
 ```
 
-## Return Value
+## Return value
 
 ```tsx
 UiWallet | null;

package/dist/dapp-kit/react/hooks/use-dapp-kit.md

@@ -1,12 +1,12 @@
 # useDAppKit
 
-> React hook to access the full dApp Kit instance
+> React hook to access the full dApp Kit instance for calling actions directly.
 
 The `useDAppKit` hook provides direct access to the dApp Kit instance within React components,
 enabling you to call actions and access the underlying functionality.
 
 > **Warning:** All dApp Kit hooks must be used within components that are descendants of
-> [DAppKitProvider](../dapp-kit-provider). Using them outside will result in an error.
+> [`DAppKitProvider`](../dapp-kit-provider). Using them outside will result in an error.
 
 ## Usage
 
@@ -27,7 +27,7 @@ enabling you to call actions and access the underlying functionality.
 }
 ```
 
-## Return Value
+## Return value
 
 ```ts
 {
@@ -54,7 +54,7 @@ enabling you to call actions and access the underlying functionality.
 
 ## Examples
 
-### Transaction Execution
+### Transaction execution
 
 ```tsx
 
@@ -83,7 +83,7 @@ enabling you to call actions and access the underlying functionality.
 }
 ```
 
-### Subscribing to State Changes
+### Subscribing to state changes
 
 ```tsx
 

package/dist/dapp-kit/react/hooks/use-wallet-connection.md

@@ -1,12 +1,12 @@
 # useWalletConnection
 
-> React hook to manage wallet connection and disconnection
+> React hook to manage wallet connection status and information in a Sui dApp.
 
 The `useWalletConnection` hook provides access to the current wallet connection status and
 information.
 
 > **Warning:** All dApp Kit hooks must be used within components that are descendants of
-> [DAppKitProvider](../dapp-kit-provider). Using them outside will result in an error.
+> [`DAppKitProvider`](../dapp-kit-provider). Using them outside will result in an error.
 
 ## Usage
 
@@ -32,7 +32,7 @@ information.
 }
 ```
 
-## Return Value
+## Return value
 
 ```tsx
 {

package/dist/dapp-kit/react/hooks/use-wallets.md

@@ -1,11 +1,11 @@
 # useWallets
 
-> React hook to list available wallets
+> React hook to list all available Sui wallets detected by dApp Kit.
 
 The `useWallets` hook provides access to all available wallets.
 
 > **Warning:** All dApp Kit hooks must be used within components that are descendants of
-> [DAppKitProvider](../dapp-kit-provider). Using them outside will result in an error.
+> [`DAppKitProvider`](../dapp-kit-provider). Using them outside will result in an error.
 
 ## Usage
 
@@ -26,7 +26,7 @@ The `useWallets` hook provides access to all available wallets.
 }
 ```
 
-## Return Value
+## Return value
 
 ```tsx
 UiWallet[]

package/dist/dapp-kit/state.md

@@ -1,21 +1,21 @@
 # State
 
-> Access and subscribe to wallet connection state in dApp Kit
+> Access and subscribe to wallet connection state in dApp Kit.
 
 The Sui dApp Kit SDK uses [nanostores](https://github.com/nanostores/nanostores) for state
 management, providing a lightweight, framework-agnostic solution that works across React, Vue,
 Vanilla JavaScript, and other frameworks.
 
-## Available Stores
+## Available stores
 
 The dApp Kit exposes four reactive stores that you can subscribe to:
 
-- **`$connection`** - Current wallet connection state
-- **`$currentNetwork`** - Currently selected network
-- **`$currentClient`** - Client instance for the current network
-- **`$wallets`** - List of available wallets
+- **`$connection`:** Current wallet connection state
+- **`$currentNetwork`:** Currently selected network
+- **`$currentClient`:** Client instance for the current network
+- **`$wallets`:** List of available wallets
 
-## Accessing Stores
+## Accessing stores
 
 All stores are available through the `dAppKit.stores` property:
 
@@ -32,7 +32,7 @@ const client = dAppKit.stores.$currentClient.get();
 const wallets = dAppKit.stores.$wallets.get();
 ```
 
-## Subscribing to State Changes
+## Subscribing to state changes
 
 Subscribe to any store to react to state changes:
 
@@ -51,9 +51,9 @@ const unsubscribe = dAppKit.stores.$connection.subscribe((connection) => {
 unsubscribe();
 ```
 
-## Store Details
+## Store details
 
-### Connection Store (`$connection`)
+### Connection store (`$connection`)
 
 Contains the current wallet connection state with status flags:
 
@@ -83,7 +83,7 @@ if (connection.isConnected && connection.wallet && connection.account) {
 }
 ```
 
-### Current Network Store (`$currentNetwork`)
+### Current network store (`$currentNetwork`)
 
 Contains the currently selected network as a string:
 
@@ -96,9 +96,9 @@ dAppKit.stores.$currentNetwork.subscribe((network) => {
 });
 ```
 
-Note: This store is read-only. Use `dAppKit.switchNetwork()` to change networks.
+This store is read-only. Use `dAppKit.switchNetwork()` to change networks.
 
-### Current Client Store (`$currentClient`)
+### Current client store (`$currentClient`)
 
 Contains the SuiClient instance for the current network:
 
@@ -111,9 +111,9 @@ const balance = await client.getBalance({
 });
 ```
 
-Note: This store automatically updates when the network changes.
+This store automatically updates when the network changes.
 
-### Wallets Store (`$wallets`)
+### Wallets store (`$wallets`)
 
 Contains the list of available wallets:
 
@@ -126,7 +126,7 @@ wallets.forEach((wallet) => {
 });
 ```
 
-## Subscribing to State Changes
+## Subscribing to state changes
 
 You can subscribe directly to stores:
 

package/dist/dapp-kit/theming.md

@@ -1,6 +1,6 @@
 # Theming
 
-> Customize the appearance of dApp Kit UI components
+> Customize the appearance of dApp Kit UI components.
 
 The dApp Kit web components use a theming system compatible with
 [shadcn/ui](https://ui.shadcn.com/docs/theming). Components are customized using CSS custom
@@ -11,47 +11,47 @@ properties (CSS variables), allowing you to match them to your application's des
 > automatically inherit your theme. You can also use [shadcn/ui's theme
 > builder](https://ui.shadcn.com/themes) to create custom themes.
 
-## CSS Custom Properties
+## CSS custom properties
 
 All dApp Kit web components support the following CSS custom properties:
 
 ### Colors
 
 These color variables follow the shadcn/ui naming convention. Colors can be defined using any valid
-CSS color format (hex, rgb, hsl, oklch, etc.).
+CSS color format (hex, rgb, hsl, oklch, and others).
 
-- **`--background`** - Background color of the component. Used as the default background for UI
+- **`--background`:** Background color of the component. Used as the default background for UI
   elements.
-- **`--foreground`** - Foreground color of the component. Used as the default text color.
-- **`--primary`** - Primary color used for interactive elements such as buttons and links.
-- **`--primary-foreground`** - Text or icon color placed on top of primary elements.
-- **`--secondary`** - Secondary color used for less prominent interactive elements.
-- **`--secondary-foreground`** - Text or icon color placed on top of secondary elements.
-- **`--border`** - Border color for UI elements.
-- **`--accent`** - Accent color used for highlights and decorative elements.
-- **`--accent-foreground`** - Text or icon color placed on top of accent elements.
-- **`--muted`** - Background color for subtle or muted UI elements (e.g., placeholders, disabled
-  states).
-- **`--muted-foreground`** - Text or icon color for muted UI elements.
-- **`--popover`** - Background color for floating elements such as popovers, dropdowns, or tooltips.
-- **`--popover-foreground`** - Text or icon color inside popover elements.
-- **`--ring`** - Color used for focus rings (visible focus indicators on interactive elements).
+- **`--foreground`:** Foreground color of the component. Used as the default text color.
+- **`--primary`:** Primary color used for interactive elements such as buttons and links.
+- **`--primary-foreground`:** Text or icon color placed on top of primary elements.
+- **`--secondary`:** Secondary color used for less prominent interactive elements.
+- **`--secondary-foreground`:** Text or icon color placed on top of secondary elements.
+- **`--border`:** Border color for UI elements.
+- **`--accent`:** Accent color used for highlights and decorative elements.
+- **`--accent-foreground`:** Text or icon color placed on top of accent elements.
+- **`--muted`:** Background color for subtle or muted UI elements (for example, placeholders and
+  disabled states).
+- **`--muted-foreground`:** Text or icon color for muted UI elements.
+- **`--popover`:** Background color for floating elements such as popovers, dropdowns, or tooltips.
+- **`--popover-foreground`:** Text or icon color inside popover elements.
+- **`--ring`:** Color used for focus rings (visible focus indicators on interactive elements).
 
 ### Typography
 
-- **`--font-sans`** - Font family used for text content.
-- **`--font-weight-medium`** - Medium font weight for text (typically used for buttons and
+- **`--font-sans`:** Font family used for text content.
+- **`--font-weight-medium`:** Medium font weight for text (typically used for buttons and
   interactive elements).
-- **`--font-weight-semibold`** - Semibold font weight for text (typically used for headings or
+- **`--font-weight-semibold`:** Semibold font weight for text (typically used for headings or
   emphasized text).
 
 ### Layout
 
-- **`--radius`** - Border radius used for UI elements.
+- **`--radius`:** Border radius used for UI elements.
 
 ## Usage
 
-### Global Theming
+### Global theming
 
 Apply custom properties to affect all dApp Kit components:
 
@@ -67,7 +67,7 @@ Apply custom properties to affect all dApp Kit components:
 }
 ```
 
-### Component-Specific Theming
+### Component-specific theming
 
 Target specific components:
 
@@ -84,7 +84,7 @@ mysten-dapp-kit-connect-modal {
 }
 ```
 
-### Dark Mode
+### Dark mode
 
 Implement dark mode by overriding the custom properties:
 
@@ -126,7 +126,7 @@ Or use a class-based approach:
 </div>
 ```
 
-## Example: Complete Theme
+## Example: complete theme
 
 Here's a complete theme example matching a custom design system:
 
@@ -159,7 +159,7 @@ Here's a complete theme example matching a custom design system:
 }
 ```
 
-## Framework Integration
+## Framework integration
 
 ### React
 

package/dist/dapp-kit/web-components/connect-button.md

@@ -1,6 +1,6 @@
 # Connect Button
 
-> Framework-agnostic web component for wallet connection
+> Framework-agnostic web component providing a complete wallet connection UI for Sui dApps.
 
 The `<mysten-dapp-kit-connect-button>` Web Component provides a complete wallet connection UI. It
 displays a "Connect Wallet" button when no wallet is connected, and shows the connected account with
@@ -10,7 +10,7 @@ a menu when a wallet is active.
 > page reload. This provides a seamless user experience but can be
 > [disabled](../dapp-kit-instance#disabling-auto-connect) if needed.
 
-## Basic Usage
+## Basic usage
 
 ### Vanilla
 
@@ -51,12 +51,12 @@ The connect button component automatically handles:
 
 ## Properties
 
-- **instance** - The dApp Kit instance
+- **instance:** The dApp Kit instance
 - **modalOptions** (optional) - Configuration options for the connect modal
-  - `filterFn` - Function to filter available wallets
-  - `sortFn` - Function to sort available wallets
+  - `filterFn`: Function to filter available wallets
+  - `sortFn`: Function to sort available wallets
 
-## Custom Button Text
+## Custom button text
 
 Use the default slot to customize the button text when not connected:
 
@@ -66,12 +66,12 @@ Use the default slot to customize the button text when not connected:
 </mysten-dapp-kit-connect-button>
 ```
 
-## Modal Integration
+## Modal integration
 
 The connect button automatically manages its own modal. You don't need to add a separate
 `<mysten-dapp-kit-connect-modal>` component when using the connect button.
 
-## Connected State
+## Connected state
 
 When a wallet is connected, the button transforms into an account menu that displays:
 
@@ -83,7 +83,7 @@ When a wallet is connected, the button transforms into an account menu that disp
   - Managing connection
   - Disconnecting
 
-## Server-Side Rendering (SSR)
+## Server-side rendering (SSR)
 
 The `<mysten-dapp-kit-connect-button>` Web Component can be only client-side rendered, as wallets
 are detected in the browser. For Next.js guide see [here](../getting-started/next-js).

package/dist/dapp-kit/web-components/connect-modal.md

@@ -1,24 +1,24 @@
 # Connect Modal
 
-> Framework-agnostic web component for wallet selection
+> Framework-agnostic web component for wallet selection and connection in Sui dApps.
 
 The `<mysten-dapp-kit-connect-modal>` Web Component provides a modal dialog for wallet connection.
 While most apps should use the [`Connect Button`](./connect-button) which includes an integrated
 modal, the standalone modal is useful for advanced scenarios requiring custom trigger mechanisms.
 
-## When to Use
+## When to use
 
 Use the standalone modal when you need:
 
-- **Custom trigger elements** - Menu items, keyboard shortcuts, or other non-button triggers
-- **Complex UI flows** - Integration into existing navigation or custom wallet management interfaces
-- **Programmatic control** - Opening the modal based on application logic or user actions
-- **Multiple triggers** - Different parts of your UI that can open the same modal
+- **Custom trigger elements:** Menu items, keyboard shortcuts, or other non-button triggers
+- **Complex UI flows:** Integration into existing navigation or custom wallet management interfaces
+- **Programmatic control:** Opening the modal based on application logic or user actions
+- **Multiple triggers:** Different parts of your UI that can open the same modal
 
 For standard wallet connection with a button, use the [Connect Button](./connect-button) component
 instead.
 
-## Basic Usage
+## Basic usage
 
 ### Vanilla
 
@@ -90,8 +90,8 @@ DApp Kit React bindings provide a [React wrapper](../react/components/connect-mo
 
 ## Properties
 
-- **instance** - The dApp Kit instance
-- **open** - Boolean to control modal visibility programmatically
+- **instance:** The dApp Kit instance
+- **open:** Boolean to control modal visibility programmatically
 - **filterFn** (optional) - Function to filter available wallets
   - Type: `(wallet: UiWallet, index: number, array: UiWallet[]) => boolean`
 - **sortFn** (optional) - Function to sort available wallets
@@ -121,11 +121,11 @@ await modal?.close('user-cancelled');
 
 The modal fires several events during its lifecycle:
 
-- **open** - Fired before the modal opens (cancelable)
-- **opened** - Fired after the modal has fully opened
-- **close** - Fired before the modal closes (cancelable)
-- **closed** - Fired after the modal has fully closed
-- **cancel** - Fired when clicking backdrop or pressing Escape (cancelable)
+- **open:** Fired before the modal opens (cancelable)
+- **opened:** Fired after the modal has fully opened
+- **close:** Fired before the modal closes (cancelable)
+- **closed:** Fired after the modal has fully closed
+- **cancel:** Fired when clicking backdrop or pressing Escape (cancelable)
 
 ```js
 const modal = document.querySelector('mysten-dapp-kit-connect-modal');
@@ -151,7 +151,7 @@ modal?.addEventListener('cancel', (event) => {
 
 ## Examples
 
-### Programmatic Control
+### Programmatic control
 
 ```js
 const modal = document.querySelector('mysten-dapp-kit-connect-modal');
@@ -171,7 +171,7 @@ async function performAction() {
 }
 ```
 
-## Server-Side Rendering (SSR)
+## Server-side rendering (SSR)
 
 The `<mysten-dapp-kit-connect-modal>` Web Component can be only client-side rendered, as wallets are
 detected in the browser. For Next.js guide see [here](../getting-started/next-js).

package/dist/kiosk/advanced-examples.md

@@ -1,6 +1,6 @@
 # Advanced Examples
 
-> Advanced Kiosk SDK usage patterns and examples
+> Advanced Kiosk SDK usage patterns and code examples for complex scenarios.
 
 # Some extended examples
 

package/dist/kiosk/from-v1.md

@@ -1,6 +1,6 @@
 # Migrating from Kiosk SDK V1
 
-> Migrate from Kiosk SDK v1 to the current version
+> Migrate from Kiosk SDK v1 to the current version with the builder-pattern API.
 
 The original version of Kiosk SDK provided basic experimentation with the Kiosk API. The new version
 of the SDK (0.7+) provides a more robust experience for building kiosk/transfer policy transactions.

package/dist/kiosk/index.md

@@ -1,9 +1,9 @@
 # Kiosk SDK
 
-> TypeScript SDK for interacting with Sui Kiosk on-chain commerce
+> TypeScript SDK for interacting with Sui Kiosk onchain commerce.
 
-Kiosk SDK is a tool to interact with Sui/Mysten Kiosk. You can use it to query kiosk related data,
-build transactions to interact, and extend Kiosk to support custom rules.
+Kiosk SDK is a tool to interact with Sui and Mysten Kiosk. You can use it to query kiosk related
+data, build transactions to interact, and extend Kiosk to support custom rules.
 
 ## Installation
 
@@ -14,9 +14,9 @@ npm i @mysten/kiosk
 ## About
 
 The Kiosk SDK exports a client extension that integrates with Sui clients. Add it to your client
-using `$extend(kiosk())` to access kiosk functionality via `client.kiosk`.
+using `$extend(kiosk())` to access kiosk functionality through `client.kiosk`.
 
-> **Note:** The Kiosk SDK requires `SuiJsonRpcClient` or `SuiGraphQLClient`. It does not work with
+> The Kiosk SDK requires `SuiJsonRpcClient` or `SuiGraphQLClient`. It does not work with
 > `SuiGrpcClient` because it uses event queries that are not available in gRPC.
 
 - [Read more about setting up the Kiosk client extension](/kiosk/kiosk-client/introduction)

package/dist/kiosk/kiosk-client/introduction.md

@@ -1,13 +1,13 @@
 # Kiosk Client
 
-> Introduction to the KioskClient for querying and managing kiosks
+> Introduction to the KioskClient extension for querying and managing kiosks on Sui.
 
 The Kiosk SDK exports a client extension that provides all Kiosk functionality.
 
-> We recommend you keep only one client instance throughout your dApp or script. For example, in
+> We recommend you keep only one client instance throughout your app or script. For example, in
 > React, you'd use a context to provide the client.
 
-> **Note:** The Kiosk SDK requires `SuiJsonRpcClient` or `SuiGraphQLClient`. It does not work with
+> The Kiosk SDK requires `SuiJsonRpcClient` or `SuiGraphQLClient`. It does not work with
 > `SuiGrpcClient` because it uses event queries that are not available in gRPC.
 
 ## Setting up the kiosk extension
@@ -15,8 +15,8 @@ The Kiosk SDK exports a client extension that provides all Kiosk functionality.
 Add the kiosk extension to your Sui client using `$extend()`. The extension currently supports
 `mainnet` and `testnet`. See the next section for usage on other networks.
 
-_Mysten Kiosk rules and extensions are not supported in Devnet due to network wipes (that would
-require constantly changing the package IDs)._
+Mysten Kiosk rules and extensions are not supported in Devnet due to network wipes (that would
+require constantly changing the package IDs).
 
 ```typescript
 
@@ -29,7 +29,7 @@ const client = new SuiJsonRpcClient({
 const { kioskOwnerCaps } = await client.kiosk.getOwnedKiosks({ address: '0x...' });
 ```
 
-### Using the kiosk extension on devnet or localnet
+### Using the kiosk extension on Devnet or Localnet
 
 To use all the functionality of Kiosk SDK outside of `mainnet` and `testnet`, pass the `packageIds`
 for the rules and extensions you want to use.

package/dist/kiosk/kiosk-client/kiosk-transaction/examples.md

@@ -1,12 +1,12 @@
 # Examples
 
-> Kiosk transaction code examples
+> Practical code examples for kiosk transactions including minting, listing, and purchasing.
 
-The following dApp-focused examples demonstrate how to use the SDK to interact with Kiosk.
+The following app-focused examples demonstrate how to use the SDK to interact with Kiosk.
 
 ## Minting into Kiosk example
 
-For every scenario using Kiosk in dApps, the user who has connected their wallet either has at least
+For every scenario using Kiosk in apps, the user who has connected their wallet either has at least
 one kiosk already or you must create it for them.
 
 The SDK supports the scenario of `silently` creating the kiosk, as part of our Programmable

package/dist/kiosk/kiosk-client/kiosk-transaction/kiosk-transaction.md

@@ -1,6 +1,6 @@
 # KioskTransaction
 
-> Build kiosk transactions for listing, purchasing, and managing items
+> Build kiosk transactions for listing, purchasing, and managing items on Sui.
 
 `KioskTransaction` is the client to build transactions that involve Kiosk. It's used similar to
 `Transaction`, and helps in building a transaction.

package/dist/kiosk/kiosk-client/kiosk-transaction/managing.md

@@ -1,6 +1,6 @@
 # Managing Owned Kiosk
 
-> Manage kiosk items: place, list, delist, and withdraw
+> Manage kiosk items by placing, listing, delisting, and withdrawing using the Kiosk SDK.
 
 The kiosk extension (`client.kiosk`) helps in managing a kiosk.
 
@@ -9,7 +9,7 @@ create a `KioskTransaction`.
 
 ## Available functions
 
-### take
+### `take`
 
 Removes an item from the Kiosk and returns a `TransactionArgument` to use it in a different
 Programmable Transaction Block (PTB) call.
@@ -37,7 +37,7 @@ kioskTx.finalize();
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### transfer
+### `transfer`
 
 Similar to `take`, but transfers the item to an address internally.
 
@@ -61,7 +61,7 @@ kioskTx
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### place
+### `place`
 
 Places an item in the kiosk.
 
@@ -83,7 +83,7 @@ kioskTx
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### list
+### `list`
 
 Lists an item for sale (the item must be in the kiosk).
 
@@ -106,7 +106,7 @@ kioskTx
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### placeAndList
+### `placeAndList`
 
 List an item for sale by first placing it in the kiosk (places the item and lists it for sale). It's
 a short hand for `place()` and `list()`.
@@ -130,7 +130,7 @@ kioskTx
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### delist
+### `delist`
 
 Removes the listing, keeping the item placed in the kiosk.
 
@@ -152,7 +152,7 @@ kioskTx
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### withdraw
+### `withdraw`
 
 Withdraw (all or specific amount) from a kiosk.
 
@@ -168,7 +168,7 @@ kioskTx.withdraw('address_to_transfer_funds', 100000n).finalize();
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### borrowTx (callback)
+### `borrowTx` (callback)
 
 Borrows an item from a kiosk. This function follows the `callback` approach, similar to the
 ownerCap. The return of the item happens automatically after the execution of the callback.
@@ -199,10 +199,10 @@ kioskTx
 await signAndExecuteTransaction({ tx: tx });
 ```
 
-### borrow / return
+### `borrow` / `return`
 
 Similar to `borrowTx`, borrows an item from the kiosk, but returns two transaction arguments: `item`
-& `promise`. You can use the `item` in your PTBs, but you must always call the `return()` function
+and `promise`. You can use the `item` in your PTBs, but you must always call the `return()` function
 with the `item` and the `Promise`.
 
 ```typescript

package/dist/kiosk/kiosk-client/kiosk-transaction/purchasing.md

@@ -1,6 +1,6 @@
 # Purchasing from a kiosk
 
-> Purchase items from kiosks with transfer policy resolution
+> Purchase items from kiosks with automatic transfer policy rule resolution.
 
 One of the base functionalities of the SDK is a seamless purchasing flow, allowing for ease of rules
 resolving (hiding away the calls). The SDK supports all four rules by default, and works for

package/dist/kiosk/kiosk-client/querying.md

@@ -1,6 +1,6 @@
 # Querying
 
-> Query kiosk contents, items, and transfer policies
+> Query kiosk contents, owned kiosks, items, and transfer policies using the Kiosk SDK.
 
 You can use `client.kiosk` to query kiosk data. It helps you get owned kiosks for an address, as
 well as fetching all the contents of a specified kiosk.