From d4aa648fd0a00f5f0429adee1555aa767959772f Mon Sep 17 00:00:00 2001 From: Melody Serra Date: Tue, 26 Nov 2024 17:56:30 -0500 Subject: [PATCH] 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 <75431177+nickfrosty@users.noreply.github.com> * fix: spacing --------- Co-authored-by: Nick Frostbutter <75431177+nickfrosty@users.noreply.github.com> --- docs/intro/quick-start/reading-from-network.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/intro/quick-start/reading-from-network.md b/docs/intro/quick-start/reading-from-network.md index 268f06a2a..e65d0abdb 100644 --- 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,