Skip to content

Commit

Permalink
Lighthouse to v0.3.5
Browse files Browse the repository at this point in the history
  • Loading branch information
yorickdowne committed Nov 18, 2020
1 parent b733eee commit 85ce959
Show file tree
Hide file tree
Showing 3 changed files with 21 additions and 8 deletions.
20 changes: 16 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ Currently supported clients:

Currently supported optional components:
- geth, local eth1 node.
- nethermind, local eth1 node - appears to work, no long-term test done yet
- openethereum, local eth1 node - testing only, DB corruption observed on mainnet
- nethermind, local eth1 node - testing only, issues with API calls
> Use one of the local eth1 node options or a 3rd-party provider of eth1 chain data to "feed"
> your eth2 beacon node, so you can [propose](https://ethos.dev/beacon-chain/) blocks.
- slasher, Running slasher is optional, but helps secure the chain and may result in additional earnings.
Expand Down Expand Up @@ -231,7 +231,10 @@ the way you need them, with `.env.bak` as a guide.

### Eth1

Run:<br />
If not building from source, run:<br />
`sudo docker-compose build --pull eth1`

Else, if building from source:<br />
`sudo docker-compose build --no-cache eth1`

Then stop, remove and start eth1:<br />
Expand All @@ -240,11 +243,20 @@ Then stop, remove and start eth1:<br />

### Client

Beacon and validator share the same image, we only need to rebuild one.
Beacon and validator share the same image for most clients, we only need to rebuild one.

If not building from source, run:<br />
`sudo docker-compose build --pull beacon`

Run:<br />
Else, if building from source:<br />
`sudo docker-compose build --no-cache beacon`

For Prysm, also run:<br />
`sudo docker-compose build --pull validator`

Or, if building from source:<br />
`sudo docker-compose build --no-cache validator`

Then restart the client:<br />
`sudo docker-compose down && sudo docker-compose up -d eth2`

Expand Down
7 changes: 4 additions & 3 deletions SETUP.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,8 @@ Please choose:
* Nimbus
* Your source of eth1 data
* geth
* nethermind - appears to work, no long-term tests done yet
* openethereum - testing only, DB corruption observed
* nethermind - testing only, API calls not stable
* 3rd-party
* Whether to run a slasher (experimental for Prysm)
* Whether to run a grafana dashboard for monitoring
Expand Down Expand Up @@ -86,7 +86,8 @@ exposed to the host, and for everything but Grafana to the Internet via your fir
- Set the `NETWORK` variable to either "mainnet" or a test network such as "medalla"
- If using geth as the eth1 node, comment out the `GETH1_NETWORK` variable, to use the main net, or set it to a test network such as "--goerli",
with the two dashes.
- With other eth1 nodes, the `ETH1_NETWORK` variable serves the same function, and can be set to `ethereum` to use the main eth1 network.
- With other eth1 nodes, the `ETH1_NETWORK` variable serves the same function. It can be set to `mainnet` to use the main eth1 network with
Nethermind, or `ethereum` to use the main eth1 network with OpenEthereum.
- Set the `GRAFFITI` string if you want a specific string

### Client compose files
Expand All @@ -98,8 +99,8 @@ openethereum with `:` between the file names.
- `teku-base.yml` - Teku
- `nimbus-base.yml` - Nimbus
- `geth.yml` - local geth eth1 chain node
- `nm.yml` - local nethermind eth1 chain node - appears to work, no long-term tests done yet
- `oe.yml` - local openethereum eth1 chain node - testing only, DB corruption observed
- `nm.yml` - local nethermind eth1 chain node - testing only, API calls not stable
- `shared-eth1.yml` - makes the RPC port of the eth1 node available from the host, for using the eth1 node with other nodes or with Metamask. **Not encrypted**, do not expose to Internet.
- `prysm-slasher.yml` - Prysm experimental Slasher which helps secure the chain and may result in additional earnings. The experimental slasher can lead to missed attestations do to the additional resource demand.
- `lh-grafana.yml` - grafana dashboard for Lighthouse
Expand Down
2 changes: 1 addition & 1 deletion default.env
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ ETH1_RPC_CORS=all
# use.

LH_SRC_BUILD_TARGET=$(git describe --tags $(git rev-list --tags --max-count=1))
LH_DOCKER_TAG=v0.3.4 # eventually stable or stable-latest when sigp introduce that
LH_DOCKER_TAG=v0.3.5 # eventually stable or stable-latest when sigp introduce that
# Change to Dockerfile.source to build from source
LH_DOCKERFILE=Dockerfile.binary
LH_USER=lighthouse
Expand Down

0 comments on commit 85ce959

Please sign in to comment.