|
1 | | -# ZeppelinOS vouching |
| 1 | +# ZeppelinOS vouching _(zos-vouching)_ |
| 2 | + |
| 3 | +[](https://github.com/RichardLitt/standard-readme) |
2 | 4 | [](https://travis-ci.org/zeppelinos/zos-vouching) |
3 | 5 |
|
4 | | -This package contains the ZEP token contract and the vouching logic for the on-chain dependency system. It is not meant for direct use, please see the [CLI](https://github.com/zeppelinos/zos-cli) for interacting with these contracts. |
| 6 | +> Vouching logic for the EVM packages of the ZeppelinOS smart contract platform |
| 7 | +
|
| 8 | +ZeppelinOS is a platform to develop, deploy and operate smart contract |
| 9 | +projects on Ethereum and every other EVM and eWASM-powered blockchain. |
| 10 | + |
| 11 | +This is the repository for the ZEP Token and the contracts to use it to vouch |
| 12 | +for EVM Packages. |
| 13 | + |
| 14 | +## Background |
| 15 | + |
| 16 | +ZeppelinOS provides a mechanism in which an EVM package can be registered and |
| 17 | +vouched for using ZEP tokens. The tokens vouched for an EVM package can be |
| 18 | +challenged by other ZEP holders whenever a deficiency in the EVM package is |
| 19 | +presented for evaluation. In such a situation, the package's vouched tokens |
| 20 | +could be slashed in favor of the challenger. |
| 21 | + |
| 22 | +The end goal is that this simple mechanism will allow ZEP that is vouched for |
| 23 | +an EVM package to represent: |
| 24 | + |
| 25 | +* A measure of the quality of the code of the EVM package. |
| 26 | +* A measure of the support that the EVM package has from the community. |
| 27 | +* A financial buffer for the development of new features in the EVM package. |
| 28 | +* A financial buffer for the auditing of the code of the EVM package. |
| 29 | + |
| 30 | +## Install |
| 31 | + |
| 32 | +First, install [Node.js](http://nodejs.org/) and [npm](https://npmjs.com/). |
| 33 | +Then, install the vouching contracts running: |
| 34 | + |
| 35 | +```sh |
| 36 | +npm install zos-vouching |
| 37 | +``` |
| 38 | + |
| 39 | +## Usage |
| 40 | + |
| 41 | +Currently, the ZeppelinOS vouching mechanism can be used only by calling the |
| 42 | +[Vouching.sol](contracts/Vouching.sol) contract directly. The address of this |
| 43 | +deployed contract can be found in the `zos.<network>.json` files, that have |
| 44 | +just been installed to the `node_modules/zos-vouching/` directory. |
| 45 | + |
| 46 | +For example, open `truffle console --network <network>` and run: |
| 47 | + |
| 48 | +```sh |
| 49 | +truffle(<network>)> vouching = Vouching.at(<vouching-contract-address>) |
| 50 | +``` |
| 51 | + |
| 52 | +Then create a dependency calling: |
| 53 | + |
| 54 | +```sh |
| 55 | +truffle(<network>)> vouching.create(name, owner, dependencyAddress, initialStake) |
| 56 | +``` |
| 57 | + |
| 58 | +Where `name` is a string that will represent the dependency, `owner` is the |
| 59 | +address of the account that will own the dependency, `dependencyAddress` is |
| 60 | +the address of the EVM package and `initialStake` is the amount to be vouched. |
| 61 | + |
| 62 | +After the dependency is created, the owner can vouch or unvouch tokens to the |
| 63 | +EVM package: |
| 64 | + |
| 65 | +```sh |
| 66 | +truffle(<network>)> vouching.vouch(name, amount) |
| 67 | +``` |
| 68 | + |
| 69 | +or: |
| 70 | + |
| 71 | +```sh |
| 72 | +truffle(<network>)> vouching.unvouch(name, amount) |
| 73 | +``` |
| 74 | + |
| 75 | +## Security |
| 76 | + |
| 77 | +If you find a security issue, please contact us at [email protected]. We |
| 78 | +give rewards for reported issues, according to impact and severity. |
| 79 | + |
| 80 | +## Maintainers |
| 81 | + |
| 82 | +* [@facuspagnuolo](https://github.com/facuspagnuolo/) |
| 83 | +* [@fiiiu](https://github.com/fiiiu) |
| 84 | + |
| 85 | +## Contribute |
| 86 | + |
| 87 | +To contribute, join our |
| 88 | +[community channel on Telegram](https://t.me/zeppelinos) where you can talk to |
| 89 | +all the ZeppelinOS developers, contributors, partners and users. |
| 90 | + |
| 91 | +You can also follow the recent developments of the project in our |
| 92 | +[blog](https://blog.zeppelin.solutions/) and |
| 93 | +[Twitter account](https://twitter.com/zeppelinorg). |
| 94 | + |
| 95 | +## License |
| 96 | + |
| 97 | +[MIT](LICENSE.md) © Zeppelin |
0 commit comments