Comment on page
🪙
Djed Stablecoin Protocols
Djed is a stablecoin protocol that is:
- crypto-backed: under normal conditions, every stablecoin is backed by an independent asset, with intrinsic value, for which it can be redeemed at any time.
- autonomous: once deployed to a blockchain, the protocol can run by itself, with no need to be operated by a third party. As a consequence of being autonomous, Djed can also be:
- zero-governance: a deployment of Djed does not need to be governed by anyone.
- immutable: a deployment and its parameters can remain unchanged, non-updatable, thus guaranteeing that no one will ever be able to update the contract's logic, in ways that could be undesirable or even malicious for those who hold funds in the contract.
- rent-seeking free: since there is no need for a third party to operate a Djed deployment, there is also no need for any third party to extract abusive fees from the deployment. Djed deployments can become free and public infra-structure on the underlying blockchains.
- formally verified: stability theorems for version V1 (a.k.a. "Minimal Djed") have been formally proven using Isabelle and checked with bounded model checking using Lustre.
- empirically battle-tested: the longest-running deployment of Djed has been deployed in Q1 2021 and its stablecoin has never lost the peg, despite numerous severe market crashes experienced by the cryptocurrency industry.
- peer-reviewed: after a long and thorough peer-review process, the academic paper about the minimal version of Djed was accepted at the IEEE International Conference on Blockchain and Cryptocurrency.
Note that, although the protocol was designed with the intention to have the characteristics listed above, implementations and deployments of the protocol may diverge from these intentions.
The 4 actions that everyone can take when interacting with a Djed deployment.
The Djed protocol maintains a reserve of BaseCoins (BCs, usually the native currency of the underlying blockchain), which are used to back the StableCoins (SCs) that are issued. In addition to StableCoins, the protocol also issues ReserveCoins (RCs).
A ReserveCoin represents ownership of a portion of the surplus of the underlying reserves of BCs in the Djed protocol. As such, ReserveCoins have a leveraged volatile price that increases when the price of BCs increases and decreases when the price of BCs decreases. Furthermore, ReserveCoin holders ultimately benefit from fees paid to the Djed protocol, since fees are accumulated into the reserve and hence contribute to the reserve surplus.
In a Djed deployment, the SCs can be pegged to anything (e.g. USD, EUR, a particular stock, an index such as the S&P500, ...). For simplicity, the explanations below assume a peg to the USD.
The Djed protocol aims to maintain a reserve ratio significantly above 100% to cushion the value of SCs and maintain the peg even if the price of BCs falls dramatically. For example, when the reserve ratio is 400%, it is able to tolerate an instantaneous BC price crash of 75% without losing the peg.
SC holders are always allowed to sell back SCs to the protocol. The protocol pays 1 USD worth of BCs per SC if the reserve ratio is above 100% or R/S per SC otherwise, where R is the protocol's total BC reserve and S is the SC supply.
Everyone is allowed to buy SCs from the protocol for a price of 1 USD worth of BCs per SC, whenever the reserve ratio is above a specified minimum reserve ratio threshold. When the reserve ratio is below threshold, the purchase of SCs from the protocol is disallowed, because it would reduce the reserve ratio further.
Everyone allowed to buy RCs, as long as the reserve ratio remains below a maximum reserve ratio threshold. This prevents excessive dilution of previous RC holders. This restriction only applies when the SC supply is above a threshold.
RC holders are allowed to sell RCs, as long as the reserve ratio remains above the minimum ratio threshold. This aims to ensure that all SCs remain sufficiently backed.
The explanations above are provided for your information, to explain in layman's terms how the protocol generally works. These informal explanations should not be taken as a substitute for the protocol's actual code.