From 34c8bfcba5e376f1febb2a5e6c40201006e1364d Mon Sep 17 00:00:00 2001 From: Arnaud Date: Thu, 27 Feb 2025 18:00:09 +0100 Subject: [PATCH] Update specs/marketplace.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Adam Uhlíř --- specs/marketplace.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/marketplace.md b/specs/marketplace.md index 8b7243f..0f91dd9 100644 --- a/specs/marketplace.md +++ b/specs/marketplace.md @@ -228,7 +228,7 @@ There is a slashing scheme orchestrated by the smart contract to incentivize cor The slashing works as follows: -- It is slashed by `config.collateral.slashPercentage` **of the originally required collateral** (hence the slashing amount is always the same for a given request). +- When SP misses a proof and a validator trigger detection of this event using the `markProofAsMissing()` call, the SP is slashed by `config.collateral.slashPercentage` **of the originally required collateral** (hence the slashing amount is always the same for a given request). - If the number of slashes exceeds `config.collateral.maxNumberOfSlashes`, the slot is freed, the remaining collateral is burned, and the slot is offered to other nodes for repair. The smart contract also emits the `SlotFreed(requestId, slotIndex)` event. If, at any time, the number of freed slots exceeds the value specified by the `request.ask.maxSlotLoss` parameter, the dataset is considered lost, and the request is deemed _failed_. The collateral of all SPs that hosted the slots associated with the storage request is burned, and the `RequestFailed(requestId)` event is emitted.