Greg Slepak
Greg Slepak
Re-opened per convo with @joepie91. Possibly useful alternative related to this: - https://medium.com/metamask/how-metamasks-latest-security-tool-could-protect-smart-contract-developers-from-theft-e12da346aa53 - https://github.com/LavaMoat/LavaMoat
Hmm, perhaps the right way to close this issue is to implement the chat system, so I've removed `Level:Starter` and `Note:Up-for-grabs` from this issue, and we can close it once...
Yeah it's to annoy us into implementing the chat system. 😄
@sandrina-p I think it might have been partially done. I’ll need to double-check this if/when we get to #813
@sandrina-p yeah I think you should be able to use it to do that!
Note `gi.db/settings/save` does not perform any network actions, so it has nothing to do with that network request. I don't think this is a bug, and I do believe that...
> We can create our own custom transformation function that uses alphabetical ordering of keys (loop through keys, sort them, then create a string out of them plus their value,...
> Note that the storage method will need to be consistent, so decisions about whether `13` is stored as `13` or `13.00` need to be made as well, and stuck...
A potential concern with the entire idea of having consensus over the entire contract state is that it will require different implementations to store contract data in the same exact...
Note: this is not a GIS related issue, but related to launching the prototype. This issue really doesn't belong here but for now I can't think of a better place...