![eos_wallpaper.png](https://steemitimages.com/DQmTWRn2cNwwgUhzZPfbtZRF8UUZ1cmi39u66BNc56V91R3/eos_wallpaper.png)


Hello EOSians,
## My Background
I am a developer. I was involved in a DApp development over **Steem Blockchain** for last 2 months. Anyways, I will be releasing it soon.

In the meanwhile, I was exploring **EOS** blockchain theoretically. And suddenly today, a doubt occurred to me. 

## Question
#### It is related to EOS Block Producer (BP) - What if 21 BPs are attacked simultaneously? EOS blockchain HACKED!!!..

## Answers
***
> everyone with a full node can monitor what the block producers are doing. If they get hacked and produce invalid blocks everyone will see that and instantly vote the block producers out. yielding new 21 producers which are not hacked.

**My opinion**: OK. But, then rest of the other nodes should always be incentivized in order to take-up as and when the 1st 21 nodes is hacked. Otherwise, they won't remain as full-node.
***
***
> There are 100 back up producers who can take over in the event of (for example) a DDOS attack that took down all of the top 21.  The next 21 would step in immediately to produce blocks in their place.

**My opinion**: If this is the case, then what if 121 BPs get hacked simultaneously? Then again we have to incentivize other _100 nodes in queue_, so that they can take-up as and when the (21 BPs + 100 Back-up nodes) are attacked.
***
***
> There is a concept called “Rate Limiting“
In the whitepaper, will signifiantly prevent the Sillby Attack

**My opinion**: Rate limiting- tracks bandwidth, database storage, and computational usage. But how does it protect the EOS BPs?
***
***
> Current thinking is 50% of token inflation is split among the 100 standby BPs in proportion to their votes gained.

**My opinion**: I am not sure about this information whether it is correct. But then my Q. is What if 121 nodes get DDOS attacked then?
***
***
>  each BP requires 4TB ram, 1-10gps net connections
>  each bp is not a static web-site

**My opinion**: No matter it is not a static website. But still there are ways to hack any form of IP (centralised).
***
***
> The producing node of each BP would not be exposed
And DDOSing all 121 all over the world with various configurations at exactly the same time would be next to impossible

**My opinion**: I don't think so. Because, in Steemit top 50 is exposed. If it is correct, then possibly the attack might not be possible. But again, where the information about the hidden nodes is stored. Is the information stored in Blockchain? But EOS blockchain is not private. 
***
***
> It will be prevented by 
1. rate-limiting
2. high network gps

**My opinion**: I don't think it will be difficult with quantum computers , super-computers.
***
***
> based on current knowledge of computer science, we can say that the possibility is extremely tiny, but even if it happen, we can handle
but EOS’s hard-fork will be much smoothier than BTC/ETH

**My opinion**: I agree with this. The retrieval from attack is possible through Hard-fork which is not difficult as compared to BTC/ ETH because of the fact that less nodes involved in EOS.
***

### Telegram Screenshots
[#EOS developer Telegram chat](https://t.me/joinchat/EaEnSUPktgfoI-XPfMYtcQ)
 ![eos_blockchain_discussion_telegram_1.png](https://steemitimages.com/DQmaQKxkE8oXJmH34acNxUbt4RWU5LWCQTBGm4idGpSRfEQ/eos_blockchain_discussion_telegram_1.png)

[#EOS Hong Kong Telegram chat](https://t.me/EOSHongKong)
![eos_blockchain_discussion_telegram_2.png](https://steemitimages.com/DQmSMsC478paZH2GP2S7jEMv1HdtiWhZQMPR9iuC9VJ4BN9/eos_blockchain_discussion_telegram_2.png)

![eos_blockchain_discussion_telegram_3.png](https://steemitimages.com/DQmYZxqjjeiuTMbQRCmADwsssFN71yKvrPg9gobPHs4K5LB/eos_blockchain_discussion_telegram_3.png)

![eos_blockchain_discussion_telegram_4.png](https://steemitimages.com/DQmdeETctdFNyjwBzamgt6Pfxuakqdfh9mXbYjjhERkjYq5/eos_blockchain_discussion_telegram_4.png)

![eos_blockchain_discussion_telegram_5.png](https://steemitimages.com/DQmWnH8qZMgpPx4asXShXuK3XHJjNZffRv1VU51Gh3mxLnM/eos_blockchain_discussion_telegram_5.png)

![eos_blockchain_discussion_telegram_6.png](https://steemitimages.com/DQmPQyqnpNnf7ALFak8a27ZMYvEU4D7uJmyHo6V38VUsUJE/eos_blockchain_discussion_telegram_6.png)

![eos_blockchain_discussion_telegram_7.png](https://steemitimages.com/DQmckF1bM3DkueVox6PHHc2E8D9mgPd1JrwQiMBPDn9pJiC/eos_blockchain_discussion_telegram_7.png)

![eos_blockchain_discussion_telegram_8.png](https://steemitimages.com/DQmQz2kRwCm3rd7rUisC1TUcMLuWgbofRVsd5PuN7rmpb7n/eos_blockchain_discussion_telegram_8.png)

![eos_blockchain_discussion_telegram_9.png](https://steemitimages.com/DQmZi3SR5Xuz1Ff6Ar1Q5vrELbS4FiBciSHmqh7xdhRUCYv/eos_blockchain_discussion_telegram_9.png)

![eos_blockchain_discussion_telegram_10.png](https://steemitimages.com/DQmbX3Ahj3xp1LKGTwzS8DorxbsZGtuFCCDNFtSEXGdvwaP/eos_blockchain_discussion_telegram_10.png)

![eos_blockchain_discussion_telegram_11.png](https://steemitimages.com/DQmRTdaYJDyN6gvQy45KsxbecKkL1f4CFAnDUW55Hv3y88J/eos_blockchain_discussion_telegram_11.png)

## Conclusion
Well, the answer to this question is not found so far from the discussion. If anyone has, can participate in the comment section.

I will be taking further topics in this discussion forum.

Stay tuned for more such detailed discussion.