Merge branch 'main' into rpc_overview

Author: laviniat1996

ton/addresses/formats.mdx

@@ -22,7 +22,7 @@ of messages and is inspired by the [corresponding TL-B schemes](https://github.c
 
 In existent workchains, the raw format consists of two components separated by a colon:
 
-- `workchain_id`: a signed 32-bit integer identifying the workchain.<br />
+- `workchain_id`: a signed 8-bit integer identifying the workchain.<br />
   Examples: `-1` for the MasterChain and `0` for the BaseChain.
 - `account_id`: a 256-bit identifier that is derived from a smart contract `state_init`.
 

ton/addresses/overview.mdx

@@ -40,7 +40,7 @@ And four components:
 
 ### WorkChain id
 
-TON Blockchain is actually a collection of blockchains, with WorkChain being one of them. TON supports up to `2^32` unique WorkChains, each with its own rules and even virtual machines. The 32-bit `workchain_id` prefix in smart contract addresses ensures interoperability, allowing contracts to send and receive messages across different WorkChains.
+TON Blockchain is actually a collection of blockchains, with WorkChain being one of them. TON supports up to `2^32` unique WorkChains, each with its own rules and even virtual machines. The 8- or 32-bit `workchain_id` prefix in smart contract addresses ensures interoperability, allowing contracts to send and receive messages across different WorkChains.
 
 Currently, two WorkChains are active:
 
@@ -86,7 +86,7 @@ addr_extern$01 len:(## 9) external_address:(bits len)
 
 - **Every actor is a smart contract**, each with a unique address for message routing.
 - **Main internal address fields**:
-  - `workchain_id` (32-bit): identifies the WorkChain.
+  - `workchain_id` (8- or 32-bit): identifies the WorkChain.
   - `account_id` (256-bit): a hash of the contract’s initial code and data.
 - **Active WorkChains**: MasterChain and BaseChain, both using 256-bit ids.
 - **Flexibility**: TON supports up to `2^32` WorkChains, allowing future chains to customize address lengths (64–512 bits).