Liquid staking update, core dev call and update validator keys (#712)

* Add files via upload

* Update 07-24-core-devs-call.md

* fix broken RPC url

* fix all the broken anchors and hyperlinks

* chore: fix some comments (#702)

Signed-off-by: zhoufanjin <[email protected]>

* shutterized -> to change to shutter enabled

* fix core dev call layout

* Core Devs Call Notes July 31, 2024

* remove custom signer from interact page

* fix: 07-31-core-devs-call format

* Core Devs Call Notes Aug 7, 2024

* "Liquid Staking" Page Update (#709)

* Update _generate_validator_keys_wagyu.md (#710)

Adding a warning about entering a withdrawal address at the key generation step in Wagyu. This idea comes after seeing multiple validators not paying attention to it recently and ending up having to update their withdrawal credential using Ethdo after which is not really easy for non technical people. This warning should hopefully prevent such cases in the future.

* Update voluntary-exit.md (#711)

Fixing a warning that wasn't really exact, as updating a 0x00 withdrawal credential is also possible on an exited validator as well but is much more challenging because the node is most often offline.

---------

Signed-off-by: zhoufanjin <[email protected]>
Co-authored-by: Armagan Ercan <[email protected]>
Co-authored-by: Armagan Ercan <[email protected]>
Co-authored-by: zhoufanjin <[email protected]>
Co-authored-by: zengzengzenghuy <[email protected]>
Co-authored-by: jackgale.eth <[email protected]>
Co-authored-by: theChim9 <[email protected]>

docs/node/management/voluntary-exit.md

@@ -11,7 +11,7 @@ Voluntary exit procedures vary depending on your client.
 :::caution
 Exits are non-reversible; once you have exited you cannot restart your validator.
 
-You must have a `0x01` type withdrawal address before exiting your validator [withdrawal credentials](withdrawals.md#check-withdrawal-credential). 
+It is recommended to update your withdrawal credentials to the `0x01` type before exiting your validator. Updating your withdrawal credentials later, when your node is stopped, will be more difficult. [withdrawal credentials](withdrawals.md#check-withdrawal-credential). 
 :::
 
 ### Dappnode

docs/node/manual/validator/_partials/_generate_validator_keys_wagyu.md

@@ -24,6 +24,10 @@
 
   ![DAppNode Step 3j](/img/node/dappnode-step3j.png)
 
+:::caution Be sure to enter a withdrawal address at this step. This address will be used to receive partial or full withdrawals. You can also choose not to enter an address at this step, but please note that updating it later can be difficult. [Withdrawals](../node/management/withdrawals.md)
+
+Please note that once you have chosen a withdrawal address (either at this step or later), it will not be possible to update it to another address. Therefore, make sure to choose an address that you control and that is secure. :::
+
   :::info 
   If you are running this program to generate keys within the context of the DAppNode Gnosis Chain Hardware Validator Incentive Program, make sure to generate 4 validators and to fill in the ETH1 Withdrawal Address Field with an address you have full control over.  Also make sure to choose a directory that reflects the folder where you want the files to be saved.
   :::
@@ -44,4 +48,4 @@
 
   ![DAppNode Step 3o](/img/node/dappnode-step3o.png)
 
-  The key generation is complete, and your keys have been saved to the folder you selected.
+  The key generation is complete, and your keys have been saved to the folder you selected.

docs/tools/liquid-staking.md

@@ -4,66 +4,84 @@
 
 # Liquid Staking
 
-Liquid staking providers allow anyone to stake without running the infrastructure themselves. It also gives stakers an opportunity to use their tokenized staked resources (sGNO & rGNO) for yield farming, borrowing or compounding while still protecting the protocol.
+Liquid staking allows anyone to stake on Gnosis Chain without running the infrastructure themselves. It also gives stakers an opportunity to use their tokenized staked resources (osGNO) for liquidity, yield farming or lending while still helping to secure Gnosis Chain.
 
-:::note
-Staked GNO (sGNO) and reward GNO (rGNO) can be converted to GNO following the Gnosis Execution Layer \<->\ Gnosis Beacon Chain merge. At that time the staking app will allow you to burn your sGNO and rGNO to redeem your original GNO deposit + your accrued GNO reward.
-:::
-
-## Stakewise Basics
+StakeWise - a long-standing partner of the Gnosis ecosystem - is the primary provider of liquid-staking for GNO, through their osGNO token. Following the [launch of StakeWise V3](https://stakewise.medium.com/announcing-the-launch-of-stakewise-v3-on-gnosis-chain-0231285bd8e3) in July 2024, GNO holders can stake with any of a variety of providers through StakeWise to mint osGNO. 
 
-1) Go to [https://app.stakewise.io](https://app.stakewise.io) and connect your wallet (We use MetaMask in this example, you can also use WalletConnect, Ledger or other options).
+This page explains how liquid staking with StakeWise works.
 
 ![](/img/node/stakewise-1.png)
 
-2) If your MetaMask is not yet connected to Gnosis, switch by clicking on the network button, selecting Gnosis, and pressing **Switch**.
+## osGNO
+
+StakeWise V3 provides users with a marketplace of staking providers, each competing to offer the highest yields, the lowest fees and the most consistent performance. By distributing demand for staking among a selection of providers, StakeWise helps to decentralise the network's validator set and increase the quantity of assets securing the network. However, in unifying arrangements with each of these providers around a single liquid-staking token — osGNO — it also provides a consistent and reliable experience for users, regardless of their chosen provider.
+
+*"osGNO"* stands for overcollateralized staked token. *"Overcollateralized"* refers to the limits on osGNO issuance, where only 90% of the stake (i.e. GNO tokens) provided can be made liquid through osGNO. However, 100% of the provided stake serves as backing for the liquid-staking token, leaving a substantial buffer in the event that stake is slashed for any reason.
 
 ![](/img/node/stakewise-2.png)
 
+osGNO ([0xF490c80aAE5f2616d3e3BDa2483E30C4CB21d1A0](https://gnosisscan.io/token/0xf490c80aae5f2616d3e3bda2483e30c4cb21d1a0)) is a non-rebasing token, meaning that the balance of tokens held by the user is naturally static, but the value of each token rises continually as the underlying amount of GNO per token increases due to staking rewards. This enables seemless integration of osGNO into other DeFi applications like decentralised exchanges and lending protocols. This also means that osGNO is not issued 1:1 with GNO tokens, and you will receive less osGNO tokens than the underlying amount of GNO tokens backing them.
+
+StakeWise processes two fees as part of its V3 implementation on Gnosis Chain: 
+
+* A flat fee of 5% of all staking rewards associated with your osGNO tokens is sent to StakeWise DAO. This fee is omitted for users who stake with StakeWise but do not mint osGNO; and
+
+* A *"Vault Fee"* is set by the provider and charged on all rewards earned by the GNO you stake with them. For StakeWise's own Genesis Vault, this fee is set at 15% of all rewards earned.
+
+## StakeWise Tutorial
+
+To access StakeWise V3 on Gnosis Chain and mint osGNO, simply:
+
+1) Head to [https://app.stakewise.io](https://app.stakewise.io), connect your wallet, and switch to Gnosis Chain.
+
 ![](/img/node/stakewise-3.png)
 
-3) Confirm the Network switch in MetaMask.
+2) On the Stake interface, you can select the amount of GNO you wish to stake, approve it for staking and then stake immediately into osGNO with the provider(s) allocated by the app.
 
 ![](/img/node/stakewise-4.png)
 
-4) Enter the GNO deposit amount into the Stake interface. Enter any amount of GNO to get started.  Note you can also change the recipient address if desired. You will receive the same amount of sGNO tokens relative to the GNO you stake.
-
-Agree to the terms and press confirm.
+3) Alternatively, head to the Vaults interface to select the provider you wish to stake with. Once you've selected a provider and moved to their page, select *"Stake"*, enter the amount of GNO, approve it and then stake it.
 
 ![](/img/node/stakewise-5.png)
 
-5) Confirm the deposit transaction in your wallet. You should now see sGNO added in the interface.
+4) Where you've staked with a specific vault, the relevant vault page will then show the amount staked with an option to *"Unstake"*. Below, it will also show the amount of osGNO minted for your stake, as well as options to *"Mint"* and *"Burn"* osGNO as appropriate.
 
-![](/img/node/sGNO.png)
+![](/img/node/stakewise-6.png)
 
-## Tokens (sGNO & rGNO)
+There you have it! You can now use your osGNO tokens freely, safe in the knowledge that your deposited GNO is earning staking rewards with StakeWise V3.
 
-* sGNO address on Gnosis:
-  [0xa4ef9da5ba71cc0d2e5e877a910a37ec43420445 ](https://blockscout.com/xdai/mainnet/token/0xA4eF9Da5BA71Cc0D2e5E877a910A37eC43420445/token-transfers)
-* rGNO address on Gnosis:
-  [0x6ac78efae880282396a335ca2f79863a1e6831d4 ](https://blockscout.com/xdai/mainnet/token/0x6aC78efae880282396a335CA2F79863A1e6831D4/token-transfers)
+![](/img/node/stakewise-7.png)
 
-You can [import to MetaMask](https://consensys.net/blog/metamask/how-to-add-your-custom-tokens-in-metamask/) as you would other tokens, or click on the 🦊 in Blockscout to add!
+## V2 Migration
 
-![](/img/node/blockscout-1.png)
+:::note
+StakeWise V2 has been deprecated, so will no longer be maintained. Please migrate to StakeWise V3 to continue earning staking rewards and supporting the network.
+:::
 
-At all times the total amount of tokens that have been issued to users is sGNO + rGNO = GNO deposits + GNO rewards \* (100% — 10%), where 10% is StakeWise commission.
+Prior to the [V3 launch](https://stakewise.medium.com/announcing-the-launch-of-stakewise-v3-on-gnosis-chain-0231285bd8e3), StakeWise operated its V2 staking protocol for GNO on Gnosis Chain. Though support for V2 has been deprecated, liquidity for some V2 assets remain on the chain.
 
-### sGNO
+StakeWise V2 consisted of 2 core assets:
 
-sGNO represents your initial stake of GNO deposited to the pool. Exchanging or transferring your sGNO balance will result in lower rGNO earned to your account, as you will have a smaller proportional amount staked that is earning rewards.
+* sGNO ([0xa4ef9da5ba71cc0d2e5e877a910a37ec43420445 ](https://gnosisscan.io/address/0xa4ef9da5ba71cc0d2e5e877a910a37ec43420445)) represents the initial stake of GNO deposited into StakeWise. This figure is static, but is used as the basis to calculate rewards owing to the user; and
 
-### rGNO
+* rGNO ([0x6ac78efae880282396a335ca2f79863a1e6831d4 ](https://gnosisscan.io/address/0x6ac78efae880282396a335ca2f79863a1e6831d4)) represents the earned staking rewards and are updated on a periodic basis, based on the amount of sGNO held. The V2 contracts frequently check and update the rGNO balance of all sGNO holders, to reflect both rewards earned and deductions from any slashing.
 
-rGNO represent earned staking rewards and are updated on a periodic basis.  Contracts check and update your reward balance based on staked GNO increases in the staking pool (or decreases if slashed).
+In V2, StakeWise charged a 10% commission for operating the network on all staking rewards before distributing them as rGNO. At all times, the total amount of tokens that had been issued to users in StakeWise V2 was equal to: *sGNO + rGNO = GNO deposits + (GNO rewards * (100% — 10%))*.
 
-The interface shows the time until the next update to your rGNO.
+![](/img/node/stakewise-8.png)
 
-![Time until next rGNO update](/img/node/next-update.png)
+If you hold or purchase any remaining sGNO or rGNO, StakeWise has provided a migration interface to move the underlying GNO tokens into V3. Follow this [tutorial](https://docs.stakewise.io/guides/stakewise-v2/migrate-to-stakewise-v3-on-gnosis-chain) to migrate, and check the Genesis Vault in V3 to find your migrated GNO.
 
-:::note
-**Coming Soon**: Use your rGNO in DeFi protocols on Gnosis to borrow and stake additional GNO! 
+## Learn More
 
-Since rGNO tokens represent your rewards in a StakeWise Pool, exchanging or transferring your rGNO will mean that you transferred your rewards to someone else. It will not impact your future earnings.
-:::
+You can find out more about StakeWise V3, the Gnosis deployment and osGNO with the following resources:
+
+* Read the StakeWise V3 [Documentation](https://docs.stakewise.io/);
+
+* Read StakeWise's [launch blog post](https://stakewise.medium.com/stakewise-v3-on-gnosis-chain-what-to-expect-how-to-migrate-1149a5367c76) on what to expect with osGNO;
+
+* Watch the Gnosis [Community Call](https://www.youtube.com/watch?v=fVVWtY_YBFo) with StakeWise from July 2024; and
+
+* Reach out to the community through the [StakeWise Discord Server](https://discord.gg/StakeWise).
 
+If you're interested in operating a vault in StakeWise V3, check out the recording of the [Vault Operator Workshop](https://www.youtube.com/watch?v=kX11K4ymn1Q).

updates/2024/08-07-core-devs-call.md

@@ -0,0 +1,148 @@
+---
+title: Gnosis Core Devs Call Notes
+
+---
+
+---
+title: Core Devs Call - 2024/08/07
+authors: [dapplion, armaganercan, filoozom]
+tags: [CoreDevsCall, Gnosis Chain]
+---
+
+# Gnosis Core Devs Call Notes
+
+Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression.
+
+Participants represent teams:
+
+Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team.
+
+With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community.
+
+Watch the record [here](https://www.youtube.com/watch?v=Jr4cBtp6Q1M)
+
+Aug 7, 2024
+
+# Client Team Updates
+## EL
+
+* **Nethermind**: 
+    * RC 1.28.0 https://github.com/NethermindEth/nethermind/releases/tag/1.28.0-rc 
+    * Would enable snap sync client by default
+    * Full release early next week
+    * Includes bug fixes and eth_simulate
+        * Potentially some block processing improvement
+    * Depending on the node: 2-3% or 10-15%
+    * Focus on stability
+    * Next version should be more performance oriented
+
+
+* **Erigon**: 
+  * Second alpha of Erigon v3 
+    * Introducing OtterSync, which makes it extremely fast to sync minimal, full and archive nodes
+        * Most of the time is spent downloading data
+        * A minimal node is like a full node without history (EIP-4444)
+            * Should be able to validate
+            * Should consume less than 100 GB of SSD
+  * Started working on Shutter
+  * Automated QA testing for tracking the tip on Erigon v2 and Erigon v3
+    * Erigon v3 is likely failing Hive tests on Gnosis
+    * There’s an ongoing issue with snapshot availability for Chiado
+        * There might not be enough Erigon Chiado nodes
+
+* **Geth**:
+    * Was able to sync Chiado
+        * It can produce blocks but they are incorrect
+        * Wanted to sync Erigon for Chiado but that’s quite slow and runs out of memory
+        * Needs to be able to debug one specific block
+    * How can one attach a debugger when a specific block is being executed?
+
+
+* **Reth**: 
+  * Testing post merge implementation with self generated blocks from Nethermind using engine api and feeding them to reth
+ * Currently stuck with wrong state root on block
+ * Different state root that might be related to AuRa
+    * Is it possible to export state diffs about everything in Erigon? If not, Nethermind is willing to implement some tools to that effect.
+        * Erigon has state diffs for transactions and system transactions, but not sure if there’s a tool to consume that data
+        * This is really necessary and slowing everything down for Guillaume and Reth on GC as well
+        * In Erigon v3 there’s state diffs for virtual transactions at the beginning and end of block
+
+# Chain Infra
+
+* **Gateway**
+  * The RPC was offline for a few seconds during the day because of the provider
+  * Recently updated one of the nodes
+
+# Innovation
+
+* Shutter
+    * Working on the dashboard
+    * Finished the data collection part
+    * Start a Grafana dashboard and web dashboard
+    * Debugging remaining issues with a long-running test
+        * 90% of the transactions got included immediately
+        * Looking into why the remaining 10% are not being included
+            * Potentially latency issues
+    * Ongoing discussion about p2p discovery because the current one used by the keypers is a bit difficult to implement in the C# library
+    * Nethermind is checking if they can implement a simpler version of Kademlia DHT
+
+
+# Testing
+
+* Hive
+    * Setting up proper debugging
+* Ethereum/tests
+    * https://github.com/NethermindEth/nethermind/pull/6833
+    * This would allow Nethermind to run the Ethereum tests
+    * Looking into how to make this work for Gnosis
+
+# Research
+
+* Gas Market
+    * No updates
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+