Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update readme #12

Open
wants to merge 10 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .soliumignore
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
node_modules
contracts/Migrations.sol
44 changes: 44 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,3 +9,47 @@
[coveralls-url]: https://coveralls.io/github/parity-contracts/auto-updater?branch=master

Operations contracts for parity's auto-updater.

## Description

The `Operations` contract interface provides a registry of release data for different clients. For
each registered client it is possible to fetch the latest release of a given release track
(e.g. stable, beta, nightly), and for each release there is a registry of binary checksums for each
available platform.

The interface is implemented by the `SimpleOperations` contract which has an owner. The owner of the
`SimpleOperations` contract can set client owners, which can themselves manage their own client
releases using:

- `addRelease(bytes32 _release, uint32 _forkBlock, uint8 _track, uint24 _semver, bool _critical)`
- `addChecksum(bytes32 _release, bytes32 _platform, bytes32 _checksum)`

Additionally, there's an `OperationsProxy` contract that is a specialised multisig proxy wallet for
the `Operations` contract. It splits the client management primitives into a two step process, where
a delegate account can propose releases (or checksums) which must then be approved by a confirmer
account. The delegates and confirmers are defined per track.

### Note

Due to the way data is stored in the `SimpleOperations` contract, the semantics of client removal
are a bit tricky. Whenever a client is removed by the contract owner, only ownership of the client
from the current client owner is removed, the existing release and build data is kept. The getters
in the contract are guarded against this behavior, and check that the client is currently not
removed (i.e. no owner) before accessing the data. **If a removed client is then re-added (with
`setClient`) all of the previous release and build information is available and returned by the
getters.**

## Getting started

This project uses the [Truffle](http://truffleframework.com/) framework. To install the required
dependencies run:

```
yarn install
```

To run the test suite:

```
yarn test
```
Loading