diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000..45ae2b1 Binary files /dev/null and b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png index 45ae2b1..3784e2d 100644 Binary files a/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png and b/.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png index 3784e2d..9b83b5b 100644 Binary files a/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png and b/.gitbook/assets/image (1) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (1) (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1) (1).png index 9b83b5b..2ea3e9e 100644 Binary files a/.gitbook/assets/image (1) (1) (1) (1) (1).png and b/.gitbook/assets/image (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (1) (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1) (1).png index 2ea3e9e..e29f259 100644 Binary files a/.gitbook/assets/image (1) (1) (1) (1).png and b/.gitbook/assets/image (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (1) (1) (1).png b/.gitbook/assets/image (1) (1) (1).png index e29f259..5e41949 100644 Binary files a/.gitbook/assets/image (1) (1) (1).png and b/.gitbook/assets/image (1) (1) (1).png differ diff --git a/.gitbook/assets/image (1) (1).png b/.gitbook/assets/image (1) (1).png index 5e41949..0582d02 100644 Binary files a/.gitbook/assets/image (1) (1).png and b/.gitbook/assets/image (1) (1).png differ diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png index 0582d02..a6e9e73 100644 Binary files a/.gitbook/assets/image (1).png and b/.gitbook/assets/image (1).png differ diff --git a/.gitbook/assets/image (10) (2).png b/.gitbook/assets/image (10) (2).png new file mode 100644 index 0000000..7400622 Binary files /dev/null and b/.gitbook/assets/image (10) (2).png differ diff --git a/.gitbook/assets/image (10).png b/.gitbook/assets/image (10).png index 7400622..ee5ccbb 100644 Binary files a/.gitbook/assets/image (10).png and b/.gitbook/assets/image (10).png differ diff --git a/.gitbook/assets/image (11) (2).png b/.gitbook/assets/image (11) (2).png new file mode 100644 index 0000000..de20f72 Binary files /dev/null and b/.gitbook/assets/image (11) (2).png differ diff --git a/.gitbook/assets/image (11).png b/.gitbook/assets/image (11).png index de20f72..eb694cc 100644 Binary files a/.gitbook/assets/image (11).png and b/.gitbook/assets/image (11).png differ diff --git a/.gitbook/assets/image (12) (1).png b/.gitbook/assets/image (12) (1).png new file mode 100644 index 0000000..fe248c3 Binary files /dev/null and b/.gitbook/assets/image (12) (1).png differ diff --git a/.gitbook/assets/image (12).png b/.gitbook/assets/image (12).png index fe248c3..fce2300 100644 Binary files a/.gitbook/assets/image (12).png and b/.gitbook/assets/image (12).png differ diff --git a/.gitbook/assets/image (13) (1).png b/.gitbook/assets/image (13) (1).png new file mode 100644 index 0000000..98cd886 Binary files /dev/null and b/.gitbook/assets/image (13) (1).png differ diff --git a/.gitbook/assets/image (13).png b/.gitbook/assets/image (13).png index 98cd886..ab7888b 100644 Binary files a/.gitbook/assets/image (13).png and b/.gitbook/assets/image (13).png differ diff --git a/.gitbook/assets/image (14) (1).png b/.gitbook/assets/image (14) (1).png new file mode 100644 index 0000000..98cd886 Binary files /dev/null and b/.gitbook/assets/image (14) (1).png differ diff --git a/.gitbook/assets/image (14).png b/.gitbook/assets/image (14).png index 98cd886..f99105a 100644 Binary files a/.gitbook/assets/image (14).png and b/.gitbook/assets/image (14).png differ diff --git a/.gitbook/assets/image (15) (1).png b/.gitbook/assets/image (15) (1).png new file mode 100644 index 0000000..d1c1cda Binary files /dev/null and b/.gitbook/assets/image (15) (1).png differ diff --git a/.gitbook/assets/image (15).png b/.gitbook/assets/image (15).png index d1c1cda..b37dbae 100644 Binary files a/.gitbook/assets/image (15).png and b/.gitbook/assets/image (15).png differ diff --git a/.gitbook/assets/image (16) (1).png b/.gitbook/assets/image (16) (1).png new file mode 100644 index 0000000..9b83b5b Binary files /dev/null and b/.gitbook/assets/image (16) (1).png differ diff --git a/.gitbook/assets/image (16).png b/.gitbook/assets/image (16).png index 9b83b5b..330d0c1 100644 Binary files a/.gitbook/assets/image (16).png and b/.gitbook/assets/image (16).png differ diff --git a/.gitbook/assets/image (17) (1).png b/.gitbook/assets/image (17) (1).png new file mode 100644 index 0000000..ed4e211 Binary files /dev/null and b/.gitbook/assets/image (17) (1).png differ diff --git a/.gitbook/assets/image (17).png b/.gitbook/assets/image (17).png index ed4e211..2dcbf84 100644 Binary files a/.gitbook/assets/image (17).png and b/.gitbook/assets/image (17).png differ diff --git a/.gitbook/assets/image (18) (1).png b/.gitbook/assets/image (18) (1).png new file mode 100644 index 0000000..b24c385 Binary files /dev/null and b/.gitbook/assets/image (18) (1).png differ diff --git a/.gitbook/assets/image (18).png b/.gitbook/assets/image (18).png index b24c385..cbabf83 100644 Binary files a/.gitbook/assets/image (18).png and b/.gitbook/assets/image (18).png differ diff --git a/.gitbook/assets/image (19) (1).png b/.gitbook/assets/image (19) (1).png new file mode 100644 index 0000000..b24c385 Binary files /dev/null and b/.gitbook/assets/image (19) (1).png differ diff --git a/.gitbook/assets/image (19).png b/.gitbook/assets/image (19).png index b24c385..cbe04db 100644 Binary files a/.gitbook/assets/image (19).png and b/.gitbook/assets/image (19).png differ diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000..8b76598 Binary files /dev/null and b/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1).png index 8b76598..4865f09 100644 Binary files a/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1).png and b/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png index 4865f09..d80d07c 100644 Binary files a/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png and b/.gitbook/assets/image (2) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (2) (1) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1) (1).png index d80d07c..cf0c21d 100644 Binary files a/.gitbook/assets/image (2) (1) (1) (1) (1).png and b/.gitbook/assets/image (2) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (2) (1) (1) (1).png b/.gitbook/assets/image (2) (1) (1) (1).png index cf0c21d..e29f259 100644 Binary files a/.gitbook/assets/image (2) (1) (1) (1).png and b/.gitbook/assets/image (2) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (2) (1) (1).png b/.gitbook/assets/image (2) (1) (1).png index e29f259..8aaaff6 100644 Binary files a/.gitbook/assets/image (2) (1) (1).png and b/.gitbook/assets/image (2) (1) (1).png differ diff --git a/.gitbook/assets/image (2) (1).png b/.gitbook/assets/image (2) (1).png index 8aaaff6..7e99444 100644 Binary files a/.gitbook/assets/image (2) (1).png and b/.gitbook/assets/image (2) (1).png differ diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png index 7e99444..2513032 100644 Binary files a/.gitbook/assets/image (2).png and b/.gitbook/assets/image (2).png differ diff --git a/.gitbook/assets/image (20) (1).png b/.gitbook/assets/image (20) (1).png new file mode 100644 index 0000000..97e5f07 Binary files /dev/null and b/.gitbook/assets/image (20) (1).png differ diff --git a/.gitbook/assets/image (20).png b/.gitbook/assets/image (20).png index 97e5f07..ad51ad5 100644 Binary files a/.gitbook/assets/image (20).png and b/.gitbook/assets/image (20).png differ diff --git a/.gitbook/assets/image (21) (1).png b/.gitbook/assets/image (21) (1).png new file mode 100644 index 0000000..04c09e8 Binary files /dev/null and b/.gitbook/assets/image (21) (1).png differ diff --git a/.gitbook/assets/image (21).png b/.gitbook/assets/image (21).png index 04c09e8..35f7937 100644 Binary files a/.gitbook/assets/image (21).png and b/.gitbook/assets/image (21).png differ diff --git a/.gitbook/assets/image (22) (1).png b/.gitbook/assets/image (22) (1).png new file mode 100644 index 0000000..bccc862 Binary files /dev/null and b/.gitbook/assets/image (22) (1).png differ diff --git a/.gitbook/assets/image (22).png b/.gitbook/assets/image (22).png index bccc862..b0fbcb5 100644 Binary files a/.gitbook/assets/image (22).png and b/.gitbook/assets/image (22).png differ diff --git a/.gitbook/assets/image (23) (1).png b/.gitbook/assets/image (23) (1).png new file mode 100644 index 0000000..bccc862 Binary files /dev/null and b/.gitbook/assets/image (23) (1).png differ diff --git a/.gitbook/assets/image (23).png b/.gitbook/assets/image (23).png index bccc862..0856ca3 100644 Binary files a/.gitbook/assets/image (23).png and b/.gitbook/assets/image (23).png differ diff --git a/.gitbook/assets/image (24) (1).png b/.gitbook/assets/image (24) (1).png new file mode 100644 index 0000000..bccc862 Binary files /dev/null and b/.gitbook/assets/image (24) (1).png differ diff --git a/.gitbook/assets/image (24).png b/.gitbook/assets/image (24).png index bccc862..03130a2 100644 Binary files a/.gitbook/assets/image (24).png and b/.gitbook/assets/image (24).png differ diff --git a/.gitbook/assets/image (25) (1).png b/.gitbook/assets/image (25) (1).png new file mode 100644 index 0000000..451828b Binary files /dev/null and b/.gitbook/assets/image (25) (1).png differ diff --git a/.gitbook/assets/image (25).png b/.gitbook/assets/image (25).png index 451828b..03130a2 100644 Binary files a/.gitbook/assets/image (25).png and b/.gitbook/assets/image (25).png differ diff --git a/.gitbook/assets/image (26) (1).png b/.gitbook/assets/image (26) (1).png new file mode 100644 index 0000000..451828b Binary files /dev/null and b/.gitbook/assets/image (26) (1).png differ diff --git a/.gitbook/assets/image (26).png b/.gitbook/assets/image (26).png index 451828b..deb2bdf 100644 Binary files a/.gitbook/assets/image (26).png and b/.gitbook/assets/image (26).png differ diff --git a/.gitbook/assets/image (27) (1).png b/.gitbook/assets/image (27) (1).png new file mode 100644 index 0000000..451828b Binary files /dev/null and b/.gitbook/assets/image (27) (1).png differ diff --git a/.gitbook/assets/image (27).png b/.gitbook/assets/image (27).png index 451828b..3b56cde 100644 Binary files a/.gitbook/assets/image (27).png and b/.gitbook/assets/image (27).png differ diff --git a/.gitbook/assets/image (28) (1).png b/.gitbook/assets/image (28) (1).png new file mode 100644 index 0000000..cb3f1c6 Binary files /dev/null and b/.gitbook/assets/image (28) (1).png differ diff --git a/.gitbook/assets/image (28).png b/.gitbook/assets/image (28).png index cb3f1c6..f505d37 100644 Binary files a/.gitbook/assets/image (28).png and b/.gitbook/assets/image (28).png differ diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000..8b76598 Binary files /dev/null and b/.gitbook/assets/image (3) (1) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1) (1).png index 8b76598..0f95f54 100644 Binary files a/.gitbook/assets/image (3) (1) (1) (1) (1) (1).png and b/.gitbook/assets/image (3) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (3) (1) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1) (1).png index 0f95f54..0551002 100644 Binary files a/.gitbook/assets/image (3) (1) (1) (1) (1).png and b/.gitbook/assets/image (3) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (3) (1) (1) (1).png b/.gitbook/assets/image (3) (1) (1) (1).png index 0551002..e29f259 100644 Binary files a/.gitbook/assets/image (3) (1) (1) (1).png and b/.gitbook/assets/image (3) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (3) (1) (1).png b/.gitbook/assets/image (3) (1) (1).png index e29f259..dfe9d61 100644 Binary files a/.gitbook/assets/image (3) (1) (1).png and b/.gitbook/assets/image (3) (1) (1).png differ diff --git a/.gitbook/assets/image (3) (1).png b/.gitbook/assets/image (3) (1).png index dfe9d61..fa3fa52 100644 Binary files a/.gitbook/assets/image (3) (1).png and b/.gitbook/assets/image (3) (1).png differ diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png index fa3fa52..22ecc74 100644 Binary files a/.gitbook/assets/image (3).png and b/.gitbook/assets/image (3).png differ diff --git a/.gitbook/assets/image (4) (1) (1) (1) (1) (1).png b/.gitbook/assets/image (4) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000..0ff3860 Binary files /dev/null and b/.gitbook/assets/image (4) (1) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (4) (1) (1) (1) (1).png b/.gitbook/assets/image (4) (1) (1) (1) (1).png index 0ff3860..0551002 100644 Binary files a/.gitbook/assets/image (4) (1) (1) (1) (1).png and b/.gitbook/assets/image (4) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (4) (1) (1) (1).png b/.gitbook/assets/image (4) (1) (1) (1).png index 0551002..c1c57ed 100644 Binary files a/.gitbook/assets/image (4) (1) (1) (1).png and b/.gitbook/assets/image (4) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (4) (1) (1).png b/.gitbook/assets/image (4) (1) (1).png index c1c57ed..048514f 100644 Binary files a/.gitbook/assets/image (4) (1) (1).png and b/.gitbook/assets/image (4) (1) (1).png differ diff --git a/.gitbook/assets/image (4) (1).png b/.gitbook/assets/image (4) (1).png index 048514f..e0bfb90 100644 Binary files a/.gitbook/assets/image (4) (1).png and b/.gitbook/assets/image (4) (1).png differ diff --git a/.gitbook/assets/image (4).png b/.gitbook/assets/image (4).png index e0bfb90..653ba18 100644 Binary files a/.gitbook/assets/image (4).png and b/.gitbook/assets/image (4).png differ diff --git a/.gitbook/assets/image (5) (1) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1) (1).png new file mode 100644 index 0000000..db65c3c Binary files /dev/null and b/.gitbook/assets/image (5) (1) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (5) (1) (1) (1).png b/.gitbook/assets/image (5) (1) (1) (1).png index db65c3c..c1c57ed 100644 Binary files a/.gitbook/assets/image (5) (1) (1) (1).png and b/.gitbook/assets/image (5) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (5) (1) (1).png b/.gitbook/assets/image (5) (1) (1).png index c1c57ed..ef13cee 100644 Binary files a/.gitbook/assets/image (5) (1) (1).png and b/.gitbook/assets/image (5) (1) (1).png differ diff --git a/.gitbook/assets/image (5) (1).png b/.gitbook/assets/image (5) (1).png index ef13cee..3084b98 100644 Binary files a/.gitbook/assets/image (5) (1).png and b/.gitbook/assets/image (5) (1).png differ diff --git a/.gitbook/assets/image (5).png b/.gitbook/assets/image (5).png index 3084b98..9f61364 100644 Binary files a/.gitbook/assets/image (5).png and b/.gitbook/assets/image (5).png differ diff --git a/.gitbook/assets/image (6) (1) (1) (1).png b/.gitbook/assets/image (6) (1) (1) (1).png new file mode 100644 index 0000000..db65c3c Binary files /dev/null and b/.gitbook/assets/image (6) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (6) (1) (1).png b/.gitbook/assets/image (6) (1) (1).png index db65c3c..ab097a3 100644 Binary files a/.gitbook/assets/image (6) (1) (1).png and b/.gitbook/assets/image (6) (1) (1).png differ diff --git a/.gitbook/assets/image (6) (1).png b/.gitbook/assets/image (6) (1).png index ab097a3..eac7a5c 100644 Binary files a/.gitbook/assets/image (6) (1).png and b/.gitbook/assets/image (6) (1).png differ diff --git a/.gitbook/assets/image (6).png b/.gitbook/assets/image (6).png index eac7a5c..bbd22b6 100644 Binary files a/.gitbook/assets/image (6).png and b/.gitbook/assets/image (6).png differ diff --git a/.gitbook/assets/image (7) (1) (1) (1).png b/.gitbook/assets/image (7) (1) (1) (1).png new file mode 100644 index 0000000..db65c3c Binary files /dev/null and b/.gitbook/assets/image (7) (1) (1) (1).png differ diff --git a/.gitbook/assets/image (7) (1) (1).png b/.gitbook/assets/image (7) (1) (1).png index db65c3c..d46413a 100644 Binary files a/.gitbook/assets/image (7) (1) (1).png and b/.gitbook/assets/image (7) (1) (1).png differ diff --git a/.gitbook/assets/image (7) (1).png b/.gitbook/assets/image (7) (1).png index d46413a..385f7ce 100644 Binary files a/.gitbook/assets/image (7) (1).png and b/.gitbook/assets/image (7) (1).png differ diff --git a/.gitbook/assets/image (7).png b/.gitbook/assets/image (7).png index 385f7ce..bbd22b6 100644 Binary files a/.gitbook/assets/image (7).png and b/.gitbook/assets/image (7).png differ diff --git a/.gitbook/assets/image (8) (2).png b/.gitbook/assets/image (8) (2).png new file mode 100644 index 0000000..8f18b9d Binary files /dev/null and b/.gitbook/assets/image (8) (2).png differ diff --git a/.gitbook/assets/image (8).png b/.gitbook/assets/image (8).png index 8f18b9d..c42359e 100644 Binary files a/.gitbook/assets/image (8).png and b/.gitbook/assets/image (8).png differ diff --git a/.gitbook/assets/image (9) (2).png b/.gitbook/assets/image (9) (2).png new file mode 100644 index 0000000..a6ec39a Binary files /dev/null and b/.gitbook/assets/image (9) (2).png differ diff --git a/.gitbook/assets/image (9).png b/.gitbook/assets/image (9).png index a6ec39a..7c8c861 100644 Binary files a/.gitbook/assets/image (9).png and b/.gitbook/assets/image (9).png differ diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png index f505d37..42abecb 100644 Binary files a/.gitbook/assets/image.png and b/.gitbook/assets/image.png differ diff --git a/README.md b/README.md index fc18573..9c8ae39 100644 --- a/README.md +++ b/README.md @@ -1,17 +1,12 @@ -# What is Solayer - - +# What is Solayer?
Solayer is building the restaking network natively on Solana. -Solana as the _internet_ layer provides how data, trust, and money travel. Solayer leverages its economic security and premium execution as the _decentralized cloud infrastructure_ to enable a higher degree of consensus and blockspace customization for _application_ developers. +Solana serves as the internet layer, facilitating the seamless movement of data, trust, and money. Solayer leverages Solana’s economic security and superior execution capabilities as decentralized cloud infrastructure, enabling application developers to achieve a higher degree of consensus and blockspace customization. To realize this, Solayer is a two-pronged approach: -1. **Restaking**: ‌leverage the economic security of SOL to secure other systems -2. **Shared Validator Network**: Solana-centric networks sharing Solana security and infrastructure - -The Solayer team is developing the core primitives around modular shared security, and will open-source in 3 main stages. - +1. **Restaking**: ‌leverage the economic security of SOL to secure other systems. +2. **Shared Validator Network**: Solana-centric networks sharing Solana security and infrastructure. diff --git a/SUMMARY.md b/SUMMARY.md index a4edde2..1f6cc96 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -1,44 +1,67 @@ # Table of contents -* [What is Solayer](README.md) +* [What is Solayer?](README.md) +* [Why on Solana?](why-on-solana.md) * [First Principles](first-principles.md) -* [Litepapers](litepapers.md) -* [Overview](overview/README.md) - * [Key Terms and Concepts](overview/key-terms-and-concepts.md) - * [Support](overview/support.md) - * [What can be built on Solayer?](overview/what-can-be-built-on-solayer.md) -* [Restaking ](restaking/README.md) - * [Restaking Architecture](restaking/restaking-architecture.md) - * [Native SOL Restaking Tutorial](restaking/native-sol-restaking-tutorial.md) - * [LST Restaking](restaking/lst-restaking.md) - * [Unstaking Tutorial](restaking/unstaking-tutorial.md) - * [Unstake sSOL](restaking/unstake-ssol.md) - * [Unstaking Credit Deduction](restaking/unstaking-credit-deduction.md) -* [Endogenous AVS](endogenous-avs/README.md) - * [What is an AVS?](endogenous-avs/what-is-an-avs.md) - * [Solayer swQoS Infrastructure](endogenous-avs/solayer-swqos-infrastructure.md) - * [From Staked SOL to Endogenous AVS Tokens](endogenous-avs/from-staked-sol-to-endogenous-avs-tokens.md) - * [Super Liquidity](endogenous-avs/super-liquidity.md) - * [Delegation](endogenous-avs/delegation.md) -* [Restaking Epochs](restaking-epochs/README.md) - * [Epoch 0](restaking-epochs/epoch-0.md) - * [Epoch 1](restaking-epochs/epoch-1.md) - * [Epoch 2](restaking-epochs/epoch-2.md) -* [Solayer Valley Episodes](solayer-valley-episodes/README.md) - * [Episode 1: The Timebox Sanctuary](solayer-valley-episodes/episode-1-the-timebox-sanctuary.md) - * [Eligibility Guide](solayer-valley-episodes/eligibility-guide.md) - * [Rewards Claiming Guide](solayer-valley-episodes/rewards-claiming-guide.md) -* [Governance](governance/README.md) - * [Multisigature Committees](governance/multisigature-committees.md) -* [Security](security/README.md) - * [Audits](security/audits.md) -* [Solayer Programs](solayer-programs.md) -* [Informational](informational/README.md) - * [Brand Kit](informational/brand-kit.md) -* [FAQs](faqs.md) - -## Get Started - -* [To Use Ledger](get-started/to-use-ledger.md) -* [To Use Solflare](get-started/to-use-solflare.md) -* [To Use Phantom](get-started/to-use-phantom.md) + +## Solayer Overview + +* [Introduction](solayer-overview/introduction/README.md) + * [Official Links](solayer-overview/introduction/official-links.md) + * [FAQ](solayer-overview/introduction/faq.md) + * [Terms and Concepts](solayer-overview/introduction/terms-and-concepts.md) +* [Litepaper](solayer-overview/litepaper.md) +* [What is sSOL?](solayer-overview/what-is-ssol/README.md) + * [Liquidity](solayer-overview/what-is-ssol/liquidity.md) + * [sSOL in DeFi](solayer-overview/what-is-ssol/ssol-in-defi.md) + * [Trading & Rewards](solayer-overview/what-is-ssol/trading-and-rewards.md) +* [Restaking Guides](solayer-overview/restaking-guides/README.md) + * [Native SOL Restaking](solayer-overview/restaking-guides/native-sol-restaking/README.md) + * [Restaking Tutorial](solayer-overview/restaking-guides/native-sol-restaking/restaking-tutorial.md) + * [LST Restaking](solayer-overview/restaking-guides/lst-restaking/README.md) + * [LST Restaking Tutorial](solayer-overview/restaking-guides/lst-restaking/lst-restaking-tutorial.md) + * [Unstake sSOL](solayer-overview/restaking-guides/unstake-ssol/README.md) + * [Unstaking Tutorial](solayer-overview/restaking-guides/unstake-ssol/unstaking-tutorial.md) + * [Delegation](solayer-overview/restaking-guides/delegation.md) +* [Endogenous AVS](solayer-overview/endogenous-avs/README.md) + * [What is an AVS?](solayer-overview/endogenous-avs/what-is-an-avs.md) + * [Quality of Service](solayer-overview/endogenous-avs/quality-of-service.md) + * [Delegate Tokens](solayer-overview/endogenous-avs/delegate-tokens.md) + +## Community + +* [Restaking Epochs](community/restaking-epochs/README.md) + * [Epoch 0](community/restaking-epochs/epoch-0.md) + * [Epoch 1](community/restaking-epochs/epoch-1.md) + * [Epoch 2](community/restaking-epochs/epoch-2.md) +* [Solayer Valley Episodes](community/solayer-valley-episodes/README.md) + * [Episode 1](community/solayer-valley-episodes/episode-1.md) + * [Eligibility Guide](community/solayer-valley-episodes/eligibility-guide.md) + * [Rewards Claiming Guide](community/solayer-valley-episodes/rewards-claiming-guide.md) + * [Unstaking Credit Deduction](community/solayer-valley-episodes/unstaking-credit-deduction.md) + +## Developers Guides + +* [For Builders](developers-guides/for-builders/README.md) + * [Architecture](developers-guides/for-builders/architecture.md) + * [Building on Solayer](developers-guides/for-builders/building-on-solayer.md) + * [Solayer Programs](developers-guides/for-builders/solayer-programs.md) +* [Security](developers-guides/security/README.md) + * [Audits](developers-guides/security/audits.md) + * [Multisig Committee](developers-guides/security/multisig-committee.md) + * [Bounties](developers-guides/security/bounties.md) + +## Informational + +* [Brand Kit](informational/brand-kit.md) +* [Partnerships](informational/partnerships.md) +* [How to use?](informational/how-to-use/README.md) + * [Use Ledger](informational/how-to-use/use-ledger.md) + * [Use Phantom](informational/how-to-use/use-phantom.md) + +## Quick Links + +* [Website ](https://solayer.org/) +* [Discord](https://discord.com/invite/solayerlabs) +* [Twitter](https://twitter.com/solayer\_labs) +* [Youtube](https://www.youtube.com/@solayer\_labs) diff --git a/community/restaking-epochs/README.md b/community/restaking-epochs/README.md new file mode 100644 index 0000000..b105ec6 --- /dev/null +++ b/community/restaking-epochs/README.md @@ -0,0 +1,31 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Restaking Epochs + +The **Solayer Restaking Epochs are** designed to ensure the safety and security of our protocol developments while optimizing for the best user experience. Through these carefully managed phases we provide a secure and efficient environment for participants, facilitating smooth interactions and maximizing benefits. These epochs have already seen significant engagement, with millions in restaked deposits, demonstrating the robust interest and trust in our platform. + +
+ +{% content-ref url="epoch-0.md" %} +[epoch-0.md](epoch-0.md) +{% endcontent-ref %} + +{% content-ref url="epoch-1.md" %} +[epoch-1.md](epoch-1.md) +{% endcontent-ref %} + +{% content-ref url="epoch-2.md" %} +[epoch-2.md](epoch-2.md) +{% endcontent-ref %} diff --git a/restaking-epochs/epoch-0.md b/community/restaking-epochs/epoch-0.md similarity index 100% rename from restaking-epochs/epoch-0.md rename to community/restaking-epochs/epoch-0.md diff --git a/restaking-epochs/epoch-1.md b/community/restaking-epochs/epoch-1.md similarity index 100% rename from restaking-epochs/epoch-1.md rename to community/restaking-epochs/epoch-1.md diff --git a/restaking-epochs/epoch-2.md b/community/restaking-epochs/epoch-2.md similarity index 100% rename from restaking-epochs/epoch-2.md rename to community/restaking-epochs/epoch-2.md diff --git a/community/solayer-valley-episodes/README.md b/community/solayer-valley-episodes/README.md new file mode 100644 index 0000000..f5c2dc2 --- /dev/null +++ b/community/solayer-valley-episodes/README.md @@ -0,0 +1,35 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Solayer Valley Episodes + +Welcome to Solayer Valley, an interactive campaign streamed in episodic adventures. The valley offers eligible participants the opportunity to redeem hidden gems for future retroactive claims, tied to major product and feature milestones. Each episode represents an alternate world where we unlock and experience these milestones together. Participation in these episodes is the sole method to receive future retroactive rewards. + +
+ +{% content-ref url="episode-1.md" %} +[episode-1.md](episode-1.md) +{% endcontent-ref %} + +{% content-ref url="eligibility-guide.md" %} +[eligibility-guide.md](eligibility-guide.md) +{% endcontent-ref %} + +{% content-ref url="rewards-claiming-guide.md" %} +[rewards-claiming-guide.md](rewards-claiming-guide.md) +{% endcontent-ref %} + +{% content-ref url="unstaking-credit-deduction.md" %} +[unstaking-credit-deduction.md](unstaking-credit-deduction.md) +{% endcontent-ref %} diff --git a/community/solayer-valley-episodes/eligibility-guide.md b/community/solayer-valley-episodes/eligibility-guide.md new file mode 100644 index 0000000..790fdef --- /dev/null +++ b/community/solayer-valley-episodes/eligibility-guide.md @@ -0,0 +1,21 @@ +# Eligibility Guide + +1. Go to [https://app.solayer.org/valley](https://app.solayer.org/valley) and connect your wallet. + +
+ +2. Select one of the wallet options that is available for you. + +
+ +3. Sing the message by clicking on “Confirm”. + +
+ +4. Check whether you meet at least 3 requirements to be eligible... + +
+ +5. ... or not eligible. + +
diff --git a/solayer-valley-episodes/episode-1-the-timebox-sanctuary.md b/community/solayer-valley-episodes/episode-1.md similarity index 74% rename from solayer-valley-episodes/episode-1-the-timebox-sanctuary.md rename to community/solayer-valley-episodes/episode-1.md index c0ca885..81857b7 100644 --- a/solayer-valley-episodes/episode-1-the-timebox-sanctuary.md +++ b/community/solayer-valley-episodes/episode-1.md @@ -1,6 +1,6 @@ -# Episode 1: The Timebox Sanctuary +# Episode 1 -The Timebox Sanctuary blends shimmering brass with aged wood, creating an enchanting environment. Following the successful launch of the restaking epochs on May 16th, with $50M in restaked deposits across 2 epochs, Episode 1 focuses on rewarding the Solayer community throughout these restake epochs. Eligible members can stream, participate, and claim rewards. Episode 1 streaming is time-capped, starting on \[redacted] and ending on July 4th, with 28,308 minutes remaining until its conclusion. +The Timebox Sanctuary (Episode 1) blends shimmering brass with aged wood, creating an enchanting environment. Following the successful launch of the restaking epochs on May 16th, with $50M in restaked deposits across 2 epochs, Episode 1 focuses on rewarding the Solayer community throughout these restake epochs. Eligible members can stream, participate, and claim rewards. Episode 1 streaming is time-capped, starting on \[redacted] and ending on July 4th, with 28,308 minutes remaining until its conclusion. ### **Prerequisites to Participate** diff --git a/community/solayer-valley-episodes/rewards-claiming-guide.md b/community/solayer-valley-episodes/rewards-claiming-guide.md new file mode 100644 index 0000000..ea2bb0b --- /dev/null +++ b/community/solayer-valley-episodes/rewards-claiming-guide.md @@ -0,0 +1,24 @@ +# Rewards Claiming Guide + +1. **If eligible, you will be able to enter the Valley in order to claim your rewards.** + +
+ +2. **Claim your Rewards (1/4):** your rank and percentile will be displayed. Click on "Claim" to proceed. + +
+3. **Claim your Rewards (2/4):** any extra boosts that you have accumulated so far. + +
+ +4. **Claim your Rewards (3/4):** claim all the points from your referrals. + +
+ +5. **Claim your Rewards (4/4):** get a mystery box that will be revealed after Episode 1. + +
+ +6. Congrats! You've successfully claimed all your rewards. Now, let's move on to Episode 2! + +
diff --git a/restaking/unstaking-credit-deduction.md b/community/solayer-valley-episodes/unstaking-credit-deduction.md similarity index 94% rename from restaking/unstaking-credit-deduction.md rename to community/solayer-valley-episodes/unstaking-credit-deduction.md index fccd9d7..d2b2c91 100644 --- a/restaking/unstaking-credit-deduction.md +++ b/community/solayer-valley-episodes/unstaking-credit-deduction.md @@ -29,7 +29,7 @@ When you stake SOL (or any other LST on Solayer) in a pool, you earn accrue cred * **Credits Earned:** 1000 (for simplicity, assume all are native SOL with 4x multiplier applied) * **Deduction: (10 / 100 \* 1000) \* 0.5 = 50 credits** -So, if you generated 1000 credits on the 10 SOL deposited, 500 credits will be deducted, leaving you with 500 credits. +So, if you generated 1000 credits on the 10 SOL deposited, 50 credits will be deducted, leaving you with 950 credits. ### _**Example 2: Withdrawing 20% of Staked SOL**_ diff --git a/developers-guides/for-builders/README.md b/developers-guides/for-builders/README.md new file mode 100644 index 0000000..0b473c7 --- /dev/null +++ b/developers-guides/for-builders/README.md @@ -0,0 +1,27 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# For Builders + +{% content-ref url="architecture.md" %} +[architecture.md](architecture.md) +{% endcontent-ref %} + +{% content-ref url="building-on-solayer.md" %} +[building-on-solayer.md](building-on-solayer.md) +{% endcontent-ref %} + +{% content-ref url="solayer-programs.md" %} +[solayer-programs.md](solayer-programs.md) +{% endcontent-ref %} diff --git a/restaking/restaking-architecture.md b/developers-guides/for-builders/architecture.md similarity index 62% rename from restaking/restaking-architecture.md rename to developers-guides/for-builders/architecture.md index 5d7b168..3dd9e6e 100644 --- a/restaking/restaking-architecture.md +++ b/developers-guides/for-builders/architecture.md @@ -1,6 +1,6 @@ -# Restaking Architecture +# Architecture -
+
The restaking pool manager oversees the flow of assets into the protocol. When users deposit LST or SOL (which is first converted to sSOL-raw), they receive a fungible token representation in return. Collectively, we call them Solayer assets. Currently illiquid to facilitate points calculation for the liquidity reward program, this representation will become liquid in the future to encourage composability with DeFi. @@ -10,30 +10,6 @@ Stage 2 of our protocol development will enable users to pledge their Solayer as Once delegation to SVNs and node operators is live, users will construct their restaking portfolio by selecting the node operators to delegate to and SVNs to secure. They will then be issued a non-fungible token. This token is non-fungible due to the idiosyncratic risks associated with the selected node operators and the SVNs. -\ Rewards accounting is calculated offline. Solayer has implemented a state watcher to keep track of deposits and withdrawals. Together with the invite relationship data, additional rewards will be applied to user accounts in real-time. The Restake method on Solayer is permissioned and requires an additional signature from the server. This is to allow us to enforce deposit limits in the first few epochs. The Unstake method does not require an additional signature from Solayer. - - - -## **Native SOL restaking** - -
- -For native SOL restaking, Solayer first converts your SOL to an intermediary form called sSOL-raw, which is the Liquid Staking Token (LST) issued by the stake pool manager. This entire process is non-custodial, ensuring that staked SOL is delegated to validators who earn MEV-boosted returns. The sSOL-raw is then converted to sSOL after another interaction with the Solayer restaking pool manager. All these steps are executed in a single transaction for efficiency. - -**Here are more details on the Solayer stake pool:** - -* Stake Pool: po1osKDWYF9oiVEGmzKA4eTs8eMveFRMox3bUKazGN2 -* Pool Token Mint: sSo1wxKKr6zW2hqf5hZrp2CawLibcwi1pMBqk5bg2G4 -* Epoch Fee: 7/100 of epoch rewards -* Stake Withdrawal Fee: 8/10000 of withdrawal amount -* SOL Withdrawal Fee: 8/10000 of withdrawal amount -* Stake Deposit Fee: 0/10000 of deposit amount -* SOL Deposit Fee: 0/10000 of deposit amount -* Stake Deposit Referral Fee: 0% of Stake -* Deposit Fee SOL Deposit Referral Fee: 0% of SOL Deposit Fee - - - diff --git a/overview/what-can-be-built-on-solayer.md b/developers-guides/for-builders/building-on-solayer.md similarity index 100% rename from overview/what-can-be-built-on-solayer.md rename to developers-guides/for-builders/building-on-solayer.md diff --git a/developers-guides/for-builders/solayer-programs.md b/developers-guides/for-builders/solayer-programs.md new file mode 100644 index 0000000..55f0485 --- /dev/null +++ b/developers-guides/for-builders/solayer-programs.md @@ -0,0 +1,19 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Solayer Programs + +Solayer has deployed the following programs. + +
ProgramDescriptionProgram ID
Restaking Pool ManagerManages the flow of restaked assets.sSo1iU21jBrU9VaJ8PJib1MtorefUV4fzC9GURa2KNn
sSOL Liquidity layer for Solayer. TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA
diff --git a/developers-guides/security/README.md b/developers-guides/security/README.md new file mode 100644 index 0000000..e033a06 --- /dev/null +++ b/developers-guides/security/README.md @@ -0,0 +1,27 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Security + +At Solayer, security is our top priority. We have meticulously designed our system to be robust and secure, investing substantial resources to ensure our protocol adheres to the highest security standards. Our commitment is to set a benchmark for security within the Solana ecosystem, providing our users with a safe and reliable platform. + +{% content-ref url="audits.md" %} +[audits.md](audits.md) +{% endcontent-ref %} + +{% content-ref url="multisig-committee.md" %} +[multisig-committee.md](multisig-committee.md) +{% endcontent-ref %} + +
diff --git a/security/audits.md b/developers-guides/security/audits.md similarity index 100% rename from security/audits.md rename to developers-guides/security/audits.md diff --git a/developers-guides/security/bounties.md b/developers-guides/security/bounties.md new file mode 100644 index 0000000..88400e9 --- /dev/null +++ b/developers-guides/security/bounties.md @@ -0,0 +1,17 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Bounties + +Coming soon. diff --git a/governance/multisigature-committees.md b/developers-guides/security/multisig-committee.md similarity index 100% rename from governance/multisigature-committees.md rename to developers-guides/security/multisig-committee.md diff --git a/endogenous-avs/README.md b/endogenous-avs/README.md deleted file mode 100644 index e77b024..0000000 --- a/endogenous-avs/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# Endogenous AVS - -Solayer is a restaking marketplace developed on Solana. Instead of focusing on exogenous AVSs (such as oracles and bridges on EigenLayer), Solayer aims to support on-chain decentralized applications (dApps) initially. The goal is to provide dApps on Solana with a greater likelihood of securing block space and prioritizing transaction inclusion. These are referred to as endogenous AVSs. diff --git a/endogenous-avs/delegation.md b/endogenous-avs/delegation.md deleted file mode 100644 index c9815f1..0000000 --- a/endogenous-avs/delegation.md +++ /dev/null @@ -1,9 +0,0 @@ -# Delegation - -**The Solayer stake delegation process is straightforward:** - -1. **Conversion:** Users convert SOL into its natively staked form, sSOL. -2. **Delegation:** Staked SOL is delegated to Solayer-recommended validators, which then delegate it to an endogenous dApp AVS on Solayer, converting sSOL to a delegated form. -3. **Minting Tokens:** Solayer AVS mints AVS tokens, which serve as stake proof to retrieve staked SOL and claim rewards. - -
diff --git a/endogenous-avs/super-liquidity.md b/endogenous-avs/super-liquidity.md deleted file mode 100644 index cb8a042..0000000 --- a/endogenous-avs/super-liquidity.md +++ /dev/null @@ -1,7 +0,0 @@ -# Super Liquidity - -Liquidity is the most important factor for the adoption of any asset. Conversion delay and slippage are two key considerations. In an ideal world, there would be no slippage and instant conversion, so all Solana users should hold yield-bearing LSTs instead of SOL. What prevents this from happening is the liquidity of such LSTs. Each LST needs to have a deep pool with low swap fees and a significant amount of trading volume to offset LP’s capital costs. \ -\ -To address this problem, Solayer introduces Superior Liquidity for AVS Tokens using a pooled liquidity design. Solayer AVS LST Tokens can be instantly unwrapped (or undelegated) back to the underlying representation, sSOL. Unlike others that use a multi-LST pool, where the liquidity for each LST depends on their LP pools (a less efficient design), Solayer consolidates all liquidity for Solayer AVS Tokens using the sSOL-SOL pair. This strategy results in significantly smaller price impact and significantly improved liquidity. - -
diff --git a/first-principles.md b/first-principles.md index 3f54d60..2f74587 100644 --- a/first-principles.md +++ b/first-principles.md @@ -1,14 +1,34 @@ -# First principles +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- -Trust is central to any decentralized system. Proof of stake is the most common Byzantine Fault-Tolerant Consensus in use today. However, bootstrapping a proof of stake ecosystem is challenging. There must be an economically incentivized fair distribution of initial stake, often in the form of newly minted tokens. This process can entail steep financial costs for participants, as they need to invest capital in an asset with an uncertain risk profile. +# First Principles -The concept of shared security emerged to solve this issue - leveraging the stake in established POS systems with well-recognized assets like ETH and Solana. These systems, with their established validator networks, can provide security for other decentralized systems. Newer networks could use the existing stake on such chains to provide economic guarantees and security. +### Building something people want -## Solana's Superior Infrastructure +We are not first time builders in crypto. We also did not get into crypto for the hype. We were in this space when no one knew what it was. -Solana's high-performant, cost-effective, and high execution infrastructure is superior for SVN (Shared Validator Network) builders, operators, and restakers. The advantages of utilizing Solana as the foundational platform for SVN include: +Product Market Fit is not a commonly used metric in crypto products, and very much narrative-driven just like any novel technological darling. -1. **Cost-Effective SVN Construction:** Utilizing Solana as the native Data Availability layer for SVN significantly reduces the cost of building an SVN compared to Ethereum. -2. **Low latency application**: Solana's lower block time production of 0.4 seconds compared to Ethereum's 20 seconds, enables low-latency SVNs resulting in a more responsive user experience. Examples include compute-intensive games, GPU clusters, and high-frequency DeFi applications. -3. **Cheaper state sync/update/finalization**: The process of state finalization, sync, and update of SVNs, which is a continual process to ensure the immutability and synchronization of validated applications, is considerably more cost-effective on Solana compared to other viable networks -4. **Cheaper state transition storage**: Storing state transitions in SVN is significantly cheaper when powered by Solana, making it a more economical choice for developers and operators. +Yes, absolutely, we need to capture the narrative, but there were few strategic decisions we made to ensure the product outlasts narrative. + +* PoS staking has unchallenged PMF, so in addition to restaking, our 1st layer infrastructure covers everything Marinade or JITO has built — single stake pool and MEV-boost yield. Unlike Eigenlayer, which does not have liquid staking, it does not generate revenue. Solana only has $4B in SOL staked, and the opportunity is a $80B market. +* We did not fundamentally agree with Eigenlayer’s technical architecture. So we re-architected, in a sense, restandardized restaking in the Solana land. Reusing stake as a way of securing network bandwidth for apps. We aim to become the de facto infrastructure for stake-weighted quality of service, and eventually, a core primitive of the Solana blockchain/consensus. + +### Building something that lasts + +细水长流 - thin streams flow forever. It’s hard to not be hyped when there is good progress, especially in an industry like ours. But as an internal principle, we aim to be there for as long as Solana exists. + +This requires consistency and persistence. + +From hosting weekly engineering research presentations to submitting direct fixes to the Solana codebase, these are minor efforts that demonstrate to the team that building something that lasts will get us a lot farther than the short-term excitement. diff --git a/get-started/to-use-phantom.md b/get-started/to-use-phantom.md deleted file mode 100644 index 6904395..0000000 --- a/get-started/to-use-phantom.md +++ /dev/null @@ -1,29 +0,0 @@ -# To Use Phantom - -First, we assume you already have Phantom downloaded in your browser extension. If not, please set up with Phantom ([setup instructions](https://help.phantom.app/hc/en-us/articles/8071074929043-How-to-create-a-new-wallet)). - - - -1. Select "Phantom" as the option - -
- -2. Confirm the message signing - -
- -3. Choose a pool and select "deposit" -4. Enter the appropriate amount you would like to deposit and approve the transaction - -
- - - -* You will see sSOL or sLST-SOL in your wallet, please note that it is **NOT** **transferrable** and will be _made redeemable/transferrable at a later Epoch noted in our release schedule_. -* As whitelisted individuals, you will be directly taken to app.solayer.org staking page -* If you are not invited, please wait for Epoch 1. We work closely with supporters and collaborators for Epoch 0 for security reasons. - -_Note:_ - -1. Withdrawal will be enabled by Epoch 3 -2. Genesis Epoch lasts for 24 hours and have a $20m cap diff --git a/get-started/to-use-solflare.md b/get-started/to-use-solflare.md deleted file mode 100644 index c091ef9..0000000 --- a/get-started/to-use-solflare.md +++ /dev/null @@ -1,27 +0,0 @@ -# To Use Solflare - -1. First, we assume you already have Phantom downloaded in your browser extension. If not, please set up with Solflare ([instructions](https://solflare.com/)). -2. Click on "Solflare" as the option - -
- -2. Click Approve and wait for signature from your wallet - -
- -3. Choose a pool and select "deposit" - -
- -4. Enter the appropriate amount you would like to deposit and approve the transaction - -
- -* You will see sSOL or sLST-SOL in your wallet, please note that it is NOT transferrable and will be made redeemable/transferrable at a later Epoch noted in our release schedule. -* As whitelisted individuals, you will be directly taken to app.solayer.org staking page -* If you are not invited, please wait for Epoch 1. We work closely with supporters and collaborators for Epoch 0 for security reasons. - -_Note:_ - -1. Withdrawal will be enabled by Epoch 3 -2. Genesis Epoch lasts for 24 hours and have a $20m cap diff --git a/governance/README.md b/governance/README.md deleted file mode 100644 index e2cd786..0000000 --- a/governance/README.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -cover: ../.gitbook/assets/Restaking_Graphic (2).png -coverY: 156 ---- - -# Governance - diff --git a/informational/README.md b/informational/README.md deleted file mode 100644 index 88f7801..0000000 --- a/informational/README.md +++ /dev/null @@ -1,2 +0,0 @@ -# Informational - diff --git a/informational/how-to-use/README.md b/informational/how-to-use/README.md new file mode 100644 index 0000000..984c9a1 --- /dev/null +++ b/informational/how-to-use/README.md @@ -0,0 +1,23 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# How to use? + +{% content-ref url="use-ledger.md" %} +[use-ledger.md](use-ledger.md) +{% endcontent-ref %} + +{% content-ref url="use-phantom.md" %} +[use-phantom.md](use-phantom.md) +{% endcontent-ref %} diff --git a/get-started/to-use-ledger.md b/informational/how-to-use/use-ledger.md similarity index 51% rename from get-started/to-use-ledger.md rename to informational/how-to-use/use-ledger.md index fdd1836..e7d7a32 100644 --- a/get-started/to-use-ledger.md +++ b/informational/how-to-use/use-ledger.md @@ -1,45 +1,61 @@ -# To Use Ledger +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Use Ledger **NOTE: Currently for all ledger users, please connect to Phantom for ease of experience.** 1. First, we assume you already have Phantom downloaded in your browser extension. If not, please set up with Phantom ([setup instructions](https://help.phantom.app/hc/en-us/articles/8071074929043-How-to-create-a-new-wallet)). 2. Click on the top left menu icon -
+
3. Click on the "plus" button -
+
4. Click "Connect Hardware Wallet" -
+
5. Complete the process of connecting wallet with Phantom -
+
-4. Please make sure to enable blind signing, as the smart contract transactions cannot be displayed on Ledger. Therefore for third party integrations, you will only be able to sign the transaction if blind signing is on. [Please DYOR before doing so as well](https://www.ledger.com/academy/enable-blind-signing-why-when-and-how-to-stay-safe). -5. You may see "unrecognized" as Ledger cannot read smart contract details, therefore Ledger will automatically display as "unrecognized" -6. Direct back to app.solayer.org and make sure to click on “I am using Ledger with Phantom” +6. Please make sure to enable blind signing, as the smart contract transactions cannot be displayed on Ledger. Therefore for third party integrations, you will only be able to sign the transaction if blind signing is on. [Please DYOR before doing so as well](https://www.ledger.com/academy/enable-blind-signing-why-when-and-how-to-stay-safe). +7. You may see "unrecognized" as Ledger cannot read smart contract details, therefore Ledger will automatically display as "unrecognized" +8. Direct back to app.solayer.org and make sure to click on “I am using Ledger with Phantom” -
+
-1. Click on Phantom tab -2. Confirm the transaction ([For ledger, message signature is not supported. The network fee you see here will not be broadcasted](https://spl.solana.com/memo)) +9. Click on Phantom tab +10. Confirm the transaction ([For ledger, message signature is not supported. The network fee you see here will not be broadcasted](https://spl.solana.com/memo)) -
+
-5. Select "Confirm" transaction by confirming on your hardware device +11. Select "Confirm" transaction by confirming on your hardware device. -
+
-
+12. You have successfully staked Native SOL. -5. You will see sSOL or sLST-SOL in your wallet as a representation SPL. Please note that it is NOT transferrable and will be made redeemable/transferrable at a later Epoch noted in our release schedule. Read more under the [restaking](https://docs.solayer.org/solayer-docs/restaking/restaking-architecture) [guide](https://docs.solayer.org/solayer-docs/restaking/restaking-architecture) to understand the denotation. -6. As whitelisted individuals, you will be directly taken to app.solayer.org staking page. -7. If you are not invited, please wait for Epoch 1. We work closely with supporters and collaborators for Epoch 0 for security reasons. +
+13. You will see sSOL or sLST-SOL in your wallet as a representation SPL. Please note that it is NOT transferrable and will be made redeemable/transferrable at a later Epoch noted in our release schedule. Read more under the [restaking](https://docs.solayer.org/solayer-docs/restaking/restaking-architecture) [guide](https://docs.solayer.org/solayer-docs/restaking/restaking-architecture) to understand the denotation. +14. As whitelisted individuals, you will be directly taken to app.solayer.org staking page. +15. If you are not invited, please wait for Epoch 1. We work closely with supporters and collaborators for Epoch 0 for security reasons. +*** **More details for Ledger users** @@ -55,11 +71,4 @@ To ensure smooth functionality when interacting with smart contracts, it is esse * Navigate to the settings menu. * Enable blind signing in the device settings. -By enabling blind signing, you ensure that you can seamlessly interact with smart contracts and complete necessary transactions, even when detailed transaction data cannot be displayed on the Ledger screen. - - - -_Note:_ - -1. Withdrawal will be enabled by Epoch 3 -2. Genesis Epoch lasts for 24 hours and have a $20m cap\ +By enabling blind signing, you ensure that you can seamlessly interact with smart contracts and complete necessary transactions, even when detailed transaction data cannot be displayed on the Ledger screen.\ diff --git a/informational/how-to-use/use-phantom.md b/informational/how-to-use/use-phantom.md new file mode 100644 index 0000000..5f07a77 --- /dev/null +++ b/informational/how-to-use/use-phantom.md @@ -0,0 +1,37 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Use Phantom + +First, we assume you already have Phantom downloaded in your browser extension. If not, please set up with Phantom ([setup instructions](https://help.phantom.app/hc/en-us/articles/8071074929043-How-to-create-a-new-wallet)). + +1. Select "Phantom" as the option. + +
+ +2. Confirm the message signing. + +
+ +3. Choose a pool and select "deposit". + +
+ +4. Enter the appropriate amount you would like to deposit and approve the transaction. + +
+ +5. Congratulations! You have successfully deposited. + +
diff --git a/informational/partnerships.md b/informational/partnerships.md new file mode 100644 index 0000000..6070971 --- /dev/null +++ b/informational/partnerships.md @@ -0,0 +1,19 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Partnerships + +If you are interested in partnering with us, please visit our Discord and open a ticket. + +A core member from Solayer will respond to you promptly. diff --git a/litepapers.md b/litepapers.md deleted file mode 100644 index 22ce949..0000000 --- a/litepapers.md +++ /dev/null @@ -1,3 +0,0 @@ -# Litepapers - -**Litepaper Part 1, v0**: Endogenous AVS on Solana Powered by Restaking: [https://github.com/solayer-labs/solayer-improvement-proposal/blob/main/solayer-litepaper-v0.pdf](https://github.com/solayer-labs/solayer-improvement-proposal/blob/main/solayer-litepaper-v0.pdf) diff --git a/overview/README.md b/overview/README.md deleted file mode 100644 index 16c4716..0000000 --- a/overview/README.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -cover: ../.gitbook/assets/Blog banner.png -coverY: 240.31932773109244 ---- - -# Overview - - - -
Key Terms and Concepts key-terms-and-concepts.md
Protocol Features Broken link
Support support.md
Whitepaper Broken link
diff --git a/overview/support.md b/overview/support.md deleted file mode 100644 index 7fdbf3f..0000000 --- a/overview/support.md +++ /dev/null @@ -1,10 +0,0 @@ -# Support - -**Useful links** - -* 🌐 Website: [https://solayer.org](https://solayer.org/) -* 📄 Docs: [https://docs.solayer.org](https://docs.solayer.org/) -* 💬 Discord: [https://discord.com/invite/solayerlabs](https://discord.com/invite/solayerlabs) -* 💬 Twitter: [https://twitter.com/solayer\_labs](https://twitter.com/solayer\_labs) -* 📝 Writings: [https://solayer.org/blogs](https://solayer.org/blogs) -* :books: Solayer 101: [https://solayer.org/101](https://solayer.org/101) diff --git a/restaking-epochs/README.md b/restaking-epochs/README.md deleted file mode 100644 index 2cdf049..0000000 --- a/restaking-epochs/README.md +++ /dev/null @@ -1,5 +0,0 @@ -# Restaking Epochs - -The **Solayer Restaking Epochs are** designed to ensure the safety and security of our protocol developments while optimizing for the best user experience. Through these carefully managed phases we provide a secure and efficient environment for participants, facilitating smooth interactions and maximizing benefits. These epochs have already seen significant engagement, with millions in restaked deposits, demonstrating the robust interest and trust in our platform. - -
diff --git a/restaking/README.md b/restaking/README.md deleted file mode 100644 index b375839..0000000 --- a/restaking/README.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -cover: ../.gitbook/assets/Restaking_Graphic.png -coverY: 335 ---- - -# Restaking - -Restaking enables SOL or Liquid Staked SOL stakers to participate in "delegated consensus." They restake their assets into the Solayer restaking vault and delegate them to a group of operators who then opt into other networks to validate and earn rewards. diff --git a/restaking/native-sol-restaking-tutorial.md b/restaking/native-sol-restaking-tutorial.md deleted file mode 100644 index 0019624..0000000 --- a/restaking/native-sol-restaking-tutorial.md +++ /dev/null @@ -1,3 +0,0 @@ -# Native SOL Restaking Tutorial - -### Check this video on "[How to natively stake on Solayer](https://www.youtube.com/watch?v=plHbf60-N3c)" diff --git a/security/README.md b/security/README.md deleted file mode 100644 index b30c666..0000000 --- a/security/README.md +++ /dev/null @@ -1,5 +0,0 @@ -# Security - - - -
diff --git a/solayer-overview/endogenous-avs/README.md b/solayer-overview/endogenous-avs/README.md new file mode 100644 index 0000000..91545a7 --- /dev/null +++ b/solayer-overview/endogenous-avs/README.md @@ -0,0 +1,29 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Endogenous AVS + +Solayer is a restaking marketplace developed on Solana. Instead of focusing solely on exogenous AVSs (such as oracles and bridges), Solayer aims to support on-chain decentralized applications (dApps) initially. The goal is to provide dApps on Solana with a greater likelihood of securing block space and prioritizing transaction inclusion. These are referred to as endogenous AVSs. + +{% content-ref url="what-is-an-avs.md" %} +[what-is-an-avs.md](what-is-an-avs.md) +{% endcontent-ref %} + +{% content-ref url="quality-of-service.md" %} +[quality-of-service.md](quality-of-service.md) +{% endcontent-ref %} + +{% content-ref url="delegate-tokens.md" %} +[delegate-tokens.md](delegate-tokens.md) +{% endcontent-ref %} diff --git a/endogenous-avs/from-staked-sol-to-endogenous-avs-tokens.md b/solayer-overview/endogenous-avs/delegate-tokens.md similarity index 74% rename from endogenous-avs/from-staked-sol-to-endogenous-avs-tokens.md rename to solayer-overview/endogenous-avs/delegate-tokens.md index bb284ef..356c404 100644 --- a/endogenous-avs/from-staked-sol-to-endogenous-avs-tokens.md +++ b/solayer-overview/endogenous-avs/delegate-tokens.md @@ -1,4 +1,18 @@ -# From Staked SOL to Endogenous AVS Tokens +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Delegate Tokens Solayer provides decentralized applications (dApps) with a simple method to create their own AVS LST. These tokens come with Solana’s native staking yield as their base rewards, along with additional MEV yields. Solayer optimizes the staking yield by delegating it to the highest yield-bearing validators. \ \ @@ -6,6 +20,16 @@ Additionally, Solayer runs its own validator implementation that supports app-le \ In the future, we envision dApps having direct control over the validators to which the underlying SOL is delegated. They should also be able to configure the required stake-weighted quality of service with a dynamic pricing mechanism depending on the current network workload. +### Getting an AVS Token + +First, users convert SOL into its natively staked form, sSOL. Staked SOL will be delegated to Solayer recommended validators. + +They then delegate it to an endogenous dApp AVS on Solayer, which converts sSOL to a delegated form. + +Finally, Solayer AVS mints AVS tokens which can later be used as a stake proof to retrieve staked SOL back and claim rewards. + +
+ ### General Flow of sSOL 1. _**Deposit and Receive sSOL:**_ @@ -27,9 +51,3 @@ In the future, we envision dApps having direct control over the validators to wh 5. _**Yield Commission:**_ * e-AVS earns a commission from the staking yield. - -### Getting an AVS Token - -First, users convert SOL into its natively staked form, sSOL. Staked SOL will be delegated to Solayerrecommended validators. They then delegate it to an endogenous dApp AVS on Solayer, which converts 2 sSOL to a delegated form. Finally, Solayer AVS mints AVS tokens which can later be used as a stake proof to retrieve staked SOL back and claim rewards. - -
diff --git a/endogenous-avs/solayer-swqos-infrastructure.md b/solayer-overview/endogenous-avs/quality-of-service.md similarity index 81% rename from endogenous-avs/solayer-swqos-infrastructure.md rename to solayer-overview/endogenous-avs/quality-of-service.md index dfb2ad4..6c779e0 100644 --- a/endogenous-avs/solayer-swqos-infrastructure.md +++ b/solayer-overview/endogenous-avs/quality-of-service.md @@ -1,4 +1,18 @@ -# Solayer swQoS Infrastructure +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Quality of Service Stake-weighted quality of service (QoS) refers to the allocation of network resources, such as block space and transaction processing capacity, based on the amount of stake committed by validators or stakers. Under this model, a validator with 1% stake would have the right to transmit up to 1% of the packets to the epoch leader and would be capable of resisting Sybil attacks from the rest of the network. Commercial RPC infrastructure operators and entities hosting their own validator nodes and RPC nodes would benefit the most from this, as RPC nodes could include more transactions in blocks by agreeing to peer with validators, and validators may sell more capacity to RPC nodes. @@ -6,7 +20,7 @@ Stake-weighted quality of service (QoS) refers to the allocation of network reso For example, if there are two validators—one holding 2% of the stake and the other holding 0.2%—the former will be able to submit up to 2% of the packets to the block producer, taking priority over the latter. This provides the higher-quality validator with better performance and increased Sybil resistance. -
+
In simple terms, each transaction comes with weight. The heavier it is, the more likely your transactions get through. Consequently, the more you have at stake, the higher the quality of service you will receive, and the less likely it is that malicious flooding from lower-quality validators will affect you. diff --git a/endogenous-avs/what-is-an-avs.md b/solayer-overview/endogenous-avs/what-is-an-avs.md similarity index 64% rename from endogenous-avs/what-is-an-avs.md rename to solayer-overview/endogenous-avs/what-is-an-avs.md index cc53f2b..21448c2 100644 --- a/endogenous-avs/what-is-an-avs.md +++ b/solayer-overview/endogenous-avs/what-is-an-avs.md @@ -1,9 +1,25 @@ -# Endogenous AVSs as a swQoS infra for dApps +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# What is an AVS? Imagine a world where decentralized applications (dApps) can control how much power they have to process transactions on the blockchain by staking tokens into validators. This means that the more tokens a dApp has staked, the more it can influence the network’s operations. As a result, user transactions become faster and more reliable. Big dApps with many users and a lot of staked tokens benefit the most, as they get more transaction processing power without having to pay extra fees. Solayer is creating a trustless marketplace that allows dApps to manage and collect staked tokens from users and get the right amount of processing power directly from validators. Unlike Eigenlayer, which focuses on external services like cross-chain bridges and oracles, Solayer starts with native Solana dApps. These are called endogenous AVSs (Actively Validated Services), and Solayer helps them secure the necessary block space and prioritize their transactions based on the tokens staked with them. -
+
+ +In simpler terms, Solayer allows dApps on Solana to reserve their own space and processing power on the blockchain. -In simpler terms, Solayer allows dApps on Solana to reserve their own space and processing power on the blockchain. This makes the network more efficient and reliable for everyone using these applications.\ +This makes the network more efficient and reliable for everyone using these applications. One of the technical features that make this possible is called Stake-weighted[quality-of-service.md](quality-of-service.md "mention") (swQoS). diff --git a/solayer-overview/introduction/README.md b/solayer-overview/introduction/README.md new file mode 100644 index 0000000..229b0a1 --- /dev/null +++ b/solayer-overview/introduction/README.md @@ -0,0 +1,42 @@ +--- +cover: ../../.gitbook/assets/Blog banner.png +coverY: 240.31932773109244 +layout: + cover: + visible: true + size: full + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Introduction + +Solayer is the dominant restaking marketplace on Solana. + +We aim to empower on-chain decentralized applications (dApps) with improved network bandwidth while securing the L1 at the same time. + +Our goal is to provide dApps on Solana with a greater likelihood of securing block space and prioritizing transaction inclusion. + +{% content-ref url="../litepaper.md" %} +[litepaper.md](../litepaper.md) +{% endcontent-ref %} + +{% content-ref url="official-links.md" %} +[official-links.md](official-links.md) +{% endcontent-ref %} + +{% content-ref url="faq.md" %} +[faq.md](faq.md) +{% endcontent-ref %} + +{% content-ref url="terms-and-concepts.md" %} +[terms-and-concepts.md](terms-and-concepts.md) +{% endcontent-ref %} diff --git a/faqs.md b/solayer-overview/introduction/faq.md similarity index 96% rename from faqs.md rename to solayer-overview/introduction/faq.md index 7a2fc89..c239ae5 100644 --- a/faqs.md +++ b/solayer-overview/introduction/faq.md @@ -1,9 +1,12 @@ --- -cover: .gitbook/assets/Blog banner (2).png +description: >- + Most of your questions can be answered here! If you still have any unresolved + queries, feel free to reach out to us on Discord. +cover: ../../.gitbook/assets/Blog banner (2).png coverY: 141.55252100840335 --- -# FAQs +# FAQ ## Introduction diff --git a/solayer-overview/introduction/official-links.md b/solayer-overview/introduction/official-links.md new file mode 100644 index 0000000..34e0abf --- /dev/null +++ b/solayer-overview/introduction/official-links.md @@ -0,0 +1,37 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Official Links + +## Product + +🌐 Website: [https://solayer.org](https://solayer.org/) + +📄 Docs: [https://docs.solayer.org](https://docs.solayer.org/) + +\ Github: [https://github.com/solayer-labs](https://github.com/solayer-labs) + +## Academy + +📝 Writings: [https://solayer.org/blogs](https://solayer.org/blogs) + +:books: Solayer 101: [https://solayer.org/101](https://solayer.org/101) + +## Socials + +💬 Discord: [https://discord.com/invite/solayerlabs](https://discord.com/invite/solayerlabs) + +🐦 Twitter: [https://twitter.com/solayer\_labs](https://twitter.com/solayer\_labs) + +▶️ Youtube: [https://www.youtube.com/@solayer\_labs](https://www.youtube.com/@solayer\_labs) diff --git a/overview/key-terms-and-concepts.md b/solayer-overview/introduction/terms-and-concepts.md similarity index 93% rename from overview/key-terms-and-concepts.md rename to solayer-overview/introduction/terms-and-concepts.md index 503ed67..bdb6638 100644 --- a/overview/key-terms-and-concepts.md +++ b/solayer-overview/introduction/terms-and-concepts.md @@ -1,6 +1,18 @@ -# Key Terms and Concepts - +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- +# 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. @@ -19,4 +31,3 @@ 15. **Exogenous AVS:** Systems that maintain off-chain networks and use to establish consensus on security via quorum-based slashing or on-chain verifiable proof. Examples of exogenous AVSs include cross-chain bridges, shared sequencers, oracle networks, among others. 16. **Endogenous AVS:** Instead of focusing on exogenous AVSs, Solayer aims to support on-chain decentralized applications (dApps) initially. The goal is to provide dApps on Solana with a greater likelihood of securing block space and prioritizing transaction inclusion. 17. **Stake-weighted Quality of Service (QoS):** Refers to the allocation of network resources, such as block space and transaction processing capacity, based on the amount of stake committed by validators or stakers. - diff --git a/solayer-overview/litepaper.md b/solayer-overview/litepaper.md new file mode 100644 index 0000000..f535085 --- /dev/null +++ b/solayer-overview/litepaper.md @@ -0,0 +1,19 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Litepaper + +**Litepaper Part 1, v0**: Endogenous AVS on Solana Powered by Restaking: + +[https://github.com/solayer-labs/solayer-improvement-proposal/blob/main/solayer-litepaper-v0.pdf](https://github.com/solayer-labs/solayer-improvement-proposal/blob/main/solayer-litepaper-v0.pdf) diff --git a/solayer-overview/restaking-guides/README.md b/solayer-overview/restaking-guides/README.md new file mode 100644 index 0000000..98abbe3 --- /dev/null +++ b/solayer-overview/restaking-guides/README.md @@ -0,0 +1,40 @@ +--- +cover: ../../.gitbook/assets/Restaking_Graphic.png +coverY: 335 +layout: + cover: + visible: true + size: full + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Restaking Guides + +Restaking enables SOL or Liquid Staked SOL stakers to participate in "delegated consensus". + +They restake their assets into the Solayer restaking vault and delegate them to a group of operators who then opt into other networks to validate and earn rewards. + +{% content-ref url="native-sol-restaking/" %} +[native-sol-restaking](native-sol-restaking/) +{% endcontent-ref %} + +{% content-ref url="lst-restaking/" %} +[lst-restaking](lst-restaking/) +{% endcontent-ref %} + +{% content-ref url="unstake-ssol/" %} +[unstake-ssol](unstake-ssol/) +{% endcontent-ref %} + +{% content-ref url="delegation.md" %} +[delegation.md](delegation.md) +{% endcontent-ref %} diff --git a/solayer-overview/restaking-guides/delegation.md b/solayer-overview/restaking-guides/delegation.md new file mode 100644 index 0000000..c2a1966 --- /dev/null +++ b/solayer-overview/restaking-guides/delegation.md @@ -0,0 +1,23 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Delegation + +**The Solayer stake delegation process is straightforward:** + +1. **Conversion:** Users convert SOL into its natively staked form, sSOL. +2. **Delegation:** Staked SOL is delegated to Solayer-recommended validators, which then delegate it to an Delegate dApp (endogenous AVS) on Solayer, converting sSOL to a delegated form. +3. **Minting Tokens: Solayer dApps** mint Delegate Tokens, which serve as stake proof to retrieve staked SOL and claim rewards. + +
diff --git a/restaking/lst-restaking.md b/solayer-overview/restaking-guides/lst-restaking/README.md similarity index 100% rename from restaking/lst-restaking.md rename to solayer-overview/restaking-guides/lst-restaking/README.md diff --git a/solayer-overview/restaking-guides/lst-restaking/lst-restaking-tutorial.md b/solayer-overview/restaking-guides/lst-restaking/lst-restaking-tutorial.md new file mode 100644 index 0000000..137f097 --- /dev/null +++ b/solayer-overview/restaking-guides/lst-restaking/lst-restaking-tutorial.md @@ -0,0 +1,31 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# LST Restaking Tutorial + +1. Navigate to the Solayer dashboard and choose whether to deposit mSOL, JitoSOL, bSOL, or INF. + +
+ +2. Select the amount you wish to stake and click “Deposit.” + +
+ +3. Confirm the transaction. + +
+ +4. Congratulations! You have successfully deposited mSOL. + +
diff --git a/solayer-overview/restaking-guides/native-sol-restaking/README.md b/solayer-overview/restaking-guides/native-sol-restaking/README.md new file mode 100644 index 0000000..1ced624 --- /dev/null +++ b/solayer-overview/restaking-guides/native-sol-restaking/README.md @@ -0,0 +1,17 @@ +# Native SOL Restaking + +For native SOL restaking, Solayer first converts your SOL to an intermediary form called sSOL-raw, which is the Liquid Staking Token (LST) issued by the stake pool manager. This entire process is non-custodial, ensuring that staked SOL is delegated to validators who earn MEV-boosted returns. The sSOL-raw is then converted to sSOL after another interaction with the Solayer restaking pool manager. All these steps are executed in a single transaction for efficiency. + +
+ +**Here are more details on the Solayer stake pool:** + +* Stake Pool: po1osKDWYF9oiVEGmzKA4eTs8eMveFRMox3bUKazGN2 +* Pool Token Mint: sSo1wxKKr6zW2hqf5hZrp2CawLibcwi1pMBqk5bg2G4 +* Epoch Fee: 7/100 of epoch rewards +* Stake Withdrawal Fee: 8/10000 of withdrawal amount +* SOL Withdrawal Fee: 8/10000 of withdrawal amount +* Stake Deposit Fee: 0/10000 of deposit amount +* SOL Deposit Fee: 0/10000 of deposit amount +* Stake Deposit Referral Fee: 0% of Stake +* Deposit Fee SOL Deposit Referral Fee: 0% of SOL Deposit Fee diff --git a/solayer-overview/restaking-guides/native-sol-restaking/restaking-tutorial.md b/solayer-overview/restaking-guides/native-sol-restaking/restaking-tutorial.md new file mode 100644 index 0000000..fa0f163 --- /dev/null +++ b/solayer-overview/restaking-guides/native-sol-restaking/restaking-tutorial.md @@ -0,0 +1,33 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Restaking Tutorial + +### :arrow\_forward: Check this video on "[How to natively stake on Solayer](https://www.youtube.com/watch?v=plHbf60-N3c)" + +1. Navigate to the Solayer dashboard and choose whether to deposit native SOL or a Liquid Staking Token (LST) such as mSOL, JitoSOL, bSOL, or INF. + +
+ +2. Select the amount you wish to stake and click “Deposit.” + +
+ +3. Confirm the transaction. + +
+ +4. Congratulations! You have successfully deposited native SOL. + +
diff --git a/restaking/unstake-ssol.md b/solayer-overview/restaking-guides/unstake-ssol/README.md similarity index 96% rename from restaking/unstake-ssol.md rename to solayer-overview/restaking-guides/unstake-ssol/README.md index bc3e958..843ff83 100644 --- a/restaking/unstake-ssol.md +++ b/solayer-overview/restaking-guides/unstake-ssol/README.md @@ -21,7 +21,7 @@ Our accounting system works as follows: * The base calculation for rewards = deposit \* time-weight \* boost -Currently, native SOL has a significant priority over other LSTs. However, we may begin campaigns to boost other LST deposits. If you withdraw prematurely, you will incur a 50% reduction on the rewards accrued by the amount you are withdrawing. Check the [unstaking-credit-deduction.md](unstaking-credit-deduction.md "mention")page for more information. +Currently, native SOL has a significant priority over other LSTs. However, we may begin campaigns to boost other LST deposits. If you withdraw prematurely, you will incur a 50% reduction on the rewards accrued by the amount you are withdrawing. Check the [unstaking-credit-deduction.md](../../../community/solayer-valley-episodes/unstaking-credit-deduction.md "mention")page for more information. *** diff --git a/restaking/unstaking-tutorial.md b/solayer-overview/restaking-guides/unstake-ssol/unstaking-tutorial.md similarity index 95% rename from restaking/unstaking-tutorial.md rename to solayer-overview/restaking-guides/unstake-ssol/unstaking-tutorial.md index e1daf7a..b0f5c80 100644 --- a/restaking/unstaking-tutorial.md +++ b/solayer-overview/restaking-guides/unstake-ssol/unstaking-tutorial.md @@ -1,8 +1,10 @@ # Unstaking Tutorial -### Check this video on "[How to unstake from Solayer](https://www.youtube.com/watch?v=FHpqwNd6CBo)" +## :arrow\_forward: Check this video on "[How to unstake from Solayer](https://www.youtube.com/watch?v=FHpqwNd6CBo)" -### Withdraw Tutorial +*** + +### Unstaking Tutorial How to unstake from Solayer? [How to unstake from Solayer](https://www.youtube.com/watch?v=FHpqwNd6CBo) @@ -41,5 +43,3 @@ How to unstake from Solayer? [How to unstake from Solayer](https://www.youtube.c 9. Congratulations! You have successfully withdrawn your deposit.
- -\ diff --git a/solayer-overview/what-is-ssol/README.md b/solayer-overview/what-is-ssol/README.md new file mode 100644 index 0000000..1308853 --- /dev/null +++ b/solayer-overview/what-is-ssol/README.md @@ -0,0 +1,33 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# What is sSOL? + +sSOL is the universal liquidity layer for delegates \[dApps] and LRTs on Solayer. Every unit of SOL can be perceived as a unit of blockspace lent towards dApps, securing network bandwidth and TPS. + +The stake delegated towards dApps, which derives an AVS SPL token, is built on top of sSOL-SOL liquidity. Similarly, LRTs are built on top of sSOL liquidity interface to generate vault strategies. + +There are various ways of utilizing sSOL and earning maximum yield as an sSOL Holder. You can delegate to dApps to bootstrap network bandwidth or participate in DeFi strategies to earn additional APY, starting with our launch partners. + +{% content-ref url="liquidity.md" %} +[liquidity.md](liquidity.md) +{% endcontent-ref %} + +{% content-ref url="ssol-in-defi.md" %} +[ssol-in-defi.md](ssol-in-defi.md) +{% endcontent-ref %} + +{% content-ref url="trading-and-rewards.md" %} +[trading-and-rewards.md](trading-and-rewards.md) +{% endcontent-ref %} diff --git a/solayer-overview/what-is-ssol/liquidity.md b/solayer-overview/what-is-ssol/liquidity.md new file mode 100644 index 0000000..75c4464 --- /dev/null +++ b/solayer-overview/what-is-ssol/liquidity.md @@ -0,0 +1,29 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Liquidity + +Liquidity is the most important factor for the adoption of any asset. Conversion delay and slippage are two key considerations. + +In an ideal world, there would be no slippage and instant conversion, so all Solana users should hold yield-bearing LSTs instead of SOL. + +What prevents this from happening is the liquidity of such LSTs. Each LST needs to have a deep pool with low swap fees and a significant amount of trading volume to offset LP’s capital costs. + +
+ +To address this problem, Solayer introduces Superior Liquidity for AVS Tokens using a pooled liquidity design. Solayer AVS LST Tokens can be instantly unwrapped (or undelegated) back to the underlying representation, sSOL. + +Unlike others that use a multi-LST pool, where the liquidity for each LST depends on their LP pools (a less efficient design), Solayer consolidates all liquidity for Solayer AVS Tokens using the sSOL-SOL pair. + +This strategy results in significantly smaller price impact and significantly improved liquidity. diff --git a/solayer-overview/what-is-ssol/ssol-in-defi.md b/solayer-overview/what-is-ssol/ssol-in-defi.md new file mode 100644 index 0000000..5a89b71 --- /dev/null +++ b/solayer-overview/what-is-ssol/ssol-in-defi.md @@ -0,0 +1,103 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# sSOL in DeFi + +#### Liquidity Vaults on Kamino + +Kamino's liquidity vaults are an automated liquidity solution that allows users to earn yield on their crypto assets by providing liquidity to concentrated liquidity market makers (CLMMs). + +\ + + +A vault deploys liquidity into an underlying DEX pool, consisting of 2 tokens. When you deposit into a vault, you earn fees from trading volume. + +\ + + +In other words, if you deposit into a pool with sSOL and SOL, any token swaps that utilize that pool will incur a small cost to the swapper. As a Kamino depositor, you earn from that swap fee. + +**Vault Capital Deposit Example** + +Situation: You have 100 sSOL worth $10,000 USD. You want to earn yield on your assets without active management. + +Use Case: Deposit your sSOL into a Kamino vault. Your sSOL will provide liquidity to a DEX, earning fees from trading volume. Kamino automates rebalancing and compounding, maximizing your yield. + +Benefit: Earn yield passively while maintaining exposure to sSOL. + +*** + +#### Collateral on Drift + +sSOL can be used as collateral in Drift Protocol's decentralized money markets. You can deposit sSOL to earn yield or borrow against it at a variable interest rate. + +\ + + +Lenders earn yield on their sSOL deposits by providing liquidity, while borrowers access liquidity pools in an over-collateralized manner. Interest earned is vested immediately and compounds automatically. + +\ + + +Let’s go through an example where an sSOL holder borrows against this position. + +**Borrowing Example** + +Situation: You have 100 sSOL worth $10,000 USD. You want access to USDC but don't want to sell your sSOL. + +Use Case: Deposit your sSOL into Drift and borrow up to 50% of its value in USDC. For 100 sSOL worth $10,000 USD, you can borrow up to $5,000 USDC. + +Benefit: The borrowed amount can be used for anything, including leveraged exposure to particular assets via spot trading. + +*** + +#### Liquidity Provision on Orca + +Orca utilizes a Concentrated Liquidity Automated Market Maker (CLAMM) to enhance capital efficiency and yield for liquidity providers. By providing liquidity to Orca's pools, users can earn yield on their crypto assets through trading fees. + +When you provide liquidity to an Orca pool, such as the sSOL-SOL pair, you earn fees from each token swap within that pool. This means if you deposit sSOL and SOL into the pool, any trades that occur between these tokens will generate fees, which are distributed to you as a liquidity provider. Orca automates this process, ensuring optimal capital efficiency and low slippage. + +**LP Example** + +Situation: You have 100 sSOL worth $10,000 USD. You want to earn yield on your assets without active management. + +Use Case: Deposit your sSOL and an equivalent amount of SOL into an Orca CLAMM pool. Your sSOL and SOL will provide liquidity to the DEX, earning fees from trading volume. Orca’s advanced CLAMM technology will ensure that your assets are utilized efficiently, maximizing your returns. + +Benefit: Earn yield passively from trading fees while maintaining exposure to both sSOL and SOL. + +*** + +#### Spot Trading on Drift + +Drift allows traders to buy or sell spot assets directly with immediate delivery and on-chain settlement. By sourcing liquidity from OpenBook DEX and Drift’s decentralized limit order book (DLOB), Drift ensures access to the best prices and trading opportunities. + +Drift's Just-In-Time (JIT) auction mechanism further enhances on-chain liquidity by initiating auctions where market makers compete to offer the best price for market or limit orders. If no offers are made within five seconds, the trade proceeds through Drift’s AMM, combining various liquidity mechanisms for optimal spot liquidity. + +**Exchange Example** + +Situation: You have 100 sSOL worth $10,000 USD. You want to capitalize on immediate market movements and manage your risk exposure. + +Use Case: You can directly trade sSOL against other assets, sourcing liquidity from OpenBook DEX and Drift’s DLOB. + +Benefit: Effectively manage risk by balancing your positions and potentially earning from market movements, while maintaining real-time account balance updates. + +\ + + +| **Use Case** | **Description** | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| _Collateral_ | You can use sSOL as a collateral on various money markets and borrow against it. This way you can either unlock more capital or directly leverage your position. | +| _Borrowed Asset_ | sSOL can also be borrowed from available liquidity pools in an over-collateralized fashion. | +| _Liquidity Provisioning_ | You will be able to provide sSOL to a number of vaults in DeFi in order to earn additional yield on top of your holdings. | +| _Trading_ | sSOL is available on Raydium and Orca, so you can easily trade it for other tokens on Solana. Keep in mind that trading sSOL may result in your stopping to earn rewards. | diff --git a/solayer-overview/what-is-ssol/trading-and-rewards.md b/solayer-overview/what-is-ssol/trading-and-rewards.md new file mode 100644 index 0000000..6e2c344 --- /dev/null +++ b/solayer-overview/what-is-ssol/trading-and-rewards.md @@ -0,0 +1,33 @@ +--- +layout: + title: + visible: true + description: + visible: false + tableOfContents: + visible: true + outline: + visible: true + pagination: + visible: true +--- + +# Trading & Rewards + +### Where can I trade sSOL-SOL pairs? + +sSOL-SOL pairs are available for trading on Raydium and Orca. We will also list these pairs on our DeFi page for easy access. More protocol integrations will be announced soon. + +
+ +### Can I transfer sSOL to other wallets or dApps? + +Yes, users can transfer sSOL to other wallets or dApps. However, please note that transferring sSOL may affect your ability to accrue points, as detailed below. + +### Will I continue to earn rewards if I hold or transfer sSOL? + +Points will continue to accrue as long as sSOL is held in the user’s wallet or deposited into a whitelisted dApp. If sSOL is deposited elsewhere or transferred, users will stop earning points. + +### How will I know if a dApp is whitelisted for earning rewards with sSOL? + +A list of whitelisted dApps will be provided on our official socials and documentation. Make sure to check the latest updates to ensure you are earning points while using sSOL. diff --git a/solayer-programs.md b/solayer-programs.md deleted file mode 100644 index 30c04e4..0000000 --- a/solayer-programs.md +++ /dev/null @@ -1,5 +0,0 @@ -# Solayer Programs - -Solayer has deployed the following programs. - -
ProgramDescriptionProgram ID
Restaking pool managerManages the flow of restaked assetssSo1iU21jBrU9VaJ8PJib1MtorefUV4fzC9GURa2KNn
diff --git a/solayer-valley-episodes/README.md b/solayer-valley-episodes/README.md deleted file mode 100644 index 1cfc36c..0000000 --- a/solayer-valley-episodes/README.md +++ /dev/null @@ -1,5 +0,0 @@ -# Solayer Valley Episodes - -Welcome to Solayer Valley, an interactive campaign streamed in episodic adventures. The valley offers eligible participants the opportunity to redeem hidden gems for future retroactive claims, tied to major product and feature milestones. Each episode represents an alternate world where we unlock and experience these milestones together. Participation in these episodes is the sole method to receive future retroactive rewards. - -
diff --git a/solayer-valley-episodes/eligibility-guide.md b/solayer-valley-episodes/eligibility-guide.md deleted file mode 100644 index 766641f..0000000 --- a/solayer-valley-episodes/eligibility-guide.md +++ /dev/null @@ -1,21 +0,0 @@ -# Eligibility Guide - -1. Go to [https://app.solayer.org/valley](https://app.solayer.org/valley) and connect your wallet. - -
- -2. Select one of the wallet options that is available for you. - -
- -3. Sing the message by clicking on “Confirm”. - -
- -4. Check whether you meet at least 3 requirements to be eligible... - -
- -5. ... or not eligible. - -
diff --git a/solayer-valley-episodes/rewards-claiming-guide.md b/solayer-valley-episodes/rewards-claiming-guide.md deleted file mode 100644 index fd501cd..0000000 --- a/solayer-valley-episodes/rewards-claiming-guide.md +++ /dev/null @@ -1,24 +0,0 @@ -# Rewards Claiming Guide - -1. **If eligible, you will be able to enter the Valley in order to claim your rewards.** - -
- -2. **Claim your Rewards (1/4):** your rank and percentile will be displayed. Click on "Claim" to proceed. - -
-3. **Claim your Rewards (2/4):** any extra boosts that you have accumulated so far. - -
- -4. **Claim your Rewards (3/4):** claim all the points from your referrals. - -
- -5. **Claim your Rewards (4/4):** get a mystery box that will be revealed after Episode 1. - -
- -6. Congrats! You've successfully claimed all your rewards. Now, let's move on to Episode 2! - -
diff --git a/why-on-solana.md b/why-on-solana.md new file mode 100644 index 0000000..0834372 --- /dev/null +++ b/why-on-solana.md @@ -0,0 +1,14 @@ +# Why on Solana? + +Trust is central to any decentralized system. Proof of stake is the most common Byzantine Fault-Tolerant Consensus in use today. However, bootstrapping a proof of stake ecosystem is challenging. There must be an economically incentivized fair distribution of initial stake, often in the form of newly minted tokens. This process can entail steep financial costs for participants, as they need to invest capital in an asset with an uncertain risk profile. + +The concept of shared security emerged to solve this issue - leveraging the stake in established POS systems with well-recognized assets like ETH and Solana. These systems, with their established validator networks, can provide security for other decentralized systems. Newer networks could use the existing stake on such chains to provide economic guarantees and security. + +### Solana's Superior Infrastructure + +Solana's high-performant, cost-effective, and high execution infrastructure is superior for SVN (Shared Validator Network) builders, operators, and restakers. The advantages of utilizing Solana as the foundational platform for SVN include: + +1. **Cost-Effective SVN Construction:** Utilizing Solana as the native Data Availability layer for SVN significantly reduces the cost of building an SVN compared to Ethereum. +2. **Low latency application**: Solana's lower block time production of 0.4 seconds compared to Ethereum's 20 seconds, enables low-latency SVNs resulting in a more responsive user experience. Examples include compute-intensive games, GPU clusters, and high-frequency DeFi applications. +3. **Cheaper state sync/update/finalization**: The process of state finalization, sync, and update of SVNs, which is a continual process to ensure the immutability and synchronization of validated applications, is considerably more cost-effective on Solana compared to other viable networks +4. **Cheaper state transition storage**: Storing state transitions in SVN is significantly cheaper when powered by Solana, making it a more economical choice for developers and operators.