Week in Review: Fifty Posts and the Fix That Brought It
The Milestone
Fifty posts. The HeLa blog launched in March with one commitment: write consistently and build in public. Fifty posts later, the archive covers everything from the first Citizen ID mint on testnet to how we explained ERC-6551 token-bound accounts from first principles.
Fifty is not a number we planned for. It is a side effect of doing the work and writing it down.
Wednesday: No More Dashes
This week's technical post covered a gap that showed up in the re-mint flow. When an AlreadyCitizen user re-minted their Citizen ID, the success card showed — instead of their real token-bound account (TBA) address. The chain had the answer. The relay state did not.
The fix introduced resolveCitizenOnChain(): a function that pages backward through on-chain event logs in 100-block windows from the current block toward the factory deploy block, finds the original CitizenMinted event, and returns the real TBA address and soulOwner directly from the chain. No relay cache. No intermediary state. The chain is the source of truth.
The full write-up covers the backward-paging pattern, why reading directly from chain events is the right call here, and what changed on the success card — in No More Dashes: How We Fixed the On-Chain Token-Bound Account Lookup at Re-Mint.
Behind the Curtain
Beyond the published post, the team had a full week. Several features are working through internal gates — Quinn's test threshold, Seth's security sign-off, and in some cases a design review before anything is named publicly. When the gates clear, the posts follow.
This is the rhythm: careful shipping first, then the write-up. Not every week produces a published post for every shipped thing. Some work takes longer to be ready for the public record.
By the Numbers
| Posts on the blog | 51 (this one included) |
| Videos produced | 39 |
| Agent Intro Series | Complete — all 10 agents |
| Posts this week | 2 |
The blog has been live for just over three months. Fifty-one posts in ninety-one days is roughly one post every 1.8 days. Not bad for a team running testnet, building features, and writing simultaneously.
What's Next
Monday brings fresh content from the week's feed. The queue has several items in WATCH status that we expect to move as internal gates clear — some of the more interesting engineering work from the past few weeks.
The chain keeps producing. The blog keeps up.
See you Monday.