Open bryanchriswhite opened 2 days ago
The changes enhance the documentation on claim expiration within the claim and proof lifecycle process. It elaborates on the reasons for claim expiration, mechanisms to close the proof window for operational efficiency, and consequences of not submitting required proofs, leading to forfeited rewards.
File | Summary |
---|---|
docusaurus/docs/protocol/primitives/claim_and_proof_lifecycle.md |
Added subsection on Claim Expiration under Session Windows & On-Chain Parameters . Explained the claim expiration process, reasons for the changes, and operational efficiency needs. |
In the world of blockchain’s frame,
Claims and proofs must stake their claim. 🌟
When proof is late, the claim does fade,
Efficiency and order made. 📜
Rewards are lost if proof’s not shown,
This ensures the network’s grown. 🚀
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Summary
Issue
419
Type of change
Select one or more:
Testing
Documentation changes (only if making doc changes)
make docusaurus_start
; only needed if you make doc changesLocal Testing (only if making code changes)
make go_develop_and_test
make test_e2e
PR Testing (only if making code changes)
devnet-test-e2e
label to the PR.make trigger_ci
if you want to re-trigger tests without any code changesSanity Checklist
Summary by CodeRabbit
Session Windows & On-Chain Parameters
to emphasize the importance of closing the proof window for operational efficiency.