Sergey Rodionov

@ferrouswheel yes. I guess (but it should be studied) the main problem is in relatively "heavy" libraries (as web3) which we use, so it simply takes time to import them....

It is relatively easy to make, but it will add two optional parameters (amount and expiration) which might be confusing.

Personally, I don't like such interactive command line dialogs. It should be easy to use snet-cli from bash script. So I would make it like this: ``` snet client call...

@ferrouswheel In https://github.com/singnet/snet-sdk-python/issues/9 you proposed to store all information in "project" directories as git does. It is ok for service providers but not for clients. How it will work on...

@raamb We need to define user stories and based on them think about general architecture to solve this and several other issues https://github.com/singnet/snet-cli/issues/174 https://github.com/singnet/snet-cli/issues/175 #176 https://github.com/singnet/snet-cli/issues/181 (plus unification with SDK...

Ok... Actually I don't see much difference, it doesn't matter what we consider the "canonical" version. We can easilly support both points of view. We simply should have two "commands":...

Should we close it?

Now snet-cli and daemon use development releases in order to get ABI of contracts. But it should be noted that snet-cli gets address of Registry and AgentFactory from networks/*.json files...

* I'm a little bit warring about F-string. From the first glance f-string might be a security risk (because inside {} you can execute arbitrary function). * I'm strongly against...

- About f-strings... yes it seems you cannot pass arbitrary string from outside and than "execute" it in f-string... I would still vote for allowing old %-format just because I...