sander2

Yea I was using that. It just has a lot of noise. For dev work that is not a problem. However, we're starting to use dry-run to demonstrate the effects...

This also applies to lending (supplying) limit

Someone from the community ran into this as well - I think this should be given some priority

@nud3l tagging you at your request

To add to that, I think we'd need to have a `process_slashes` function that takes a vaultid and a vector of nominators. This way, we can make the weight dependent...

Thank you for the report @jonathanudd . Point number 5 indicates that the problem likely originates upstream, would you be able to submit the report to substrate?

Started on this task. I'm trying to add the relay to the node service. The reason for not going the offchain worker is that the offchain worker is executed in...

If we want mandatory replace requests, we can simplify replaces a lot by removing the `request_replace` and `withdraw_replace` extrinsics, and modifying `accept_replace` such that it can be called by the...

I think the following steps need to be done. A problem is that by making replace request originate from the old_vault, we can't supply a btc address as argument. Instead,...

> Why not? Do you mean from a UX perspective? In that case we can just use the master key which is already in the Vault's wallet. The master key...