Merge pull request #29 from PufferFinance/update/remove-testnet-discl…

…aimers

Make instructions more generic for testnet/mainnet

docs/registration.md

@@ -18,15 +18,15 @@ The [Puffer Dashboard](https://launchpad.puffer.fi/Setup) UI is subject to chang
 
 
 # Registering a Validator
+The [Puffer Dashboard](https://launchpad.puffer.fi/Setup) supports launching both testnet and mainnet validators depending on the RPC that your wallet is connected to. 
+
 ### Step 1: Setup Wallet
 ![alt text](/img/holesky-config.png)
-Follow [the instructions](https://holesky.dev/), to add the Holesky network to your wallet.
+Follow [the instructions](https://holesky.dev/), to add the Holesky network to your wallet. If you're using mainnet, the default mainnet wallet config can be used or an RPC can be added [here](https://chainlist.org/chain/1).
 
 ### Step 2: Get Coral-CLI Command
 Navigate to https://launchpad.puffer.fi/Setup to copy the Coral-CLI command. 
 
-Make sure your wallet is set to the Holesky network. 
-
 Run the command where you [installed the Coral-CLI](/nodes/setup#setup-coral-cli).
 
 #### Without Enclave
@@ -39,7 +39,7 @@ The following **example** command will create a local validator keystore file in
 cargo run --bin coral-cli validator keygen --guardian-threshold 1 --module-name 0x5055464645525f4d4f44554c455f300000000000000000000000000000000000 --withdrawal-credentials 0x0100000000000000000000005ee9246f01e95c08ee767029c1d18765bb1779d0 --guardian-pubkeys 0x049cc1fbaa3cffd3e4c1f935c47720d013938ccb822a9cbd20c5f09ab65ae8300e7986b6ce75e916d3b59599ece72134adf2972d06a76a8ba5f3747d356117c342 --fork-version 0x01017000 --password-file password.txt --output-file registration.json
  ```
 
-#### With Enclave
+#### With Enclave (currently only supported on testnet)
 > ![alt text](/img/enclave-cli-cmd.png)
 1. Copy the displayed command
 2. Edit `<OPTIONAL_ENCLAVE_URL>` and `<PATH_TO_REGISTRATION_JSON>` 

docs/setup.md

@@ -7,7 +7,7 @@ slug: /nodes/setup
 In order to run a [validator](https://ethereum.org/en/developers/docs/nodes-and-clients/run-a-node/), you will need to run an Execution Layer client, a Consensus Layer client, and the validator software.
 
 :::note
-Puffer is in testnet and is using the 🦁 [Holesky testnet](https://holesky.dev/), so make sure to set the network to `holesky`
+Puffer is live on Mainnet! If you wish to setup a testnet validator, we're using the 🦁 [Holesky testnet](https://holesky.dev/), so make sure to set the network to `holesky`, otherwise use `mainnet`
 :::
 
 ### Easy Mode
@@ -53,6 +53,10 @@ cargo build --release
 ## Setup Validator Enclave (optional)
 Follow along to setup your enclave to run a validator with a 1 ETH bond.
 
+:::caution TEE Registrations are not yet supported on mainnet 🚧  
+As part of our ongoing commitment to security and operational excellence, we are taking a phased approach to implementing enclave-based registrations. Due to recent changes in Intel’s support for certain enclave hardware, access to the necessary hardware has become more challenging. To ensure the highest standards of security, enclave-registrations will not be available during the initial phase of our mainnet launch.
+:::
+
 :::caution
 Secure-Signer requires Ubuntu 20.04!
 :::
@@ -155,7 +159,7 @@ f3b600f2d50b4c1cc42495f6c4f20bdb0c9a1dd17d5923de83d2723c2d1cab04
 The following command run a container with the name `puffer_secure_signer_container` built from the pulled `puffer_validator` image. Notice we are mounting our volume `Puffer-Validator-Backup` to the `/Validator` enclave directory so any changes to the `/Validator` enclave directory persist if the container is removed:
 
 :::caution
-Ensure image tag matches latest version described on testnet repository before running the next command! (Here image tag is 1.1.0)
+Ensure image tag matches latest version described on [here](https://hub.docker.com/r/pufferfi/validator/tags) before running the next command! (Here image tag is 1.1.0)
 :::
 
 ```