Gabriel Facco de Arruda

> The documentation of the `Platform` trait are normally good enough that you shouldn't have to read the JS code. Feel free to point out things that you don't understand...

This issue should get some level of priority, as it makes it impossible to have different rules for specific windows of the same app.

Alright, that's a really good point. I'd also like to ask that for gov2 these aspects should be taking into consideration from the get go, because like this issue, it...

Would the implementation of meta transactions allow for calls dispatched from inside another extrinsic charge fee from that inner call's origin instead of the outer call's signer?

- [x] Improve NftLocation account derivation (ref. DescribeLocation) - [x] Implement custom registered calls struct to avoid encoding calls that could change in the futute - [x] Create a repo...

> I would love to see this added to the `inv4` pallet. I think expiry and minimum lifetime should be considered as a basic functionality for multisigs, but a lot...

> My plan is the following: > > - Add two optional arguments to the `operate_multisig` extrinsic representing minimum time and expiry time. > - Add two new fields to...

Hey all, I've been away from this issue for a bit, has anyone managed to find a workaround to solve this until it gets fixed?

> Reproduces on sway 1.7 and 1.8. Reproduces on 1.9-dev-0695f3fa

Requires #208 for this implementation to be fair, solving the issue of minimum proposal lifetime by allowing the multisigs themselves to decide how they want that to work.