The Great Celo Stake Off: Baklava Testnet Launch!

Testnets Baklava Testnet
1

Today is the day where you, future chefs of Celo, will “Learn to Cook” by participating in a dry-run warm up, where you’ll get comfortable with the protocol and the operating environment before The Great Celo Stake Off (TGCSO) officially starts. In this phase, asset placeholders will have no value: they will not count towards TGCSO and are not eligible as BTUs (Baklava Testnet Units). As a reminder, the network will reset at the next phase (Dec 11th at 1600 UTC) at which point Eligible Participants may accumulate BTUs counting toward leaderboard ranking. Details are always updated on the forum post.

By participating in TGCSO you are accepting the Terms & Conditions.

  1. Get Started by setting up your validator: Instructions
  2. Look out for a separate email containing faucet instructions (registration required to get this email).
  3. Once set-up, play with the CLI (Command Line Interface) to familiarize yourself with the network
  4. See where you stand: Checkout the Leaderboard (your validator address will be featured), Celostats for network statistics, and Blockscout for exploring the blockchain
  5. Join the Thursday Dec 4th 2019 Webinar on TGCSO design with Q&A
  6. Feeling extra confident? Or still feeling lost? You can still register to be a mentor/mentee (email hello@celo.org).
3 Likes
2

At https://docs.celo.org/v/master/getting-started/baklava-testnet/running-a-validator#hardware-requirements, the standard requirements for running a Validator node is given as:

  • Memory: 8 GB RAM
  • CPU: Quad core 3GHz (64-bit)
  • Disk: 256 GB of SSD storage, plus a secondary HDD desirable

Observation: in my experience on Alfajores, dual-core and 4 GB (+ swap because of the memory leak) is sufficient. Is the quad-core / 8 GB of RAM really a requirement, or a recommendation? And, is this just for the validator nodes? Are there requirements/recommendations for the attestation, proxy, and full nodes?

3

How do you expect the Validator to be isolated from the Internet when it is wanting to use outgoing Internet connections for Docker pulls, peers, websocket, etc. Please give us UFW firewall rules to lock it down, but allow all outgoing that is needed.

And are you aware the IP given out by the proxy-node Docker container is unreachable on a LAN by the Validator? I assume you don’t want that connection routed via the Internet either.