Skip to content

Commit

Permalink
[Docs] Claim expiration (#649)
Browse files Browse the repository at this point in the history
  • Loading branch information
bryanchriswhite authored Jul 5, 2024
1 parent a15452f commit 6c3dd65
Showing 1 changed file with 17 additions and 2 deletions.
19 changes: 17 additions & 2 deletions docusaurus/docs/protocol/primitives/claim_and_proof_lifecycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ to all readers.
:::

- [Introduction](#introduction)
- [Session Windows & On-Chain Parameters](#session-windows--on-chain-parameters)
- [Claim Expiration](#claim-expiration)
- [Session](#session)
- [Session Duration](#session-duration)
- [Session End](#session-end)
Expand Down Expand Up @@ -126,6 +128,18 @@ gantt

- [`poktroll.shared.Params` / `sharedtypes.Params`](https://github.com/pokt-network/poktroll/blob/main/proto/poktroll/shared/params.proto)

### Claim Expiration

If a claim requires a proof (as determined by [Probabilistic Proofs](probabilistic_proofs.md)) and a `Supplier` fails
to submit a `Proof` before the `Proof Window` closes, the claim will expire and the `Supplier` will forfeit any
rewards for the work done.

Claims MUST expire (and therefore the proof window MUST close) for the following reasons:

1. The mint & burn associated with a given claim's settlement MUST occur while the application stake is still locked and applications must be allowed to complete unstaking in finite time.
1. Claim settlement SHOULD be limited to considering claims created within a rolling window of blocks to decouple settlement from a long-tail accumulation of unsettled claims.
1. Proofs MUST be pruned to prevent network state bloat over time. Pruning proofs makes the number of proofs in network state at any given time a function of recent relay demand.

## Session

A session is a necessary pre-requisite for the `Claim & Proof` lifecycle to work.
Expand Down Expand Up @@ -331,8 +345,9 @@ After the `Proof Window` opens, a `Supplier` has several blocks, a `Proof Window
to submit a `SubmitProof` transaction containing a `Proof`. If it is submitted too
early or too late, it will be rejected by the protocol.

If a `Supplier` fails to submit a `Proof` during the Proof Window, the Claim will
expire and the supplier will forfeit rewards for the claimed work done.
If a proof is required (as determined by [Probabilistic Proofs](probabilistic_proofs.md)) and a `Supplier` fails to
submit a `Proof` during the Proof Window, the Claim will expire, and the supplier will forfeit rewards for the claimed
work done. See [Claim Expiration](#claim-expiration) for more.

See [Session Windows & On-Chain Parameters](#session-windows--on-chain-parameters) for more details.

Expand Down

0 comments on commit 6c3dd65

Please sign in to comment.