Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 36 million developers.Sign up
The first release of Colony is called
glider - after the smallest of the spaceships from Conway's Game of life.
glider implements the following features of the Colony Protocol as described in the Colony Whitepaper, and it will be continuously upgraded to implement new functionality.
Reputation, including the submission of reputation root hashes and dispute resolution amongst submitted hashes.
Bring your own token supports any colony to use an ERC20 token as a means of accounting for reputation.
Domains allow for the management of multiple token funding pots, with specialized reputation score according to domain and skill.
Modular Permissions allow for granular control over ability to interact with a colony at the domain level.
Payments and Tasks perform the secure transfer of funds (and reputation) as compensation for work done for the colony.
Rewards distribute periodically a set amount of revenue to all colony contributors, proportional to their contributions to the colony.
Importantly, there are some aspects of
glider that, in their current implementation, require some amount of "trust" in the sense that they are not under fully decentralized/distributed control.
The Meta Colony is permissioned and controlled by the core contributors to the colonyNetwork repo, as are contract upgrades and maintenance
CLNY is currently locked for transfer beyond a whitelisted set of addresses
Domains are restricted to single-level within the root domain (nested domains are currently prohibited).
Tasks are partially in a "trusty" state, insofar as there is no dispute resolution system implemented at this time to handle work disputes. While Payments can be seen as trustful Tasks.
glider is deployed to
Preserve ownership of
joincolony.eth ENS root node to allow us to set other subdomains. The
colony.joincolony.eth subdomains however remain under the control of the Network as their owner in ENS.
Introduce the ability for the Network to be initialised with a
Colony version different to 1.
Upgrades contracts to
solidity 0.5.8 #616
Reputation mining client functionality which allows a client started with
--auto option to automatically:
- submit at the earliest possible time up to as many submissions as it is entitled to (depending on their staked CLNY tokens and up to a max of 12) in a mining cycle
- respond to disputes
- confirm the last remaining hash after the mining window closes
- visualisations of reputation update log and reputation state
Extract a set of convenience functions useful when working with the contracts via the
truffle console #617
Event name changes for Colony domain role updates where the role specific events:
ColonyAdministrationRoleSet have been replaced by a generic
Additionally we now emit
RecoveryRoleSet event when the
Recovery role is assigned or unassigned.
Documentation updates. API docs are now auto generated from the interface contracts
natspec comments. #622
The existing Görli testnet deployment is upgraded to this version. Latest
Colony contract version is
2. Addresses for the Network and Extension contracts remain unchanged:
ColonyNetwork: 0x79073fc2117dD054FCEdaCad1E7018C9CbE3ec0B OneTxPaymentFactory: 0x3e03f868450ffD588E2cB2034fA2e0F74F9FFbe3 OldRolesFactory:` 0xbe86Bef84fFD76E906e1ffa368a42B538e7aEf75
The current colonyNetwork release is
glider, which implements some, but not all, of the Colony Protocol:
- The Reputation system
- Meta Colony and the CLNY Token
- Colony funding and rewards
- Single-level domains
- Payments and Tasks
- Work ratings
- Roles and domain-level permissions
- Contract upgradability and recovery
- ENS integration
glider-rc.1 is deployed to the Görli testnet, and can be accessed at:
The extension factories are at: