Nuno

@kim if we look at the TODO, I am not sure what exactly we need to do to "fetch eagerly", given that we seem to fetch as early as we...

> Maybe we need to incorporate it into the setup of the peer in upstream. That seems like the right thing to do yeah

Yes! The only `registry.rs` we have in this project. Will adjust the title anyway.

This is exactly how I pictured doing the `account import` and `account export` :)

I gave this some more thought and I'm not sure whether it's worth implementing this feature. The way I imagine the feature, - on `export`, a file path arg is...

> > on export (...) we essentially require the user to remember the name of their key-pairs > > What's wrong with that? As a user I would just call...

> > Note that you point out the user-unfriendly step there: to perform a step, you first need to perform another one, ... > > This step is optional, it's...

> A couple of things to consider: > > * When in the CLI execution lifecycle to we want to check this? Once everything is done, in `main`. > *...

That solution is simple indeed, but it means that it won't work whenever the runtime is at any newer version unknown to the client, which will create unnecessary incompatibility.

> If a runtime version is known to the client, they're compatible, aren't they? I meant "unkown", edited to reflect that.