Chris Mckay
0d3dab84ad
|
5 years ago | |
---|---|---|
contracts | 5 years ago | |
migrations | 5 years ago | |
nginx/conf.d | 5 years ago | |
public | 5 years ago | |
src | 5 years ago | |
test | 5 years ago | |
.dockerignore | 5 years ago | |
.editorconfig | 5 years ago | |
.gitignore | 5 years ago | |
.prettierignore | 5 years ago | |
.solcover.js | 5 years ago | |
.soliumignore | 6 years ago | |
.soliumrc.json | 6 years ago | |
.yarnrc | 5 years ago | |
CLA.md | 6 years ago | |
CODE-OF-CONDUCT.md | 6 years ago | |
CONTRIBUTING.md | 6 years ago | |
Dockerfile | 5 years ago | |
GOVERNANCE.md | 6 years ago | |
Jenkinsfile | 5 years ago | |
Jenkinsfile.release | 5 years ago | |
LICENSE | 6 years ago | |
README.md | 5 years ago | |
genesis.json | 5 years ago | |
jest.config.js | 5 years ago | |
mocha-reporter-config.json | 6 years ago | |
package.json | 5 years ago | |
truffle-box.json | 6 years ago | |
truffle-config.js | 5 years ago | |
tsconfig.json | 5 years ago | |
yarn.lock | 5 years ago |
README.md
Permissioning Smart Contracts
Note: The contracts in this repository are currently in the process of going through a third party audit. Please contact us before using in a production environment.
Using
The Pantheon documentation describes how to use the contracts for onchain permissioning.
Development
Linting
Linting is set up using solium. To run it over your code execute yarn run lint
.
Testing
yarn test
Permissioning Management Dapp (under development)
The Permissisioning Management Dapp is still in BETA. It is under active development and shouldn't be used in any production system.
The Dapp will facilitate managing permissioning rules and maintaining the list of admin accounts that can edit rules.
At the moment, these instructions won't say anything about linking the Dapp with your Pantheon node. This integration will be documented in the future. The instructions here are targeted to developers working on the Dapp development, not users.
This is the easiest way to get started for development with the permissioning Dapp:
Compile and migrate the contracts
- Get rid of your environment variables named
NODE_INGRESS_CONTRACT_ADDRESS
andACCOUNT_INGRESS_CONTRACT_ADDRESS
- you might need to restart your terminal session after removing it to have your changes applied. If you are using a.env
file, you can comment out the variables. - Start a terminal session and start a truffle Ganache node running
truffle develop
. This will start a Ganache node and create a truffle console session. - In the truffle console, run all migrations from scratch with
migrate --reset
. Keep this terminal session open to maintain your Ganache node running.
Start the development server
- Run
yarn install
to install all required dependencies. (You only need to runyarn install
if you are running the app for the first time.) - Run
yarn run build
to build the dapp. - Run
yarn run start
to start the web server that is serving our dapp. - In your browser, connect Metamask to the Ganache network (the default endpoint is
http://127.0.0.1:9545/
) - When you start Ganache, it gives you a list of accounts and private keys. Import the first one in Metamask to impersonate the first admin of the system.
- Navigate to
http://localhost:3000
to access the Permissioning Dapp. - All changes made to the smart contracts or to the dapp code are automatically refreshed on the website. There is no need to restart the web server after making changes.
Build the permissioning Dapp for deployment
- Compile and migrate the contracts
- Run
yarn run build
will assemble index.html and all other files inbuild/
- You can use your preferred web server technology to serve the contents of
build/
as static files. - You will need to set up MetaMask as for the development server