Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions concepts/oracle.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -62,3 +62,10 @@ In the event that a provider fails to include a committed transaction (txnj) in
3. The Oracle communicates that txnj was not seen in the Oracle Contract.
4. The Oracle Contract, upon receiving this information, initiates the slashing procedure. This involves penalizing the provider by triggering a slash event, which results in the forfeiture of the stake held by the provider contract as a guarantee of honest behavior.
5. The confiscated stake is subsequently allocated to the bidder as compensation for the provider's failure to include the committed transaction, thereby ensuring that the bidder is recompensed for the provider's breach of trust.

## Funds Locking
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this part of the oracle description?

We offer a mechanism for locking and unlocking funds associated with a pre-confirmed bid.

Funds movement involves locking the bid amount in escrow when a commitment is processed. This occurs only once per bid, meaning if there are multiple commitments for the same bid, the funds will be locked only once.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this how it is implemented? The solution we had discussed locks the deposited amount until the oracle settles and not when commitments are processed.


The funds are released when the Oracle resolves the commitment. If the provider is slashed, the locked funds are unlocked and returned to the bidder.