Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sccp-2124 #2033

Merged
merged 7 commits into from
Jul 8, 2024
Merged
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
26 changes: 26 additions & 0 deletions content/sccp/sccp-2124.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
sccp: 2124
title: Synth Redemption - Treasury Council
network: Ethereum
status: Vote_Pending
type: Governance
author: Kaleb (@kaleb-keny)
---

## Simple Summary

The SCCP proposes deprecating volatile non-sUSD synths on Ethereum by setting the discountRate to zero. To accommodate potential future redemptions by users claiming sUSD, an equivalent value of the deprecated synths, in sUSD, would be minted and sent to the Treasury Council, would would be in charge of redeeming users without the need for the SC to sign off on the redemption.

## Abstract

<!--A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what *will* be done if the SIP is implemented, not *why* it should be done or *how* it will be done. If the SIP proposes deploying a new contract, write, "we propose to deploy a new contract that will do x".-->

After this SCCP is implemented, debt of stakeholders will remain unchanged, however Treasury Council will receive the equivalent value of the volatile synth in sUSD on ethereum in order to manage redemptions going forward.

## Motivation

In order to allow Treasury to continue to service accidental redemptions, this SCCP is proposed, whereby the value of synth is minted to Treasury Council who would be responsible of managing that process in the future.

## Copyright

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
Loading