Update Faucet Link, Upgraded guides section (#720)

* 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.

* Add files via upload

* Update 08-21-core-devs-call.md

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

* Updates 08-21-core-devs-call.md for a small typo

* Core Devs call notes Aug 28

* feat: Cookbook Onboard integration (#715)

* Update 08-28-core-devs-call.md - fix format

* Added dRPC to community Faucets (#698)

* chore(bridges): update deprecated url to https://github.com/tokenbridge/

* add section for running node with eth swarm setup

* feat(bridges): add Hashi integration overview

* chore(bridges): add testnet contracts for Hashi integration

* fix: error

* added custom signers guides

* Add Confidential Computing category and Secret Network tooling (#719)

* Create confidential-computing

* Delete docs/technicalguides/confidential-computing

* Create secret-network.md

* Update secret-network.md

* Updated the faucet link

* fix naming for confidential computing

---------

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]>
Co-authored-by: Anton Dosta <[email protected]>
Co-authored-by: Martin <[email protected]>
Co-authored-by: zengzengzenghuy <[email protected]>
Co-authored-by: skundu42 <[email protected]>
Co-authored-by: Patrick | Secret Network <[email protected]>

docs/about/networks/README.md

@@ -26,4 +26,4 @@ keywords:
 | CL Explorer        | https://gnosischa.in/            | https://beacon.chiadochain.net       |
 | Fork monitor       | https://forkmon.gnosischain.com  | https://forkmon.chiadochain.net      |
 | EthStats           | https://ethstats.gnosischain.com | https://ethstats.chiadochain.net     |
-| Faucet             | https://gnosisfaucet.com         | https://faucet.chiadochain.net/      |
+| Faucet             | https://faucet.gnosischain.com/  | https://faucet.chiadochain.net/      |

docs/technicalguides/Confidential Computing/secret-network.md

@@ -0,0 +1,19 @@
+# Secret Network
+
+On most blockchains, all data is public by default. While this works for many of the popular Web3 applications we see today, having the ability to keep some data confidential unlocks powerful new capabilities. Incorporating decentralized confidential computing (DeCC) enables things like private voting for DAOs, secure random number generation for gaming, encrypted databases for various applications, encrypted data tied to NFTs, sealed-bid auctions, and encrypted order books for DeFi applications. All of this can be built on Gnosis by utilizing [Secret Network](https://scrt.network)’s Confidential Computing Layer.
+
+## Integrating Secret's Confidential Computing Layer​
+
+You can integrate Secret’s CCL into an existing Gnosis application, or design a new application from the ground up to take advantage of the unique use-cases it enables.
+
+To start, check out Secret Network’s [Confidential Computing Layer](https://scrt.network/confidential-computing-layer) landing page to get an overview of how it works, and example use-cases for inspiration. From there you’ll find multiple links to Secret's CCL documentation:
+
+1. [Basics](https://docs.scrt.network/secret-network-documentation/confidential-computing-layer/ethereum-evm-developer-toolkit/basics) - explains the cross-chain communication technologies used, and how to connect a MetaMask wallet to Secret Network.
+
+2. [Use-cases](https://docs.scrt.network/secret-network-documentation/confidential-computing-layer/ethereum-evm-developer-toolkit/usecases) - provides tutorials showing how to build various types of EVM applications using Secret’s CCL. All of these tutorials can be used to deploy a contract on Gnosis.
+
+3. [Supported Networks](https://docs.scrt.network/secret-network-documentation/confidential-computing-layer/ethereum-evm-developer-toolkit/supported-networks) - provides a list of gateway contract addresses. This is how your Gnosis application will communicate with Secret.
+
+## Get Support
+
+To get CCL development help, you can join the Secret Network [Discord](https://scrt.network/discord) or [Telegram](https://scrt.network/SCRTCommunity). You can also [get in touch](mailto:[email protected]) with the Secret Network team directly.