Docs update with more pricing info

docs/docs.json

@@ -27,6 +27,14 @@
               "learning-lit/backup-and-recovery",
               "learning-lit/threshold-cryptography"
             ]
+          },
+          {
+            "group": "Pricing",
+            "pages": [
+              "learning-lit/pricing/payment-model",
+              "learning-lit/pricing/current-prices",
+              "learning-lit/pricing/example-lit-action-costs"
+            ]
           }
         ]
       },

docs/learning-lit/communicating-with-lit-nodes.mdx

@@ -51,6 +51,6 @@ The following is the complete request lifecycle when communicating with the Lit
 
 ## Active Nodes
 
-The Naga node operator set was selected via a staking contest that ran following the Lit TGE. The top 10 node operators based on "[stake weight](https://github.com/LIT-Protocol/LITKEY-Token-Paper-v1/blob/main/%24LITKEY%20Whitepaper%20-%20v1.pdf)" were selected by the community.
+The Naga node operator set was selected via a staking contest that ran following the Lit TGE. The top 10 node operators based on "[stake weight](https://github.com/LIT-Protocol/LITKEY-Token-Paper-v1/blob/main/LITKEY-Whitepaper-Updated-Oct-25.pdf)" were selected by the community.
 
 Interested in running a node? [Reach out.](https://forms.gle/n4WKtsyxaduEz8dDA)

docs/learning-lit/cryptoeconomic-security.mdx

@@ -15,4 +15,4 @@ While threshold cryptography and TEEs provide technical security guarantees, the
 
 Additionally, token holders who aren't node operators themselves will be able to delegate their $LITKEY tokens to a node operator(s) of their choice, curating the set of active node operators and helping distribute cryptographic security across a broader set of participants.
 
-You can learn more about the role and utility of the $LITKEY token by checking out the [token whitepaper](https://github.com/LIT-Protocol/LITKEY-Token-Paper-v1/blob/main/%24LITKEY%20Whitepaper%20-%20v1.pdf).
+You can learn more about the role and utility of the $LITKEY token by checking out the [token whitepaper](https://github.com/LIT-Protocol/LITKEY-Token-Paper-v1/blob/main/LITKEY-Whitepaper-Updated-Oct-25.pdf).

docs/learning-lit/distributed-key-generation.mdx

@@ -4,15 +4,15 @@ title: "Distributed Key Generation"
 
 ## Intro
 
-All Lit Protocol node operators use a [Distributed Key Generation (DKG)](https://github.com/LIT-Protocol/whitepaper/blob/main/Lit%20Protocol%20Whitepaper%20(2024).pdf) process to collectively generate all of the signing and encryption keys managed by the network. DKG ensures that no single node or party ever has access to any key in its entirety, as the entire key never exists at all. Instead, more than a threshold of the Lit nodes must come together (more than two-thirds of the network) to generate these keys and perform signing and decryption operations.
+All Lit Protocol node operators use a [Distributed Key Generation (DKG)](https://github.com/LIT-Protocol/LITKEY-Token-Paper-v1/blob/main/LITKEY-Whitepaper-Updated-Oct-25.pdf) process to collectively generate all of the signing and encryption keys managed by the network. DKG ensures that no single node or party ever has access to any key in its entirety, as the entire key never exists at all. Instead, more than a threshold of the Lit nodes must come together (more than two-thirds of the network) to generate these keys and perform signing and decryption operations.
 
 ## Root Keys
 
 All signing keys are derived hierarchically from a set of root keys. These root keys are periodically refreshed or reshared (see below) and are backed up regularly. See the recovery section below for more information on the backup process.
 
 ## Key Refresh and Resharing
 
-Periodically, key shares are updated with a refresh scheme. This rotates the private key shares among an existing set of participating node operators without changing the underlying private key, a process known as [Proactive Secret Sharing.](https://github.com/LIT-Protocol/whitepaper/blob/main/Lit%20Protocol%20Whitepaper%20(2024).pdf) This method helps ensure the integrity of private key material for long periods of time while minimizing the risk of key compromise.
+Periodically, key shares are updated with a refresh scheme. This rotates the private key shares among an existing set of participating node operators without changing the underlying private key, a process known as [Proactive Secret Sharing.](https://github.com/LIT-Protocol/LITKEY-Token-Paper-v1/blob/main/LITKEY-Whitepaper-Updated-Oct-25.pdf) This method helps ensure the integrity of private key material for long periods of time while minimizing the risk of key compromise.
 
 The key refresh protocol is performed by first linearizing all of the key shares, running the same DKG algorithm with existing participants, then checking that the public key doesn't change.
 

docs/learning-lit/pricing/current-prices.mdx

@@ -0,0 +1,48 @@
+---
+title: "Current Prices"
+---
+import { CurrentPricesTable } from "/snippets/CurrentPricesTable.jsx";
+import { PriceProvider } from "/snippets/PriceProvider.jsx";
+
+The following table shows the current pricing for Lit Protocol services on the **Naga Prod / Mainnet V1** network. Prices are displayed in both $LITKEY tokens and USD (based on current market rates).
+
+<Note>
+Most prices update dynamically based on network usage. The values shown below reflect real-time prices fetched from the blockchain. Note that PKP Minting cost is static and does not change with network utilization.
+</Note>
+
+<PriceProvider component={CurrentPricesTable} />
+
+## Understanding the Price Table
+
+### Base vs Max Prices
+
+- **Base Price**: The minimum price when network usage is low
+- **Max Price**: The maximum price when the network is at full capacity
+- **Current Price**: The actual price at this moment, which varies between base and max based on usage
+
+### Product Types
+
+- **PKP Sign**: Signing operations using your Programmable Key Pair
+- **Decryption and Access Control**: Decrypting data and enforcing access control conditions
+- **Lit Action**: Executing serverless JavaScript functions (pricing varies by component)
+- **Sign Session Key**: Session-based signing operations
+- **PKP Minting**: Creating a new Programmable Key Pair (static price, does not vary with network usage)
+
+### Lit Action Pricing Components
+
+Lit Actions have multiple pricing components that are charged based on resource usage:
+
+- **Base Amount**: Fixed cost per Lit Action execution
+- **Runtime Length**: Cost per second of execution time
+- **Memory Usage**: Cost per megabyte of memory used
+- **Code Length**: Cost based on the size of your Lit Action code
+- **Response Length**: Cost based on the size of the response data
+- **Signatures**: Cost per signature generated
+- **Broadcasts**: Cost per broadcast operation
+- **Contract Calls**: Cost per smart contract call
+- **Call Depth**: Cost based on call stack depth
+- **Decrypts**: Cost per decryption operation
+- **Fetches**: Cost per HTTP fetch request
+
+The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage.
+

docs/learning-lit/pricing/example-lit-action-costs.mdx

@@ -0,0 +1,26 @@
+---
+title: "Example Lit Action Costs"
+---
+import { ExampleLitActionCosts } from "/snippets/ExampleLitActionCosts.jsx";
+import { PriceProvider } from "/snippets/PriceProvider.jsx";
+
+This page demonstrates real-world cost estimates for common Lit Action operations. The costs are calculated using current real-time prices from the blockchain and show how different resource usage affects the total cost.
+
+<Note>
+These are estimates based on current prices and the specified resource usage. Actual costs may vary slightly based on network conditions and exact resource consumption.
+</Note>
+
+<PriceProvider component={ExampleLitActionCosts} />
+
+## Understanding the Cost Breakdown
+
+Each example shows a detailed breakdown of costs by component:
+
+- **Base Amount**: Fixed cost per Lit Action execution
+- **Runtime Length**: Cost based on execution time (charged per second)
+- **Fetches**: Cost per HTTP fetch request
+- **Signatures**: Cost per signature generated
+- **Decrypts**: Cost per decryption operation
+
+The total cost is the sum of all applicable components based on the operation's resource usage.
+

docs/learning-lit/pricing/payment-model.mdx

@@ -0,0 +1,63 @@
+---
+title: "Payment Model"
+---
+
+Lit Protocol uses a token-based payment system to ensure the decentralized network can sustain itself for providing cryptographic services.
+
+## How Network Usage Payments Work
+
+### Token Deposit System
+
+To use Lit Protocol's services, you must first load tokens into the **Ledger Contract** on Lit Chain. This contract acts as a prepaid account that holds your [$LITKEY](/governance/litkey/overview) tokens and automatically deducts fees as you use the network.
+
+### Dynamic Pricing Model
+
+Lit Protocol uses a dynamic pricing model that adjusts based on network usage:
+
+- **Base Price**: The minimum price for each service when the network has low usage
+- **Max Price**: The maximum price when the network is at full capacity
+- **Current Price**: The actual price at any given moment, which fluctuates between the base and max price based on current network usage
+
+This pricing mechanism ensures:
+- Fair pricing during low-usage periods (you pay less when demand is low)
+- Network stability during high-usage periods (prices increase to manage demand)
+- Market price discovery for Lit network capacity
+
+### Pricing in $LITKEY Tokens
+
+All services on Lit Protocol are priced in **[$LITKEY](/governance/litkey/overview) tokens**, the native token of Lit Chain. When you use network services such as:
+
+- **PKP Signing**: Generating signatures with your Programmable Key Pair
+- **Decryption and Access Control**: Decrypting data and enforcing access control conditions
+- **Lit Actions**: Executing serverless JavaScript functions
+- **Sign Session Key**: Session-based signing operations
+
+The network automatically deducts the appropriate amount of [$LITKEY](/governance/litkey/overview) tokens from your ledger balance based on the current dynamic price.
+
+### Automatic Deduction
+
+When you make a request to the network, the system:
+1. Checks your ledger balance
+2. Calculates the current price for the requested service
+3. Deducts the required tokens from your balance
+4. Processes your request
+
+If your balance is insufficient, the request will fail. You can check your balance and deposit more tokens as needed using the [Payment Manager](/sdk/getting-started/payment-manager-setup).
+
+## Getting Started
+
+To start using Lit Protocol's paid services:
+
+1. **Acquire [$LITKEY](/governance/litkey/overview) tokens** - [Get tokens](/governance/litkey/getting-litkey) from exchanges or other sources
+2. **Set up Payment Manager** - Configure your payment system using the [Payment Manager Setup Guide](/sdk/getting-started/payment-manager-setup)
+3. **Deposit tokens** - Load tokens into the ledger contract
+4. **Use the network** - Start making requests; tokens will be deducted automatically
+
+For detailed information on current pricing, see the [Current Prices](/learning-lit/pricing/current-prices) page.
+
+## Additional Costs
+
+There are additional costs associated with using Lit Protocol's services that are not covered by the network usage payments. These include:
+
+- **Gas on Lit Chain** - Lit Chain is the database for Lit network.  When you make a transaction on Lit Chain, you will need to pay for the gas used by the transaction.  Examples of operations that would require a transaction on Lit Chain are things like changing PKP Permissions, transferring PKPs, and launching smart contracts on Lit Chain.  Lit Chain gas is priced in $LITKEY tokens and the gas price is very low compared to other chains.
+- **PKP Minting** - When you mint a new PKP, you will need to pay a specific fee for the minting operation.  This fee is not dynamic and is a fixed cost.  Check out the [Current Prices page](/learning-lit/pricing/current-prices) to see the price right now.

docs/lit-pricing-constants.js

@@ -0,0 +1,43 @@
+// Shared constants and helper functions for Lit Protocol pricing components
+// This file is automatically included on every page by Mintlify
+
+window.LitPricingConstants = {
+  // LitActionPriceComponent enum values
+  LitActionPriceComponent: {
+    baseAmount: 0,
+    runtimeLength: 1,
+    memoryUsage: 2,
+    codeLength: 3,
+    responseLength: 4,
+    signatures: 5,
+    broadcasts: 6,
+    contractCalls: 7,
+    callDepth: 8,
+    decrypts: 9,
+    fetches: 10,
+  },
+
+  // NodePriceMeasurement enum values
+  NodePriceMeasurement: {
+    perSecond: 0,
+    perMegabyte: 1,
+    perCount: 2,
+  },
+
+  // Helper function to convert wei to tokens
+  weiToTokens: (wei, ethers) => {
+    if (!ethers || !ethers.utils) {
+      return 0;
+    }
+    return parseFloat(ethers.utils.formatUnits(wei, 18));
+  },
+
+  // Helper function to format price display
+  formatPrice: (priceInTokens, priceInUSD) => {
+    if (priceInUSD === null) {
+      return `${priceInTokens.toFixed(6)} LITKEY`;
+    }
+    return `${priceInTokens.toFixed(6)} LITKEY ($${priceInUSD.toFixed(6)})`;
+  },
+};
+