Author: Jon Dao, @johndao (Forum), @johndao1337 (Twitter)  
Related discussions (optional): [Recent discussion on Discord](https://discord.com/channels/844609594582892564/862598674214027274/1098528421790879744)  
First publication date: 2023/04/20  

## Summary

The summary briefly sums up what intention the YIP has and what changes the YIP will introduce. E.g.: Currently minting on the uBTC engine seems to be not attractive enough. In oder to make it more attractive to mint uBTC we propose to lower the interest rate on all uBTC V3 engines engines to Y%.

## Rationale
The rationale explains why the author thinks the YIP will add value to the youves platform and it's users. It offers any DAO participant enough information to understand: 

### Motivation
The intention of the change: What benefits does it provide? What problems will it solve? What is the motivation behind the change?

### Analysis

Ideally the rationale also includes supporting data that was either used for the analysis or that project the effects of the change into the future. Pictures, graphs, diagrams tables can be included to the extent it makes sense. 

A nice graph which helps to understand the rationale:

![](https://i.imgur.com/AHRfBgd.png)

### Methodology 
If data was acquired through a certain methodology, then this methodology should be explained too.

In short, everything should be mentioned that other DAO participands need in order to understand the proposal and the changes it will introduce. 

### Proposal

Specify the proposed change(s) that will be made by this proposal. What parameters/contracts/factors will be changed? Are there new contracts introduced?

Or a table with parameters, values or projections:

| Column 1 | Column 2 | Column 3 |
| -------- | -------- | -------- |
| Text     | Text     | Text     |


## Code

### Source code in SmartPy (or any other language used)

The source code of the lambda should be published here or a link to the source code in a repository should be offered, so the code can be reviewed by other members of the community.

Link to [GitHub repo with the source code](https://github.com/youves-com/youves-governance-script)

```
class HenReunionContract(sp.Contract):


    def __init__(self, metadata, end_party):
        """Initializes the contract.
        """
        # Define the contract storage data types for clarity
        self.init_type(sp.TRecord(
            # The contract metadata
            metadata=sp.TBigMap(sp.TString, sp.TBytes),
            # The timestamp when the party ends
            end_party=sp.TTimestamp,
            # The participants bigmap
            participants=sp.TBigMap(sp.TAddress, sp.TUnit)))

        # Initialize the contract storage
        self.init(
            metadata=metadata,
            end_party=end_party,
            participants=sp.big_map())
```
### Compiled Michelson code

The compiled Michelson code of the above SmartPy code should be offered as well so other users can compare if the code above would compile to the same Michelson code. You can also place that in an external repo and link to it, especially if you have multiple pieces of code etc.

```
 { { DROP ;
    NIL operation ;
    PUSH address "KT1J4CiyWPmtFPXAjpgBezM5hoVHXHNzWBHK" ;
    CONTRACT %set_administrator (pair address nat) ;
    IF_NONE { PUSH int 253 ; FAILWITH } {} ;
    PUSH mutez 0 ;
    PUSH (pair address nat) (Pair "tz1V28Zqfftk8o6ehc5UdJPzuyZW99yJ4Gj5" 0) ;
    TRANSFER_TOKENS ;
    CONS } }
```

### SHA256 Hash of the Michelson code

Please provide a SHA256 Hash of the above Michelson code here.

`7060c418fc5c5c9baf27a2432b4193ec76ca9c302f91e785a6e7da9114447662`