Skip to content

Commit 70feead

Browse files
authored
Merge pull request #964 from LIT-Protocol/docs/faqs
feat(docs): Add FAQ section to documentation and update index formatting
2 parents 04a240b + 092ccc7 commit 70feead

File tree

3 files changed

+23
-5
lines changed

3 files changed

+23
-5
lines changed

docs/docs.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,12 @@
125125
"sdk/resources/supported-evm-chains",
126126
"sdk/resources/network-status"
127127
]
128+
},
129+
{
130+
"group": "FAQ",
131+
"pages": [
132+
"faqs/index"
133+
]
128134
}
129135
]
130136
},

docs/faqs/index.mdx

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: 'FAQ'
3+
description: 'Common questions about using the Lit JS SDK'
4+
---
5+
6+
# Frequently Asked Questions
7+
8+
## What's the default `responseStrategy` for `executeJs` in v8?
9+
10+
The behavior matches v7. When you omit `responseStrategy`, the SDK calls `processLitActionResponseStrategy` with `{ strategy: 'leastCommon' }`. If you provide an unrecognized value, the helper still falls back to `leastCommon`.
11+
12+
This default keeps compatibility with `Lit.Actions.runOnce`. Only the node that runs the `runOnce` block returns a value, so selecting the least-common response ensures that single result is preserved. When `runOnce` is not used, all nodes should emit the same payload, making least- vs most-common equivalent—the former stayed in place because it was the quickest path to enabling the new `runOnce` flow in v8.

docs/index.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: "What is Lit Protocol"
3-
description: "Decentralized key management and private compute"
2+
title: 'What is Lit Protocol'
3+
description: 'Decentralized key management and private compute'
44
---
55

66
<Tip>
@@ -62,9 +62,9 @@ Developers can utilize Lit's programmable and chain-agnostic signing capabilitie
6262
Lit enables the creation of data oracles that securely fetch off-chain data for use in on-chain applications, bridging the gap between smart contracts and real-world information.
6363

6464
> **📝 Data Oracle Kit**
65-
>
65+
>
6666
> The [Lit Oracle Kit](https://github.com/LIT-Protocol/lit-oracle-kit) demonstrates how the Lit Network can be used to sign data pulled from the web (or another blockchain) and write it to chain.
67-
>
67+
>
6868
> **Note:** This kit is currently built for V7 of the Lit SDK. A V8 version is coming soon!
6969
7070
### AI Agents and Infrastructure
@@ -77,6 +77,6 @@ Projects in this category are focused on delivering essential infrastructure cri
7777

7878
## Next Steps
7979

80-
To learn more about how Lit Protocol works and keeps assets and data secure, continue on to the sections ahead.
80+
To learn more about how Lit Protocol works and keeps assets and data secure, continue on to the sections ahead.
8181

8282
If you're a developer looking to build with the Lit SDK, check out the [Build with Lit](https://litprotocol.mintlify.app/sdk/introduction) section to get started.

0 commit comments

Comments
 (0)