# Tweag - Ouroborus Peras protocol

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

* Supplier: Tweag
* Contract Name: Ouroboros Peras Protocol
* Contract Date: 12th January 2025 - 12th March 2025

### Contract Details

<table data-full-width="true"><thead><tr><th width="152">Milestone</th><th width="158">Completion Date</th><th width="326">Milestone Description</th><th>Milestone Amount</th><th width="160">Milestone Status<select><option value="tuQZQU0qZdoU" label="Not Started" color="blue"></option><option value="egD9AGmh1U3S" label="On Track" color="blue"></option><option value="Re3cd2eP2WaH" label="Complete" color="blue"></option><option value="bEAnsa2nIuMk" label="Delayed" color="blue"></option></select></th><th width="165.77783203125">MAF</th></tr></thead><tbody><tr><td>Milestone 1 - Midway Checkpoint</td><td>2nd Feb 2025</td><td>Deliver a presentation to the Technical Steering Committee within the Administrator highlighting initial progress, any findings to date and any risks of issues to the project.</td><td>$0</td><td><span data-option="Re3cd2eP2WaH">Complete</span></td><td>No MAF required, presentation successfully delivered to the TSC on 5th Feb 2025</td></tr><tr><td>Milestone 2 - Peras Implementation Plan</td><td>23rd Feb 2025</td><td><p>Design document is reviewed by Consensus architects, Peras researchers and the Peras innovation team and agreed to contain either:</p><p>a. A coherent plan to implement Peras in the node, or;</p><p>b. A compelling reasoning as to why such implementation is not currently possible.</p></td><td>$226,569</td><td><span data-option="Re3cd2eP2WaH">Complete</span></td><td><a href="https://drive.google.com/file/d/12y5XLY5Y6_dVWrD7V5R9KZIKs_7duXwn/view?usp=drive_link">https://drive.google.com/file/d/12y5XLY5Y6_dVWrD7V5R9KZIKs_7duXwn/view?usp=drive_link</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2025-delivery-assurance-contract-updates/technical-steering-committee-contracts/tweag-ouroborus-peras-protocol.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.