Skip to content
Smart contracts that provide some of the basic functions of the Telos blockchain
Branch: master
Clone or download
Pull request Compare This branch is 319 commits ahead, 334 commits behind EOSIO:master.
marlonwilliams Merge pull request #44 from Telos-Foundation/whitelistupdate
Updated whitelist feature to support per-account create limits
Latest commit 07b7401 Feb 8, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
eosio.amend proper operator Dec 22, 2018
eosio.arbitration removed arbitration setconfig assertion for max_elected_arbs being le… Dec 17, 2018
eosio.bios pull all of native.hpp in Nov 26, 2018
eosio.saving proper operator Dec 22, 2018
eosio.system New ricardians for telos.tfvt,, eosio.amend, and TFVT voti… Dec 11, 2018
eosio.token Initial testing modules for eosio.trail contract Nov 20, 2018
eosio.trail merge eosio.trail.cpp, from the patch branch Dec 17, 2018
eosio.wrap rename sudo to wrap in README (and yes I know the binary action data … Oct 10, 2018
telos.tfvt added assertion that pervents members from being nominated or adding … Dec 16, 2018
token.registry changed hpp include for token.registry Dec 14, 2018
.gitignore added wasm, wast, and abi to gitignore Nov 25, 2018
CMakeLists.txt update CMake Dec 13, 2018
LICENSE add license file Jul 12, 2018 bump version to 1.5.1 Nov 27, 2018
UnitTestsExternalProject.txt passthrough LLVM_DIR to unit tests external project Nov 27, 2018 Merge branch 'get-resource-limits-fix' into metric3 Aug 1, 2018


Version : 1.5.1

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.


To build the contracts and the unit tests:

  • 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.
You can’t perform that action at this time.