Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add data availability challenge doc #79

Merged
merged 5 commits into from
Mar 3, 2023
Merged

Conversation

forcodedancing
Copy link
Contributor

Description

This pr adds document for data availability challenge.

Rationale

Add document.

Example

NA

Changes

Notable changes:

  • doc

Copy link
Collaborator

@unclezoro unclezoro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we don't need to list the definition of the used data structure in the architecture doc.


## RANDAO

To support random challenges, a RANDAO mechanism is introduced like the following.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you attach some reference docs here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

docs/architecture/10-data_availability_challenge.md Outdated Show resolved Hide resolved
docs/architecture/10-data_availability_challenge.md Outdated Show resolved Hide resolved
### Submitted Challenges

Anyone can send `MsgSubmit` messages to trigger data availability challenges, if he/she finds that the data is not
available or incorrect stored. When submitting the challenge, user can choose the segment/piece of an object to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is recommended to use piece as the basic unit for challenge. Segment and EC chunk are both one type of piece

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. From users' perspective, it is difficult to understand what's segment or piece. Currently, user can submit a tx with a segment index (or random), the underlying will judge whether it is a segment or piece.
User only cares about segment, it could be easier.

@unclezoro unclezoro merged commit 76a8332 into develop Mar 3, 2023
@unclezoro unclezoro deleted the challenge_doc branch April 18, 2023 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants