Skip to content

Commit 5fa707a

Browse files
authored
Merge branch 'naga' into feat/naga-prod
2 parents 444c72e + e03e310 commit 5fa707a

File tree

6 files changed

+40
-8
lines changed

6 files changed

+40
-8
lines changed

docs/docs.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,7 @@
158158
"group": "$LITKEY Token",
159159
"pages": [
160160
"governance/litkey/overview",
161+
"governance/litkey/getting-litkey",
161162
"governance/litkey/initial-allocation-and-distribution",
162163
"governance/litkey/staking",
163164
"governance/litkey/lit-chain",

docs/governance/litkey/bridging-and-addresses.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ title: "Token Bridging and Contract Addresses"
66
The Lit Protocol TGE will take place on Aerodrome on 10/30 at 00:00 UTC. [Details here](https://x.com/LitProtocol/status/1981794852712132716).
77
</Note>
88

9-
The [Hyperlane Nexus Bridge](https://nexus.hyperlane.xyz/) can be used to quickly bridge LITKEY to all the networks listed in the table below.
9+
The [Hyperlane Nexus Bridge](https://nexus.hyperlane.xyz/?origin=base&token=0x9D132d5678253FD88f7DB51Ac2AC13FC40a63547&destination=litchain) can be used to quickly bridge LITKEY to all the networks listed in the table below.
1010

1111

1212
## Official Contract Addresses
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: "Getting $LITKEY"
3+
---
4+
5+
To obtain $LITKEY, you can buy it on a number of leading DEXs and CEXs listed below. You can use the [Hyperlane Nexus Bridge](https://nexus.hyperlane.xyz/?origin=base&token=0x9D132d5678253FD88f7DB51Ac2AC13FC40a63547&destination=litchain) to quickly bridge LITKEY to all the networks listed on [this page](/governance/litkey/bridging-and-addresses).
6+
7+
## DEXs and CEXs
8+
9+
* [Aerodrome](https://aerodrome.finance/swap?from=eth&to=0xf732a566121fa6362e9e0fbdd6d66e5c8c925e49&chain0=8453&chain1=8453) is a DEX on Base
10+
* [PancakeSwap](https://pancakeswap.finance/swap?inputCurrency=BNB&outputCurrency=0x0bbea6812fb3fcbca126edb558e551b3f1702026) is a DEX on BSC
11+
* [ByBit](https://www.bybit.com/en/) is a CEX that supports deposits and withdrawals of $LITKEY for Base, Ethereum, and Arbitrum One
12+
* [Wasabi](https://app.wasabi.xyz/?market=LITKEYWETH&network=base) is a DEX on Base that supports up to 3x leverage and shorting of $LITKEY

docs/governance/litkey/overview.mdx

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,6 @@
22
title: "Overview"
33
---
44

5-
<Note>
6-
The Lit Protocol TGE will take place on Aerodrome on 10/30 at 00:00 UTC. [Details here](https://x.com/LitProtocol/status/1981794852712132716).
7-
</Note>
8-
95
The \$LITKEY token underpins the entire Lit Protocol ecosystem, serving as a multi-dimensional work, payment, and governance token. Together, these dimensions aim to facilitate a self-sustaining token economy in which tokens are staked to secure the network, used as rewards to incentivize operator participation, exchanged to access cryptographic services, and to govern the continued growth and development of the Lit ecosystem.
106

117
## Work Token: Securing and Incentivizing Service Providers

docs/learning-lit/how-it-works.mdx

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,31 @@ Each Lit Protocol node participates in a Distributed Key Generation (DKG) proces
1515

1616
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.
1717

18+
Today this includes:
19+
20+
| Scheme | Curve |
21+
|--------|-------|
22+
| `EcdsaK256Sha256` | secp256k1 |
23+
| `EcdsaP256Sha256` | NIST P-256 |
24+
| `EcdsaP384Sha384` | NIST P-384 |
25+
| `SchnorrEd25519Sha512` | ed25519 |
26+
| `SchnorrEd448Shake256` | ed448 |
27+
| `SchnorrK256Taproot` | secp256k1 |
28+
| `SchnorrK256Sha256` | secp256k1 |
29+
| `SchnorrP256Sha256` | NIST P-256 |
30+
| `SchnorrP384Sha384` | NIST P-384 |
31+
| `SchnorrRistretto25519Sha512` | Ristretto25519 |
32+
| `SchnorrRedJubjubBlake2b512` | Jubjub |
33+
| `SchnorrRedDecaf377Blake2b512` | Decaf377 |
34+
| `SchnorrkelSubstrate` | sr25519 |
35+
36+
37+
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.
38+
1839
## Policy Enforcement and Data Orchestration – Lit Actions
1940

2041
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.
2142

2243
## Further Reading
2344

24-
For an in-depth overview of how Lit keeps keys and assets secure, please check out the [security](/learning-lit/security) section.
45+
For an in-depth overview of how Lit keeps keys and assets secure, please check out the [security](/learning-lit/security) section.

docs/node-ops/staking-and-delegation.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,10 @@ After meeting the minimum self-stake requirement, any node operator can increase
4141

4242
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.
4343

44+
## Consensus Threshold Rule
45+
46+
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`.
47+
4448
## Slashing
4549

4650
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.
@@ -62,5 +66,3 @@ Slashed funds are sent to a contract that is initially administered by the Lit P
6266
### Governance Oversight
6367

6468
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.
65-
66-

0 commit comments

Comments
 (0)