Skip to content
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
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ The following graphic shows an exemplary DAO setup:

![A potential DAO setup](./images/dao-plugin.svg)

An examplary DAO setup showing interactions between the three core contract pieces triggered by different user groups: The `DAO` and `PermissionManager` contract in blue and red, respectively, as well as two `Plugin` contracts in green. Bear in mind, the `DAO` and `Permission Manager` components both coexist within the same `DAO` contract. Function calls are visualized as black arrows and require permission checks (red, dashed arrow). In this example, the permission manager determines whether the token voting plugin can execute actions on the DAO, a member can change its settings, or if an DeFi-related plugin is allowed to invest in a certain, external contract.
An exemplary DAO setup showing interactions between the three core contract pieces triggered by different user groups: The `DAO` and `PermissionManager` contract in blue and red, respectively, as well as two `Plugin` contracts in green. Bear in mind, the `DAO` and `Permission Manager` components both coexist within the same `DAO` contract. Function calls are visualized as black arrows and require permission checks (red, dashed arrow). In this example, the permission manager determines whether the token voting plugin can execute actions on the DAO, a member can change its settings, or if an DeFi-related plugin is allowed to invest in a certain, external contract.

### Framework Contracts

Expand Down
4 changes: 2 additions & 2 deletions packages/contracts/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Before starting make sure that you have created an `.env` file from the `.env.ex
Now you can get started running your repository locally:

1. Install packages from the root folder with `yarn`
2. Change directory into this package (`/pacakages/contracts`)
2. Change directory into this package (`/packages/contracts`)
3. Run `yarn build` to compile the contracts
4. Run `yarn test` to execute the test suite (this can take a while, so see [performance optimizations](#performance-optimizations) for ways to speed up the tests).

Expand All @@ -38,7 +38,7 @@ When testing locally:

Default values for all required environment variables are provided when running against hardhat, check the [`.env.example`](./.env.example) for details of what these are and what they mean.

The private key provided by default is a hardhat publically known key for `0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266`. Don't use it outside of a local development context.
The private key provided by default is a hardhat publicly known key for `0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266`. Don't use it outside of a local development context.

> Tests can be sped up if needed. See [the test performance optimization](#performance-optimizations) section for more info.

Expand Down
2 changes: 1 addition & 1 deletion packages/contracts/hardhat.config.ts
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ for (const network of Object.keys(hardhatNetworks) as SupportedNetworks[]) {
}

if (networkExtensions[network] == undefined) {
console.log(`WARNING: newtork ${network} is not found in networks.ts file`);
console.log(`WARNING: network ${network} is not found in networks.ts file`);
continue;
}

Expand Down
Loading