Skip to content

Commit ad9652d

Browse files
committed
Updating references from rsk node to lovell
1 parent d33cc1f commit ad9652d

8 files changed

Lines changed: 63 additions & 62 deletions

File tree

docs/02-developers/08-libraries/01-rsk-precompiled-abis/index.md

Lines changed: 29 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -58,31 +58,32 @@ If the version to be installed is not defined in the command line, the version w
5858

5959
## Versioning table
6060

61-
| Package Version | Rootstock version |
62-
|-----------------|---------------|
63-
| 1.0.0-ORCHID | ORCHID-0.6.2 |
64-
| 2.0.0-WASABI | WASABI-1.0.0 |
65-
| 2.0.1-WASABI | WASABI-1.0.0 |
66-
| 3.0.0-PAPYRUS | PAPYRUS-2.0.0 |
67-
| 3.0.0-PAPYRUS | PAPYRUS-2.2.0 |
68-
| 3.0.0-IRIS | IRIS-3.0.0 |
69-
| 3.1.0-IRIS | IRIS-3.1.0 |
70-
| 3.2.0-IRIS | IRIS-3.2.0 |
71-
| 3.3.0-IRIS | IRIS-3.3.0 |
72-
| 4.0.0-HOP | HOP-4.0.0 |
73-
| 4.1.0-HOP | HOP-4.1.0 |
74-
| 4.1.1-HOP | HOP-4.1.1 |
75-
| 4.2.0-HOP | HOP-4.2.0 |
76-
| 4.3.0-HOP | HOP-4.3.0 |
77-
| 4.4.0-HOP | HOP-4.4.0 |
78-
| 5.0.0-fingerroot | FINGERROOT-5.0.0 |
79-
| 5.1.0-fingerroot | FINGERROOT-5.1.0 |
80-
| 5.2.0-fingerroot | FINGERROOT-5.2.0 |
81-
| 5.3.0-fingerroot | FINGERROOT-5.3.0 |
82-
| 5.4.0-fingerroot | FINGERROOT-5.4.0 |
83-
| 6.0.0-ARROWHEAD | ARROWHEAD-6.0.0 |
84-
| 6.3.0-ARROWHEAD | ARROWHEAD-6.3.0 |
85-
| 6.3.1-ARROWHEAD | ARROWHEAD-6.3.1 |
86-
| 6.4.0-ARROWHEAD | ARROWHEAD-6.4.0 |
87-
| 6.5.0-ARROWHEAD | ARROWHEAD-6.5.0 |
88-
61+
| Package Version | Rootstock version |
62+
|------------------|-------------------|
63+
| 1.0.0-ORCHID | ORCHID-0.6.2 |
64+
| 2.0.0-WASABI | WASABI-1.0.0 |
65+
| 2.0.1-WASABI | WASABI-1.0.0 |
66+
| 3.0.0-PAPYRUS | PAPYRUS-2.0.0 |
67+
| 3.0.0-PAPYRUS | PAPYRUS-2.2.0 |
68+
| 3.0.0-IRIS | IRIS-3.0.0 |
69+
| 3.1.0-IRIS | IRIS-3.1.0 |
70+
| 3.2.0-IRIS | IRIS-3.2.0 |
71+
| 3.3.0-IRIS | IRIS-3.3.0 |
72+
| 4.0.0-HOP | HOP-4.0.0 |
73+
| 4.1.0-HOP | HOP-4.1.0 |
74+
| 4.1.1-HOP | HOP-4.1.1 |
75+
| 4.2.0-HOP | HOP-4.2.0 |
76+
| 4.3.0-HOP | HOP-4.3.0 |
77+
| 4.4.0-HOP | HOP-4.4.0 |
78+
| 5.0.0-fingerroot | FINGERROOT-5.0.0 |
79+
| 5.1.0-fingerroot | FINGERROOT-5.1.0 |
80+
| 5.2.0-fingerroot | FINGERROOT-5.2.0 |
81+
| 5.3.0-fingerroot | FINGERROOT-5.3.0 |
82+
| 5.4.0-fingerroot | FINGERROOT-5.4.0 |
83+
| 6.0.0-ARROWHEAD | ARROWHEAD-6.0.0 |
84+
| 6.3.0-ARROWHEAD | ARROWHEAD-6.3.0 |
85+
| 6.3.1-ARROWHEAD | ARROWHEAD-6.3.1 |
86+
| 6.4.0-ARROWHEAD | ARROWHEAD-6.4.0 |
87+
| 6.5.0-ARROWHEAD | ARROWHEAD-6.5.0 |
88+
| 6.5.1-ARROWHEAD | ARROWHEAD-6.5.1 |
89+
| 7.0.0-LOVELL | LOVELL-7.0.0 |

docs/03-node-operators/04-setup/02-installation/java.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ cd ~/rskj-node-jar
4141
```
4242
3. **Move the JAR**: Move or copy the just downloaded jar file to your directory.
4343
```jsx
44-
mv ~/Downloads/rskj-core-6.5.0-ARROWHEAD-all.jar SHA256SUMS.asc /Users/{user}/rskj-node-jar/
44+
mv ~/Downloads/rskj-core-7.0.0-LOVELL-all.jar SHA256SUMS.asc /Users/{user}/rskj-node-jar/
4545
```
4646

4747
<!-- ### Configuration
@@ -69,7 +69,7 @@ mv ~/Downloads/rskj-core-6.5.0-ARROWHEAD-all.jar SHA256SUMS.asc /Users/{user}/rs
6969

7070
:::tip[Tip]
7171

72-
Replace `<PATH-TO-THE-RSKJ-JAR>` with the actual path to your JAR file. For example, `C:/RskjCode/rskj-core-6.5.0-ARROWHEAD-all.jar`.
72+
Replace `<PATH-TO-THE-RSKJ-JAR>` with the actual path to your JAR file. For example, `C:/RskjCode/rskj-core-7.0.0-LOVELL-all.jar`.
7373
:::
7474

7575
## Using Import Sync
@@ -115,7 +115,7 @@ Replace `<PATH-TO-THE-RSKJ-JAR>` with your JAR file path. For configuration deta
115115

116116
:::info[Info]
117117

118-
After starting the node, if there's no output, this means it's running correctly.
118+
After starting the node, if there's no output, this means it's running correctly.
119119
:::
120120

121121
1. To confirm, open a new console tab (it is important you do not close this tab or interrupt the process) and test the node's RPC server. A sample cURL request:
@@ -182,5 +182,5 @@ To change networks on the RSKj node, use the following commands:
182182
```
183183

184184
:::tip[Tip]
185-
Replace `<PATH-TO-THE-RSKJ-FATJAR>` with the actual path to your jar file. For example: `C:/RskjCode/rskj-core-6.5.0-ARROWHEAD-all.jar`.
186-
:::
185+
Replace `<PATH-TO-THE-RSKJ-FATJAR>` with the actual path to your jar file. For example: `C:/RskjCode/rskj-core-7.0.0-LOVELL-all.jar`.
186+
:::

docs/03-node-operators/04-setup/02-installation/ubuntu.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Choose `mainnet` and press `Enter` to continue
3939

4040
## Install via Direct Downloads
4141

42-
You can also download the RSKj Ubuntu Package for the latest RSKj release `ARROWHEAD 6.5.0` and install it with the `dpkg` command. Follow this [download link](https://launchpad.net/~rsksmart/+archive/ubuntu/rskj/+packages) to download the matching package for your ubuntu system.
42+
You can also download the RSKj Ubuntu Package for the latest RSKj release `LOVELL 7.0.0` and install it with the `dpkg` command. Follow this [download link](https://launchpad.net/~rsksmart/+archive/ubuntu/rskj/+packages) to download the matching package for your ubuntu system.
4343

4444
```shell
4545
# first install openjdk-17-jre or oracle-java17-installer
@@ -101,4 +101,4 @@ sudo service rsk restart
101101
sudo service rsk status
102102
```
103103

104-
<img alt="scripts" class="setup-node-ubuntu" src="/img/ubuntu/ubuntu4.png"></img>
104+
<img alt="scripts" class="setup-node-ubuntu" src="/img/ubuntu/ubuntu4.png"></img>

docs/03-node-operators/04-setup/03-configuration/05-verbosity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ A logback configuration example can be downloaded from [here](https://github.com
120120
If you're running a node [using the release jar file](/node-operators/setup/installation/java) use the following command:
121121

122122
```bash
123-
java -cp rskj-core-6.0.0-ARROWHEAD-all.jar -Dlogback.configurationFile=/full/path/to/logback.xml co.rsk.Start
123+
java -cp rskj-core-7.0.0-LOVELL-all.jar -Dlogback.configurationFile=/full/path/to/logback.xml co.rsk.Start
124124
```
125125

126126
#### Using logback with a compiled node
@@ -131,4 +131,4 @@ If you're running a node [by compiling the code](/node-operators/setup/installat
131131
-Dlogback.configurationFile=/full/path/to/logback.xml
132132
```
133133

134-
> Note: path should be written without abbreviations (full path)
134+
> Note: path should be written without abbreviations (full path)

docs/03-node-operators/04-setup/04-node-runner/linux.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Run these commands in the terminal:
3737
```shell
3838
git clone --recursive https://github.com/rsksmart/rskj.git
3939
cd rskj
40-
git checkout tags/ARROWHEAD-6.5.0 -b ARROWHEAD-6.5.0
40+
git checkout tags/LOVELL-7.0.0 -b LOVELL-7.0.0
4141
```
4242

4343
*Note:* It is better to download the code into a short path.
@@ -59,7 +59,7 @@ This will download and set important components (e.g. Gradle Wrapper).
5959

6060
## IntelliJ IDEA setup
6161

62-
### Compiling the node
62+
### Compiling the node
6363

6464
Now, you can launch IntelliJ IDEA:
6565

docs/03-node-operators/04-setup/04-node-runner/macos.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Run these commands on Git command line:
4242
```shell
4343
git clone --recursive https://github.com/rsksmart/rskj.git
4444
cd rskj
45-
git checkout tags/ARROWHEAD-6.5.0 -b ARROWHEAD-6.5.0
45+
git checkout tags/LOVELL-7.0.0 -b LOVELL-7.0.0
4646
```
4747

4848
*Note:* It is better to download the code into a short path.
@@ -64,7 +64,7 @@ This will download and set important components (e.g. Gradle Wrapper).
6464

6565
## IntelliJ IDEA setup
6666

67-
### Compiling the node
67+
### Compiling the node
6868

6969
Now, you can launch IntelliJ IDEA.
7070
When IntelliJ IDEA is launched you should have a window with different options.
@@ -204,4 +204,4 @@ In order to run tests, we can simply go to the `Testing` tab where you can see a
204204

205205
## Any problems?
206206

207-
Check out the [troubleshooting section](/node-operators/troubleshooting/), hope it helps!
207+
Check out the [troubleshooting section](/node-operators/troubleshooting/), hope it helps!

docs/03-node-operators/04-setup/reproducible-build.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,9 @@ Create a ```Dockerfile``` to setup the build environment.
5050
apt-get clean
5151
gpg --keyserver https://secchannel.rsk.co/release.asc --recv-keys 1A92D8942171AFA951A857365DECF4415E3B8FA4
5252
gpg --finger 1A92D8942171AFA951A857365DECF4415E3B8FA4
53-
git clone --single-branch --depth 1 --branch ARROWHEAD-6.5.0 https://github.com/rsksmart/rskj.git /code/rskj
54-
git clone https://github.com/rsksmart/reproducible-builds
55-
CP /Users/{$USER}/reproducible-builds/rskj/6.5.0-arrowhead/Dockerfile /Users/{$USER}/code/rskj
53+
git clone --single-branch --depth 1 --branch LOVELL-7.0.0 https://github.com/rsksmart/rskj.git /code/rskj
54+
git clone https://github.com/rsksmart/reproducible-builds
55+
CP /Users/{$USER}/reproducible-builds/rskj/7.0.0-lovell/Dockerfile /Users/{$USER}/code/rskj
5656
WORKDIR /code/rskj
5757
gpg --verify SHA256SUMS.asc
5858
sha256sum --check SHA256SUMS.asc
@@ -69,21 +69,21 @@ Create a ```Dockerfile``` to setup the build environment.
6969
brew cleanup
7070
gpg --keyserver https://secchannel.rsk.co/release.asc --recv-keys 1A92D8942171AFA951A857365DECF4415E3B8FA4
7171
gpg --finger 1A92D8942171AFA951A857365DECF4415E3B8FA4
72-
git clone --single-branch --depth 1 --branch ARROWHEAD-6.5.0 https://github.com/rsksmart/rskj.git ./code/rskj
73-
git clone https://github.com/rsksmart/reproducible-builds
74-
CP /Users/{$USER}/reproducible-builds/rskj/6.5.0-arrowhead/Dockerfile /Users/{$USER}/code/rskj
72+
git clone --single-branch --depth 1 --branch LOVELL-7.0.0 https://github.com/rsksmart/rskj.git ./code/rskj
73+
git clone https://github.com/rsksmart/reproducible-builds
74+
CP /Users/{$USER}/reproducible-builds/rskj/7.0.0-lovell/Dockerfile /Users/{$USER}/code/rskj
7575
cd ./code/rskj
7676
gpg --verify SHA256SUMS.asc
7777
sha256sum --check SHA256SUMS.asc
7878
./configure.sh
79-
./gradlew clean build -x test
79+
./gradlew clean build -x test
8080
```
8181
</TabItem>
8282
</Tabs>
8383

8484
**Response:**
8585

86-
You should get the following as the final response,
86+
You should get the following as the final response,
8787
after running the above steps:
8888

8989
```bash
@@ -106,7 +106,7 @@ If you are not familiar with Docker or the ```Dockerfile``` format: what this do
106106
To create a reproducible build, run the command below in the same directory:
107107

108108
```bash
109-
docker build -t rskj/6.5.0-arrowhead .
109+
docker build -t rskj/7.0.0-lovell .
110110
```
111111

112112
:::danger[Error]
@@ -127,7 +127,7 @@ This may take several minutes to complete. What is done is:
127127
The last step of the build prints the `sha256sum` of the files, to obtain `SHA-256` checksums, run the following command in the same directory as shown above:
128128

129129
```bash
130-
docker run --rm rskj/6.5.0-arrowhead sh -c 'sha256sum * | grep -v javadoc.jar'
130+
docker run --rm rskj/7.0.0-lovell sh -c 'sha256sum * | grep -v javadoc.jar'
131131
```
132132

133133
## Check Results
@@ -137,11 +137,11 @@ After running the build process, a JAR file will be created in ```/rskj/rskj-cor
137137
You can check the SHA256 sum of the result file and compare it to the one published by Rootstock for that version.
138138

139139
```bash
140-
294f99ec76befa7d9ef18eca28d0c884ceb463ce855ef23ddb7a476e551ba191 rskj-core-6.5.0-ARROWHEAD-all.jar
141-
ec4ea3143fb95fbf878b24c8d00ebe5994c4586ecf92930743b26dc77395c17a rskj-core-6.5.0-ARROWHEAD-sources.jar
142-
7721f59632d9ff825b0bb23cf52fa3eff347852068a03d792ce18d0deae547ae rskj-core-6.5.0-ARROWHEAD.jar
143-
16283f4aebbf5b5b35c63f098d81fb0d2aeb5e9fc3be51128ab300333127077f rskj-core-6.5.0-ARROWHEAD.module
144-
ee4f7e684044302e3819f8c50d9b85af5b3391d14e6ed6110b98e8387a1b2837 rskj-core-6.5.0-ARROWHEAD.pom
140+
604b75665d9750da216ddc9849cb2276a06192321b3c6829685600e1f2d534fb rskj-core-7.0.0-LOVELL-all.jar
141+
05fb616708088a6c65326c01d7e79b2c332d5f2ca83246c9075f65e5fa2781fe rskj-core-7.0.0-LOVELL-sources.jar
142+
8d131bbc8d1d346ec4a91ce4eb9db59f6c7649bb7698b11bc1abbaf33f75caaa rskj-core-7.0.0-LOVELL.jar
143+
e85d0783b39ef93fda5f98588f7e4ae5d57784096ce9b3a1f43eb3d99a49d275 rskj-core-7.0.0-LOVELL.module
144+
d651adc77b82046a976bf5c7e858b741443bc8ffa8372b8e5bac9b92dc8c294d rskj-core-7.0.0-LOVELL.pom
145145
```
146146

147147
For SHA256 sum of older versions check the [releases page](https://github.com/rsksmart/rskj/releases).
@@ -153,4 +153,4 @@ More Resources
153153

154154
* [Install Rootstock Node](/node-operators/setup/installation/)
155155
* See [Reproducible builds](https://github.com/rsksmart/reproducible-builds/tree/master/rskj)
156-
* Check out the [latest rskj releases](https://github.com/rsksmart/rskj/releases)
156+
* Check out the [latest rskj releases](https://github.com/rsksmart/rskj/releases)

docs/04-resources/03-faqs/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Here are some frequently asked questions about the Rootstock and RIF Platforms.
5353
<Accordion.Item eventKey="5">
5454
<Accordion.Header as="h3">What is the current state of the Rootstock project?</Accordion.Header>
5555
<Accordion.Body>
56-
- As of March 2024, the latest released version of Rootstock is the [Arrowhead v6.0.0](https://github.com/rsksmart/rskj/releases), an update that is mainly focused on bringing Ethereum compatibility enhancements to the Rootstock virtual machine, along with notable improvements and performance optimization in the PowPeg protocol. Read more [Arrowhead 6.0.0: What You Need To Know About Rootstock’s Upcoming Network Upgrade](https://blog.rootstock.io/noticia/arrowhead-6-0-0/)
56+
- As of February 2025, the latest released version of Rootstock is the [Lovell v7.0.0](https://github.com/rsksmart/rskj/releases), an update that is mainly focused on bringing Ethereum compatibility enhancements to the Rootstock virtual machine, along with notable improvements and performance optimization in the PowPeg protocol. Read more [Introducing Lovell 7.0.0: What You Need To Know About Rootstock’s Upcoming Network Upgrade](https://blog.rootstock.io/noticia/introducing-lovell-7-0-0/)
5757
- Live statistics about the entire Rootstock network are available at Rootstock Stats, and all the necessary source codes can be found at the Rootstock GitHub organization: [github.com/rsksmart](https://github.com/rsksmart).
5858
</Accordion.Body>
5959
</Accordion.Item>
@@ -98,7 +98,7 @@ Here are some frequently asked questions about the Rootstock and RIF Platforms.
9898
<Accordion.Item eventKey="10">
9999
<Accordion.Header as="h3">How is Rootstock different from drivechains?</Accordion.Header>
100100
<Accordion.Body>
101-
- A drivechain is a special sidechain with a specific type of 2 way peg called “hashrate escrow.” This peg mechanism gives most Bitcoin miners control of sidechain withdrawals but incentivizes miners to be honest and not abuse their powers. To achieve this, miners publicly confirm or reject withdrawals during a long period that can last 3 months. During this period, the community can detect cheaters that confirm invalid withdrawals. The peg is secure as long as there are strong long-term incentives for the honest majority of miners not to cheat. Rootstock, on the contrary, does not rely on monetary incentives. It uses a federation of PowHSM devices, and the tamper-proof devices vote on withdrawals. At the same time, each device enforces the same type of “hashrate escrow” but with a much-reduced timeframe of days. Therefore both Drivechains and Rootstock require the miner hashrate to support every withdrawal.
101+
- A drivechain is a special sidechain with a specific type of 2 way peg called “hashrate escrow.” This peg mechanism gives most Bitcoin miners control of sidechain withdrawals but incentivizes miners to be honest and not abuse their powers. To achieve this, miners publicly confirm or reject withdrawals during a long period that can last 3 months. During this period, the community can detect cheaters that confirm invalid withdrawals. The peg is secure as long as there are strong long-term incentives for the honest majority of miners not to cheat. Rootstock, on the contrary, does not rely on monetary incentives. It uses a federation of PowHSM devices, and the tamper-proof devices vote on withdrawals. At the same time, each device enforces the same type of “hashrate escrow” but with a much-reduced timeframe of days. Therefore both Drivechains and Rootstock require the miner hashrate to support every withdrawal.
102102
- Drivechains are promising but not currently available as they require a soft-fork in Bitcoin, which has been historically considered controversial and may never be performed. While drivechains may provide greater decentralization, the drivechain peg mechanism has never been tested, so the drivechain peg security is still uncertain.
103103
</Accordion.Body>
104104
</Accordion.Item>
@@ -120,7 +120,7 @@ Here are some frequently asked questions about the Rootstock and RIF Platforms.
120120
</Accordion.Body>
121121
</Accordion.Item>
122122
</Accordion>
123-
123+
124124

125125
## Rootstock and RIF Token
126126

@@ -335,4 +335,4 @@ Here are some frequently asked questions about the Rootstock and RIF Platforms.
335335
- The Rootstock 2 way peg is a protocol that allows users to transfer bitcoins from the Bitcoin blockchain to the Rootstock blockchain and back, creating a token called RBTC that is pegged to the value of Bitcoin. The Rootstock 2 way peg works by locking bitcoins in a multi-signature address on the Bitcoin side and releasing an equivalent amount of RBTC on the Rootstock side. The reverse process is also possible by burning RBTC on the Rootstock side and unlocking bitcoins on the Bitcoin side. A group of reputable organizations controls the multi-signature address called the PowPeg Federation, which uses special hardware devices called PowHSMs to protect private keys and validate transactions. The PowHSMs only sign transactions approved by both the Rootstock and Bitcoin networks using a proof-of-work mechanism. This way, the Rootstock 2 way peg ensures high security and decentralization for the peg-in and peg-out transactions.
336336
</Accordion.Body>
337337
</Accordion.Item>
338-
</Accordion>
338+
</Accordion>

0 commit comments

Comments
 (0)