@gala-chain/launchpad-sdk 5.0.4-beta.6 → 5.0.4-beta.60

package/dist/examples/locks/lock-unlock-workflow.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Lock/Unlock Tokens Demo
+ *
+ * Demonstrates batch lock and unlock operations on GalaChain.
+ * Lock operations place holds on tokens, preventing transfers until unlocked.
+ *
+ * Use cases:
+ * - Staking
+ * - Escrow
+ * - Vesting schedules
+ * - Governance voting
+ *
+ * @example
+ * ```bash
+ * # Run from SDK package directory
+ * ENVIRONMENT=stage npm run demo:locks
+ * ```
+ */
+export declare const runLockUnlockWorkflowDemo: import("../utils").WrappedDemoFunction;
+//# sourceMappingURL=lock-unlock-workflow.d.ts.map

package/dist/examples/locks/lock-unlock-workflow.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"lock-unlock-workflow.d.ts","sourceRoot":"","sources":["../../../examples/locks/lock-unlock-workflow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAaH,eAAO,MAAM,yBAAyB,wCAsKpC,CAAC"}

package/dist/examples/messages/messages-lifecycle.d.ts

@@ -0,0 +1,37 @@
+#!/usr/bin/env tsx
+/**
+ * Unified Messages Lifecycle Demo
+ *
+ * Demonstrates the complete message lifecycle using the unified /v1/messages endpoint:
+ * - fetchMessages() - Query messages by type, token, or user
+ * - createMessage() - Create CHAT or COMMENT messages
+ * - updateMessage() - Edit message content
+ * - deleteMessage() - Remove a message
+ *
+ * Key concepts:
+ * - Unified endpoint handles both CHAT and COMMENT message types
+ * - Full CRUD operations on messages
+ * - Author and moderator permissions for edits/deletes
+ * - Pagination support for large message sets
+ *
+ * @example
+ * ```bash
+ * # View and manage messages
+ * PRIVATE_KEY=0x... npm run demo:messages:lifecycle
+ *
+ * # Test with create/update/delete operations
+ * PRIVATE_KEY=0x... CREATE_MESSAGE=true npm run demo:messages:lifecycle
+ * ```
+ *
+ * @since 7.0.0
+ * @category Messages
+ */
+import '../utils/suppress-logging';
+export declare const metadata: {
+    name: string;
+    description: string;
+    category: string;
+    sdkMethods: string[];
+    tags: string[];
+};
+//# sourceMappingURL=messages-lifecycle.d.ts.map

package/dist/examples/messages/messages-lifecycle.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"messages-lifecycle.d.ts","sourceRoot":"","sources":["../../../examples/messages/messages-lifecycle.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AAGH,OAAO,2BAA2B,CAAC;AA+XnC,eAAO,MAAM,QAAQ;;;;;;CAMpB,CAAC"}

package/dist/examples/messages/messages-pinning.d.ts

@@ -0,0 +1,37 @@
+#!/usr/bin/env tsx
+/**
+ * Messages Pinning Demo
+ *
+ * Demonstrates message pinning operations via the unified /v1/messages endpoint:
+ * - getPinnedMessage() - Get the currently pinned message for a token
+ * - pinMessage() - Pin a message to the top
+ * - unpinMessage() - Unpin a message
+ *
+ * Key concepts:
+ * - Pin operations work with the unified messages API
+ * - Only one message per token can be pinned
+ * - Pinning a new message replaces the old one
+ * - Useful for important announcements or featured content
+ *
+ * @example
+ * ```bash
+ * # View pinned messages
+ * npm run demo:messages:pinning
+ *
+ * # Test pinning operations
+ * PRIVATE_KEY=0x... PIN_MESSAGE=true npm run demo:messages:pinning
+ * ```
+ *
+ * @since 7.0.0
+ * @category Messages
+ */
+import '../utils/suppress-logging';
+export declare const runMain: import("../utils").WrappedDemoFunction;
+export declare const metadata: {
+    name: string;
+    description: string;
+    category: string;
+    sdkMethods: string[];
+    tags: string[];
+};
+//# sourceMappingURL=messages-pinning.d.ts.map

package/dist/examples/messages/messages-pinning.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"messages-pinning.d.ts","sourceRoot":"","sources":["../../../examples/messages/messages-pinning.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAEH,OAAO,2BAA2B,CAAC;AAoBnC,eAAO,MAAM,OAAO,wCAsUlB,CAAC;AAEH,eAAO,MAAM,QAAQ;;;;;;CAMpB,CAAC"}

package/dist/examples/moderators/claim-invite.d.ts

@@ -0,0 +1,28 @@
+/**
+ * Claim Moderator Invite Demo
+ *
+ * Demonstrates claiming and managing moderator invites.
+ * Note: Requires a valid invite code from a token owner.
+ *
+ * **Prerequisites:**
+ * - JWT authentication required
+ * - A valid invite code (obtained from token owner via createModeratorInvite)
+ *
+ * **Roles:**
+ * - MODERATOR: Manage comments, chat, ban/unban users
+ * - TECHNICAL_PRODUCER: Simulcast, stream key, start/stop stream
+ * - MANAGER: All of the above + recordings + stream settings
+ *
+ * @example
+ * ```bash
+ * # Basic run (shows workflow without actual claiming)
+ * npm run demo:moderators:claim-invite
+ *
+ * # With an actual invite code
+ * INVITE_CODE=abc123... npm run demo:moderators:claim-invite
+ * ```
+ *
+ * @since 5.7.0
+ */
+export declare const runClaimModeratorInviteDemo: import("../utils").WrappedDemoFunction;
+//# sourceMappingURL=claim-invite.d.ts.map

package/dist/examples/moderators/claim-invite.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"claim-invite.d.ts","sourceRoot":"","sources":["../../../examples/moderators/claim-invite.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAMH,eAAO,MAAM,2BAA2B,wCA+ItC,CAAC"}

package/dist/examples/moderators/invite-management.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Moderator Invite Management Demo
+ *
+ * This example demonstrates the complete moderator invite lifecycle:
+ * - Creating invites with different roles
+ * - Listing invites for a token
+ * - Getting invite details by code (public endpoint)
+ * - Revoking invites
+ * - Claiming invites (as the invited user)
+ * - Viewing moderated tokens
+ *
+ * **Prerequisites:**
+ * - Must be the token owner to create/list/revoke invites
+ * - JWT authentication required
+ *
+ * **Roles:**
+ * - MODERATOR: Manage comments, chat, ban/unban users
+ * - TECHNICAL_PRODUCER: Simulcast, stream key, start/stop stream
+ * - MANAGER: All of the above + recordings + stream settings
+ *
+ * @example
+ * ```bash
+ * # Run with a test wallet (token owner)
+ * PRIVATE_KEY=0x... ENVIRONMENT=development npm run demo:moderators
+ * ```
+ *
+ * @since 5.7.0
+ */
+export declare const runModeratorInviteManagementDemo: import("../utils").WrappedDemoFunction;
+//# sourceMappingURL=invite-management.d.ts.map

package/dist/examples/moderators/invite-management.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"invite-management.d.ts","sourceRoot":"","sources":["../../../examples/moderators/invite-management.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AAOH,eAAO,MAAM,gCAAgC,wCA4P3C,CAAC"}

package/dist/examples/moderators/moderated-tokens-portfolio.d.ts

@@ -0,0 +1,18 @@
+#!/usr/bin/env tsx
+/**
+ * Moderated Tokens Portfolio Demo
+ *
+ * Demonstrates moderator portfolio and management:
+ * - View all tokens you moderate
+ * - Analyze moderation responsibilities
+ * - Track moderation activities per token
+ * - Manage moderation across multiple tokens
+ * - Role assignment and permissions
+ *
+ * @example
+ * ```bash
+ * npm run demo:moderators:moderated-tokens
+ * ```
+ */
+export {};
+//# sourceMappingURL=moderated-tokens-portfolio.d.ts.map

package/dist/examples/moderators/moderated-tokens-portfolio.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"moderated-tokens-portfolio.d.ts","sourceRoot":"","sources":["../../../examples/moderators/moderated-tokens-portfolio.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;GAcG"}

package/dist/examples/monitoring/demo-stream-events.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Real-Time Stream Events Monitoring Demo
+ *
+ * This example demonstrates subscribing to real-time WebSocket events:
+ * - Stream status changes (ACTIVE/IDLE/DISABLED)
+ * - Viewer count updates
+ * - User ban/unban events
+ * - Proper subscription cleanup
+ *
+ * @example
+ * ```bash
+ * # Run with a test token
+ * PRIVATE_KEY=0x... TOKEN_NAME=mytoken npm run demo:monitoring:stream-events
+ * ```
+ */
+export declare const runMain: import("../utils").WrappedDemoFunction;
+//# sourceMappingURL=demo-stream-events.d.ts.map

package/dist/examples/monitoring/demo-stream-events.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"demo-stream-events.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/demo-stream-events.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAMH,eAAO,MAAM,OAAO,wCA4KlB,CAAC"}

package/dist/examples/monitoring/demo-watch-pools.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Watch for New DEX Pool Creation - Demo
+ *
+ * This example demonstrates how to watch for newly created DEX pools in real-time.
+ * The watcher polls for new pools at regular intervals and notifies you immediately
+ * when matching pools are detected.
+ *
+ * @example
+ * ```bash
+ * # Install dependencies
+ * npm install
+ *
+ * # Run with a test wallet
+ * PRIVATE_KEY=0x3dfd8710588ffee0a62a2b2320d5dd9ea6a57768eedd64a92751cb46a483142d npm run demo:watch-pools
+ * ```
+ */
+export {};
+//# sourceMappingURL=demo-watch-pools.d.ts.map

package/dist/examples/monitoring/demo-watch-pools.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"demo-watch-pools.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/demo-watch-pools.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG"}

package/dist/examples/monitoring/demo-watch-tokens.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Watch for New Launchpad Token Creation - Demo
+ *
+ * This example demonstrates how to watch for newly created launchpad tokens in real-time.
+ * The watcher polls for new tokens at regular intervals and notifies you immediately
+ * when new tokens are created.
+ *
+ * @example
+ * ```bash
+ * # Install dependencies
+ * npm install
+ *
+ * # Run with a test wallet
+ * PRIVATE_KEY=0x3dfd8710588ffee0a62a2b2320d5dd9ea6a57768eedd64a92751cb46a483142d npm run demo:watch-tokens
+ * ```
+ */
+export {};
+//# sourceMappingURL=demo-watch-tokens.d.ts.map

package/dist/examples/monitoring/demo-watch-tokens.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"demo-watch-tokens.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/demo-watch-tokens.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;GAeG"}

package/dist/examples/monitoring/fees-collection-e2e.d.ts

@@ -0,0 +1,36 @@
+/**
+ * Fee Collection Monitoring E2E Test
+ *
+ * Proves that the liquidity monitor catches collectFees events using the multi-wallet pattern.
+ *
+ * Key insight: Fees are only generated from EXTERNAL traders - trading with your own
+ * wallet against your own LP position won't generate fees. So we need:
+ * 1. Primary wallet (LP provider) - owns the position, starts the monitor, collects fees
+ * 2. Secondary wallet (trader) - funded by primary, does trades to generate fees
+ *
+ * The backend broadcasts collectFees events with the SAME structure as liquidity events:
+ * - amounts, poolAlias, poolFee, poolHash, positionId, userAddress, userBalanceDelta, transactionId
+ *
+ * Run: npm run demo:watch:fees:e2e
+ */
+import '../utils/suppress-logging';
+interface TestResults {
+    monitorStarted: boolean;
+    positionFound: boolean;
+    traderFunded: boolean;
+    tradesExecuted: boolean;
+    feesAccumulated: boolean;
+    feesCollected: boolean;
+    feeCollectionEventDetected: boolean;
+    eventDetails: {
+        transactionId?: string;
+        positionId?: string;
+        amounts?: [string, string];
+        poolFee?: number;
+        userAddress?: string;
+    };
+    error?: string;
+}
+declare function runFeesCollectionE2E(): Promise<TestResults>;
+export { runFeesCollectionE2E };
+//# sourceMappingURL=fees-collection-e2e.d.ts.map

package/dist/examples/monitoring/fees-collection-e2e.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"fees-collection-e2e.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/fees-collection-e2e.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAIH,OAAO,2BAA2B,CAAC;AAwBnC,UAAU,WAAW;IACnB,cAAc,EAAE,OAAO,CAAC;IACxB,aAAa,EAAE,OAAO,CAAC;IACvB,YAAY,EAAE,OAAO,CAAC;IACtB,cAAc,EAAE,OAAO,CAAC;IACxB,eAAe,EAAE,OAAO,CAAC;IACzB,aAAa,EAAE,OAAO,CAAC;IACvB,0BAA0B,EAAE,OAAO,CAAC;IACpC,YAAY,EAAE;QACZ,aAAa,CAAC,EAAE,MAAM,CAAC;QACvB,UAAU,CAAC,EAAE,MAAM,CAAC;QACpB,OAAO,CAAC,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;QAC3B,OAAO,CAAC,EAAE,MAAM,CAAC;QACjB,WAAW,CAAC,EAAE,MAAM,CAAC;KACtB,CAAC;IACF,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED,iBAAe,oBAAoB,IAAI,OAAO,CAAC,WAAW,CAAC,CAoY1D;AAOD,OAAO,EAAE,oBAAoB,EAAE,CAAC"}

package/dist/examples/monitoring/fees-collection-guaranteed.d.ts

@@ -0,0 +1,49 @@
+/**
+ * Fee Collection Monitoring E2E Test - Guaranteed Fee Generation
+ *
+ * Extended version of fees-collection-e2e.ts that GUARANTEES fee accumulation by:
+ * 1. Querying current pool tick via getSwapPoolPrice()
+ * 2. Creating LP position that spans the current price (in-range)
+ * 3. Funding two external trader wallets for bidirectional trades
+ * 4. Executing alternating trades to generate fees through our position
+ * 5. Collecting accumulated fees and verifying liquidity monitor catches the event
+ *
+ * Key insight: Fees are only generated from EXTERNAL traders trading through in-range positions.
+ * Position must span current pool tick to earn fees from trades.
+ *
+ * Run: npm run demo:watch:fees:guaranteed
+ */
+import '../utils/suppress-logging';
+interface TestResults {
+    monitorStarted: boolean;
+    poolStateQueried: boolean;
+    positionInRange: boolean;
+    positionCreated: boolean;
+    tradersCreated: boolean;
+    tradersFunded: boolean;
+    tradesExecuted: number;
+    feesAccumulated: boolean;
+    feeAmount0: string;
+    feeAmount1: string;
+    feesCollected: boolean;
+    feeCollectionEventDetected: boolean;
+    eventDetails: {
+        transactionId?: string;
+        positionId?: string;
+        amounts?: [string, string];
+        poolFee?: number;
+        userAddress?: string;
+    };
+    poolState: {
+        tick?: number;
+        price?: string;
+    };
+    positionTicks: {
+        tickLower?: number;
+        tickUpper?: number;
+    };
+    error?: string;
+}
+declare function runGuaranteedFeesE2E(): Promise<TestResults>;
+export { runGuaranteedFeesE2E };
+//# sourceMappingURL=fees-collection-guaranteed.d.ts.map

package/dist/examples/monitoring/fees-collection-guaranteed.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"fees-collection-guaranteed.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/fees-collection-guaranteed.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;GAcG;AAIH,OAAO,2BAA2B,CAAC;AAyDnC,UAAU,WAAW;IACnB,cAAc,EAAE,OAAO,CAAC;IACxB,gBAAgB,EAAE,OAAO,CAAC;IAC1B,eAAe,EAAE,OAAO,CAAC;IACzB,eAAe,EAAE,OAAO,CAAC;IACzB,cAAc,EAAE,OAAO,CAAC;IACxB,aAAa,EAAE,OAAO,CAAC;IACvB,cAAc,EAAE,MAAM,CAAC;IACvB,eAAe,EAAE,OAAO,CAAC;IACzB,UAAU,EAAE,MAAM,CAAC;IACnB,UAAU,EAAE,MAAM,CAAC;IACnB,aAAa,EAAE,OAAO,CAAC;IACvB,0BAA0B,EAAE,OAAO,CAAC;IACpC,YAAY,EAAE;QACZ,aAAa,CAAC,EAAE,MAAM,CAAC;QACvB,UAAU,CAAC,EAAE,MAAM,CAAC;QACpB,OAAO,CAAC,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;QAC3B,OAAO,CAAC,EAAE,MAAM,CAAC;QACjB,WAAW,CAAC,EAAE,MAAM,CAAC;KACtB,CAAC;IACF,SAAS,EAAE;QACT,IAAI,CAAC,EAAE,MAAM,CAAC;QACd,KAAK,CAAC,EAAE,MAAM,CAAC;KAChB,CAAC;IACF,aAAa,EAAE;QACb,SAAS,CAAC,EAAE,MAAM,CAAC;QACnB,SAAS,CAAC,EAAE,MAAM,CAAC;KACpB,CAAC;IACF,KAAK,CAAC,EAAE,MAAM,CAAC;CAChB;AAED,iBAAe,oBAAoB,IAAI,OAAO,CAAC,WAAW,CAAC,CAqnB1D;AAOD,OAAO,EAAE,oBAAoB,EAAE,CAAC"}

package/dist/examples/monitoring/liquidity-e2e-test.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Liquidity Monitoring E2E Test - Full Round-Trip
+ *
+ * Tests the complete liquidity monitoring lifecycle:
+ * 1. Start liquidity monitor
+ * 2. Add liquidity to GALA/GUSDC pool
+ * 3. Verify ADD event is detected
+ * 4. Remove the liquidity (full position close)
+ * 5. Verify REMOVE event is detected
+ * 6. Confirm position is gone (liquidity = 0)
+ *
+ * Run: npm run demo:watch:liquidity:e2e
+ */
+export declare const runLiquidityE2ETest: import("../utils").WrappedDemoFunction;
+//# sourceMappingURL=liquidity-e2e-test.d.ts.map

package/dist/examples/monitoring/liquidity-e2e-test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"liquidity-e2e-test.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/liquidity-e2e-test.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AA4BH,eAAO,MAAM,mBAAmB,wCA8U9B,CAAC"}

package/dist/examples/monitoring/liquidity-monitor.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Liquidity Monitor Demo
+ *
+ * Demonstrates real-time monitoring of DEX liquidity position changes.
+ * Monitors all liquidity changes globally - perfect for whale watching,
+ * market analysis, and LP tracking.
+ *
+ * Note: The backend broadcasts position change events without distinguishing
+ * between add and remove operations. Events represent position updates.
+ *
+ * Events are broadcast globally - you can monitor ALL DEX liquidity activity,
+ * not just your own transactions.
+ */
+import '../utils/suppress-logging';
+declare function runLiquidityMonitor(): Promise<void>;
+export { runLiquidityMonitor };
+//# sourceMappingURL=liquidity-monitor.d.ts.map

package/dist/examples/monitoring/liquidity-monitor.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"liquidity-monitor.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/liquidity-monitor.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAIH,OAAO,2BAA2B,CAAC;AAanC,iBAAe,mBAAmB,kBAkFjC;AAKD,OAAO,EAAE,mBAAmB,EAAE,CAAC"}

package/dist/examples/monitoring/pool-creation-integration.d.ts

@@ -0,0 +1,27 @@
+#!/usr/bin/env tsx
+/**
+ * Integration Test: DEX Pool Creation Event Monitoring
+ *
+ * This comprehensive integration test demonstrates the full workflow:
+ * 1. Initialize SDK with wallet
+ * 2. Check pre-flight conditions (balance, token availability)
+ * 3. START MONITORING for pool creation events (BEFORE creating pool)
+ * 4. Create a real DEX pool via liquidity position
+ * 5. Wait for WebSocket event delivery
+ * 6. Verify event data matches pool created
+ * 7. Test filter combinations (token, pair, fee tier)
+ *
+ * CRITICAL: Pool creation must be monitored BEFORE the action to prevent
+ * race conditions where events arrive before listeners are ready.
+ *
+ * @example
+ * ```bash
+ * npm run demo:subscribe:pools:integration
+ * ```
+ *
+ * Cost: ~10-20 GALA on STAGE (minimal liquidity provision)
+ * Runtime: ~45-60 seconds (includes WebSocket polling)
+ * Network: STAGE (requires STAGE environment configured)
+ */
+export {};
+//# sourceMappingURL=pool-creation-integration.d.ts.map

package/dist/examples/monitoring/pool-creation-integration.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"pool-creation-integration.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/pool-creation-integration.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;GAuBG"}

package/dist/examples/monitoring/pool-liquidity-tracker.d.ts

@@ -0,0 +1,15 @@
+/**
+ * Pool Liquidity Tracker Demo
+ *
+ * Demonstrates monitoring liquidity position changes for a specific token pair.
+ * Tracks liquidity activity and detects whale transactions.
+ *
+ * Note: The backend broadcasts position change events without distinguishing
+ * between add and remove operations. Events represent position updates.
+ *
+ * Use Case: Monitor GALA/GUSDC pool liquidity for market analysis.
+ */
+import '../utils/suppress-logging';
+declare function runPoolLiquidityTracker(): Promise<void>;
+export { runPoolLiquidityTracker };
+//# sourceMappingURL=pool-liquidity-tracker.d.ts.map

package/dist/examples/monitoring/pool-liquidity-tracker.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"pool-liquidity-tracker.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/pool-liquidity-tracker.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAIH,OAAO,2BAA2B,CAAC;AAanC,iBAAe,uBAAuB,kBAgGrC;AAKD,OAAO,EAAE,uBAAuB,EAAE,CAAC"}

package/dist/examples/monitoring/subscribe-liquidity-added.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Subscribe to DEX Liquidity Added Events
+ *
+ * Demonstrates real-time monitoring of liquidity addition events using
+ * the `subscribeToDexLiquidityAdded()` SDK method.
+ *
+ * **Important Backend Behavior:**
+ * The backend broadcasts all liquidity position changes without distinguishing
+ * between add and remove operations. The `subscribeToDexLiquidityAdded` method
+ * is a semantic alias for `subscribeToDexLiquidityChanged` - both receive the
+ * same events. Use this method when your intent is to focus on liquidity additions.
+ *
+ * **Use Cases:**
+ * - LP deposit tracking: Monitor when users add liquidity to positions
+ * - Whale watching: Detect large liquidity additions
+ * - Market analysis: Track overall DEX liquidity growth
+ * - Dashboard displays: Show real-time liquidity addition feed
+ *
+ * @example
+ * ```bash
+ * # Run with wallet
+ * PRIVATE_KEY=0x... npm run demo:monitoring:liquidity-added
+ * ```
+ *
+ * @since 4.3.0
+ */
+import '../utils/suppress-logging';
+declare function runLiquidityAddedDemo(): Promise<void>;
+export { runLiquidityAddedDemo };
+//# sourceMappingURL=subscribe-liquidity-added.d.ts.map

package/dist/examples/monitoring/subscribe-liquidity-added.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"subscribe-liquidity-added.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-liquidity-added.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAIH,OAAO,2BAA2B,CAAC;AAanC,iBAAe,qBAAqB,kBAuHnC;AAKD,OAAO,EAAE,qBAAqB,EAAE,CAAC"}

package/dist/examples/monitoring/subscribe-liquidity-removed.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Subscribe to DEX Liquidity Removed Events
+ *
+ * Demonstrates real-time monitoring of liquidity removal events using
+ * the `subscribeToDexLiquidityRemoved()` SDK method.
+ *
+ * **Important Backend Behavior:**
+ * The backend broadcasts all liquidity position changes without distinguishing
+ * between add and remove operations. The `subscribeToDexLiquidityRemoved` method
+ * is a semantic alias for `subscribeToDexLiquidityChanged` - both receive the
+ * same events. Use this method when your intent is to focus on liquidity removals.
+ *
+ * **Use Cases:**
+ * - LP exit tracking: Monitor when users remove liquidity from positions
+ * - Whale watching: Detect large liquidity withdrawals
+ * - Risk management: React to liquidity decreases in pools you trade
+ * - Market analysis: Track overall DEX liquidity changes
+ *
+ * @example
+ * ```bash
+ * # Run with wallet
+ * PRIVATE_KEY=0x... npm run demo:monitoring:liquidity-removed
+ * ```
+ *
+ * @since 4.3.0
+ */
+import '../utils/suppress-logging';
+declare function runLiquidityRemovedDemo(): Promise<void>;
+export { runLiquidityRemovedDemo };
+//# sourceMappingURL=subscribe-liquidity-removed.d.ts.map

package/dist/examples/monitoring/subscribe-liquidity-removed.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"subscribe-liquidity-removed.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-liquidity-removed.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAIH,OAAO,2BAA2B,CAAC;AAanC,iBAAe,uBAAuB,kBAgHrC;AAKD,OAAO,EAAE,uBAAuB,EAAE,CAAC"}

package/dist/examples/monitoring/subscribe-pool-creations.d.ts

@@ -0,0 +1,29 @@
+#!/usr/bin/env tsx
+/**
+ * Basic Demo: Monitor DEX Pool Creation Events
+ *
+ * This demo shows how to use `subscribeToDexPoolAdded()` to listen for
+ * real-time DEX pool creation events via WebSocket.
+ *
+ * The demo demonstrates:
+ * - Basic subscription setup
+ * - Position-independent token filtering
+ * - Pair filtering (order-independent)
+ * - Fee tier filtering
+ * - Combined filters
+ * - Cleanup patterns
+ *
+ * @example
+ * ```bash
+ * npm run demo:subscribe:pools
+ * ```
+ *
+ * Note: This demo listens for real WebSocket events from the backend.
+ * To see actual pool creation events, run the integration test which
+ * creates a real pool: `npm run demo:subscribe:pools:integration`
+ */
+/**
+ * Main demo function
+ */
+export declare const runMain: import("../utils/sdk-setup").WrappedDemoFunction;
+//# sourceMappingURL=subscribe-pool-creations.d.ts.map

package/dist/examples/monitoring/subscribe-pool-creations.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"subscribe-pool-creations.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-pool-creations.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;GAsBG;AAMH;;GAEG;AACH,eAAO,MAAM,OAAO,kDAsNlB,CAAC"}

package/dist/examples/monitoring/subscribe-token-creations.d.ts

@@ -0,0 +1,21 @@
+#!/usr/bin/env tsx
+/**
+ * Real-Time Token Creation Broadcasting
+ *
+ * Demonstrates the REAL architecture for token creation monitoring:
+ * - WebSocket broadcasts token creation events globally to all connected clients
+ * - ~1-2 second latency (vs 15-30+ seconds with polling)
+ * - No need for polling or REST API calls
+ *
+ * This replaces the polling-based onLaunchpadTokenCreation() with instant notifications.
+ *
+ * Usage:
+ * ```bash
+ * npm run demo:subscribe:tokens
+ * ```
+ *
+ * Costs: Free (just listening, no transactions)
+ * Runtime: Continuous until interrupted (Ctrl+C)
+ */
+export {};
+//# sourceMappingURL=subscribe-token-creations.d.ts.map

package/dist/examples/monitoring/subscribe-token-creations.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"subscribe-token-creations.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/subscribe-token-creations.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;GAiBG"}

package/dist/examples/monitoring/token-creation-integration.d.ts

@@ -0,0 +1,32 @@
+#!/usr/bin/env tsx
+/**
+ * Integration Demo: Token Creation + Monitoring Architecture
+ *
+ * This demo illustrates two distinct paths for token creation monitoring:
+ *
+ * ⚡ PATH 1 - CREATOR'S OWN TOKEN (Instant WebSocket):
+ * ✅ `launchToken()` returns instant websocket confirmation (<2 seconds)
+ * ✅ Result contains transactionId, vaultAddress from backend
+ * ✅ This is what happens internally - websocket confirms own transactions
+ *
+ * 📡 PATH 2 - MONITORING OTHERS' TOKENS (Polling-Based):
+ * ⚠️  `onLaunchpadTokenCreation()` uses REST API polling (NOT real-time websocket)
+ * ⚠️  Expected delay: 15-30+ seconds (waits for backend indexing)
+ * ⚠️  Why? Backend only emits transaction-specific events, no broadcast channel
+ * ⚠️  Use for: Trading bots, monitoring third-party token launches
+ *
+ * ARCHITECTURE NOTE:
+ * The backend doesn't emit broadcast events for token creation to all clients.
+ * Non-creators must poll REST API to discover new tokens.
+ * This demo shows both approaches with accurate timing expectations.
+ *
+ * @example
+ * ```bash
+ * npm run demo:watch:integration
+ * ```
+ *
+ * Cost: ~100-110 GALA on STAGE (100 pre-buy + launch fee)
+ * Runtime: ~90 seconds (includes polling wait)
+ */
+export {};
+//# sourceMappingURL=token-creation-integration.d.ts.map

package/dist/examples/monitoring/token-creation-integration.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"token-creation-integration.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/token-creation-integration.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG"}

package/dist/examples/monitoring/websocket-event-handlers.d.ts

@@ -0,0 +1,22 @@
+#!/usr/bin/env tsx
+/**
+ * WebSocket Event Handlers Comprehensive Demo
+ *
+ * Demonstrates all 25 WebSocket event handler callbacks supported by the SDK:
+ * - Authentication events (onAuthenticated, onConnection)
+ * - Stream events (onStreamStatusChanged, onViewerCountChanged, etc.)
+ * - Chat events (onStreamChatMessage, onUserTyping, etc.)
+ * - Ban events (onBanEnforcement, onUserBanned, onUserUnbanned)
+ * - Content moderation (onContentFlagged, onFlagResolved, etc.)
+ * - Subscription events (onRoomSubscribed, onTokenSubscribed, etc.)
+ *
+ * Shows how to register and use all available event handler callbacks
+ * with proper type safety and error handling.
+ *
+ * @example
+ * ```bash
+ * npm run demo:monitoring:websocket-events
+ * ```
+ */
+export declare const run: import("../utils").WrappedDemoFunction;
+//# sourceMappingURL=websocket-event-handlers.d.ts.map

package/dist/examples/monitoring/websocket-event-handlers.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"websocket-event-handlers.d.ts","sourceRoot":"","sources":["../../../examples/monitoring/websocket-event-handlers.ts"],"names":[],"mappings":";AAEA;;;;;;;;;;;;;;;;;;GAkBG;AAsYH,eAAO,MAAM,GAAG,wCAAuD,CAAC"}