Skip to content

docs: enhance key management documentation with cryptographic schemes… #992

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: naga
Choose a base branch
from
Open

docs: enhance key management documentation with cryptographic schemes… #992

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c6e9f13
docs: enhance key management documentation with cryptographic schemes…
Ansonhkg Nov 7, 2025
edce647
docs: remove bls
Ansonhkg Nov 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 22 additions & 1 deletion docs/learning-lit/how-it-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,31 @@ Each Lit Protocol node participates in a Distributed Key Generation (DKG) proces

The Lit network supports multiple cryptographic curves, signing schemes, and key types. Additional curves and schemes can be added as desired to enable additional interoperability with a wide variety of protocols and standards.

Today this includes:

| Scheme | Curve |
|--------|-------|
| `EcdsaK256Sha256` | secp256k1 |
| `EcdsaP256Sha256` | NIST P-256 |
| `EcdsaP384Sha384` | NIST P-384 |
| `SchnorrEd25519Sha512` | ed25519 |
| `SchnorrEd448Shake256` | ed448 |
| `SchnorrK256Taproot` | secp256k1 |
| `SchnorrK256Sha256` | secp256k1 |
| `SchnorrP256Sha256` | NIST P-256 |
| `SchnorrP384Sha384` | NIST P-384 |
| `SchnorrRistretto25519Sha512` | Ristretto25519 |
| `SchnorrRedJubjubBlake2b512` | Jubjub |
| `SchnorrRedDecaf377Blake2b512` | Decaf377 |
| `SchnorrkelSubstrate` | sr25519 |


Refer to the [PKP Sign guide](/sdk/auth-context-consumption/pkp-sign#available-signing-schemes) for the full scheme-by-curve matrix that SDK users call directly.

## Policy Enforcement and Data Orchestration – Lit Actions

Each Lit node contains a JavaScript execution environment which allows developers to write arbitrary code that dictates how the secrets and keys managed by the network are used. These programs are called Lit Actions, immutable JS serverless functions that govern signing and encryption / decryption operations. Lit Actions can natively fetch and process data from any on or off-chain source, be used to create complex transaction automations (e.g. dollar-cost-averaging), define rules for usage and access, create spending policies, trigger signature generation, and more.

## Further Reading

For an in-depth overview of how Lit keeps keys and assets secure, please check out the [security](/learning-lit/security) section.
For an in-depth overview of how Lit keeps keys and assets secure, please check out the [security](/learning-lit/security) section.
6 changes: 4 additions & 2 deletions docs/node-ops/staking-and-delegation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,10 @@ After meeting the minimum self-stake requirement, any node operator can increase

Each node operator has the ability to set their own commission rate, which determines the percentage of staking rewards that are retained prior to being distributed to delegators. This allows operators to compete on both performance and pricing. Commission rates are managed and displayed on the Lit staking portal.

## Consensus Threshold Rule

All Lit validator and signing operations are guarded by a threshold rule that requires at least `ROUNDUP(MAX(3, 2N/3))` participating nodes for a committee of size `N`.
Copy link

Copilot AI Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The mathematical formula 2N/3 is ambiguous and could be misinterpreted. Consider writing it as 2*N/3 or (2N)/3 to make it clear that N should be multiplied by 2 before dividing by 3. Alternatively, you could express it in clearer prose, such as "two-thirds of N".

Suggested change
All Lit validator and signing operations are guarded by a threshold rule that requires at least `ROUNDUP(MAX(3, 2N/3))` participating nodes for a committee of size `N`.
All Lit validator and signing operations are guarded by a threshold rule that requires at least `ROUNDUP(MAX(3, 2*N/3))` participating nodes for a committee of size `N`.

Copilot uses AI. Check for mistakes.

## Slashing

Slashing has been implemented to ensure that node operators keep their machines online and responsive at all times, preventing any downtime that could disrupt the network. Unlike some other protocols where slashing may also enforce computational ‘correctness,’ Lit Protocol relies on Trusted Execution Environments (TEEs) and threshold consensus mechanisms to guarantee the accuracy and integrity of operations. As a result, slashing in Lit Protocol is specifically designed to enforce availability and liveness rather than correctness.
Expand All @@ -62,5 +66,3 @@ Slashed funds are sent to a contract that is initially administered by the Lit P
### Governance Oversight

Outside of integrating slashing outcomes with the Lit governance process to ensure consistent enforcement of rules while maintaining flexibility to address edge cases, the Lit Protocol Council will serve an important role in overseeing the parameters associated with the slashing process itself. This includes configuring the slashing penalty itself, as well as managing the kick counter and decay mechanism.


Loading