Skip to content
Token and related smart contracts for token economies
Branch: develop
Clone or download
schemar Merge pull request #140 from jasonklein/banks/gh139/npm-packaging
Provide certain contracts ABIs and BINs via NPM package
Latest commit 3cbfc0a Mar 5, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
dist Repo: add scripts and files for packaging as npm module; update license Mar 5, 2019
test Tests: specify 'use strict' in each JS file Feb 4, 2019
tools Repo: add scripts and files for packaging as npm module; update license Mar 5, 2019
.gitignore Repo: add scripts and files for packaging as npm module; update license Mar 5, 2019
.soliumrc.json Style: lint BrandedToken and related contracts and tests. Jan 8, 2019
.travis.yml Repo: stet link to forthcoming 0.10.0 release in comments in change log Feb 12, 2019 Repo: setup basic components. Oct 8, 2018
LICENSE Repo: expand definition of GC in readme Feb 5, 2019 Repo: update English Sentence style guidance Feb 1, 2019

Branded Tokens - Tokenizing Mainstream Applications


A Branded Token allows a mainstream application to create a value-backed token designed specifically for its application's context. A Branded Token implements the required and optional EIP-20 Standard Token interface.

Holders of branded tokens must be able to redeem the value that backs those branded tokens. Branded tokens are only usable within the application context. The application can maintain a policy on accepting new holders.

A Utility Branded Token, which also implements the EIP-20 Standard Token interface, is the utility token representation of the Branded Token on a sidechain. This representation is orchestrated via a gateway, comprising a Gateway contract on the same chain as the Branded Token, and a CoGateway contract on the sidechain with the Utility Branded Token.

A composer is a contract that can be used to optimize the transactions required to perform an action. A Gateway Composer, a type of composer, facilitate's staking value for branded tokens and minting a utility representation of those branded tokens with a Utility Branded Token through a gateway for use within the given application, thereby reducing both the number of transactions to execute and the number of contracts to call in order to stake and mint.

The complete Branded Token specification is in a draft proposal and subject to change. For more information on the specification, please consult OIP-0001 in the OpenST Improvement Proposals repository.

Related Projects

Significant related projects are:

  • brandedtoken.js: a library for interacting with BrandedToken and GatewayComposer contracts.
  • mosaic-contracts: a set of meta-blockchains on top of Ethereum to scale (D)Apps
  • mosaic.js: a web3 interface to scale (D)Apps on Ethereum
  • openst-contracts: a framework for building token economies
  • openst.js: a library for deploying and interacting with a token economy


There are multiple ways to contribute to this project. However, before contributing, please first review the Code of Conduct.

To participate in the discussion on technical matters, please join the project's Discourse forum channel or review the project's issues.

To contribute code, please ensure that your submissions adhere to the Style Guide; please also be aware, this project is under active development and we have not yet established firm contribution guidelines or acceptance criteria.


OpenST blockchain infrastructure empowers new economies for mainstream businesses and emerging (D)Apps. The smart contracts in this repository are intended for use with the OpenST Protocol, a framework for tokenizing businesses.

For more information on the OpenST Protocol, please consult the Whitepaper.

While this software is available as-is for anyone to use, we caution that this is in early stage and under heavy ongoing development and improvement. Please report bugs and suggested improvements.

You can’t perform that action at this time.