Lee ByeongJun

> > Most of the parsing code was referenced from the [jasonparser](https://github.com/buger/jsonparser) package. > > Since most of the logic is taken from the [buger/jasonparser](https://github.com/buger/jsonparser). Please make sure the MIT...

> Add OnBloc's implementation of `uint256` to `examples/gno.land/p/demo`, battle test it, see how it works, and later down the line consider adding it to GnoVM stdlibs or implementing a native...

In the `math_int8.gno` file, the paths for the `Add8`, `Sub8`, `Mul8`, and `Quo8` functions are recognized as `math/overflow`. It seems that this file also needs to be modified the import...

> would be nice to automate this, any idea? It would definitely be convenient to automate, but for now I can only think of scanning the directory with a shell...

> ping @notJoon Oh, I toatally forgot about this PR. Is there anything else I need to work on? like the automation that we talked before.

> It requires adding an exception in code to simply split between "normal" and "long" packages; no automation / code-generation needed. Yes, I've updated to based on your comment, and...

> Will take a look at this and give feedback 🙏 Thank you @zivkovicmilos! I'm still trying to understand most things, every feedback would be greatly helpful

> do you think it's possible to include not only pkg path but which function(i.e function name) triggered event?? I agree. Rather than just exposing the package name, it must...

The event messages that were previously being outputted have been improved to be displayed in JSON style. Especially when triggering multiple events, the previous version had poor readability, but with...

> From the review meeting, let's use `EventString` instead of a custom, amino-registered GnoEvent. In order to apply this change, I modified the existing `Emit` function. Instead of using the...