> For the complete documentation index, see [llms.txt](https://pankuku.gitbook.io/kuku_wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pankuku.gitbook.io/kuku_wiki/knowledge-center/security/binance-smart-chain.md).

# Binance Smart Chain

***Why we choose Binance Smart Chain (BSC)***

Far most for it's **Advance Security** advantages.\
**BSC** uses the [**The Proof-of-Staked-Authority (PoSA)**](/kuku_wiki/knowledge-center/glossary-and-vocab.md) mechanism to achieve **Network Consensus** and maintain **Blockchain Security**.\
**PoSA**, as applied by the network, is a **combination** of [**Delegated-Proof-of-Stake (DPoS)**](/kuku_wiki/knowledge-center/glossary-and-vocab.md) and [**Proof-of-Authority (PoA)**](/kuku_wiki/knowledge-center/glossary-and-vocab.md). \
Furthermore, **staking models are more environmentally friendly** and **support faster block generation**.&#x20;

***BSC Advantages*** :arrow\_double\_down:

**Transaction Speed**\
BSC is currently one of the **fastest smart contract platforms**, contributing to its fast growth. Blocks are generated every **3 seconds** **compared** to **Ethereum’s 13 seconds**, making it at least **four times faster**.

**Low Gas Fees**\
It currently costs an average of **5** [**Gwei**](/kuku_wiki/knowledge-center/glossary-and-vocab.md) to process a transaction on **BSC**, which is far cheaper than the **40** [**Gwei**](/kuku_wiki/knowledge-center/glossary-and-vocab.md) charged on **Ethereum**. That is an **8x cheaper** price tag to run a [**dApp**](/kuku_wiki/knowledge-center/glossary-and-vocab.md) on BSC than running the same app on **Ethereum**.&#x20;

**Cross-Chain Compatibility** \
Not only is BSC **compatible** with Ethereum virtual machine (**EVM**), it also supports pegged coins from several other blockchains allowing users to create several tokens to use on the network. **Cross-chain compatibility** increases token **liquidity**, **utility**, and **value**.&#x20;

**EVM Compatibility**\
Choosing to fork the Geth **Ethereum** client makes **BSC** more familiar to Solidity developers, which gives the **Binance** network easy access to an already vibrant community of developers and users. Additionally, since it’s cheaper to run **dApps** on **BSC**, it makes it easy to **port applications** over from **Ethereum**, which is **faster** and **cheaper** to **execute**.&#x20;

**Credible Platform and Company** \
**Binance** is one of the most popular exchanges, and its credibility is shared across all its platforms, including the **BSC**. The exchange also plays an important role in the **PoSA consensus** by **vetting all validators** on the network, **ensuring** that the **blockchain** is **secure** and **reliable**.

***To read more about BSC, check out these articles***

{% embed url="<https://academy.binance.com/en/articles/an-introduction-to-binance-smart-chain-bsc>" %}
***All rights to this article belong to Binance***
{% endembed %}

{% embed url="<https://coinmarketcap.com/alexandria/article/what-is-binance-smart-chain>" %}
***All rights to this article belong to Coinmarketcap and/or mister Werner Vermaak***
{% endembed %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pankuku.gitbook.io/kuku_wiki/knowledge-center/security/binance-smart-chain.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
