NoBey/openzeppelin-contracts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
5b5d91c9d46e436818ca3ef8fbfa9394fc6a33c6
openzeppelin-contracts/contracts/token/ERC777
History
Nicolás Venturo 97894a140d Adhere to naming convention (#2150) 
* Upgrade to latest solhint rc

* Add private-vars-leading-underscore linter rule

* Add leading underscore to GSNRecipient constants

* Remove leading underscore from ERC165Checker functions

* Add leading underscore to multiple private constants

* Fix linter errors in mocks

* Add leading underscore to ERC777's ERC1820 registry

* Add changelog entry
2020-03-27 13:49:08 -03:00
..
ERC777.sol
Adhere to naming convention (#2150)
2020-03-27 13:49:08 -03:00
IERC777.sol
Fix operatorBurn description typo. (#2091)
2020-02-17 16:31:26 -03:00
IERC777Recipient.sol
Migrate Contracts to Solidity v0.6 (#2080)
2020-02-14 11:12:32 -03:00
IERC777Sender.sol
Migrate Contracts to Solidity v0.6 (#2080)
2020-02-14 11:12:32 -03:00
README.adoc
migrate content to format for new docs site
2019-07-17 17:16:47 -03:00

README.adoc 

= ERC 777
This set of interfaces and contracts are all related to the [ERC777 token standard](https://eips.ethereum.org/EIPS/eip-777).

TIP: For an overview of ERC777 tokens and a walkthrough on how to create a token contract read our xref:ROOT:tokens.adoc#ERC777[ERC777 guide].

The token behavior itself is implemented in the core contracts: {IERC777}, {ERC777}.

Additionally there are interfaces used to develop contracts that react to token movements: {IERC777Sender}, {IERC777Recipient}.

== Core

{{IERC777}}

{{ERC777}}

== Hooks

{{IERC777Sender}}

{{IERC777Recipient}}