The block in TON It has Flexible structure unlike blockchains with a fixed block size. This allows for efficient storage of different types of data.
Three levels of architecture#
| The level | Appointment |
|---|---|
| Masterchain | Main chain, coordinates other, metadata networks |
| The worker girls . | Sub-attaches for protocols or applications |
| Shardchains | Parallel segments of the wormchains |
Block layout#
Header in Masterchain
| The field | Appointment |
|---|---|
| Link to previous block | Cryptographic hash → chain consistency |
| The root hash (root hash) | The root of the Merck tree → data integrity |
| What is the workchain ID ? | The shard that owns the block. |
| The number of the next slot | Time to create the next block |
| Additional data | Validator, limits, version of the protocol |
The main part (Body) in shorthand
- Variable size;
- The transactions (transfers, contracts and operations);
- Changes in the balance sheet (balance sheets, storage facilities).
Dynamic sizes
- Header fixed + small;
- Body variable → adjusted to the volume;
- Efficient scalability without loss of productivity.
The Merckle Tree#
- Each transaction/fragment is It 's hashed .;
- Hashes are paired together → new hashes;
- The process continues until the only root hash;
- Any modification Changes the hash → manipulations are obvious.
Transaction layout#
| The component | Contains |
|---|---|
| The title | Logical time, count, identification |
| Input data | Sending + originating |
| Data about the actions | Smart contract code + change of state |
| Outgoing data | Messages to other accounts/shards |
More details: TON Transaction Types.
The endless .sharding#
The paradigm of the infinite .sharding:
- Dynamically generating chords for network needs;
- Uninterrupted It 's an inter-shard connection .;
- Balancing the load;
- Infinite scaling while maintaining performance.
Work chains and parallel processing#
- The network = a lot of shards (workchains);
- Everyone is processing transactions . At the same time .;
- Block headings → overall integrity.
Each block chain contains:
- The list of transactions;
- The current status of the accounts and contracts;
- It's a header with metadata.
Security .#
| The mechanism | Appointment |
|---|---|
| The hash functions | The data integrity |
| Signed | Legitimacy of blocks and transactions |
| BFT consensus (optional) | Decentralized untrusted confirmation |
| Easy customers | Loading only headings → resource-efficient |
The advantages#
- Scalability through dynamic design + sharding;
- Efficiency through optimized architecture;
- Flexibility when the load changes;
- Cryptographically protected data.