Skip to content
Switch branches/tags
This branch is 292 commits ahead, 583 commits behind EOSIO:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


BOSCore Version : v3.0.4

EOSIO Contracts Version: v1.6.0 (part 1.8.1-1.8.3)

The design of the EOSIO blockchain calls for a number of smart contracts that are run at a privileged permission level in order to support functions such as block producer registration and voting, token staking for CPU and network bandwidth, RAM purchasing, multi-sig, etc. These smart contracts are referred to as the system, token, msig and wrap (formerly known as sudo) contracts.

This repository contains examples of these privileged contracts that are useful when deploying, managing, and/or using an EOSIO blockchain. They are provided for reference purposes:

The following unprivileged contract(s) are also part of the system.


The ibc contracts had moved to a independent repository ibc_contracts.


Using CDT Docker:

  • First, setup BOSCore CDT Docker following this.
  • Second, change the volumes in docker-compose.yml file to your path where bos.contracts located.
  • Then call cd /data/bos.contracts && in the CDT Docker instance.

From Scratch:

  • First, ensure that your eosio is compiled to the core symbol for the EOSIO blockchain that intend to deploy to.
  • Second, make sure that you have sudo make installed eosio.
  • Then just run the in the top directory to build all the contracts and the unit tests for these contracts.

After build:

  • The unit tests executable is placed in the build/tests and is named unit_test.
  • The contracts are built into a bin/<contract name> folder in their respective directories.
  • Finally, simply use cleos to set contract by pointing to the previously mentioned directory.


Contributing Guide

Code of Conduct




See LICENSE for copyright and license terms. makes its contribution on a voluntary basis as a member of the EOSIO community and is not responsible for ensuring the overall performance of the software or any related applications. We make no representation, warranty, guarantee or undertaking in respect of the software or any related documentation, whether expressed or implied, including but not limited to the warranties or merchantability, fitness for a particular purpose and noninfringement. In no event shall we be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or documentation or the use or other dealings in the software or documentation. Any test results or performance figures are indicative and will not reflect performance under all conditions. Any reference to any third party or third-party product, service or other resource is not an endorsement or recommendation by We are not responsible, and disclaim any and all responsibility and liability, for your use of or reliance on any of these resources. Third-party resources may be updated, changed or terminated at any time, so the information here may be out of date or inaccurate.


Smart contracts that provide some of the basic functions of the BOSCore blockchain




No packages published