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

prposal for formal lookback limits #121

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

vyzo
Copy link

@vyzo vyzo commented Jun 25, 2021

No description provided.

@vyzo vyzo requested review from Stebalien, raulk and arajasek June 25, 2021 19:53
@Stebalien
Copy link
Member

  1. If we actually need to set limits, this would need to be a FIP and would need to be enforced in actors. However, I think we just need to figure out what the existing limits are.
  2. In terms of state lookback: We lookback one chain finality (900 epochs) for the block miner's worker key & power. I'm not aware of any other lookback.
  3. In terms of chain lookback (for randomness/beacons), the answer is likely a month plus a bit. But really, there's no reason not to keep the entire chain (not the messages, just the block headers).

So the answer is: 900 epochs (1800-2000 to be safe) plus the chain headers.

@Stebalien
Copy link
Member

Anyways, what is a "booster". Are you referring to public nodes for light clients? Those nodes can probably reject all requests that try to access anything not in the current tipset. They can also refuse to execute any slashing messages not included in a block.

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