kokio-sdk 3.0.0 → 3.0.2

package/README.md

@@ -39,7 +39,8 @@ is ever held in the app.
 
 You will need:
 
-- a viem `WalletClient` connected to the target chain,
+- a viem `WalletClient` connected to the target chain, carrying an `account`
+  and an explicit RPC URL (see the note under the example),
 - the passkey `credentialId` and `rpId` registered for the device,
 - a Pimlico API key and a gas policy id (used by the bundler and paymaster).
 
@@ -48,7 +49,11 @@ import { Kokio } from "kokio-sdk";
 import { createWalletClient, http } from "viem";
 import { baseSepolia } from "viem/chains";
 
-const walletClient = createWalletClient({ chain: baseSepolia, transport: http() });
+const walletClient = createWalletClient({
+  account: knownAddress,
+  chain: baseSepolia,
+  transport: http(rpcUrl),
+});
 
 const kokio = new Kokio(
   walletClient,
@@ -81,9 +86,20 @@ const session = new Kokio(
 
 // 4. Send a user operation. The passkey signs it on the device.
 const hash = await session.deviceWallet!.toggleAccessToFunds(eSIMWalletAddress, true);
-await smartAccountClient.waitForUserOperationTransaction({ hash });
+const receipt = await smartAccountClient.waitForUserOperationReceipt({ hash });
+if (!receipt.success) throw new Error("operation reverted");
 ```
 
+Two things about the wallet client. It has to carry an `account`:
+`getSmartWallet` refuses a client without one, though it never asks it for a
+signature, since the passkey signs everything. And give `http()` a real RPC
+URL, because the SDK reads `client.transport.url` to build the public client
+it uses for contract reads.
+
+Check `receipt.success`. An operation whose calls revert is still mined and
+still returns a receipt, so the await resolving is not on its own proof the
+write landed. `receipt.receipt.transactionHash` is the onchain transaction.
+
 The contract surfaces (`deviceWallet`, `eSIMWallet`, `deviceWalletFactory`,
 `eSIMWalletFactory`, `registry`, `paymentAdapter`, `P256Verifier`) are only
 present once a `smartAccountClient` is supplied, which is why the example

package/dist/esm/types-export.js

@@ -1 +1 @@
-export { Settlement } from './types';
+export { Settlement } from './types.js';

package/dist/types/interface/eSIMWalletClass.d.ts

@@ -1,5 +1,5 @@
 import { Address, Hex } from "viem";
-import { DataBundleDetails } from "../types";
+import { DataBundleDetails } from "../types.js";
 import { KokioSmartAccountClient } from "../types.js";
 export declare class ESIMWalletSubPackage {
     client: KokioSmartAccountClient;

package/dist/types/types-export.d.ts

@@ -1,2 +1,3 @@
-export type { P256Key, Call, WebAuthnSignature, P256Credential, DataBundleDetails, Asset, SignedRequest, KokioSmartAccount, KokioSmartAccountClient, OwnerCall, OperationOptions, ScheduledOperation, ScheduledBatchOperation } from './types';
-export { Settlement } from './types';
+export type { P256Key, Call, WebAuthnSignature, P256Credential, DataBundleDetails, Asset, SignedRequest, KokioSmartAccount, KokioSmartAccountClient, OwnerCall, OperationOptions, ScheduledOperation, ScheduledBatchOperation, LazyDeploymentBatch, LazyDeployment, LazyHistoryBatch, LazyHistoryCopy } from './types.js';
+export type { KokioConstants } from './interface/constantsClass.js';
+export { Settlement } from './types.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kokio-sdk",
-  "version": "3.0.0",
+  "version": "3.0.2",
   "description": "",
   "type": "module",
   "main": "./dist/esm/config.js",