Update reading-from-network.md (#599)

* Update reading-from-network.md why behind buffering this way * Update docs/intro/quick-start/reading-from-network.md Co-authored-by: Nick Frostbutter <[email protected]> * fix: spacing --------- Co-authored-by: Nick Frostbutter <[email protected]>
solana-foundation · Nov 26, 2024 · d4aa648 · d4aa648
1 parent 6c5b4cd
commit d4aa648
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/docs/intro/quick-start/reading-from-network.md b/docs/intro/quick-start/reading-from-network.md
@@ -129,6 +129,11 @@ Let's break down the fields in the output:
 - `data` - This field contains what we generally refer to as the account "data".
   For a wallet, it's empty (0 bytes), but other accounts use this field to store
   any arbitrary data as a serialized buffer of bytes.
+
+> When data is "buffered" in this way, it maintains its integrity and can be
+> later deserialized back into its original form for use in applications. This
+> process is widely used in blockchain for efficient data handling.
+
 - `executable` - A flag that indicates whether the account is an executable
   program. For wallets and any accounts that store state, this is `false`.
 - `owner` - This field shows which program controls the account. For wallets,