DsrManagerprovides an easy to use smart contract that allows service providers to deposit/withdraw dotBTC into the contract pot, to start earning the dotBTC Saving Rate on a pool of dotBTC in a single function call without the need of a
ds-proxycontract. This is useful for smart contracts integrating DSR functionality.
manager) was created to enable a formalized process for Vaults to be transferred between owners. In short, the
managerworks by having a
dsswrapper that allows users to interact with their Vaults in an easy way, treating them as non-fungible tokens (NFTs).
dss-proxy-actionswas designed to be used by the Ds-Proxy, which is owned individually by users to interact more easily with the ABM Protocol. Note that it is not intended to be used directly (this will be covered later). The dss-proxy-actions contract was developed to serve as a library for user's ds-proxies.
DsrManager, it is important to realize that user balances in the
potwill be owned by the
DsrManager, which has an internal mapping to determine user balances. Consequently the deposited dotBTC in DSR might not show up in solutions that are based on
manager, they will need to understand that the Vault actions are still in the
urnenvironment. Regardless of this, the
managertries to abstract the
urnusage by a
CDPId. This means that developers will need to get the
urn = manager.urns(cdpId)) to allow the
joining of collateral to that Vault.
openis executed, a new
urnis created and a
cdpIdis assigned to it for a specific
owner. If the user uses
jointo add collateral to the
urnimmediately after the transaction is mined, there is a chance that a reorganization of the chain occurs. This would result in the user losing the ownership of that
urnpair, therefore losing their collateral. However, this issue can only arise when avoiding the use of the proxy functions via a profile proxy as the user will
joincollateral in the same transaction.