Engineering
NOG: a different way to organize data
How the Nano Object Graph connects a state model to understandable system behavior.
Begin with what changes.
A transaction describes an action. To understand its effect, a system also needs a precise account of the state that action can change. What exists? Who may act on it? Which transformations are valid?
An object-oriented state model makes these questions an explicit part of the design. It describes the things a system holds and the relationships that matter to their behavior.
The role of NOG.
The Nano Object Graph, or NOG, is part of NanoChain’s approach to organizing network data. It provides a way to think about objects, their relationships and the state changes that operations produce.
The aim is clarity. A builder should be able to understand which object an operation concerns, what authority is needed and what a valid result would mean. The representation makes the questions easier to ask; the protocol rules and implementation must supply the answers.
State and execution belong together.
NOG and NVM address connected responsibilities. The data model describes the state a network holds. The execution environment applies the rules for changing it. Their boundary needs to be precise enough to document, inspect and test.
That work extends into explorer views, indexing and developer interfaces. A state model becomes useful when people can understand its behavior through tools as well as through its specification.
Keep exploring
