ObolNetwork / ObolNetwork/obol-docs

Document what are the steps required for a validator to be included on-chain

Open Beginner friendly
#225 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MDX
Stars
27
Forks
61
Avg merge
1h 22m
Merged PRs (30d)
2

Description

Problem to be solved

Validators need to know the steps required to be included on-chain, but this information is not currently documented in the Obol Network documentation.

Proposed solution

Add a new section to the Obol Network documentation titled "Steps for Validators to be Included On-Chain" that outlines the necessary steps for validators to be included on-chain. This section should include the following steps:

  1. Validators must first submit an attestation to the network.
  2. The attestation must be picked up by one of the aggregators for that attestation.
  3. The aggregate is then broadcasted and picked up by a block builder.
  4. The attestation is counted as "included" when the aggregation is included in a block.

We should include it under the FAQ and errors section.

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the FAQ and errors section of the Obol Network documentation and review how nearby entries are structured. Add a section titled "Steps for Validators to be Included On-Chain" containing the four listed validator, attestation, aggregator, aggregate, and block-builder steps; the work is done when the process is documented there.

Written by the indexing model from the issue text.

Assessment

Domain
blockchain, documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.