---
# System prepended metadata

title: 'Hi, Buidlers'

---

# Hi, Buidlers

## What is ERCRef

ERC is short for Ethereum Request for Comment. ERC refers to a series of standard documents regulates the application interfaces of EVM-based smart contracts.

For example, notable ERCs include ERC20, ERC721 and ERC1155 Token standards. Also ENS are based on a few ERCs (ERC162, ERC181) etc. MetaMask and other wallets usually implement ERC712, and ERC191 for signings.

## When to use ERCRef


## When not to use ERCRef

## Why ERCRef

The ERC efforts advances the open interoperability and composability.
However, authoring ERC standards usually involves driving adoptions and getting feedback from early adotpions. Adopters also wait for ERC standards to finalize before large adotpions.

To solve the chicken-and-egg problem between adoptions vs standardizations, we propose #ERCRef. The Project ERCRef allows
ERC authors and anyone to contribute reference implementations for
any ERCs.

We hope to create a bleeding edge library of smart contracts that applies the cutting edge ERC proposals and be readily usable by smart contract developers and dApp developers.

## Philosophy behind ERCRef
- Community Effort
- 
## How To
### Extenting Contracts
### Access Control
### Tokens

## FAQ
### Data Privacy
### Copyright
### Feedback

# Using ERCRef
## Getting Started
## Debugging

# Glossary
### Tokens
Tokens can represent virtually anything in Ethereum:

reputation points in an online platform
skills of a character in a game
lottery tickets
financial assets like a share in a company
a fiat currency like USD
an ounce of gold
and more...
#### ERC20 (Token Standard)
A standard interface for tokens. The following standard allows for the implementation of a standard API for tokens within smart contracts. This standard provides basic functionality to transfer tokens, as well as allow tokens to be approved so they can be spent by another on-chain third party.

The ERC-20 introduces a standard for Fungible Tokens, in other words, they have a property that makes each Token be exactly the same (in type and value) as another Token. For example, an ERC-20 Token acts just like the ETH, meaning that 1 Token is and will always be equal to all the other Tokens.

#### EIP721(Non-Fungible Token Standard)
A standard interface for non-fungible tokens, also known as deeds.

The following standard allows for the implementation of a standard API for NFTs within smart contracts. This standard provides basic functionality to track and transfer NFTs.

This standard is inspired by the ERC-20 token standard and builds on two years of experience since EIP-20 was created. EIP-20 is insufficient for tracking NFTs because each asset is distinct (non-fungible) whereas each of a quantity of tokens is identical (fungible).

#### EIP777
This EIP defines standard interfaces and behaviors for token contracts.


#### EIP1155
A standard interface for contracts that manage multiple token types. A single deployed contract may include any combination of fungible tokens, non-fungible tokens or other configurations (e.g. semi-fungible tokens).

New functionality is possible with this design such as transferring multiple token types at once, saving on transaction costs. Trading (escrow / atomic swaps) of multiple tokens can be built on top of this standard and it removes the need to “approve” individual token contracts separately. It is also easy to describe and mix multiple fungible or non-fungible token types in a single contract.


Reference 
- https://ethereum.org/en/developers/docs
- https://eips.ethereum.org

# Community 
## Contact Us
## How everyone is using ERCRef

# Service Protocol

# About Us
## Special Thanks
## About
### Why ERCRef as a name
