Frederik Gartenmeister
Frederik Gartenmeister
Ah, I see. Well, this will need a pallet then.
@thea-leake can you incorporate this into the polkadot-v0.9.32 upgrade changes? It is mostly just switching the `saturating_*` logic on weights to the ones in the linked PR.
@gpmayorga is there some info on this? I remember we have talked about this and played around a little bit with the script I wrote to be used with a...
Haha. THis has been my wish for a long time. @gpmayorga correct me if I am wrong, but I think the issue was that we don't want to allow to...
@branan @gruberb FYI. One of my main points is that I would like to have a way for connectors to easily check wether the state of the NAV is still...
But there are three places in the loans pallet (besides the obvious update_nav extrinsic) that could update a NAV during a multi-block update (repay, borrow and write-off). We would need...
### Proposal for NAV-trait ```rust trait NAV { type Balance; // Requirement allows us to handle scenarios for the correctness of a nav in one place // E.g. `MaxNAVAge` is...
@branan @offerijns @gruberb I changed the desciption and moved this up in our board. Just wanted to have this a little bit clearer speced. I guess, we can bring this...
I would like to bring in the information about the exactness of the NAV. * So change the trait to (the `fn update` will only be needed once we have...
The problem I see here is that for Pool of pools this logic does not work or is at least dangerous. I.e. having two pallets submitting theses updates to the...