Skip to content

skalenetwork/fair-manager

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

FAIR Manager

A smart contract system that orchestrates and operates the FAIR chain. For more details of each smart contract, check SPEC.md

Install & Compile

  1. Clone the repository
  2. Run yarn install && yarn compile

Deployment

FAIR Manager is started from a fair-boot instance. We recommend using the default parameters if you are simply testing deployment of FAIR Manager.

Create a .env file in the project root directory with the following data:

MAINNET_ENDPOINT="https://your.endpoint.to.eth.mainnet.com"
TARGET="production"
CHAIN_NAME="affectionate-immediate-pollux"

If you are testing locally, this is enough and you can run: yarn hardhat run migrations/deploy.ts

Instead of the previous steps, you can simply run bash scripts/test_deploy.sh. You can change the MAINNET_ENDPOINT value to whichever you prefer inside the script.

If you want to deploy to another network other than the Hardhat local network, set the extra variables in the .env file:

PRIVATE_KEY="{your private key}"
ENDPOINT="https://endpoint.to.destination.network.com"

Then run yarn hardhat run migrations/deploy.ts --network custom

Test

You can run tests locally without any extra setup. Simply run: yarn test

Verification

Contract verification allows you to verify deployed smart contracts on block explorers using Hardhat's verification plugin via command line interface.

Required Environment Variables

ENDPOINT="https://endpoint.to.destination.network"
CHAIN_ID="your_chain_id"
EXPLORER_URL="https://your.explorer.url.com"

Usage

yarn hardhat verify --network custom <ContractAddress>

License

License

Copyright (C) 2025-present SKALE Labs

About

A smart contract system that orchestrates and operates chain

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •