Skip to content

Commit

Permalink
patch build errors
Browse files Browse the repository at this point in the history
  • Loading branch information
0o-de-lally committed Aug 23, 2024
1 parent bd14474 commit 276434e
Show file tree
Hide file tree
Showing 4 changed files with 22 additions and 22 deletions.
4 changes: 2 additions & 2 deletions docs/validators/detailed-instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,13 +101,13 @@ This assumes the `libra` binary is already built and located at `~/libra-framewo
# Copy libra binaries to cargo bins path
sudo cp -f ~/libra-framework/target/release/libra* ~/.cargo/bin/
# Check libra execution and version
# Check libra execution and version
libra version
```



### You will now need [sync your validator to the latest block](/validators/restore) and [register your validator](/validators/register).
### You will now need sync your validator to the latest block and register your validator.

#### Start Node

Expand Down
4 changes: 2 additions & 2 deletions docs/validators/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,5 +70,5 @@ These measures aim to incentivize consistent and effective network performance b

### How to become a Validator
1. [Configure and setup your machine](/validators/detailed-instructions)
2. [Sync Database to the current version](/validators/restore)
3. [Register your Validator](/validators/register)
2. Sync Database to the current version (TODO: link)
3. [Register your Validator](register)
14 changes: 7 additions & 7 deletions docs/validators/register.todo → docs/validators/register.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,12 +22,12 @@ source ~/.bashrc

# build and install the binary
cd ~/libra-framework
cargo build --release -p libra
cargo build --release -p libra

# Make the release path global and persistent
sudo cp -f ~/libra-framework/target/release/libra* ~/.cargo/bin/

# Check libra execution and version
# Check libra execution and version
libra --version

# -----------------------
Expand Down Expand Up @@ -56,7 +56,7 @@ libra txs validator vouch --vouch-for <YOUR ADDRESS>
# submit a bid to be in the validator set
libra txs validator pof --bid-pct <PERCENT YOU PAY> --expiry <WHEN EXPIRES>

# run as a fullnode and switch to the validator mode once entered the set, check the detailed instructions below the page.
# run as a fullnode and switch to the validator mode once entered the set, check the detailed instructions below the page.
```

## Detailed instructions
Expand Down Expand Up @@ -132,10 +132,10 @@ libra txs validator register -f ~/.libra/operator.yaml

### Get Vouches
0L Network uses very light reputation games to keep the validator set trusted.
Just ask an existing validator for a vouch. It helps a lot if you share your node specs and a little bit of your experience with them.
Just ask an existing validator for a vouch. It helps a lot if you share your node specs and a little bit of your experience with them.

Your friend will:
``` bash
``` bash
libra txs validator vouch --vouch-for <YOUR ADDRESS>
```

Expand All @@ -147,9 +147,9 @@ libra txs validator pof --bid-pct <PERCENT YOU PAY> --expiry <WHEN EXPIRES>

### Run the node as fullnode and then validator mode
- Once your validator enters the set you will need to stop running as a fullnode and run as a validator. Until then, you can:
- use the following instructions to: [sync database to the current state](/validators/restore) and run as a fullnode.
- use the following instructions to: sync database to the current state (TODO: link) and run as a fullnode.
- When your node is in the active set, it is time to change your node config path to point to the `validator.yaml`.
- Stop your node and run in the validator mode:
``` bash
``` bash
libra node --config-path ~/.libra/validator.yaml
```
22 changes: 11 additions & 11 deletions docs/validators/with-docker-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: 'Running a fullnode/vfn/validator node with docker'
---

:::danger WIP
This page is a work in progress.
This page is a work in progress.
Tread carefully.
:::

Expand Down Expand Up @@ -121,7 +121,7 @@ docker images | grep openlibra
openlibra main b64dbca39f51 9 minutes ago 153MB
```

## Single IP setup
## Single IP setup

### Create the docker-compose file

Expand All @@ -134,7 +134,7 @@ Place the following docker-compose.yaml file in the same folder as the Dockerfil
x-defaults: &defaults
image: "openlibra:main"
restart: "on-failure"
pid: host
pid: host
ulimits:
nproc: 500000
nofile: 500000
Expand Down Expand Up @@ -203,7 +203,7 @@ services:
- "6182:6182"
- "8080:8080"
- "9101:9101"
tower: # needs mnemonic injection
<<: *defaults
container_name: "0l-tower"
Expand Down Expand Up @@ -256,7 +256,7 @@ Here is an example of modified `fullnode.yaml` relevant entries:
```bash
...
base:
base:
data_dir: '/root/.libra/data'
execution:
Expand Down Expand Up @@ -290,15 +290,15 @@ docker compose logs -f --tail 50 fullnode
```
:::warning If the version is 0 or you're having connectvitiy issues
Do the manual DB restore as described in the [Restore section](/validators/restore#clone-and-build-the-epoch-archive-mainnet-repository) and then [clean and sync](/validators/restore#how-to-clean-the-database-and-sync-to-the-latest-state-again)
Do the manual DB restore as described in the Restore section (TODO: link) and then clean and sync (TODO: link)
:::
### Run tower
```bash
docker compose run tower
```
```
Expand All @@ -319,7 +319,7 @@ __Dual NIC setup__
Part 1: Configure second IP
Using Netplan (default ubuntu network manager), edit your `/etc/netplan/01-netcfg.yaml`
Using Netplan (default ubuntu network manager), edit your `/etc/netplan/01-netcfg.yaml`
Identify your ethernet id (enp5s0 in this example), add the second IP to its addresses list
Expand Down Expand Up @@ -358,7 +358,7 @@ Under the modified interface, you should see the second IP address
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether c8:7f:tag:tag:tag brd ff:ff:ff:ff:ff:ff
Expand All @@ -368,6 +368,6 @@ Under the modified interface, you should see the second IP address
inet your.secondary.ip.here/32 scope global enp5s0 # <--- make sure second IP appears here
valid_lft forever preferred_lft forever
############
inet6 primary:ip:v:6/64 scope global
inet6 primary:ip:v:6/64 scope global
valid_lft forever preferred_lft forever
```
```

0 comments on commit 276434e

Please sign in to comment.