@human.tech/waap-sdk 2.2.0-staging-96d8fa → 2.2.0-staging-ac3dde

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # @human.tech/waap-sdk
 
-## 2.2.0-staging-96d8fa
+## 2.2.0-staging-ac3dde
 
 ### Minor Changes
 

package/dist/index.d.mts

@@ -272,12 +272,27 @@ declare const rpcMethodRequiresUI: (method: JSON_RPC_METHOD) => boolean;
  */
 declare function handleWalletRequestAndResponse(args: RequestArguments, interactionRequired: boolean, walletMessageManager: WalletMessageManager, internalProviderEventEmitter: EventEmitter, silkOptions?: WaaPRequestOptions): Promise<any>;
 //#endregion
-//#region ../waap-core/dist/index-DFYoP6c7.d.ts
+//#region ../waap-core/dist/index-DrVqylZO.d.ts
 /** Canonical chain identifier signed into a permission token. */
 type PermissionTokenChain = `evm:${number}` | `sui:${string}` | `solana:${string}`;
 //#endregion
 //#region src/permission-token/scope.d.ts
 type HexBytes = `0x${string}`;
+/**
+ * Wildcarding is not uniform across chains, because the identifiers are not
+ * comparable. `target:*` — any supported action on a target — is available
+ * everywhere. Beyond that:
+ *
+ * - **Sui** supports `module::*`, because a Move module is a named namespace
+ *   and "every function in it" is a set the user can reason about.
+ * - **EVM** has no partial wildcard. A selector is four bytes of a hash with no
+ *   structure to generalize over, so a scope names one method or the whole
+ *   contract.
+ * - **Solana** has no explicit wildcard, but
+ *   {@link permissionTokenSolanaDiscriminator} is already a prefix match — a
+ *   discriminator authorizes every instruction whose data starts with it.
+ *   {@link permissionTokenSolanaInstruction} is the exact-payload form.
+ */
 /** A plain address authorizes only value or asset delivery to that recipient. */
 declare function permissionTokenRecipient(chain: PermissionTokenChain, address: string): string;
 /** Authorize every directly-invoked function on one EVM contract. */

package/dist/index.d.ts

@@ -272,12 +272,27 @@ declare const rpcMethodRequiresUI: (method: JSON_RPC_METHOD) => boolean;
  */
 declare function handleWalletRequestAndResponse(args: RequestArguments, interactionRequired: boolean, walletMessageManager: WalletMessageManager, internalProviderEventEmitter: EventEmitter, silkOptions?: WaaPRequestOptions): Promise<any>;
 //#endregion
-//#region ../waap-core/dist/index-DFYoP6c7.d.ts
+//#region ../waap-core/dist/index-DrVqylZO.d.ts
 /** Canonical chain identifier signed into a permission token. */
 type PermissionTokenChain = `evm:${number}` | `sui:${string}` | `solana:${string}`;
 //#endregion
 //#region src/permission-token/scope.d.ts
 type HexBytes = `0x${string}`;
+/**
+ * Wildcarding is not uniform across chains, because the identifiers are not
+ * comparable. `target:*` — any supported action on a target — is available
+ * everywhere. Beyond that:
+ *
+ * - **Sui** supports `module::*`, because a Move module is a named namespace
+ *   and "every function in it" is a set the user can reason about.
+ * - **EVM** has no partial wildcard. A selector is four bytes of a hash with no
+ *   structure to generalize over, so a scope names one method or the whole
+ *   contract.
+ * - **Solana** has no explicit wildcard, but
+ *   {@link permissionTokenSolanaDiscriminator} is already a prefix match — a
+ *   discriminator authorizes every instruction whose data starts with it.
+ *   {@link permissionTokenSolanaInstruction} is the exact-payload form.
+ */
 /** A plain address authorizes only value or asset delivery to that recipient. */
 declare function permissionTokenRecipient(chain: PermissionTokenChain, address: string): string;
 /** Authorize every directly-invoked function on one EVM contract. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@human.tech/waap-sdk",
-  "version": "2.2.0-staging-96d8fa",
+  "version": "2.2.0-staging-ac3dde",
   "description": "SDK for interacting with WaaP",
   "types": "./dist/index.d.ts",
   "exports": {