# Everlight Shards

<figure><img src="/files/1U2NZv6ABBFEPr6Hl1yY" alt=""><figcaption></figcaption></figure>

Everlight Shards are the public-facing form of Everlight’s Transaction Validation Nodes.\
\
A Shard represents a crystallized unit of validation power that, when activated, instantiates a dedicated Transaction Validation Node within the Bitcoin Everlight protocol.

While the underlying infrastructure remains node-based, the Shard framework introduces a structured, tiered, and transferable activation model that aligns participation with protocol growth.

***

#### Shards and Transaction Validation

Each activated Shard:

* Instantiates a Transaction Validation Node
* Participates in validating Everlight network transactions
* Contributes to protocol throughput and settlement security
* Earns rewards based on performance, uptime, and duration

Shards do not replace the node architecture.\
They are the structured activation layer that maps directly to validator instances.

***

#### Why Shards Exist

The Shard framework serves three primary purposes:

1. **Structured Participation**\
   Shards provide a standardized unit for validator activation.
2. **Tiered Network Contribution**\
   Different Shard tiers represent different validation capacities and reward scaling.
3. **Transferable Activation Rights**\
   Shards may be transferred through protocol-defined mechanisms, allowing dynamic network participation while preserving validation integrity.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bitcoin-everlight.gitbook.io/bitcoin-everlight-docs/everlight-shards.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.