[had external security assessment]
Branded Token 0.10 lets an application build their Branded Token for their application. Branded Token (BT) is an ERC20 contract on Ethereum mainnet that allows minting more tokens when more underlying value tokens are staked. These value tokens can be OST or e.g. a stable coin. Furthermore the Branded Token is built to be compatible with layer-2 scaling solutions so that the BT’s usage can scale to millions of users within the application.
All holders of the Branded Token can always fully redeem for the underlying value tokens. On Ethereum mainnet the Branded Token is restricted by default, in order to minimize the storage cost on Ethereum mainnet. Branded Token is part of the OpenST Protocol, as such it natively supports scaling onto Mosaic side chains where it is represented by a UtilityBrandToken (UBT) contract.
Notable changes:
- A Branded Token is an ERC20 that is fully-backed by a freely-tradable value token, OST or other, e.g. a stable coin.
- Branded Tokens are restricted by default on Ethereum mainnet, to ensure a minimal storage footprint
- Branded Tokens are compatible with scaling to millions of end-users on Mosaic side chains, where a Utility Branded Token contract represents the token
- Utility Branded Tokens are internal to allow the mainstream application to map all UBT holders to users inside their application
- Stake requests to mint more Branded Token must be accepted by the application
- Any holder of Branded Token (or Utility Branded Token on the side chain) can always redeem for the underlying value tokens that fully back the Branded Token
- To optimise the UX a user can combine the actions of requesting to mint more Branded Tokens and move those Branded Tokens into a side chain, into two transactions using a GatewayComposer contract she owns.
For a more detailed overview of the changes see the changelog