the feature with the new release. (no idea who to tag here, uzyn and prasanna seem not taggable :D )
soon :) if i get some news i will tag you.
Are you on the correct testnet chain? You should have the following block in your chain. Height: 835360 Hash: 2b0aaa626b180d822e525e1cfab74532aefe5ecccf79537ed80809a41c175397 I am able to open a vault, deposit DFI to it, take a DUSD loan, pay it back with DFI and withdraw my DFI from the vault.
That was yesterday right after the activation of the payback. 1 hour later everything was active again. I successfully tested the payback etc. The frozen vault was shown like that on defiscan too. Maybe due to the activation of dusd as collateral?
That's all good then, thought you might be on the wrong chain.
is the halting of all vaults with DUSD expected? so do we expect that to happen after the fork?
Sounds cool. Are there any changes in the paybackloan method or is just a change between the dusd and dfi for amounts necessary?
There are code changes on the account layer TX message execution to how payback is handled if the payback amount is DFI. These are the two places to look at, both in the same method. https://github.com/DeFiCh/ain/blob/31e160a05ee89086c9f3a5345efa369e120f26a9/src/masternodes/mn_checks.cpp#L2815 https://github.com/DeFiCh/ain/blob/31e160a05ee89086c9f3a5345efa369e120f26a9/src/masternodes/mn_checks.cpp#L2912
How can we find out later how many unbacked DUSD are created with this? The idea of the DFIP is to get rid of them later.
there are some new entrys in the getburninfo, http://tn01.mydefichain.com/getburninfo/
Обсуждают сегодня