← Back
Jan 2026 The Symbol Syndicate | Anthony’s Engineering Blog

Jan 2026 The Symbol Syndicate | Anthony’s Engineering Blog

Anthony’s Engineering Blog for January 2026

Share this article

Read the January 2026 English blog here

https://thesymbolsyndicate.notion.site/Jan-2026-32aa7f7eb5e4801eb847fd245a45f5c7

Anthony’s Engineering Blog for January 2026 (Japanese Translation)

A new year begins, and with it a new chapter. I hope everyone is healthy, with fresh goals and renewed hope for what lies ahead.🏴‍☠️

At the start of the year I stayed firmly focused on NEM Explorer. Going back and forth through PR feedback, I refined the logic and steadily shaped the backend into something more accurate and reliable.

Summary of Main Work

  • Completed the harvesting fee logic and integrated it into the database
  • Identified and used beneficiary and totalFee from the API
  • Made progress on the /account and /accounts endpoints
  • Added beneficiary support to lightapi/python
  • Improved test coverage and handled multiple PR feedback cycles

Details of Each Task

Nem Explorer (Puller)

  • It became clear that beneficiary and totalFee can be obtained directly from the API, which reduces extra network calls during block processing.
  • I initially implemented harvesting fee calculation based on block data, but since the API's totalFee can be used directly, that calculation implementation became unnecessary and was later removed.
  • I added a beneficiary (harvester) field to the database schema. Until now, we depended on the block signer's public key and performed additional lookups to resolve the actual beneficiary, because the signer could be a remote account. This change eliminates the need for extra API calls.
  • I continued improving the account processing logic and added more unit tests.

Nem Explorer (REST API)

  • Added a new /account endpoint so the frontend can query account information by public key or address.
  • Introduced a paginated /accounts listing endpoint that can sort by 残高 and filter by ハーベスティング状況.

Lightapi / Python

  • The beneficiary and totalFee fields were identified from the local/chain/blocks-after endpoint.
  • I extended the library to expose these fields so the puller can retrieve and use this data directly.

What’s Next

The account module is almost complete, and it is currently waiting for PR review feedback. Responding to comments may take a little time. In the meantime, to keep the momentum going, I will continue working on the namespace module.

Thank you for reading this far. See you again next time! 🏴‍☠️

Image

Anthony (Japanese translation by Radio)

Past Japanese Translations of The Symbol Syndicate | Anthony’s Engineering Blog