Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

state: Harden balance verification logic #585

Closed
renaynay opened this issue Apr 1, 2022 · 0 comments
Closed

state: Harden balance verification logic #585

renaynay opened this issue Apr 1, 2022 · 0 comments
Labels
kind:discussion question Further information is requested

Comments

@renaynay
Copy link
Member

renaynay commented Apr 1, 2022

What if a new block arrives in between requesting a proof and receiving it? Shouldn't the node verify the proof against a given block? Should clarify this case.

Originally posted by @adlerjohn in #513 (comment)
@renaynay renaynay changed the title What if a new block arrives in between requesting a proof and receiving it? Shouldn't the node verify the proof against _a given_ block? Should clarify this case. state: Harden balance verification logic Apr 1, 2022
@adlerjohn adlerjohn moved this to TODO in Celestia Node Apr 1, 2022
@adlerjohn adlerjohn added the question Further information is requested label Apr 1, 2022
@celestiaorg celestiaorg locked and limited conversation to collaborators Dec 20, 2023
@ramin ramin converted this issue into discussion #3019 Dec 20, 2023
@github-project-automation github-project-automation bot moved this from TODO to Done in Celestia Node Dec 20, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
kind:discussion question Further information is requested
Projects
No open projects
Celestia Node
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ramin @adlerjohn @renaynay