Erik Zhang

> Attributes are optional, hence we can define Content-Type as a well-known attribute in specification and check it if it was set. Can Content-Type be mandatory?

> hash: this is the only thing that can't be JSON originally and it really needs to be wrapped What is the format of hash? What is its length?

Then we can return it as a string, just like a hash of a block. ``` "0xd42561e3d30e15be6400b6df2f328e02d2bf6354c41dce433bc57687c82144bf" ```

> These servers will return session/iterator IDs from invoke* https://github.com/neo-project/neo-modules/blob/32bd86dc672b323cf29521c4d2257a66a904514c/src/RpcServer/RpcServer.SmartContract.cs#L113-L123 It won't return session id if `SessionEnabled` is `false`. > And it's important for the client to separate session errors...

Can anyone review it?

@devhawk Please check #687

According to the docs in https://docs.microsoft.com/en-us/dotnet/csharp/nullable-references > annotations: The compiler doesn't perform null analysis or emits warnings when code might dereference null. It won't emit warnings. And the result of...

> Now it won't ever emit warnings, even if the user has explicitly opted-in to getting the warnings. The users will get the warnings in IDE.

>Instead of just solving the simplest storage problem (single value storage such as TotalSupply), can we instead work on an approach that would also work for: > >Single key storage...

Automatically? Then everyone can modify the storage of your contract. I think you should call `CheckWitness` in `set`.