Sergey Rodionov

1. We can store whitelist for accessing the service in metadata. We don't need to keep it fully on-chain. We can do it right now without modifying contracts. 2. in...

-> 1.) Even if whitelist will be on-chain (and you not in this whitelist) then it will not stop you from calling service if you really want it. Ethereum blockchain...

I agree that ```snet service``` commands are rather long and we probably should do something with it. But it will be really confusing to simply remove ```metadata-``` and ```update-``` prefix...

@ferrouswheel Yes... It makes sense... We need to think how to incorporate your idea with ```snet push```....

If we store all documentation directly in IPFS metadata (not as simple link to github wiki, but directly in metadata) then each change in documentation will force change in on-chain...

@arturgontijo I would propose slightly different approach. We should check for possible errors before making transaction. For example: In ```snet organization add-members``` we should check that current identity is the...

I'm totally agree that we need to discuss... Having serviceid (or even serviceglobaId) is might be a good solution (I believe you've proposed it back in HK). (id could be...

So in any case we need to have some predefined scenarios. Two the most simplest one * **stream-as-request**, simple one time request-response scenario, but client sends request as a stream...

If we start use snet-cli as a basis for SDK it might be a problem, and there are different possible solutions...

For example it is an issue for #108. We need to optimize "imports"...