Nuno

> > it won't work whenever the runtime is at any newer version unknown to the client > > That's the whole point. If there's a need to bump the...

> > we introduced a new validation spec for some tx, which changes nothing regarding its compatibility with the runtime. > > If it changes nothing regarding compatibility, we don't...

> > For instance, #472 changes nothing to the client in terms of its compatibility > > It's not a good example. It changes the behavior and forces the client...

> > We are the only ones with a client of our runtime that we know, and our CLI is the only known client of our client that we can...

Good stuff! Some thoughts : - I always read "build from source", so "install from source" is not so much of common language. Maybe that's fine though - I would...

I was about to create a duplicate of this issue 😄 💯 agree

> Ideally it would be two separate client methods. So that you can have different handling lanes in the upstream or for some other reason? From our side, it would...

> and then fetch the project names. Do you mean to fetch the projects by name? If so, you'd still have to specify the project holder id (org or user...

Thanks, typo fixed!