Skip to content

Commit

Permalink
GITBOOK-104: Martin's Jul 1 changes
Browse files Browse the repository at this point in the history
  • Loading branch information
Palazoff authored and gitbook-bot committed Jul 2, 2024
1 parent 0a2b0d9 commit 57d4d40
Show file tree
Hide file tree
Showing 52 changed files with 77 additions and 17 deletions.
Binary file added .gitbook/assets/image (1) (1) (1) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (1) (1) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (1) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (2) (1) (1) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (2) (1) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (2) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (2) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (2) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (2).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (3) (1) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (3) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (3) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (3) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (3).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (36).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (37).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (38).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (39).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (4) (1) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (4) (1) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (4) (1).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .gitbook/assets/image (4).png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .gitbook/assets/image (40).png
Binary file added .gitbook/assets/image (41).png
Binary file added .gitbook/assets/image (42).png
Binary file added .gitbook/assets/image (43).png
Binary file added .gitbook/assets/image (44).png
Binary file added .gitbook/assets/image (45).png
Binary file added .gitbook/assets/image (46).png
Binary file added .gitbook/assets/image (5) (1) (1).png
Binary file modified .gitbook/assets/image (5) (1).png
Binary file modified .gitbook/assets/image (5).png
Binary file added .gitbook/assets/image (6) (1) (1).png
Binary file modified .gitbook/assets/image (6) (1).png
Binary file modified .gitbook/assets/image (6).png
Binary file added .gitbook/assets/image (7) (1) (1).png
Binary file modified .gitbook/assets/image (7) (1).png
Binary file modified .gitbook/assets/image (7).png
Binary file modified .gitbook/assets/image.png
4 changes: 3 additions & 1 deletion SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,13 +16,15 @@
* [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](delegation.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)
Expand Down
2 changes: 1 addition & 1 deletion delegation.md → endogenous-avs/delegation.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,4 @@
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.

<figure><img src="../.gitbook/assets/image.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (7).png" alt=""><figcaption></figcaption></figure>
2 changes: 1 addition & 1 deletion endogenous-avs/solayer-swqos-infrastructure.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,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.

<figure><img src="../.gitbook/assets/image (4) (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (4) (1) (1).png" alt=""><figcaption></figcaption></figure>

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.

2 changes: 1 addition & 1 deletion restaking-epochs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@

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.

<figure><img src="../.gitbook/assets/image (7).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (7) (1).png" alt=""><figcaption></figcaption></figure>
4 changes: 2 additions & 2 deletions restaking/restaking-architecture.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Restaking Architecture

<figure><img src="../.gitbook/assets/image (2) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (2) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>

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.

Expand All @@ -19,7 +19,7 @@ The Restake method on Solayer is permissioned and requires an additional signatu

## **Native SOL restaking**

<figure><img src="../.gitbook/assets/image (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>

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.

Expand Down
4 changes: 2 additions & 2 deletions restaking/restaking-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,11 @@

&#x20;**Step 1: Navigate to app.solayer.org**&#x20;

<figure><img src="../.gitbook/assets/image (3) (1) (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (3) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>

**Step 2: Select which LST you would like to restake.**&#x20;

<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (1) (1) (1) (1) (1) (1).png" alt=""><figcaption></figcaption></figure>

**Step 3**: Enter the amount you would like to restake for token approval.

Expand Down
2 changes: 1 addition & 1 deletion solayer-valley-episodes/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@

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.

<figure><img src="../.gitbook/assets/image (1) (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/image (1) (1) (1).png" alt=""><figcaption></figcaption></figure>
21 changes: 21 additions & 0 deletions solayer-valley-episodes/eligibility-guide.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Eligibility Guide

1. Go to [https://app.solayer.org/valley](https://app.solayer.org/valley) and connect your wallet.&#x20;

<figure><img src="../.gitbook/assets/image (3).png" alt=""><figcaption></figcaption></figure>

2. Select one of the wallet options that is available for you.&#x20;

<figure><img src="../.gitbook/assets/image (4).png" alt=""><figcaption></figcaption></figure>

3. Sing the message by clicking on “Confirm”.&#x20;

<figure><img src="../.gitbook/assets/image (5).png" alt=""><figcaption></figcaption></figure>

4. Check whether you meet at least 3 requirements to be eligible...

<figure><img src="../.gitbook/assets/image (36).png" alt=""><figcaption></figcaption></figure>

5. ... or not eligible.&#x20;

<figure><img src="../.gitbook/assets/image (6).png" alt=""><figcaption></figcaption></figure>
29 changes: 21 additions & 8 deletions solayer-valley-episodes/episode-1-the-timebox-sanctuary.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,26 @@ The Timebox Sanctuary blends shimmering brass with aged wood, creating an enchan

Participation in Episode 1 is exclusive, requiring members to meet at least 3 of the following 6 criteria, ensuring a dedicated and engaged community:

* Deposit in any of the LST pools
* Obtain a permanent referral link (deposit 10 SOL)
* Participate in Epoch 0
* Participate in at least 3 epochs
* Refer others who have deposited
* Use all invite codes
1. Got a permanent referral link
2. Deposited in any of the LST pools
3. Participated in Epoch 0
4. Participated in at least 2 Epochs
5. Referred users who have deposited
6. Invited at least 3 people

### **Completion Requirements**
### Episode 1 Explainer&#x20;

To fully stream Episode 1 and distribute rewards, 80% of qualifying participants must complete the journey. If this target is not met by July 8th, 4 days after the initial ending date, unclaimed rewards will be redistributed pro rata among the participants.
Episode 1 went live at [app.solayer.org/valley](http://app.solayer.org/valley) on the July 2nd, alongside Epoch 3.

Episode 1 is where depositors claim their rewards in conjunction with restaking deposits. This includes:

1. **Percentile Rankings** - percentile ranking shows where you stand based on your deposit amount, such as being in the top 10%.
2. **Numerical Ranks** - numerical rank indicates your position among all unique deposit addresses.
3. **Extra Credits** - extra credits provide boosts based on specific actions, such as Epoch 0 and Epoch 1 participation, as well as basic LST and native SOL boost.
4. **Referral Points** - referral points are earned based on how many people joined using your referral link and their deposit amounts.

Episodes capture your contribution to the protocol alongside product milestones. Future Episodes will offer refreshed snapshots for further claims.&#x20;

Concurrently, Epoch 3 is live for eligibility checks, and withdrawals will be enabled after EP 1 claims are completed to avoid accounting errors.&#x20;

More information on withdrawals will be provided soon.
24 changes: 24 additions & 0 deletions solayer-valley-episodes/rewards-claiming-guide.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Rewards Claiming Guide

1. **If eligible, you will be able to enter the Valley in order to claim your rewards.**&#x20;

<figure><img src="../.gitbook/assets/image (37).png" alt=""><figcaption></figcaption></figure>

2. **Claim your Rewards (1/4):** your rank and percentile will be displayed. Click on "Claim" to proceed.

<figure><img src="../.gitbook/assets/image (38).png" alt=""><figcaption></figcaption></figure>
3. **Claim your Rewards (2/4):** any extra boosts that you have accumulated so far.

<figure><img src="../.gitbook/assets/image (40).png" alt=""><figcaption></figcaption></figure>

4. **Claim your Rewards (3/4):** claim all the points from your referrals.&#x20;

<figure><img src="../.gitbook/assets/image (44).png" alt=""><figcaption></figcaption></figure>

5. **Claim your Rewards (4/4):** get a mystery box that will be revealed after Episode 1.

<figure><img src="../.gitbook/assets/image (46).png" alt=""><figcaption></figcaption></figure>

6. Congrats! You've successfully claimed all your rewards. Now, let's move on to Episode 2!

<figure><img src="../.gitbook/assets/image (43).png" alt=""><figcaption></figcaption></figure>

0 comments on commit 57d4d40

Please sign in to comment.