Hypercerts are a tool to build scalable retrospective reward systems for impact. For more details, check out our website.
/contracts
: Smart contracts (Foundry+Hardhat)- Manually deployed via hardhat tasks
- Note: This is not currently on CI/CD
- On Goerli:
- HypercertMinter (UUPS Proxy): 0x822F17A9A5EeCFd66dBAFf7946a8071C265D1d07
- Safe multi-sig: 0x8CD35a62fF56A91485eBF97491612F1552dbc1c9
- On Optimism:
- HypercertMinter (UUPS Proxy): 0x822F17A9A5EeCFd66dBAFf7946a8071C265D1d07
- Safe multi-sig: 0x560adA72a80b4707e493cA8c3B7B7528930E7Be5
/cors-proxy
: CORS proxy for Cloudflare Workers/defender
: OpenZeppelin Defender integration/docs
: documentation (Docusaurus)- on Fleek - Production build on mainnet
- on Cloudflare - Staging build on Goerli
/frontend
: frontend application (Next.js)- on Fleek - Production build on mainnet
- on Cloudflare - Staging build on Goerli
/graph
: The Graph integration/sdk
: Hypercerts SDK- Manually published to npm
/utils
: various scripts for operations- Manually run
First, make sure the environment variables are set for ./frontend
.
Take a look at ./frontend/.env.local.example
for the complete list.
- You can either set these yourself (e.g. in CI/CD)
- or copy the file to
.env.local
and populate it.
Then the do a turbo build of all apps, run the following:
yarn install
yarn build
The resulting static site can be found in ./build/
.
If you've already run the build, you can use yarn serve:build
to serve the built files
To run a dev server that watches for changes across code and Plasmic, run:
yarn dev:frontend
For setup and common operations for each subproject, navigate into the respective directory and check out the README.md
.
We also maintain a playbook for larger operations.