@opendatalabs/vana-sdk 2.2.1 → 2.2.3-canary.046cb7e

package/dist/config/features.cjs

@@ -21,30 +21,7 @@ __export(features_exports, {
   features: () => features
 });
 module.exports = __toCommonJS(features_exports);
-const features = {
-  /**
-   * Use custom ECIES implementation instead of eccrypto
-   *
-   * When false (default): Uses the original eccrypto/eccrypto-js libraries for stability
-   * When true: Uses the custom platform-specific ECIES implementation
-   *
-   * Enable by setting environment variable: VANA_USE_CUSTOM_ECIES=true
-   *
-   * @example
-   * ```bash
-   * # Use eccrypto-js (default)
-   * VANA_USE_CUSTOM_ECIES=false npm run your-app
-   *
-   * # Use custom ECIES implementation
-   * VANA_USE_CUSTOM_ECIES=true npm run your-app
-   * ```
-   *
-   * @returns Whether to use custom ECIES implementation
-   */
-  get useCustomECIES() {
-    return process.env.VANA_USE_CUSTOM_ECIES === "true";
-  }
-};
+const features = {};
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {
   features

package/dist/config/features.cjs.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/config/features.ts"],"sourcesContent":["/**\n * Feature flags for the Vana SDK\n *\n * @remarks\n * This module controls feature toggles that allow switching between different\n * implementations or enabling experimental features.\n *\n * The getter pattern is used to allow dynamic evaluation of environment variables,\n * which is necessary for tests to override the default before modules are loaded.\n *\n * ## Dual-Mode ECIES Support\n *\n * The SDK supports two encryption implementations:\n *\n * 1. **eccrypto-js** (Default)\n *    - Pure JavaScript implementation\n *    - Works everywhere (Node.js and browsers)\n *    - No native dependencies\n *    - Good performance for most use cases\n *\n * 2. **Custom ECIES** (Opt-in)\n *    - Uses native `secp256k1` module in Node.js for optimal performance\n *    - Uses `@noble/secp256k1` in browsers (pure JS)\n *    - Slightly faster in Node.js environments\n *    - Currently used by tests to ensure compatibility\n *\n * ### Architecture Notes\n * - Browser builds: Never reference native `secp256k1`, use `@noble/secp256k1` instead\n * - Node builds: Include both implementations, feature flag chooses at runtime\n * - `secp256k1`: Remains an `optionalDependency` so browser-only users don't face build issues\n *\n * ### Future Plans\n * Once the custom ECIES implementation is battle-tested:\n * 1. Make custom ECIES the default\n * 2. Eventually remove eccrypto-js dependency\n * 3. Keep the same architecture (native for Node, @noble for browser)\n */\n\n/**\n * Feature flag configuration\n */\nexport const features = {\n  /**\n   * Use custom ECIES implementation instead of eccrypto\n   *\n   * When false (default): Uses the original eccrypto/eccrypto-js libraries for stability\n   * When true: Uses the custom platform-specific ECIES implementation\n   *\n   * Enable by setting environment variable: VANA_USE_CUSTOM_ECIES=true\n   *\n   * @example\n   * ```bash\n   * # Use eccrypto-js (default)\n   * VANA_USE_CUSTOM_ECIES=false npm run your-app\n   *\n   * # Use custom ECIES implementation\n   * VANA_USE_CUSTOM_ECIES=true npm run your-app\n   * ```\n   *\n   * @returns Whether to use custom ECIES implementation\n   */\n  get useCustomECIES(): boolean {\n    // Default to false (use eccrypto for stability)\n    // Tests will override this to true since they test the custom implementation\n    return process.env.VANA_USE_CUSTOM_ECIES === \"true\";\n  },\n};\n"],"mappings":";;;;;;;;;;;;;;;;;;AAAA;AAAA;AAAA;AAAA;AAAA;AAyCO,MAAM,WAAW;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAoBtB,IAAI,iBAA0B;AAG5B,WAAO,QAAQ,IAAI,0BAA0B;AAAA,EAC/C;AACF;","names":[]}
+{"version":3,"sources":["../../src/config/features.ts"],"sourcesContent":["/**\n * Feature flags for the Vana SDK\n *\n * @remarks\n * This module controls feature toggles that allow switching between different\n * implementations or enabling experimental features.\n *\n * The getter pattern is used to allow dynamic evaluation of environment variables,\n * which is necessary for tests to override the default before modules are loaded.\n *\n * ## ECIES Encryption\n *\n * The SDK uses a custom ECIES implementation:\n * - **Node.js**: Uses native `secp256k1` module for optimal performance\n * - **Browser**: Uses `@noble/secp256k1` (pure JavaScript)\n * - Fully compatible with eccrypto format for backward compatibility\n *\n * ### Architecture Notes\n * - Browser builds: Use `@noble/secp256k1` (no native dependencies)\n * - Node builds: Use native `secp256k1` when available for better performance\n * - `secp256k1`: Remains an `optionalDependency` so browser-only users don't face build issues\n * - All encrypted data is compatible with the eccrypto format specification\n */\n\n/**\n * Feature flag configuration\n *\n * @remarks\n * Currently empty as all feature flags have been graduated to default behavior.\n * This module is kept for future feature flag additions.\n */\nexport const features = {};\n"],"mappings":";;;;;;;;;;;;;;;;;;AAAA;AAAA;AAAA;AAAA;AAAA;AA+BO,MAAM,WAAW,CAAC;","names":[]}

package/dist/config/features.d.ts

@@ -8,55 +8,24 @@
  * The getter pattern is used to allow dynamic evaluation of environment variables,
  * which is necessary for tests to override the default before modules are loaded.
  *
- * ## Dual-Mode ECIES Support
+ * ## ECIES Encryption
  *
- * The SDK supports two encryption implementations:
- *
- * 1. **eccrypto-js** (Default)
- *    - Pure JavaScript implementation
- *    - Works everywhere (Node.js and browsers)
- *    - No native dependencies
- *    - Good performance for most use cases
- *
- * 2. **Custom ECIES** (Opt-in)
- *    - Uses native `secp256k1` module in Node.js for optimal performance
- *    - Uses `@noble/secp256k1` in browsers (pure JS)
- *    - Slightly faster in Node.js environments
- *    - Currently used by tests to ensure compatibility
+ * The SDK uses a custom ECIES implementation:
+ * - **Node.js**: Uses native `secp256k1` module for optimal performance
+ * - **Browser**: Uses `@noble/secp256k1` (pure JavaScript)
+ * - Fully compatible with eccrypto format for backward compatibility
  *
  * ### Architecture Notes
- * - Browser builds: Never reference native `secp256k1`, use `@noble/secp256k1` instead
- * - Node builds: Include both implementations, feature flag chooses at runtime
+ * - Browser builds: Use `@noble/secp256k1` (no native dependencies)
+ * - Node builds: Use native `secp256k1` when available for better performance
  * - `secp256k1`: Remains an `optionalDependency` so browser-only users don't face build issues
- *
- * ### Future Plans
- * Once the custom ECIES implementation is battle-tested:
- * 1. Make custom ECIES the default
- * 2. Eventually remove eccrypto-js dependency
- * 3. Keep the same architecture (native for Node, @noble for browser)
+ * - All encrypted data is compatible with the eccrypto format specification
  */
 /**
  * Feature flag configuration
+ *
+ * @remarks
+ * Currently empty as all feature flags have been graduated to default behavior.
+ * This module is kept for future feature flag additions.
  */
-export declare const features: {
-    /**
-     * Use custom ECIES implementation instead of eccrypto
-     *
-     * When false (default): Uses the original eccrypto/eccrypto-js libraries for stability
-     * When true: Uses the custom platform-specific ECIES implementation
-     *
-     * Enable by setting environment variable: VANA_USE_CUSTOM_ECIES=true
-     *
-     * @example
-     * ```bash
-     * # Use eccrypto-js (default)
-     * VANA_USE_CUSTOM_ECIES=false npm run your-app
-     *
-     * # Use custom ECIES implementation
-     * VANA_USE_CUSTOM_ECIES=true npm run your-app
-     * ```
-     *
-     * @returns Whether to use custom ECIES implementation
-     */
-    readonly useCustomECIES: boolean;
-};
+export declare const features: {};

package/dist/config/features.js

@@ -1,27 +1,4 @@
-const features = {
-  /**
-   * Use custom ECIES implementation instead of eccrypto
-   *
-   * When false (default): Uses the original eccrypto/eccrypto-js libraries for stability
-   * When true: Uses the custom platform-specific ECIES implementation
-   *
-   * Enable by setting environment variable: VANA_USE_CUSTOM_ECIES=true
-   *
-   * @example
-   * ```bash
-   * # Use eccrypto-js (default)
-   * VANA_USE_CUSTOM_ECIES=false npm run your-app
-   *
-   * # Use custom ECIES implementation
-   * VANA_USE_CUSTOM_ECIES=true npm run your-app
-   * ```
-   *
-   * @returns Whether to use custom ECIES implementation
-   */
-  get useCustomECIES() {
-    return process.env.VANA_USE_CUSTOM_ECIES === "true";
-  }
-};
+const features = {};
 export {
   features
 };

package/dist/config/features.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/config/features.ts"],"sourcesContent":["/**\n * Feature flags for the Vana SDK\n *\n * @remarks\n * This module controls feature toggles that allow switching between different\n * implementations or enabling experimental features.\n *\n * The getter pattern is used to allow dynamic evaluation of environment variables,\n * which is necessary for tests to override the default before modules are loaded.\n *\n * ## Dual-Mode ECIES Support\n *\n * The SDK supports two encryption implementations:\n *\n * 1. **eccrypto-js** (Default)\n *    - Pure JavaScript implementation\n *    - Works everywhere (Node.js and browsers)\n *    - No native dependencies\n *    - Good performance for most use cases\n *\n * 2. **Custom ECIES** (Opt-in)\n *    - Uses native `secp256k1` module in Node.js for optimal performance\n *    - Uses `@noble/secp256k1` in browsers (pure JS)\n *    - Slightly faster in Node.js environments\n *    - Currently used by tests to ensure compatibility\n *\n * ### Architecture Notes\n * - Browser builds: Never reference native `secp256k1`, use `@noble/secp256k1` instead\n * - Node builds: Include both implementations, feature flag chooses at runtime\n * - `secp256k1`: Remains an `optionalDependency` so browser-only users don't face build issues\n *\n * ### Future Plans\n * Once the custom ECIES implementation is battle-tested:\n * 1. Make custom ECIES the default\n * 2. Eventually remove eccrypto-js dependency\n * 3. Keep the same architecture (native for Node, @noble for browser)\n */\n\n/**\n * Feature flag configuration\n */\nexport const features = {\n  /**\n   * Use custom ECIES implementation instead of eccrypto\n   *\n   * When false (default): Uses the original eccrypto/eccrypto-js libraries for stability\n   * When true: Uses the custom platform-specific ECIES implementation\n   *\n   * Enable by setting environment variable: VANA_USE_CUSTOM_ECIES=true\n   *\n   * @example\n   * ```bash\n   * # Use eccrypto-js (default)\n   * VANA_USE_CUSTOM_ECIES=false npm run your-app\n   *\n   * # Use custom ECIES implementation\n   * VANA_USE_CUSTOM_ECIES=true npm run your-app\n   * ```\n   *\n   * @returns Whether to use custom ECIES implementation\n   */\n  get useCustomECIES(): boolean {\n    // Default to false (use eccrypto for stability)\n    // Tests will override this to true since they test the custom implementation\n    return process.env.VANA_USE_CUSTOM_ECIES === \"true\";\n  },\n};\n"],"mappings":"AAyCO,MAAM,WAAW;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAoBtB,IAAI,iBAA0B;AAG5B,WAAO,QAAQ,IAAI,0BAA0B;AAAA,EAC/C;AACF;","names":[]}
+{"version":3,"sources":["../../src/config/features.ts"],"sourcesContent":["/**\n * Feature flags for the Vana SDK\n *\n * @remarks\n * This module controls feature toggles that allow switching between different\n * implementations or enabling experimental features.\n *\n * The getter pattern is used to allow dynamic evaluation of environment variables,\n * which is necessary for tests to override the default before modules are loaded.\n *\n * ## ECIES Encryption\n *\n * The SDK uses a custom ECIES implementation:\n * - **Node.js**: Uses native `secp256k1` module for optimal performance\n * - **Browser**: Uses `@noble/secp256k1` (pure JavaScript)\n * - Fully compatible with eccrypto format for backward compatibility\n *\n * ### Architecture Notes\n * - Browser builds: Use `@noble/secp256k1` (no native dependencies)\n * - Node builds: Use native `secp256k1` when available for better performance\n * - `secp256k1`: Remains an `optionalDependency` so browser-only users don't face build issues\n * - All encrypted data is compatible with the eccrypto format specification\n */\n\n/**\n * Feature flag configuration\n *\n * @remarks\n * Currently empty as all feature flags have been graduated to default behavior.\n * This module is kept for future feature flag additions.\n */\nexport const features = {};\n"],"mappings":"AA+BO,MAAM,WAAW,CAAC;","names":[]}

package/dist/controllers/permissions.cjs

@@ -43,6 +43,7 @@ var import_signatureCache = require("../utils/signatureCache");
 var import_signatureFormatter = require("../utils/signatureFormatter");
 var import_typedDataConverter = require("../utils/typedDataConverter");
 var import_base = require("./base");
+const MAX_UINT256 = 115792089237316195423570985008687907853269984665640564039457584007913129639935n;
 class PermissionsController extends import_base.BaseController {
   constructor(context) {
     super(context);
@@ -1499,20 +1500,24 @@ class PermissionsController extends import_base.BaseController {
         }
       }
       const onChainGrants = allPermissions.map(
-        (permission) => ({
-          id: BigInt(permission.id),
-          grantUrl: permission.grant,
-          grantSignature: permission.signature,
-          nonce: BigInt(permission.nonce),
-          startBlock: BigInt(permission.startBlock),
-          addedAtBlock: BigInt(permission.addedAtBlock),
-          addedAtTimestamp: BigInt(permission.addedAtTimestamp ?? "0"),
-          transactionHash: permission.transactionHash ?? "",
-          grantor: userAddress,
-          grantee: permission.grantee,
-          active: !permission.endBlock || BigInt(permission.endBlock) === 0n
-          // Active if no end block or end block is 0
-        })
+        (permission) => {
+          const endBlock = permission.endBlock === void 0 || permission.endBlock === null ? 0n : BigInt(permission.endBlock);
+          const active = !permission.endBlock || endBlock === 0n || endBlock === MAX_UINT256;
+          return {
+            id: BigInt(permission.id),
+            grantUrl: permission.grant,
+            grantSignature: permission.signature,
+            nonce: BigInt(permission.nonce),
+            startBlock: BigInt(permission.startBlock),
+            endBlock,
+            addedAtBlock: BigInt(permission.addedAtBlock),
+            addedAtTimestamp: BigInt(permission.addedAtTimestamp ?? "0"),
+            transactionHash: permission.transactionHash ?? "",
+            grantor: userAddress,
+            grantee: permission.grantee,
+            active
+          };
+        }
       );
       return onChainGrants.sort((a, b) => {
         if (a.id < b.id) return 1;