@temple-digital-group/temple-canton-js 1.0.34 → 1.0.35

package/README.md

@@ -10,11 +10,11 @@ npm install @temple-digital-group/temple-canton-js
 
 ## Configuration
 
-There are three ways to use the SDK depending on your environment:
+Call `initializeConfig()` before using any SDK functions. This is required in all environments.
 
-### 1. Browser with Custom Validator
+### Custom Validator
 
-For browser apps connecting to your own validator. Requires `initializeConfig()` with your validator URLs and a pre-authenticated JWT token.
+For apps connecting to your own validator (browser or server-side):
 
 ```javascript
 import { initializeConfig } from '@temple-digital-group/temple-canton-js';
@@ -23,8 +23,14 @@ initializeConfig({
   NETWORK: 'mainnet',
   VALIDATOR_API_URL: 'https://your-validator-url',
   VALIDATOR_SCAN_API_URL: 'https://your-scan-api-url',
-  JWT_TOKEN: 'your-jwt-token',
-  VALIDATOR_USER_PARTY_ID: 'your-user-party-id'
+  VALIDATOR_USER_PARTY_ID: 'your-user-party-id',
+  JWT_TOKEN: 'your-jwt-token',           // Browser: pass a pre-authenticated JWT
+  // — OR for server-side Auth0 —
+  // AUTH0_TOKEN_URL: 'https://your-auth0-domain/oauth/token',
+  // AUTH0_USER_ID: 'your-auth0-user-id',
+  // AUTH0_CLIENT_ID: 'your-client-id',
+  // AUTH0_CLIENT_SECRET: 'your-client-secret',
+  // AUTH0_AUDIENCE: 'your-audience',
 });
 ```
 
@@ -33,12 +39,27 @@ initializeConfig({
 | `NETWORK` | Yes | `mainnet`, `testnet`, or `localhost` |
 | `VALIDATOR_API_URL` | Yes | Base URL of the Canton validator ledger API |
 | `VALIDATOR_SCAN_API_URL` | Yes | Base URL of the Canton Scan API |
-| `JWT_TOKEN` | Yes | Pre-authenticated JWT token for ledger API calls |
 | `VALIDATOR_USER_PARTY_ID` | Yes | The user's party ID on the network |
+| `JWT_TOKEN` | Yes* | Pre-authenticated JWT token for ledger API calls |
+| `AUTH0_TOKEN_URL` | Yes* | Auth0 OAuth token endpoint |
+| `AUTH0_CLIENT_ID` | Yes* | Auth0 application client ID |
+| `AUTH0_CLIENT_SECRET` | Yes* | Auth0 application client secret |
+| `AUTH0_AUDIENCE` | Yes* | Auth0 API audience identifier |
+| `AUTH0_USER_ID` | Yes* | Auth0 user ID for the service account |
 
-### 2. Browser with Wallet Provider
+\* Provide either `JWT_TOKEN` (browser) or the `AUTH0_*` fields (server-side). The SDK fetches and caches JWT tokens automatically when Auth0 credentials are provided.
 
-For browser apps using a wallet (e.g., Loop Wallet). Requires `initializeConfig()` with base network config only. Use `returnCommand = true` to get the command back for the wallet to sign.
+To update the JWT token later without re-initializing:
+
+```javascript
+import { setJWTToken } from '@temple-digital-group/temple-canton-js';
+
+setJWTToken(newToken);
+```
+
+### Wallet Provider
+
+For apps using a wallet provider (e.g., Loop Wallet). Use `returnCommand = true` to get the command data back.
 
 ```javascript
 import { initializeConfig, createOrderProposal } from '@temple-digital-group/temple-canton-js';
@@ -47,57 +68,14 @@ initializeConfig({
   NETWORK: 'mainnet'
 });
 
-// returnCommand=true returns the command for the wallet to sign
 const command = await createOrderProposal(orderArgs, true, walletProvider);
-const result = await walletProvider.signAndSubmit(command);
 ```
 
 | Key | Required | Description |
 |-----|----------|-------------|
 | `NETWORK` | Yes | `mainnet`, `testnet`, or `localhost` |
 
-### 3. Node.js / Server-Side
-
-For server-side applications. Uses environment variables directly — no `initializeConfig()` call needed. Create a `.env` file:
-
-```env
-NETWORK=mainnet
-VALIDATOR_API_URL=https://your-validator-url
-VALIDATOR_SCAN_API_URL=https://your-scan-api-url
-
-AUTH0_TOKEN_URL=https://your-auth0-domain.auth0.com/oauth/token
-AUTH0_USER_ID=your-auth0-user-id
-AUTH0_CLIENT_ID=your-client-id
-AUTH0_CLIENT_SECRET=your-client-secret
-AUTH0_AUDIENCE=https://your-audience
-```
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| `NETWORK` | Yes | `mainnet`, `testnet`, or `localhost` |
-| `VALIDATOR_API_URL` | Yes | Base URL of the Canton validator ledger API |
-| `VALIDATOR_SCAN_API_URL` | Yes | Base URL of the Canton Scan API |
-| `AUTH0_TOKEN_URL` | Yes | Auth0 OAuth token endpoint |
-| `AUTH0_CLIENT_ID` | Yes | Auth0 application client ID |
-| `AUTH0_CLIENT_SECRET` | Yes | Auth0 application client secret |
-| `AUTH0_AUDIENCE` | Yes | Auth0 API audience identifier |
-| `AUTH0_USER_ID` | Yes | Auth0 user ID for the service account |
-
-The SDK fetches and caches JWT tokens automatically via Auth0.
-
-You can also call `initializeConfig()` in Node.js to override specific environment variables at runtime. For example, if a frontend passes a JWT token to your server:
-
-```javascript
-import { initializeConfig, getUserBalances } from '@temple-digital-group/temple-canton-js';
-
-// .env provides base config (NETWORK, VALIDATOR_API_URL, etc.)
-// Override with a token received from the frontend
-initializeConfig({ JWT_TOKEN: tokenFromFrontend });
-
-const balances = await getUserBalances(partyId);
-```
-
-Runtime config values take precedence over environment variables.
+> **Legacy:** Environment variables are still supported for backwards compatibility, but `initializeConfig()` is the recommended approach.
 
 
 ## Supported Instruments
@@ -184,6 +162,7 @@ if (counts.largestUnlocked >= requiredAmount) {
 | Function | Description |
 |----------|-------------|
 | `initializeConfig(config)` | Initialize the library with a runtime config object |
+| `setJWTToken(token)` | Update the JWT token without re-initializing the config |
 | `getConfigValue(key)` | Get a config value from runtime config or environment |
 
 ### Authentication
@@ -253,7 +232,3 @@ These functions are synchronous and work in all environments (no ledger or provi
 | Function | Description |
 |----------|-------------|
 | ~~`cancelOrders(party, orderContractIds, assetType)`~~ | Batch cancel orders (deprecated — use the [Cancel Order](https://apidocs.templedigitalgroup.com/reference/cancelorder) or [Cancel All Orders](https://apidocs.templedigitalgroup.com/reference/cancelallorders) REST API instead) |
-
-## License
-
-MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@temple-digital-group/temple-canton-js",
-  "version": "1.0.34",
+  "version": "1.0.35",
   "description": "JavaScript library for interacting with Temple Canton blockchain",
   "type": "module",
   "main": "index.js",

package/src/config/index.js

@@ -15,6 +15,18 @@ export function initializeConfig(config) {
 	appConfig = config;
 }
 
+/**
+ * Update the JWT token without re-initializing the full config.
+ * Useful when refreshing tokens for custom validator connections.
+ * @param {string} token - The new JWT token
+ */
+export function setJWTToken(token) {
+	if (!appConfig) {
+		appConfig = {};
+	}
+	appConfig.JWT_TOKEN = token;
+}
+
 /**
  * Get a configuration value from:
  * 1. App-provided config (if initializeConfig was called)

package/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 Temple Digital Group
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.