From 300d8e49f2b5ed6c7d5c3aa616ce922a53f34e84 Mon Sep 17 00:00:00 2001 From: Ian Clarke Date: Fri, 8 Mar 2024 16:30:27 -0600 Subject: [PATCH] minor --- docs/src/components/contracts.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/src/components/contracts.md b/docs/src/components/contracts.md index 8e2ba0afc..6a093f0ff 100644 --- a/docs/src/components/contracts.md +++ b/docs/src/components/contracts.md @@ -6,6 +6,11 @@ along with their data or "state". The contract controls what state is permitted and how it can be modified, and also how to efficiently synchronize state between peers. +A contract's state is just a block of bytes, and can be anything from a simple +number to a complex data structure. The contract's code defines the state's +formatting. Even the serialization format is up to the contract, so it can be +anything from JSON to Bincode, or a custom binary format. + Network users can read a contract's state and subscribe to receive immediate updates if the state is modified.