EOS uses a delegated proof-of-stake system where 21 block producers are responsible for verifying transactions and producing blocks. Transactions are stored and verified in an in-memory database called Chainbase by the block producers. This architecture allows EOS to scale transactions through parallelization across the 21 block producers, but introduces vulnerabilities since the transaction data resides in memory and block producers must coordinate to prevent issues like cartel formation or mutable transactions. Therefore, EOS implements a client-server system with a 21-server cluster model rather than a traditional blockchain architecture.

1. WHY
EOS is not
Blockchain?
7 November, 2018

2. EOS Mainent Architecture
21 Block Producers
EOS User

3. Update 1-8
Update
1-1
Update 1-2
Update 1-3
Update 1-4
Update 1-5
Update 1-6
Update 1-7
Update
The Scalability of Blockchain vs. Client Server System

4. Sharding
Raden
Netw
ork
ZK-SNARKS
POW → POS
Sidechain
Ethereum’s response to its scalability problem

5. Shrinks Consensus to 21 Block Producer
EOS’s response to blockchain scalability problem

6. Overview of EOS System Architecture
Source: Whiteblock, https://cdn0.tnwcdn.com/wp-content/blogs.dir/1/files/2018/11/EOS_Report.pdf

7. Chainbase
Cryptographically and directly verifying transaction on EOS mainet
Update to blockchain Verify transaction
How EOS BP verifies & updates transaction by Whiteblock
Detect transaction

8. CPU
Checkpoint files Transaction Log files
Something similar to how EOS BP verifies & updates transaction
Directly-
Linked or
Memory-
Resident
Application
DatabaseAdapters
SERVER
Source: Oracle, Adapted from Oracle Timesten

9. Where in the world is this EOS “Chainbase” located?
Checkpoint files Transaction Log files
Directly-
Linked or
Memory-
Resident
Application
Chainbase
Block Producer
Server requirements
1. Expected location of servers
2. Type of servers (cloud, bare metal, etc)
3. Scaling plan for hardware

10. Core Layer
The block producing layer and the heart of the
operation.
The highest priorities are security and
connectivity to other block producing nodes.
Our goal is to utilize both bare metal for block
production and multiple cloud providers to
accomplish a mix of full control and quick
scalability.
- 80 GBs - 3 TBs of RAM (as needed)
- 4-8 vCPUs
- 1 TB of SSD Storage
RAM matters to BPs of EOS!
Source: https://www.eosnewyork.io/tech
Signing Node Producing Node Storage

11. Where the in-memory DB is usually used
● High Frequency Trading
● Derivative trading
● Real time billing
● EOS DApp….
This is why RAM matters to EOS!

12. Vulnerability of in-memory DB
CPU
Directly-
Linked or
Memory-
Resident
Application
RAM resident VIRUS & Malware is eaily spread

13. BP tends to form a Cartel for Capacity Planning

14. EOS transactions are mutable with In-Memory DB
Checkpoint files Transaction Log files
Directly-
Linked or
Memory-
Resident
Application
Chainbase
21 Block Producer Servers

15. Conclusion: EOS is client-server system with 21 server cluster