Section id stringlengths 9 9 | Website URL stringlengths 35 66 | Heading stringlengths 4 119 | Text stringlengths 0 6k | YouTube Links stringclasses 1
value | Images stringlengths 0 8.32k | Data Collection Date stringclasses 13
values |
|---|---|---|---|---|---|---|
rpl000501 | https://docs.rocketpool.net/guides/redstone/docker-migration.html | Initialize your Fee Distributor | If you aren't planning to opt into the Smoothing Pool and claim all of your priority fees and MEV rewards to your fee distributor contract, you will eventually have to initialize it (create the contract instance on the chain) in order to claim rewards from it to your withdrawal address.
This is a fairly cheap operation... | 19:09:25hrs 10-06-2023 | ||
rpl000502 | https://docs.rocketpool.net/guides/redstone/docker-migration.html | Opt Into the Smoothing Pool | If you plan on taking advantage of the Smoothing Pool right away, you should opt in before the end of the first Redstone rewards period to maximize your "eligibility" amount.
Opting in can be done via running the following command:
rocketpool node join-smoothing-pool | 19:09:25hrs 10-06-2023 | ||
rpl000503 | https://docs.rocketpool.net/guides/redstone/docker-migration.html | Claim Rewards | The Redstone upgrade replaces the expensive, problematic old rewards system with a brand new one that's much cheaper, supports automatic restaking of RPL (both partial and full amounts), and - most importantly - lets you claim your rewards whenever you want.
Because there is no longer a time limit on claiming rewards, ... | 19:09:25hrs 10-06-2023 | ||
rpl000504 | https://docs.rocketpool.net/guides/redstone/docker-migration.html | Reverting to v1.4.3 | If, for any reason, something isn't to your liking and you want to revert to the previous Smartnode release, you can do so easily. The Smartnode automatically backs up your settings from the previous version when you upgrade it, so simply get the previous version (here we're demonstrating v1.4.3) and replace the settin... | 19:09:25hrs 10-06-2023 | ||
rpl000505 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | [Hybrid Mode] Guide to the Redstone Update and the Merge | This guide will cover everything you need to know in order to prepare your node for the Redstone Update and The Merge if you are using Hybrid Mode. | 19:09:25hrs 10-06-2023 | ||
rpl000506 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Things to Do Before Upgrading to v1.5.0 | Before upgrading to v1.5.0 and higher of the Smartnode, please go through the following checklist to make sure you're prepared: | 19:09:25hrs 10-06-2023 | ||
rpl000507 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Switch to a Full Execution Client | The Merge requires you to run your own Execution client, so you won't be able to use remote providers like Infura or Pocket anymore.
Because of this change, if you're currently using a light Execution client, you should switch to a full client while you're still on v1.4, let it sync to completion, and then upgrade to v... | 19:09:25hrs 10-06-2023 | ||
rpl000508 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Ensure the EC and CC are Both Externally Managed | Previous versions of the Smartnode stack allowed you to have one client locally managed, and the other externally managed. For example, you could have an Execution client that the Smartnode manages and connect it to a Consensus client that you manage externaly.
Starting with v1.5, this configuration is no longer suppor... | 19:09:25hrs 10-06-2023 | ||
rpl000509 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Set Up the Engine API | The Merge changes the way your Execution client talks to your Consensus client. Instead of using the old HTTP or Websocket based RPC system, The Merge requires a new system exposed by your Execution client called the Engine API.
This is a special connection that lets the Consensus client replace the old Proof-of-Work m... | 19:09:25hrs 10-06-2023 | ||
rpl000510 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Upgrading to v1.5.0 | Upgrading the Smartnode stack to v1.5.0 is no different than any other upgrade. Simply follow the normal directions here. | 19:09:25hrs 10-06-2023 | ||
rpl000511 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Things the Smartnode Handles Automatically | In Hybrid mode, the Smartnode will take care of some of the changes needed to support Redstone automatically once you update to v1.5.0, but you will need to handle others manually in Hybrid Mode.
Here's a brief list of what it will do for you without any manual intervention: | 19:09:25hrs 10-06-2023 | ||
rpl000512 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Your Fee Recipient | The fee recipient is the address on the Execution layer (eth1) chain that will receive all of the priority fees for blocks you propose. It is a setting provided to your Validator client when it first starts.
The Smartnode will handle setting it up to the correct address on the Validator client it manages when you upgra... | 19:09:25hrs 10-06-2023 | ||
rpl000513 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Things You Should Do After Upgrading | While the Smartnode handles most of the changes for you, there are a few additional things you should do manually: | 19:09:25hrs 10-06-2023 | ||
rpl000514 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Ensure a Successful Upgrade | The first thing to do is ensure that your node is working correctly. Consider taking the following steps:
Check the logs for errors with rocketpool service logs validator and rocketpool service logs node.Confirm with a Block Explorer (such as your Grafana dashboard and https://beaconcha.in) that you are still attesting... | 19:09:25hrs 10-06-2023 | ||
rpl000515 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Set Up MEV-Boost | MEV-boost is the system Flashbots provides to give MEV rewards to Proof-of-Stake validators after The Merge.
Rocket Pool requires all nodes to use it to maximize their returns and thus keep the protocol competitive with other staking services.
You will need to make some adjustments to your Beacon Node / Consensus clien... | 19:09:25hrs 10-06-2023 | ||
rpl000516 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Set Up a Fallback Node | Because The Merge is not compatible with remote providers like Infura and Pocket, you'll lose the ability to use them as fallback Execution clients when your primary goes offline.
The Smartnode still has the ability to provide a fallback Execution client (and now a fallback Consensus client as well), but you will now n... | 19:09:25hrs 10-06-2023 | ||
rpl000517 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Initialize your Fee Distributor | If you aren't planning to opt into the Smoothing Pool and claim all of your priority fees and MEV rewards to your fee distributor contract, you will eventually have to initialize it (create the contract instance on the chain) in order to claim rewards from it to your withdrawal address.
This is a fairly cheap operation... | 19:09:25hrs 10-06-2023 | ||
rpl000518 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Opt Into the Smoothing Pool | If you plan on taking advantage of the Smoothing Pool right away, you should opt in before the end of the first Redstone rewards period to maximize your "eligibility" amount.
Opting in can be done via running the following command:
rocketpool node join-smoothing-pool | 19:09:25hrs 10-06-2023 | ||
rpl000519 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Claim Rewards | The Redstone upgrade replaces the expensive, problematic old rewards system with a brand new one that's much cheaper, supports automatic restaking of RPL (both partial and full amounts), and - most importantly - lets you claim your rewards whenever you want.
Because there is no longer a time limit on claiming rewards, ... | 19:09:25hrs 10-06-2023 | ||
rpl000520 | https://docs.rocketpool.net/guides/redstone/hybrid-migration.html | Reverting to v1.4.3 | If, for any reason, something isn't to your liking and you want to revert to the previous Smartnode release, you can do so easily. The Smartnode automatically backs up your settings from the previous version when you upgrade it, so simply get the previous version (here we're demonstrating v1.4.3) and replace the settin... | 19:09:25hrs 10-06-2023 | ||
rpl000521 | https://docs.rocketpool.net/guides/redstone/native-migration.html | [Native Mode] Guide to the Redstone Update and the Merge | This guide will cover everything you need to know in order to prepare your node for the Redstone Update and The Merge if you are using Native Mode. | 19:09:25hrs 10-06-2023 | ||
rpl000522 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Things to Do Before Upgrading to v1.5.0 | Before upgrading to v1.5.0 and higher of the Smartnode, please go through the following checklist to make sure you're prepared: | 19:09:25hrs 10-06-2023 | ||
rpl000523 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Switch to a Full Execution Client | The Merge requires you to run your own Execution client, so you won't be able to use remote providers like Infura or Pocket anymore.
Because of this change, if you're currently using a light Execution client, you should switch to a full client while you're still on v1.4, let it sync to completion, and then upgrade to v... | 19:09:25hrs 10-06-2023 | ||
rpl000524 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Set Up the Engine API | The Merge changes the way your Execution client talks to your Consensus client. Instead of using the old HTTP or Websocket based RPC system, The Merge requires a new system exposed by your Execution client called the Engine API.
This is a special connection that lets the Consensus client replace the old Proof-of-Work m... | 19:09:25hrs 10-06-2023 | ||
rpl000525 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Upgrading to v1.5.0 | Upgrading the Smartnode stack to v1.5.0 is no different than any other upgrade. Simply follow the normal directions here. | 19:09:25hrs 10-06-2023 | ||
rpl000526 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Things You Should Do After Upgrading | In Native mode, there are several things you will need to do manually after upgrading: | 19:09:25hrs 10-06-2023 | ||
rpl000527 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Ensure a Successful Upgrade | The first thing to do is ensure that your node is working correctly. Consider taking the following steps:
Check your log scripts for the Execution client, the Consensus client, the Validator client, and the Smartnode daemon (the rp-node service) to ensure they're all functioning normally without errors.Confirm with a B... | 19:09:25hrs 10-06-2023 | ||
rpl000528 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Set up the Fee Recipient in your Validator Client | One of the critical details to set up prior to the Merge is the fee recipient specified by your validator client. As described in the overview article, this can be one of two values:
If you are opted into the Smoothing Pool, this must be the address of the Smoothing Pool contract. You can get the address from the offic... | 19:09:25hrs 10-06-2023 | ||
rpl000529 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Automatic Management via the Daemon | The Smartnode daemon will automatically determine the appropriate fee recipient for your node and manage it in case it changes (such as opting into and out of the Smoothing Pool). This is the safest option, because the Smartnode will always ensure it's set to a value that prevents penalization.
The way it does this is ... | 19:09:25hrs 10-06-2023 | ||
rpl000530 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Manual Fee Recipient Management | WARNINGBy doing this, you assume full responsibility for ensuring your fee recipient is always set to the correct address.Please read the penalty specification to understand what it must be set to given your configuration, and when you can safely change it from one value to another.Failure to do so could result in your... | 19:09:25hrs 10-06-2023 | ||
rpl000531 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Set Up MEV-Boost | MEV-boost is the system Flashbots provides to give MEV rewards to Proof-of-Stake validators after The Merge.
Rocket Pool requires all nodes to use it to maximize their returns and thus keep the protocol competitive with other staking services.
You will need to make some adjustments to your Beacon Node / Consensus clien... | 19:09:25hrs 10-06-2023 | ||
rpl000532 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Set Up a Fallback Node | Because The Merge is not compatible with remote providers like Infura and Pocket, you'll lose the ability to use them as fallback Execution clients when your primary goes offline.
The Smartnode still has the ability to provide a fallback Execution client (and now a fallback Consensus client as well), but you will now n... | 19:09:25hrs 10-06-2023 | ||
rpl000533 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Initialize your Fee Distributor | If you aren't planning to opt into the Smoothing Pool and claim all of your priority fees and MEV rewards to your fee distributor contract, you will eventually have to initialize it (create the contract instance on the chain) in order to claim rewards from it to your withdrawal address.
This is a fairly cheap operation... | 19:09:25hrs 10-06-2023 | ||
rpl000534 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Opt Into the Smoothing Pool | If you plan on taking advantage of the Smoothing Pool right away, you should opt in before the end of the first Redstone rewards period to maximize your "eligibility" amount.
Opting in can be done via running the following command:
rocketpool node join-smoothing-pool | 19:09:25hrs 10-06-2023 | ||
rpl000535 | https://docs.rocketpool.net/guides/redstone/native-migration.html | Claim Rewards | The Redstone upgrade replaces the expensive, problematic old rewards system with a brand new one that's much cheaper, supports automatic restaking of RPL (both partial and full amounts), and - most importantly - lets you claim your rewards whenever you want.
Because there is no longer a time limit on claiming rewards, ... | 19:09:25hrs 10-06-2023 | ||
rpl000536 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Preparing a Raspberry Pi | NOTEThis page has been left here for archival purposes. We no longer recommend running Rocket Pool on a Raspberry Pi due to the increased hardware and performance requirements of running an Ethereum validator.
This guide will walk you through how run a Rocket Pool node using a Raspberry Pi. While this is not typically ... | 19:09:25hrs 10-06-2023 | ||
rpl000537 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Preliminary Setup | To run a Rocket Pool node on a Raspberry Pi, you'll need to first have a working Raspberry Pi. If you already have one up and running - great! You can skip down to the Mounting the SSD section. Just make sure you have a fan attached before you go. If you're starting from scratch, then read on. | 19:09:25hrs 10-06-2023 | ||
rpl000538 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | What You'll Need | These are the recommended components that you'll need to buy in order to run Rocket Pool on a Pi:
A Raspberry Pi 4 Model B, the 8 GB modelNote: while you can use a 4 GB with this setup, we strongly recommend you go with an 8 GB for peace of mind... it's really not much more expensive.A USB-C power supply for the Pi. Yo... | 19:09:25hrs 10-06-2023 | ||
rpl000539 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Making the Fan Run More Quietly | When you get the fan, by default you're probably going to be instructed to connect it to the 5v GPIO pin, as shown in the picture below. The fan will have a connector with two holes; the black one should go to GND (pin 6), and the red one should go to +5v (pin 4).
However, in our experience, this makes the fan run very... | 19:09:25hrs 10-06-2023 | ||
rpl000540 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Installing the Operating System | There are a few varieties of Linux OS that support the Raspberry Pi. For this guide, we're going to stick to Ubuntu 20.04. Ubuntu is a tried-and-true OS that's used around the world, and 20.04 is (at the time of this writing) the latest of the Long Term Support (LTS) versions, which means it will keep getting security ... | 19:09:25hrs 10-06-2023 | ||
rpl000541 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Mounting the SSD | As you may have gathered, after following the above installation instructions, the core OS will be running off of the microSD card. That's not nearly large enough or fast enough to hold all of the Execution and Consensus blockchain data, which is where the SSD comes in. To use it, we have to set it up with a file syste... | 19:09:25hrs 10-06-2023 | ||
rpl000542 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Connecting the SSD to the USB 3.0 Ports | Start by plugging your SSD into one of the Pi's USB 3.0 ports. These are the blue ports, not the black ones:
The black ones are slow USB 2.0 ports; they're only good for accessories like mice and keyboards. If you have your keyboard plugged into the blue ports, take it out and plug it into the black ones now. | 19:09:25hrs 10-06-2023 | ||
rpl000543 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Formatting the SSD and Creating a New Partition | WARNINGThis process is going to erase everything on your SSD. If you already have a partition with stuff on it, SKIP THIS STEP because you're about to delete it all! If you've never used this SSD before and it's totally empty, then follow this step.
Run this command to find the location of your disk in the device table... | 19:09:25hrs 10-06-2023 | ||
rpl000544 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Optimizing the New Partition | Next, let's tune the new filesystem a little to optimize it for validator activity.
By default, ext4 will reserve 5% of its space for system processes. Since we don't need that on the SSD because it just stores the Execution (ETH1) and Consensus (ETH2) chain data, we can disable it:
sudo tune2fs -m 0 /dev/sda1 | 19:09:25hrs 10-06-2023 | ||
rpl000545 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Mounting and Enabling Automount | In order to use the drive, you have to mount it to the file system. Create a new mount point anywhere you like (we'll use /mnt/rpdata here as an example, feel free to use that):
sudo mkdir /mnt/rpdata
Now, mount the new SSD partition to that folder:
sudo mount /dev/sda1 /mnt/rpdata
After this, the folder /mnt/rpdata wi... | 19:09:25hrs 10-06-2023 | ||
rpl000546 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Testing the SSD's Performance | Before going any further, you should test your SSD's read/write speed and how many I/O requests it can handle per second (IOPS). If your SSD is too slow, then it won't work well for a Rocket Pool node and you're going to end up losing money over time.
To test it, we're going to use a program called fio. Install it like... | 19:09:25hrs 10-06-2023 | ||
rpl000547 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Setting up Swap Space | The Pi has 8 GB (or 4 GB if you went that route) of RAM. For our configuration, that will be plenty. Then again, it never hurts to add a little more. What we're going to do now is add what's called swap space. Essentially, it means we're going to use the SSD as "backup RAM" in case something goes horribly, horribly wro... | 19:09:25hrs 10-06-2023 | ||
rpl000548 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Creating a Swap File | The first step is to make a new file that will act as your swap space. Decide how much you want to use - a reasonable start would be 8 GB, so you have 8 GB of normal RAM and 8 GB of "backup RAM" for a total of 16 GB. To be super safe, you can make it 24 GB so your system has 8 GB of normal RAM and 24 GB of "backup RAM"... | 19:09:25hrs 10-06-2023 | ||
rpl000549 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Configuring Swappiness and Cache Pressure | By default, Linux will eagerly use a lot of swap space to take some of the pressure off of the system's RAM. We don't want that. We want it to use all of the RAM up to the very last second before relying on SWAP. The next step is to change what's called the "swappiness" of the system, which is basically how eager it is... | 19:09:25hrs 10-06-2023 | ||
rpl000550 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Overclocking the Pi | By default, the 1.5 GHz processor that the Pi comes with is a pretty capable little device. For the most part, you should be able to validate with it just fine. However, we have noticed that on rare occasions, your validator client gets stuck working on some things and it just doesn't have enough horsepower to keep up ... | 19:09:25hrs 10-06-2023 | ||
rpl000551 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Benchmarking the Stock Configuration | Before overclocking, your should profile what your Pi is capable of in its stock, off-the-shelf configuration. There are three key things to look at:
We're going to get stats on all three of them as we go. | 19:09:25hrs 10-06-2023 | ||
rpl000552 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Performance | For measuring performance, you can use LINPACK. We'll build it from source.
cd ~
sudo apt install gcc
wget http://www.netlib.org/benchmark/linpackc.new -O linpack.c
...
cc -O3 -o linpack linpack.c -lm
...
sudo mv linpack /usr/local/bin
rm linpack.c
Now run it like this:
linpack
Enter array size (q to quit) [200]:
Just ... | 19:09:25hrs 10-06-2023 | ||
rpl000553 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Temperature | Next, let's stress the Pi out and watch its temperature under heavy load. First, install this package, which will provide a tool called vcgencmd that can print details about the Pi:
sudo apt install libraspberrypi-bin
Once this is installed, reboot the Pi (this is necessary for some new permission to get applied). Next... | 19:09:25hrs 10-06-2023 | ||
rpl000554 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Stability | Testing the stability of an overclock involves answering these three questions:
Does the Pi turn on and get to a login promp / start the SSH server?Does it randomly freeze or restart during normal operations?Does it randomly freeze or restart during heavy load?
For an overclock to be truly stable, the answers must be y... | 19:09:25hrs 10-06-2023 | ||
rpl000555 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Your First Overclock - 1800 MHz (Light) | The first overclock we're going to do is relatively "light" and reliable, but still provides a nice boost in compute power. We're going to go from the stock 1500 MHz up to 1800 MHz - a 20% speedup!
Open this file:
sudo nano /boot/firmware/usercfg.txt
Add these two lines to the end:
arm_freq=1800
over_voltage=3
Then sav... | 19:09:25hrs 10-06-2023 | ||
rpl000556 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Resetting After an Unstable Overclock | If your Pi stops responding, or keeps restarting over and over, then you need to lower the overclock. To do that, follow these steps:
If the Pi works, then great! Continue below. If not, repeat the whole process with even more conservative settings. In the worst case you can just remove the arm_freq and over_voltage li... | 19:09:25hrs 10-06-2023 | ||
rpl000557 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Testing 1800 MHz | Once you're logged in, run linpack again to test the new performance. Here's an example from our test Pi:
linpack
Enter array size (q to quit) [200]:
...
Reps Time(s) DGEFA DGESL OVERHEAD KFLOPS
----------------------------------------------------
512 0.59 85.72% 3.75% 10.53% 1338253.832
1024 ... | 19:09:25hrs 10-06-2023 | ||
rpl000558 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Going to 2000 MHz (Medium) | The next milestone will be 2000 MHz. This represents a 33.3% boost in clock speed, which is pretty significant. Most people consider this to be a great balance between performance and stability, so they stop the process here.
Our recommendation for this level is to start with these settings:
arm_freq=2000
over_voltage=... | 19:09:25hrs 10-06-2023 | ||
rpl000559 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Going to 2100 MHz (Heavy) | The next step represents a solid 40% speedup over the stock configuration.
NOTE: Not all Pi's are capable of doing this while staying at over_voltage=6. Try it, and if it breaks, go back to 2000 MHz.
The configuration will look like this:
arm_freq=2100
over_voltage=6
For reference, here are our results:
linpack
Enter a... | 19:09:25hrs 10-06-2023 | ||
rpl000560 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Going to 2250 MHz (Extreme) | This is the setting we run our Pi's at, which has been stable for over a year at the time of writing. Still, users are cautioned in overclocking this high - ensure you do thorough stability tests and have plenty of thermal headroom before attempting to make this your node's production configuration!
Our configuration i... | 19:09:25hrs 10-06-2023 | ||
rpl000561 | https://docs.rocketpool.net/guides/node/local/prepare-pi.html | Next Steps | And with that, your Pi is up and running and ready to run Rocket Pool! Move on to the Choosing your ETH Clients section. | 19:09:25hrs 10-06-2023 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.