Skip to content
This repository has been archived by the owner on Nov 26, 2023. It is now read-only.

WATCHPUG - Lack of Redeem Feature #958

Open
sherlock-admin opened this issue May 24, 2023 · 8 comments
Open

WATCHPUG - Lack of Redeem Feature #958

sherlock-admin opened this issue May 24, 2023 · 8 comments
Labels
Escalation Resolved This issue's escalations have been approved/rejected Has Duplicates A valid issue with 1+ other issues describing the same vulnerability Medium A valid Medium severity issue Reward A payout will be made for this issue

Comments

@sherlock-admin
Copy link
Contributor

WATCHPUG

medium

Lack of Redeem Feature

Summary

Vulnerability Detail

The whitepaper mentions a redeeming feature that allows the user to redeem USSD for DAI (see section 4 "Mint and redeem"), but it is currently missing from the implementation.

Although there is a "redeem" boolean in the collateral settings, there is no corresponding feature that enables the redemption of USSD to any of the underlying collateral assets.

Impact

Code Snippet

https://github.com/sherlock-audit/2023-05-USSD/blob/main/ussd-contracts/contracts/interfaces/IUSSDRebalancer.sol#L13-L21

Tool used

Manual Review

Recommendation

Revise the whitepaper and docs to reflect the fact that there is no redeem function or add a redeem function.

@securitygrid
Copy link

Escalate for 10 USDC
This is valid low/info.
So far, lacking redeem is no impact.

@sherlock-admin
Copy link
Contributor Author

Escalate for 10 USDC
This is valid low/info.
So far, lacking redeem is no impact.

You've created a valid escalation for 10 USDC!

To remove the escalation from consideration: Delete your comment.

You may delete or edit your escalation comment anytime before the 48-hour escalation window closes. After that, the escalation becomes final.

@sherlock-admin sherlock-admin added the Escalated This issue contains a pending escalation label Jun 23, 2023
@0xJuancito
Copy link

Escalate for 10 USDC

This is a valid High.


Escalating the comment:

This is valid low/info.
So far, lacking redeem is no impact.


The impact is explained on the whitepaper and quoted on the "Vulnerability Detail" section from issue #218:

As per the USSD whitepaper:

If there is positive DAI balance in the collateral, USSD contract can provide
DAI for equal amount of USSD in return (that would be burned, contracting
supply).

The importance of this is said here:

Ability to mint and redeem USSD for DAI could serve as incentives to rebalance the coin when this is economically viable

And the most important feature is to have a mechanism to "help USSD recover in negative scenarios":

These methods also could be used to help USSD recover in negative scenarios:
if USSD value falls below 1 DAI and there are less than 1 DAI reserves per USSD
to refill the reserves allowing the USSD to recover it’s price by reducing supply

@sherlock-admin
Copy link
Contributor Author

Escalate for 10 USDC

This is a valid High.


Escalating the comment:

This is valid low/info.
So far, lacking redeem is no impact.


The impact is explained on the whitepaper and quoted on the "Vulnerability Detail" section from issue #218:

As per the USSD whitepaper:

If there is positive DAI balance in the collateral, USSD contract can provide
DAI for equal amount of USSD in return (that would be burned, contracting
supply).

The importance of this is said here:

Ability to mint and redeem USSD for DAI could serve as incentives to rebalance the coin when this is economically viable

And the most important feature is to have a mechanism to "help USSD recover in negative scenarios":

These methods also could be used to help USSD recover in negative scenarios:
if USSD value falls below 1 DAI and there are less than 1 DAI reserves per USSD
to refill the reserves allowing the USSD to recover it’s price by reducing supply

You've created a valid escalation for 10 USDC!

To remove the escalation from consideration: Delete your comment.

You may delete or edit your escalation comment anytime before the 48-hour escalation window closes. After that, the escalation becomes final.

@0xcuriousapple
Copy link

0xcuriousapple commented Jun 25, 2023

well this is what protocol team said that time regarding redeem
that it is intentional

image

@ctf-sec
Copy link
Collaborator

ctf-sec commented Jun 29, 2023

well this is what protocol team said that time regarding redeem that it is intentional

image

valid low based on the sponsor's feedback

@hrishibhat
Copy link
Contributor

hrishibhat commented Jul 13, 2023

Result:
Medium
Has duplicates
This issue can be considered a valid medium based on the Whitepaper description of the importance of having a the redeem function.

@sherlock-admin
Copy link
Contributor Author

sherlock-admin commented Jul 13, 2023

Escalations have been resolved successfully!

Escalation status:

@hrishibhat hrishibhat added Medium A valid Medium severity issue and removed High A valid High severity issue labels Jul 13, 2023
@sherlock-admin sherlock-admin added Escalation Resolved This issue's escalations have been approved/rejected and removed Escalated This issue contains a pending escalation labels Jul 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Escalation Resolved This issue's escalations have been approved/rejected Has Duplicates A valid issue with 1+ other issues describing the same vulnerability Medium A valid Medium severity issue Reward A payout will be made for this issue
Projects
None yet
Development

No branches or pull requests

6 participants