Skip to main content

​
1. A Neuron changes a persisted object

The application performs a normal operation, such as creating or updating an object. Ledger participation is determined by the installed service and object configuration; it is not requested by adding a special field to an API call.

​
2. The ledger records the change

New, updated, deleted, and cleared records can become ledger entries. Entries retain the information needed to identify the operation and verify its recorded representation.

​
3. Entries are collected into blocks

The Neuron groups entries by collection and closes blocks according to its configured collection interval and size threshold. The node signs the resulting block and publishes its reference.

​
4. Authorized peers synchronize

Approved contacts exchange block references over XMPP. A peer retrieves a block only when access policy permits it, then verifies the block before accepting its contents.

​
5. History can be checked

Operators can inspect block statistics, collections, signatures, and synchronization results. Applications normally inspect the higher-level contract, token, or object history exposed by their supported API.

​
Protect private ledger data

“Distributed” does not mean “public.” A deployment can require a data-protection agreement and authorization before another node can retrieve blocks. Whether a specific record is shared depends on the deployment and collection policy.