Co-authors: Raphael Roullet, Nicola Greco, Chris Chung

Original ERC thread: https://github.com/ethereum/EIPs/issues/1238

<aside> 💡 This documentation might be outdated. When in doubt, the submitted EIP is the most up-to-date source of truth.

</aside>

Table of Contents

Requirements

ERC1238 (Core)

Extensions

FAQ

Simple Summary

A badge is a token that cannot be transferred once assigned. Badges can be accumulated through time and put at stake. Simply speaking, badges are statements about a public key: they can be quantitative (e.g. reputation, experience) or qualitative (badges, titles).

Abstract

The Non-Transferable Token standard defines a set of standard APIs allowing the identification of statements (called badges or “NTTs”) attributed to a public key, such that different dapps and smart contract can use to filter users or to provide user with different badges different experiences. More importantly, this standard defines a way for which users can put their badges at stake. Badges cannot be transferred but can be lost (after staking) or can expire.

Motivation

The idea is to have tokens that once assigned cannot be transferred (like reputation) and that can be used by websites, or contracts to make users perform some actions. For example, if a user accumulates paper submissions at conferences, then they can use their paper badges to request grants. It's important that they can never share these badges.

This is the equivalent of a variety of other use cases

• Accumulating badges: degrees from academic institutions, paper publications for conferences, badges that allow for access in a building or in a special chat.
• Experience points: points accumulated in a game, points accumulated by being honest in a decentralized system for some time or a DAO.