additional docs for HIP-1259

docs.json

@@ -62,16 +62,16 @@
   },
   "fonts": {
     "heading": {
-      "family": "Styrene A",
-      "source": "/public/fonts/styrene/StyreneA-Regular-Web.woff2",
+      "family": "Styrene A Medium",
+      "source": "/public/fonts/styrene/StyreneA-Medium-Web.woff2",
       "format": "woff2",
-      "weight": 400
+      "weight": 700
     },
     "body": {
-      "family": "Styrene A",
-      "source": "/public/fonts/styrene/StyreneA-Regular-Web.woff2",
+      "family": "Styrene Light Web",
+      "source": "/public/fonts/styrene/StyreneA-Light-Web.woff2",
       "format": "woff2",
-      "weight": 400
+      "weight": 500
     }
   },
   "background": {
@@ -90,7 +90,9 @@
       "perplexity",
       "mcp",
       "cursor",
-      "vscode"
+      "vscode",
+      "add-mcp",
+      "grok"
     ]
   },
   "integrations": {
@@ -332,7 +334,8 @@
                   "hedera/core-concepts/accounts",
                   "hedera/core-concepts/accounts/account-creation",
                   "hedera/core-concepts/accounts/auto-account-creation",
-                  "hedera/core-concepts/accounts/account-properties"
+                  "hedera/core-concepts/accounts/account-properties",
+                  "hedera/core-concepts/accounts/network-accounts"
                 ]
               },
               "hedera/core-concepts/keys-and-signatures",

hedera/core-concepts/accounts.mdx

@@ -27,7 +27,7 @@ You interact with the network by submitting transactions that modify the ledger'
   ></Card>
 </Columns>
 
-## FAQ
+## FAQs
 
 <AccordionGroup>
 <Accordion title="What is a Hedera account?">
@@ -53,3 +53,4 @@ A Hedera account is a unique entity in the Hedera Network that can hold tokens.
 If an account is created with an [EVM address](/hedera/core-concepts/accounts/auto-account-creation#evm-address) via [Auto Account Creation](/hedera/core-concepts/accounts/auto-account-creation), it results in a "hollow" account. This account has an account number and alias but no account key. It can accept token transfers but cannot transfer tokens or modify account properties until the account key has been added, completing the account.
 </Accordion>
 </AccordionGroup>
+

hedera/core-concepts/accounts/network-accounts.mdx

@@ -0,0 +1,32 @@
+---
+title: "Network Accounts"
+---
+
+The Hedera network uses several special, network-controlled accounts for its operations. These accounts are fundamental to the network's fee structure, staking rewards, and overall economic model.
+
+### Special Accounts Comparison
+
+| Account ID | Name | Purpose | Accepts Deposits? | Has Keys? |
+| :--- | :--- | :--- | :--- | :--- |
+| `0.0.98` | Network Admin Fee Account | Receives the majority of network transaction fees (typically 80%). | Yes | Yes |
+| `0.0.800` | Staking Rewards Account | Holds funds for staking reward distribution. Receives a portion of daily fees (typically 10%). | Yes (donations) | No |
+| `0.0.801` | Node Rewards Account | Holds funds for node reward distribution. Receives a portion of daily fees (typically 10%). | No | No |
+| `0.0.802` | Fee Collection Account | Consolidates all transaction fees before daily distribution. | No | No |
+
+### Account Details
+
+#### Fee Collection Account (`0.0.802`)
+
+Introduced in [HIP-1259](https://hips.hedera.com/hip/hip-1259), this account serves as a temporary holding account for all transaction fees. It is fully code-controlled, has no keys, and cannot accept HBAR deposits from users. This design simplifies transaction records and improves network efficiency.
+
+#### Staking Rewards Account (`0.0.800`)
+
+This account holds the HBAR that will be distributed to users who are staking their tokens. It receives a portion of the daily accumulated fees from the Fee Collection Account. While it does not have keys, it can accept HBAR donations from the community.
+
+#### Node Rewards Account (`0.0.801`)
+
+This account holds the HBAR that will be distributed to node operators for their services. It receives a portion of the daily accumulated fees from the Fee Collection Account. It does not have keys and cannot accept HBAR deposits.
+
+#### Network Admin Fee Account (`0.0.98`)
+
+This account receives the largest portion of the daily accumulated fees from the Fee Collection Account (typically 80%). These funds are used to support the long-term growth and development of the Hedera network. Unlike the other special fee accounts, this account has keys and can accept HBAR deposits.

hedera/core-concepts/mirror-nodes.mdx

@@ -33,6 +33,40 @@ Once a record file is closed, the consensus nodes generate a signature file. The
 
 Hedera consensus nodes push new record files and signature files to the cloud storage provider – currently AWS S3 and Google File Storage are supported. Mirror nodes download these files, verify their signatures based on their hashes, and only then make them available to be processed.
 
+
+## Understanding Block Streams After [`HIP-1259`](https://hips.hedera.com/hip/hip-1259)
+
+For Mirror Node and [block stream](/hedera/support-and-community/glossary#block-stream) consumers, [HIP-1259](https://hips.hedera.com/hip/hip-1259) significantly simplifies the data related to transaction fees, leading to smaller block stream files and reduced data ingestion costs.
+
+### Simplified Fee Structure
+
+The primary change is the consolidation of all transaction fees into a single transfer to the **Fee Collection Account (`0.0.802`)**. 
+
+- **Before HIP-1259:** Each transaction record contained multiple fee-related transfers, increasing the size and complexity of the block stream.
+- **After HIP-1259:** Each transaction record now contains only a single, clear fee transfer to `0.0.802`. This reduces the amount of data per transaction, making block streams more efficient.
+
+### The Daily Synthetic Transaction
+
+A new pattern to be aware of is the **daily synthetic distribution transaction**. This is a network-generated transaction that occurs once per day at the end of each staking period. It is responsible for distributing the fees accumulated in `0.0.802`.
+
+As a block stream consumer, you can identify this transaction by the following characteristics:
+
+- It will contain a single large debit from account `0.0.802`.
+- It will have a long list of credit transfers to node operator accounts, the staking rewards account (`0.0.800`), the node rewards account (`0.0.801`), and the network treasury (`0.0.98`).
+- It appears in the block stream like any other transaction.
+
+<Info>
+  This synthetic transaction is the **only** time you will see funds being transferred out of the [Fee Collection Account](/hedera/support-and-community/glossary#fee-collection-account). All other transactions involving [`0.0.802`](https://hashscan.io/mainnet/account/0.0.802) will be credit transfers into the account.
+</Info>
+
+### Benefits for Mirror Node Operators
+
+- **Reduced Storage Costs:** Smaller block stream files mean lower storage requirements for running a mirror node.
+- **Faster Data Ingestion:** Simpler transaction records can be processed more quickly, improving the speed of data ingestion and synchronization.
+- **Easier Data Analysis:** The fee structure is more straightforward, making it easier to analyze transaction costs and network revenue.
+
+
+
 ### Smart Contract Synthetic Logs
 
 Starting with [v0.79](/hedera/networks/release-notes/mirror-node#v0.79) of Hedera Mirror Node release, synthetic event logs for Hedera Token Service (HTS) token transactions have been introduced to mimic the behavior of smart contract tokens. Synthetic events are generated for transactions such as: