mrBovo

To be rebased onto #5062

I need to add benchmarks

- Runtime upgrade integration test ➡️ It's the one using fork-off, right? - Runtime upgrade unit tests ➡️ is it the one with the `try_runtime` feature? @mnaamani

@kdembler To sum it up: given that luxor has been released, have the CI checks been updated and fixed ?

This looks like very hard to reproduce. I also suspect that the download is failing because there's no sufficient HEAP space for the file to be stored in memory before...

There shouldn't be much be much complexity here, there's a premade extrinsic called `vested_transfer` which is can be leveraged. https://github.com/paritytech/substrate/blob/ad5399644aebc54e32a107ac37ae08e6cd1f0cfb/frame/vesting/src/lib.rs#L349

I have rewritten your points @mnaamani, to make sure I understand what you are saying ### Rationale The usage of Colossus storage is reaching levels that are challenging to manage...

> By that I mean a node that doesn't accept uploads directly, but only synchs objects from other storage providers and then stores them in S3. ok so this means...

AWS SDK is available also in typescript https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/#Usage_with_TypeScript So this means that we are first rolling out an initial version where we just synch to glacier storage, right? @kdembler ####...

Remember to update benchmark if extra computation is required