Skip to content

Latest commit

 

History

History
48 lines (30 loc) · 4.83 KB

README.md

File metadata and controls

48 lines (30 loc) · 4.83 KB
Raw

A Modification of Binance Smart Chain client v1.1.9

NOTE: This version is outdated (prior The Merge) and does not work properly compared to the latest version of BSC client

The goal of Binance Smart Chain is to bring programmability and interoperability to Binance Chain. In order to embrace the existing popular community and advanced technology, it will bring huge benefits by staying compatible with all the existing smart contracts on Ethereum and Ethereum tooling. And to achieve that, the easiest solution is to develop based on go-ethereum fork, as we respect the great work of Ethereum very much.

Binance Smart Chain starts its development based on go-ethereum fork. So you may see many toolings, binaries and also docs are based on Ethereum ones, such as the name “geth”.

API Reference Discord

But from that baseline of EVM compatible, Binance Smart Chain introduces a system of 21 validators with Proof of Staked Authority (PoSA) consensus that can support short block time and lower fees. The most bonded validator candidates of staking will become validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality.

Cross-chain transfer and other communication are possible due to native support of interoperability. Relayers and on-chain contracts are developed to support that. Binance DEX remains a liquid venue of the exchange of assets on both chains. This dual-chain architecture will be ideal for users to take advantage of the fast trading on one side and build their decentralized apps on the other side. The Binance Smart Chain will be:

  • A self-sovereign blockchain: Provides security and safety with elected validators.
  • EVM-compatible: Supports all the existing Ethereum tooling along with faster finality and cheaper transaction fees.
  • Interoperable: Comes with efficient native dual chain communication; Optimized for scaling high-performance dApps that require fast and smooth user experience.
  • Distributed with on-chain governance: Proof of Staked Authority brings in decentralization and community participants. As the native token, BNB will serve as both the gas of smart contract execution and tokens for staking.

More details in White Paper.

Functionalities

Embedded a custom storage key tracer that returns storage keys looked up during contract function execution and is executed by pointing RPC calls to the debug namespace. For example, fetching the storage key for reserve values for an LP.

Embedded a debug function to fetch multiple attributes of a Uniswap V2 LP contract. "debug_fetchSloadValues" can be easily called via RPC.

Embedded a go-EVM interpreter component that returns what the storage keys and values were whenever the EVM interpreter encounters a SLOAD operation. This is achieved by cloning the Run() function and inserting a "SLOAD" detector in core/vm/interpreter.go. The run() and Call() functions in core/vm/evm.go are also cloned, and the CustomSloadCall function calls customsloadrun() within the usual Call() function to call RunWithSloadResults(). The key and value maps can then be returned. To ensure that the key and value maps are returned via available RPC calls (e.g., eth_call()), TransitionDb() and ApplyMessage() in core/state_transition.go must also be cloned.

Ability to subscribe to a list of Uniswap V2 LP clones and their latest attributes (reserves, balance, fees, etc.) extracted from new and old headers.

Ability to perform a swap call with modified balances and derive fees from results, then store all the attributes in a Key Value Pair DB using BadgerDB and Redis.

Ability to parse incoming blocks, fetch all attributes of all LPs active in the block (Token0, Token1, Reserve0, Reserve1, Token0 Balance, Token1 Balance, and LP fees), and store them in a local DB.

Replicate the functionality of the native call tracer that tracks all the external calls made during the execution of a transaction (e.g., if a contract calls another contract during the execution of the transaction (proxy contract)).

License

The bsc library (i.e. all code outside of the cmd directory) is licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file.

The bsc binaries (i.e. all code inside of the cmd directory) is licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.