-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
5916953
commit f5721b2
Showing
25 changed files
with
190 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,26 @@ | ||
# Solayer Documentation site | ||
# Introduction | ||
|
||
- **Installation** | ||
- Run the command: `$ yarn` | ||
**Solayer**: the shared validator network on Solana through the restaking collective. | ||
|
||
- **Local Development** | ||
- Run the command: `$ yarn start` | ||
- This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. | ||
Solayer is Solana's own restaking protocol. | ||
|
||
- **Build** | ||
- Run the command: `$ yarn build` | ||
- This command generates static content into the `build` directory and can be served using any static contents hosting service. | ||
#### Why use Solayer?[](https://docs.solayer.org/#why-use-solayer) <a href="#why-use-solayer" id="why-use-solayer"></a> | ||
|
||
Solana users who have staked their SOL either natively or with a liquid staking service, and who are also seeking additional rewards on top of their staking rewards, may benefit from committing their already-staked assets to Solayer's restaking protocol. In doing so, they will contribute to the security of a multitude of decentralized applications which will each repay the favor with some reward for users. | ||
|
||
Developers interested in creating new decentralized applications that require networks of validators, may find that by using Solayer they can focus on building their applications instead of launching new trust networks from scratch. These services built with Solayer will also benefit from superior economic security than if they had launched their own network of validators. | ||
|
||
\ | ||
|
||
|
||
### **What is shared validator network?** | ||
|
||
Eigenlayer initiated the restaking concept on Ethereum, allowing ETH to be used as a restake asset to bolster the security of other networks. Building on this innovation, Solayer emerges as a shared validator network aimed at enhancing the security mechanisms of decentralized networks, beginning with Solana. Rather than creating new assets or chains, restaking leverages the established economic security of networks like Ethereum and Solana. This approach provides an efficient and interoperable system that significantly scales up economic security across the blockchain ecosystem. | ||
|
||
### The rudimentary problems of cryptoeconomic security | ||
|
||
As the blockchain landscape expands with the emergence of more Layer 1 networks, we're witnessing not just a fragmentation of liquidity but also a dispersion of decentralized trust. The collateral used in these networks is typically dedicated solely to securing the Layer 1, neglecting other decentralized or off-chain services. This leads to inefficiencies in both liquidity and trust. Moreover, the inherent design of Proof of Stake (PoS) systems requires developers to establish a network effect of trust: liquidity, validators, investors, and more, to ensure the network's integrity and functionality. The analogy applies to the same as rather than building on top of AWS, developers need to set up their own development infrastructure, from operating system, programming language, web application platform, database, and other services. | ||
|
||
### **Solana’s unique advantage** | ||
|
||
Solayer aims to become a market leader in shared security protocols by leveraging its first-mover advantage, fast execution environment, and strong community alignment. With the ability to leverage Solana's parallel processing and high-speed execution, Solayer is well-suited for computationally intensive applications like gaming and AI/ML. Its competitive pricing and low latency make it a strong contender against other restaking platforms. Solana's large and decentralized proof-of-stake chain, with a market capitalization of over $35 billion and more than 1,400 nodes, provides a solid foundation for Solayer. The introduction of MEV-Boost to the Solana ecosystem through Solayer could enhance block construction efficiency and increase yield advantages, making Solana staking even more attractive. Solayer's speed and pricing advantages are expected to enable new applications beyond traditional security constraints. With full ecosystem support from Solana to Eigenlayer and the potential for the fastest execution environment with upcoming off-chain compute and ZK co-processors, Solayer is poised to offer high-quality security and attract active users for application developers. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Table of contents | ||
|
||
* [Introduction](README.md) | ||
* [Overview](overview/README.md) | ||
* [Page](overview/page.md) | ||
* [Key Terms and Concepts](overview/key-terms-and-concepts.md) | ||
* [Protocol Features](overview/protocol-features.md) | ||
* [Support](overview/support.md) | ||
* [Whitepaper](overview/whitepaper.md) | ||
* [Products](products/README.md) | ||
* [Restaking](products/restaking.md) | ||
* [Basket Restaking](products/basket-restaking.md) | ||
* [Operators](products/operators.md) | ||
* [AVS](products/avs.md) | ||
* [Governance](governance/README.md) | ||
* [Multisigature Committees](governance/multisigature-committees.md) | ||
* [Security](security/README.md) | ||
* [Audits](security/audits.md) | ||
* [Bug Bounty](security/bug-bounty.md) | ||
* [Withdrawal Delays](security/withdrawal-delays.md) | ||
* [Contracts](contracts.md) | ||
* [FAQ](faq.md) | ||
* [Informational](informational/README.md) | ||
* [Brand Kits](informational/brand-kits.md) | ||
* [Terms and Services](informational/terms-and-services.md) | ||
* [Untitled](informational/untitled.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Contracts | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# FAQ | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Governance | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# Multisigature Committees | ||
|
||
Solayer DAO is governed via the three-prong to ensure trustless checks and balances: Treasury, Operations, and Emergency. In addition, the Solayer smart contracts are upgradable by functionality, as well as other adjustable parameters, such as the ability to pause or upgrade. The three committes oversee protocol upgrades, adjustments, and emergency pauses.  | ||
|
||
### Operational Multisigature | ||
|
||
The operational multisig oversees one of the core developments of Solayer Governance. It is a 3/5 threshold multisig that can execute routine upgrades and maintenance that enforce a minimum 7-day delay on all safety-critical actiosn. It can also pause Solayer contracts in emergency situations.  | ||
|
||
### Treasury Multisigature  | ||
|
||
The Community Multisig is a 9/13 multisig composed of members of the cryptoeconomic community. In normal circumstances, the signers of the Community Multisig will simply act as observers, receiving regular updates on the Operations Multisig’s transactions, including notifications of the Operations Multisig queuing new time-locked actions. In extraordinary circumstances, the Community Multisig can perform emergency actions, including immediately executing time-critical upgrades or replacing the Operations Multisig in the event of private key compromise. | ||
|
||
Members include:  | ||
|
||
### Executor Multisig  | ||
|
||
### Emergency | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Informational | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Brand Kits | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Terms and Services | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Untitled | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# Overview | ||
|
||
|
||
|
||
<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td>Key Terms and Concepts </td><td></td><td><a href="key-terms-and-concepts.md">key-terms-and-concepts.md</a></td></tr><tr><td></td><td>Protocol Features </td><td></td><td><a href="protocol-features.md">protocol-features.md</a></td></tr><tr><td></td><td>Support </td><td></td><td><a href="support.md">support.md</a></td></tr><tr><td></td><td>Whitepaper </td><td></td><td><a href="whitepaper.md">whitepaper.md</a></td></tr></tbody></table> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# Key Terms and Concepts | ||
|
||
1. **Liquid Staking Token (LST):** A token representing a staked asset that remains liquid, allowing holders to participate in DeFi activities without unstaking. | ||
2. **Liquid Restaking Token (LRT):** A token representing a restaked asset that maintains liquidity, enabling holders to engage in decentralized finance while the asset is restaked. | ||
3. **Restaking:** The process of staking an already staked asset on a different network or protocol to enhance security and earn additional rewards. | ||
4. **Liquid Restaking Basket:** A collection of liquid restaking tokens that allows investors to diversify their restaked assets while maintaining liquidity. | ||
5. **Shared Validator Network:** A network of validators that pool resources to secure multiple blockchains, increasing efficiency and security. | ||
6. **sSOL:** A specific token that represents staked Solana (SOL) in a liquid staking protocol, allowing holders to earn staking rewards while maintaining liquidity. | ||
7. **Slashing:** A penalty mechanism in proof-of-stake networks where a portion of a validator's stake is forfeited for malicious behavior or network violations. | ||
8. **Restake Withdrawal:** The process of withdrawing assets from a restaking position, typically involving the conversion of liquid restaking tokens back into the original asset. | ||
9. **Withdrawal delay:** The time period required for the withdrawal process to complete, often implemented to ensure network security. | ||
10. **Deposit:** The act of placing assets into a staking or restaking protocol to earn rewards and participate in network security. | ||
11. **Unrestake:** The process of removing assets from a restaking position, converting liquid restaking tokens back into the original asset. | ||
12. **Restake points:** Points or credits earned through restaking that may influence rewards, governance, or other aspects of the protocol. | ||
13. **Unstake penalty:** A penalty incurred for unstaking or unrestaking assets before a specified period, often implemented to ensure network stability. | ||
|
||
Points redistribution:  | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# Page | ||
|
||
#### What is an AVS?[](https://docs.solayer.org/overview/basics#what-is-an-avs) <a href="#what-is-an-avs" id="what-is-an-avs"></a> | ||
|
||
There exists a design space of distributed applications that require active validation of their rules in ways that cannot be sufficiently implemented using smart contracts on programmable blockchains. These are services like data availability systems, oracle networks, cross-chain bridges, and more. This kind of distributed application is commonly referred to as an _actively validated service_, or AVS, a term coined by the EigenLayer team. | ||
|
||
AVSs face several major challenges to the security of their protocols. For instance, each must bootstrap an independent network of protocol participants and incentivize honest behavior. Often this involves the creation of a digital asset native to the AVS network or heavy permissioning, both approaches having a myriad of challenges on their own. In cases where several AVSs are secured by their own native assets, they do not share their security. This means that this approach to distributed applications results in weaker, more fragmented economic security than the traditional approach of smart contracts running on one blockchain network. | ||
|
||
Restaking is a mechanism which offers solutions to these problems, enabling AVSs to share economic security and collectively leverage the security of established proof-of-stake networks. | ||
|
||
#### What is restaking?[](https://docs.solayer.org/overview/basics#what-is-restaking) <a href="#what-is-restaking" id="what-is-restaking"></a> | ||
|
||
On decentralized blockchain networks secured by proof-of-stake, such as Ethereum and Solana, participants have the ability to _stake_ some of their assets into the network. In exchange, they receive the opportunity to validate that the activity on the network behaves according to some set of rules that comprise the network's protocol. If one of these validators attempts to declare spurious activity as genuine, other validators can destroy the dishonest validator's staked assets. Validators are rewarded with more digital assets by the protocol for their contribution to the security of the network. | ||
|
||
On some of these proof-of-stake networks, validators can use an application-layer _restaking_ system to opt-in to validate activity against additional sets of rules that define additional protocols. These protocols can provide validators with more rewards than they would otherwise earn by solely validating for the network's base protocol. If validators break the additional rules they agreed to, other participants in the restaking system can destroy their restaked assets. | ||
|
||
Constructing an AVS as a protocol secured by a restaking system sidesteps many of the hurdles it might face, as outlined in the previous section. This reduces the barriers to entry for new AVSs, creating the conditions for exiciting innovation to happen. | ||
|
||
#### Why restake on Solana?[](https://docs.solayer.org/overview/basics#why-restake-on-solana) <a href="#why-restake-on-solana" id="why-restake-on-solana"></a> | ||
|
||
AVSs built on top of the security of restaked Solana receive a great deal of indirect benefit from Solana's high throughput and cheap blockspace. When these services need to signal or settle anything on-chain, they can do so quickly and cheaply. This opens up greater possibilities for the kinds of services that can be built when compared against similar restaking solutions built on less performant networks like Ethereum. | ||
|
||
[\ | ||
](https://docs.solayer.org/category/overview)Liquid staking tokens[](https://docs.solayer.org/overview/additional-features#liquid-staking-tokens) | ||
|
||
Liquid staking services are a wildly popular way for users who would like to stake their assets to receive a liquid token in exchange while their assets remain locked. These applications often serve an additional purpose as a way for users who don't have the minimum capital required to stake and become a validator to instead pool their capital with others to reach the minimum stake, and often also delegate operation of the validator software to a third party. Solayer, in addition to supporting users who provide native SOL for staking and restaking, supports the restaking of several liquid staking tokens linked to already-staked SOL. As of now, the supported liquid staking tokens are JitoSOL, mSOL, and bSOL. | ||
|
||
#### Delegated AVS operation[](https://docs.solayer.org/overview/additional-features#delegated-avs-operation) <a href="#delegated-avs-operation" id="delegated-avs-operation"></a> | ||
|
||
Running software to validate a variety of AVS protocols is a task that is best left for sophisticated users who are capable of running the software efficiently and reducing the risk of service distruption. Users simply looking to receive rewards for committing their assets to be restaked may not be sufficiently sophisticated operators of AVS software to operate it safely. Or, users might simply prefer to avoid the inconvenience of running AVS software themselves. | ||
|
||
In any case, it is possible for users restaking their assets to delegate the operation of AVS software to a sophisticated entity willing to operate the AVS software on their behalf. | ||
|
||
\ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Protocol Features | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Support | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Whitepaper | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Products | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# AVS | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Basket Restaking | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Operators | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Restaking | ||
|
||
#### Liquid Staking vs Native Staking | ||
|
||
1. **Native Staking:** In native staking, users directly stake their tokens the consensus layer to support network security and earn staking rewards. Once staked, staked tokens are locked for a certain period and cannot be easily accessed or traded. Users usually run Solana validator node to natively stake to secure the network.  | ||
2. **Liquid Staking:** Liquid staking addresses the liquidity issue by issuing a representative token (such as an LST) in exchange for the staked tokens. These representative tokens can be traded, used in DeFi protocols, or even staked further while the original tokens remain locked in the staking contract. This allows users to maintain liquidity and participate in other opportunities without sacrificing their staking rewards. | ||
|
||
#### Liquid Restaking vs Native Restaking | ||
|
||
1. **Liquid** **Restaking**: the process of depositing liquid staking tokens (LSTs) into the Solayer smart contracts. At this time, the protocol supports the following LSTs: | ||
|
||
* mSOL (marginSOL) | ||
* bSOL | ||
* JITO-SOL  | ||
* mSOL (marinadeSOL) | ||
|
||
2. **Native** **Restaking**: Native restaking describes the process of setting an Solana validator's withdraw Credential to Solayer's smart contracts (SolayerPod). You must operate an Solana Validator node in order to participate in Native Restaking. | ||
|
||
If you would like to have your LST included in the Solayer restaking platform, please fill out this form:  | ||
|
||
## Introducing Liquid Restaking Token | ||
|
||
Traditionally, restaked assets, whether liquid or native, are locked and thus inaccessible for trading or use on other platforms. Solayer introduces Liquid Restaking Token (LRT) that remains accessible while being restaked to validate other services. Users who restake and receive LRT in the form of sSOL can actively participate in various DeFi platforms. Currently, sSOL is listed on the following exchanges: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Security | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
# Audits | ||
|
||
Security is a core development effort of Solayer's long-hauled commitment to building secure and scalable crypto-economic infrastructure. Here we present 2 audit reports:  | ||
|
||
1. Ottersec | ||
2. C4  | ||
|
||
Despite having thorough security reviews, we encourage community members, technical hackers, and researchers to comprehensively review the contracts, and report to [email protected], or via proper channels if any bugs have been identified.  |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Bug Bounty | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Withdrawal Delays | ||
|