You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/blacklight/learn/architecture.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
Nillion Blacklight is a decentralised verification network designed to continuously verify workloads running inside trusted execution environments (TEEs). The system is composed of three core components that work together to provide ongoing, credibly neutral verification.
6
6
7
7
* TEE Operators run workloads inside TEEs and submit proofs of liveness (that we call heartbeat transactions - HTXs).
8
-
*[**Nillion's Ethereum L2**](/blacklight/verify/network) coordinates verification, consensus, and rewards. Verification coordination is realised by the L2 assigning Blacklight nodes HTXs they should verify.
8
+
*[**Nillion's Ethereum L2**](/blacklight/learn/network) coordinates verification, consensus, and rewards. Verification coordination is realised by the L2 assigning Blacklight nodes HTXs they should verify.
9
9
* Blacklight nodes independently challenge and verify TEE attestations.
10
10
11
11
```mermaid
@@ -103,16 +103,16 @@ The central concept underpinning Nillion Blacklight is that of the heartbeat tra
103
103
104
104
## TEE Operators
105
105
106
-
TEE operators (such as [nilCC](/blind-computer/build/compute/overview) node operators) run workloads inside Trusted Execution Environments. For each active workload, operators periodically submit heartbeat transactions (HTXs) to [Nillion's Ethereum L2](/blacklight/verify/network). These heartbeats assert that the workload is still running and provide the metadata required for the network to independently verify its execution.
106
+
TEE operators (such as [nilCC](/blind-computer/build/compute/overview) node operators) run workloads inside Trusted Execution Environments. For each active workload, operators periodically submit heartbeat transactions (HTXs) to [Nillion's Ethereum L2](/blacklight/learn/network). These heartbeats assert that the workload is still running and provide the metadata required for the network to independently verify its execution.
107
107
108
108
## Nillion's Ethereum L2
109
109
110
-
[Nillion's Ethereum L2](/blacklight/verify/network) acts as the coordination and settlement layer for Nillion Blacklight. It receives heartbeat transactions (HTXs) from TEE operators and assigns each HTX to a committee of Blacklight nodes selected in a stake-weighted, probabilistic way. After the assigned Blacklight nodes verify the workload and submit their signed results back to the L2, the L2 evaluates whether the committee has reached consensus.
110
+
[Nillion's Ethereum L2](/blacklight/learn/network) acts as the coordination and settlement layer for Nillion Blacklight. It receives heartbeat transactions (HTXs) from TEE operators and assigns each HTX to a committee of Blacklight nodes selected in a stake-weighted, probabilistic way. After the assigned Blacklight nodes verify the workload and submit their signed results back to the L2, the L2 evaluates whether the committee has reached consensus.
111
111
112
112
Consensus is determined using two stake-weighted conditions: a quorum requirement (enough of the committee’s total stake has responded) and a threshold requirement (enough of the committee’s total stake agrees on the same outcome). Once these conditions are met, the L2 finalises the verification result for the HTX and distributes rewards from the reward pool (which Blacklight nodes can then claim).
113
113
114
114
## Blacklight Nodes
115
115
116
-
[Blacklight nodes](/blacklight/verify/run-node) are permissionless verifier nodes that perform the core verification work of the network. When assigned a HTX, a Blacklight node retrieves the workload’s attestation report directly from the TEE operator and independently verifies its authenticity and correctness.
116
+
Blacklight nodes are permissionless verifier nodes that perform the core verification work of the network. When assigned a HTX, a Blacklight node retrieves the workload’s attestation report directly from the TEE operator and independently verifies its authenticity and correctness.
117
117
118
118
Each node submits a signed verification result back to the L2. Once consensus is reached, nodes that contributed to the finalised outcome are eligible for rewards.
The core Solidity smart contracts for Blacklight are deployed on [Nillion's Ethereum L2](/blacklight/learn/network) and are also maintained in the [Blacklight contracts repository](https://github.com/NillionNetwork/blacklight-contracts).
4
+
5
+
## Core Contracts
6
+
7
+
-[ProtocolConfig](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/ProtocolConfig.sol) - Central governance-owned parameter store and module registry
8
+
-[StakingOperators](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/StakingOperators.sol) - ERC20 staking registry with snapshot-based voting power
9
+
-[WeightedCommitteeSelector](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/WeightedCommitteeSelector.sol) - Stake-weighted random committee selection
10
+
-[HeartbeatManager](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/HeartbeatManager.sol) - Orchestrates multi-round heartbeat verification with stake-weighted committees
11
+
-[RewardPolicy](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/RewardPolicy.sol) - Streaming budget reward allocator with stake-weighted distribution
12
+
-[NoOpSlashingPolicy](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/NoOpSlashingPolicy.sol) - Slashing policy implementation that intentionally applies no penalties or jailing
13
+
-[EmissionsController](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/EmissionsController.sol) - Token emissions scheduler with L1-to-L2 bridging
14
+
-[Interfaces](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/Interfaces.sol) - Shared contract interfaces for pluggable modules
Nillion Blacklight is the verification layer of the Blind Computer. It is powered by [Nillion's Ethereum L2](/blacklight/verify/network) and a decentralized network of permissionless, community-run Blacklight nodes that continuously challenge and verify workloads running on [nilCC](/blind-computer/build/compute/overview) and other TEE providers (such as Phala and Secret Network).
6
+
Nillion Blacklight is the verification layer of the Blind Computer. It is powered by [Nillion's Ethereum L2](/blacklight/learn/network) and a decentralized network of permissionless, community-run Blacklight nodes that continuously challenge and verify workloads running on [nilCC](/blind-computer/build/compute/overview) and other TEE providers (such as Phala and Secret Network).
7
7
8
-
Nillion Blacklight will be released very soon. You can read about its [architecture](/blacklight/learn/architecture), [verficiation protocol](/blacklight/learn/verification), and details about how [staking and rewards](/blacklight/learn/staking-and-rewards) work.
9
-
10
-
11
-
{/* ## Start Verifying
8
+
## Start Verifying
12
9
13
10
Start earning rewards by verifying existing apps — or let Blacklight's node operators verify your own apps — using Blacklight's features and tools.
14
11
@@ -18,11 +15,11 @@ Start earning rewards by verifying existing apps — or let Blacklight's nod
18
15
19
16
Nillion Blacklight has three main components.
20
17
21
-
- [**Community-run Blacklight Nodes**](/blacklight/verify/run-node): Permissionless nodes that verify TEE workloads by challenging attestation reports and monitoring enclave behavior.
18
+
-[**Community-run Blacklight Nodes**](/blacklight/run-node/setup): Permissionless nodes that verify TEE workloads by challenging attestation reports and monitoring enclave behavior.
22
19
23
-
- [**Nillion's Ethereum L2**](/blacklight/verify/network): An EVM-compatible Layer 2 network that handles verification work assignment, staking, and reward distributions.
20
+
-[**Nillion's Ethereum L2**](/blacklight/learn/network): An EVM-compatible Layer 2 network that handles verification work assignment, staking, and reward distributions.
24
21
25
-
- [**Smart Contracts**](/blacklight/verify/contracts): Solidity contracts that handle protocol configuration, manage staking, select verification committees, orchestrate verification, and distribute rewards.
22
+
-[**Smart Contracts**](/blacklight/learn/contracts): Solidity contracts that handle protocol configuration, manage staking, select verification committees, orchestrate verification, and distribute rewards.
26
23
27
24
Together, the above components form a credibly neutral trust layer that holds applications with TEE workloads accountable through continuous monitoring and verification.
28
25
@@ -33,4 +30,4 @@ Nillion Blacklight can currently verify the two categories of workloads below.
33
30
- Workloads running on Nillion's confidential compute module [nilCC](/blind-computer/build/compute/overview) that have opted-in to verification.
34
31
- Phala workloads registered with Blacklight.
35
32
36
-
The vision behind Nillion Blacklight is that, over time, it will become a universal, credibly neutral TEE trust layer that enables workload verification across many TEE providers. */}
33
+
The vision behind Nillion Blacklight is that, over time, it will become a universal, credibly neutral TEE trust layer that enables workload verification across many TEE providers.
Copy file name to clipboardExpand all lines: docs/blacklight/learn/staking-and-rewards.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Blacklight nodes are rewarded for the verification work they perform. Nodes are
6
6
7
7
Staking (and unstaking are) defined by the [corresponding smart contract](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/StakingOperators.sol).
8
8
9
-
In order to be assigned verification work by [Nillion's Ethereum L2](/blacklight/verify/network), Blacklight node operators must stake a minimum amount of NIL against their node. Currently this minimum is set to 70,000 NIL. For every HTX that is sent by a TEE operator to Nillion Blacklight, the L2 assigns a committee of Blacklight nodes to verify it. Assignment is based on stake: the more stake a Blacklight node has, the higher the chance of it being assigned work. You can read more about the [committee selection process](/blacklight/learn/verification#committee-selection).
9
+
In order to be assigned verification work by [Nillion's Ethereum L2](/blacklight/learn/network), Blacklight node operators must stake a minimum amount of NIL against their node. Currently this minimum is set to 70,000 NIL. For every HTX that is sent by a TEE operator to Nillion Blacklight, the L2 assigns a committee of Blacklight nodes to verify it. Assignment is based on stake: the more stake a Blacklight node has, the higher the chance of it being assigned work. You can read more about the [committee selection process](/blacklight/learn/verification#committee-selection).
10
10
11
11
## Rewards
12
12
@@ -15,7 +15,7 @@ Blacklight nodes will initially be rewarded from a reward pool equal to 0.5% inf
15
15
16
16
Once a Blacklight node is assigned a HTX to verify, it must verify it and report the outcome back to the L2. Once a consensus is reached by the assigned committee of nodes, rewards are distributed from the reward pool by the L2 and can be claimed by Blacklight nodes.
17
17
18
-
The greater a Blacklight nodes stake, the more work it will likely be assigned, the higher rewards it can earn. See the [budget reward allocator smart contract](https://explorer-nilav-shzvox09l5.t.conduit.xyz/address/0xb7223d0a84a8e0c5a5d384b57f2ba3b2cb216ed9) for more details.
18
+
The greater a Blacklight nodes stake, the more work it will likely be assigned, the higher rewards it can earn. See the [budget reward allocator smart contract](https://github.com/NillionNetwork/blacklight-contracts/blob/main/src/RewardPolicy.sol) for more details.
Copy file name to clipboardExpand all lines: docs/blacklight/learn/verification.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ This page describes the verification protocol utilized within Nillion Blacklight
6
6
## TEE Operators
7
7
8
8
Developers run their workloads inside trusted execution environments (TEEs), such as [nilCC](/blind-computer/build/compute/overview).
9
-
For each active workload, the TEE operators periodically submit heartbeat transactions (HTXs) to [Nillion's Ethereum L2](/blacklight/verify/network) at custom intervals (e.g., one every hour).
9
+
For each active workload, the TEE operators periodically submit heartbeat transactions (HTXs) to [Nillion's Ethereum L2](/blacklight/learn/network) at custom intervals (e.g., one every hour).
10
10
11
11
### Heartbeat Transaction (HTX)
12
12
@@ -61,7 +61,7 @@ The workload ID tracking (with both current and previous IDs) enables the networ
61
61
62
62
## Nillion's Ethereum L2
63
63
64
-
[Nillion's Ethereum L2](/blacklight/verify/network) acts as the coordination and settlement layer for Nillion Blacklight.
64
+
[Nillion's Ethereum L2](/blacklight/learn/network) acts as the coordination and settlement layer for Nillion Blacklight.
65
65
It orchestrates the verification process through smart contracts that handle committee selection, consensus evaluation, and reward distribution.
0 commit comments