You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/_Docs_GetStarted.md
+18-13Lines changed: 18 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ It is possible to use `npm` instead of `yarn`, but you'll need to adapt any inst
30
30
31
31
In order to compile the colonyNetwork smart contracts, you will need to have Docker installed and running. We recommend using Docker Community Version `2.0.0.0`. You can find instructions for installing Docker here: [Docker Installation](https://docs.docker.com/install/).
32
32
33
-
The colonyNetwork smart contracts require the `ethereum/solc:0.5.6` Docker image, so we will need to pull it down before we can begin.
33
+
The colonyNetwork smart contracts require the `ethereum/solc:0.5.8` Docker image, so we will need to pull it down before we can begin.
34
34
35
35
Make sure Docker is installed and then run the following command.
36
36
@@ -94,12 +94,14 @@ Rather than import the entire set of contracts into remix, use the included `sol
94
94
$ yarn flatten:contracts
95
95
```
96
96
97
-
Alternatively, you can put them into the directory of your choice, e.g. `~/Downloads/`:
Navigate to `colonyNetwork/build/flattened/` to find the contracts you need to import to Remix.
98
+
99
+
In Remix, you'll need to instantiate `flatIColonyNetwork.sol` to the `ColonyNetwork` address `0x79073fc2117dD054FCEdaCad1E7018C9CbE3ec0B` in order to create a new colony.
100
+
101
+
Use the address of your existing ERC20 token contract to `createColony()`, then immidiately use `getColonyCount()` to get your colony's ID.
102
+
103
+
Call `getColony()` to get your colony's address from the ID, then instantiate `flatIColony.sol` to your colony's address in Remix.
101
104
102
-
Import the flattened contract into the remix IDE, and then call `createColony()`
To deploy all contracts and run all tests, run the following command.
146
-
147
+
To deploy all contracts and run all contract tests:
148
+
```
149
+
yarn test:contracts
150
+
```
151
+
To deploy all contracts and run all reputation mining tests:
147
152
```
148
-
yarn run test:contracts
153
+
yarn test:reputation
149
154
```
150
155
151
156
For more detailed instructions, and additional steps required to set up an environment for use with [colonyJS](https://github.com/JoinColony/colonyJS), check out the colonyJS [Local Setup](/colonyjs/intro-local-setup/) documentation.
Copy file name to clipboardExpand all lines: docs/_Docs_ReputationMining.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ section: Docs
4
4
order: 6
5
5
---
6
6
7
-
The reputation mining client is usable for testing but it has limited functionality. Still, it is possible to run a single miner instance for usable reputation scores on a local test network.
Copy file name to clipboardExpand all lines: docs/_bug_rules.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ Once submitted, the issue will be responded to, verified, accepted, and rewarded
44
44
### Submission Branches
45
45
Participants in the program are free to submit bugs on two different branches in the colonyNetwork codebase:
46
46
* the current testnet release (tagged on the `develop` branch) and deployed to Görli
47
-
* against the `master` branch where we merge ongoing work
47
+
* against the `master` branch which will be tagged as the mainnet release for deployment
48
48
49
49
### Bug Severity and Bounties
50
50
In the same manner as the [Ethereum Bug Bounty Program](https://bounty.ethereum.org/), submissions will be evaluated by the Colony team according to the [OWASP risk rating methodology](https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology), which grades based on both _Impact_ and _Likelihood_.
0 commit comments