It felt like a quieter month because I was busy handling my U.S. VISA process. You’re probably wondering why I’m going to the U.S. it’s because our team is finally going to have an in-person meetup! Even though a lot of time went into VISA paperwork, I didn’t slack off at work.

Since I’ve started focusing on NEM Explorer, I spent time studying the NEM Catbuffer schema. The reason is that the NEM API doesn’t provide transaction or block size information. So I worked on calculating transaction size and block size, both of which are needed by the NEM Explorer. And of course, I also did some dependency cleanup across related project.

Summary of Key Work

• Studied NEM Catbuffer schemas
• Refactored and Improved NemBlockCalculator
• Added Coverage report to the Explorer Puller.
• Cleaned up dependency issues across several projects.

Work

Studie NEM Catbuffer Schemas

• Used JSON data returned by API and serialized it into bytes, this is more efficient for implementing size calculations in the NEM Explorer backend.
• Gained a better understanding of transaction and block structures, which helps build a more accurate and reliable NEM Explorer.
• You can explore the Catbuffer schemas here.

Added NemBlockCalculator in lightapi/python

• NEM’s API endpoints do not provide transaction and block sizes.
• There are a fews ways to calculate size:
  • Use the binary responded from the API, or
  • Serialize the data into bytes.
• Based on performance considerations, serialization is more efficient than querying via the API.