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

Week 13 and 14 update #445

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

chirag-parmar
Copy link
Contributor

No description provided.

@taxmeifyoucan taxmeifyoucan merged commit 503f228 into eth-protocol-fellows:main Sep 16, 2024
1 check passed
@taxmeifyoucan
Copy link
Contributor

Thanks for the update!

The last part is really kind of cryptic and I don't really understand what you meant like that :D It's ok to add this sort of note but be more clear so the reader isn't confused.

Regarding the question on purpose of extending the blob data, if you are really asking that - it's fundamental for data availability sampling. To recover data from its polynomial representation, it needs to be extended in 1 or even 2 dimensions. Peers are subscribing only to subset of the data so even with extension, it's still much less than original data. Checkout https://www.youtube.com/watch?v=WOdpO1tH_Us and https://www.youtube.com/watch?v=ro2AGRkLC2s

@chirag-parmar
Copy link
Contributor Author

I'll rephrase it without the philosophy XD. The idea is to source different perspectives from everyone in the cohort. Everyone has a different perspective and I want to how many see the use of erasure codes as I now see it. For example, in your answer you focus on erasure coding allowing "recovery of data" a.k.a reconstruction.

@chirag-parmar chirag-parmar deleted the week-13n14 branch September 23, 2024 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants