You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -213,7 +213,7 @@ This contract uses the `LockstakeEngine.freeNoFee` function ensuring the collate
213
213
The migrator requires to be added to the `wards` mapping of the old `LockstakeEngine`.
214
214
215
215
There are two paths that the user could take when calling the `migrate` function for the desired `urn`:
216
-
- If the `urn` doesn't have any debt. This is the simplest path where the collateral is just `free`d from the old engine and `locke`d in the new one.
216
+
- If the `urn` doesn't have any debt. This is the simplest path where the collateral is just `free`d from the old engine and `lock`ed in the new one.
217
217
- If the `urn` has debt. This path uses the `DssFlash` module to `wipe` the debt in the old `urn` to be able to move the collateral. After doing so, the debt will be `draw`n in the new `urn` and the funds will be returned to the `DssFlash` module (all happens atomically).
218
218
219
219
The first path requires the migrator to be `hope`d in the old Engine for the `urn` being migrated. An authed address needs to call this `hope` function previously. It is also required that the caller of `migrate` be an authed address in the `urn` being migrated.
0 commit comments