Part two of our HookState series. In part one we covered why raw HookState bytes are hard to read and how the Hook State Converter lets you decode them into a typed ABI schema. This article picks up where that one ended: what you do with that schema once you have it. From a JSON segment to something useful At the end of part one, you had a JSON ABI definition — a typed map of your HookState key

HookState Data Viewer: Browse On-Chain State, Build Projections, and Publish Your Hook Manifest
zgrguric·Dev.to··1 min read
D
Continue reading on Dev.to
This article was sourced from Dev.to's RSS feed. Visit the original for the complete story.