1. reset all CLR calculations by heading over to Grant CLR and by clicking Reset all CLR calculations for all rounds

1. Run this on the shell to set all the data in GrantCLRCalculation Table to active

clr_pks = [133,134,135,136,137,138,139] # TODO UPDATE 


# GET CLR
from grants.models import ( Grant, GrantCLR, GrantCLRCalculation)
all_calculations = GrantCLRCalculation.objects.all()
for clr_pk in clr_pks:
    # GET CLR
    clr_round = GrantCLR.objects.get(pk=clr_pk)
    # GET GRANTS
    grant_filters = clr_round.grant_filters
    grants = Grant.objects.filter(**grant_filters)
		
		# RUN THIS TO ENSURE GRANTS IGNORED AREN'T CONSIDERED
		grants = grants.filter(network='mainnet', hidden=False, active=True, is_clr_eligible=True, link_to_new_grant=None)

    clr_calculations = all_calculations.filter(grantclr=clr_pk)
    for grant in grants:
        cal = clr_calculations.filter(grant=grant.pk).order_by('-created_on').first()
        if cal and not cal.latest:
            cal.latest = True
            cal.save()

1. Update the grants CLR prediction curve by running

./manage.py estimate_clr mainnet <CLR-ID-1> slim true && 
./manage.py estimate_clr mainnet <CLR-ID-2> slim true

# A - RUNNING IT ASYNC
./manage.py estimate_clr mainnet <CLR-ID-1> final false &&
./manage.py estimate_clr mainnet <CLR-ID-2> final false

# B - RUNNING IT AS SYNC (RECOMMENDED)
screen  # create a new screen
./manage.py estimate_clr mainnet <CLR-ID-1> final true && 
./manage.py estimate_clr mainnet <CLR-ID-2> final true

• grantclrcalculation (check if latest flag in records set to true)

• grant (check random grants to ensure the clr prediction curve is populated)

• Ensure the .env is populated with the right variable

• Before deploying the contract update these with your address (update wherever there is a todo)
deploy.ts
inputs-mainnet.js
inputs-rinkeby.js

# ---- RINKEBY ----
## DEPLOY
yarn deploy:rinkeby
## VERIFY
yarn hardhat verify --constructor-args inputs-rinkeby.js --network rinkeby <RINKEBY_CONTRACT_ADDRESS>

# ---- MAINNET ----
## DEPLOY
yarn deploy:mainnet 
## VERIFY
yarn hardhat verify --constructor-args inputs-mainnet.js --network mainnet <MAINNET_CONTRACT_ADDRESS>

• https://rinkeby.etherscan.io/address/0x8B7E04872f4e3F12e6CEb7F25BF8C74813ad3e38#readContract

• https://rinkeby.etherscan.io/address/0x8B7E04872f4e3F12e6CEb7F25BF8C74813ad3e38#writeContract

• Updating the settings.py with mainnet contract address and round number.

• Updating the email copy.

• Updating the date to which user can claim payout

• finalize → populates the CLRMatch with the payouts which needs to happen

• prepare_final_payout → sets it ready to ready state

# finalize
./manage.py payout_round_noncustodial finalize mainnet --clr_pks=CLR-ID-1,CLR-ID-1 þgm<roundNumber>
# continue? (y/n) -> enter y

# prepare_final_payout
./manage.py payout_round_noncustodial prepare_final_payout mainnet --clr_pks=CLR-ID-1,CLR-ID-1 --clr_round=<roundNumber>
# continue? (y/n) -> enter y

• consume the data we added in STEP5 from CLR Match table

• generates chunks of that data (this is cause the distribution are too large to be uploaded in one go / block )

• and prints the chunks onto console. (Check attached file)

• waits for you to manually invoke the setPayouts and upload the chunks (1 transaction per chunk). CHECK VIDEO HERE

# set_payouts

./manage.py payout_round_noncustodial set_payouts mainnet --clr_pks=CLR-ID-1,CLR-ID-1 --clr_round=<roundNumber>
# continue? (y/n) -> enter y
# THIS IS A REAL PAYOUT FOR mainnet DAI.
# ARE YOU DOUBLE SECRET SUPER SURE? (y/n)? (y/n) -> enter y

# chunks get generated. Copy this and save it locally
# Head over to your contract -> click write contract tab -> and paste the chunk in
# Refer the video above

• Save the txnId of the final chunk you uploaded as you will need that in the FINAL STEP

• Wait until all transactions have completed before proceeding to the next step.

• Grab a grants admin address from CLR Match table

• Head over to contract's read tab

• Select payout and query with the address

• Compare to ensure the value we have in our DB is the same matching amount as what is on chain.

# verify
./manage.py payout_round_noncustodial verify mainnet --clr_pks=CLR-ID-1,CLR-ID-1 --clr_round=<roundNumber>

# this will error out with the following message as contract does not have funds

#* * * * * * * * * * * * * * * * * * * * * * * *
# Contract DAI balance is insufficient
#  Required balance:  651249.414275245880061539
#  Current balance:   0
#  Extra DAI needed:  651249.414275245880061539 Contract needs another 651249.414275245880061539 DAI
#* * * * * * * * * * * * * * * * * * * * * * * * *

• Head over to contract's write tab

• Select Finalize and sign the transaction NOTE:

• where the contract was deployed

• how much funds needs to be transferred to it

# verify
./manage.py payout_round_noncustodial verify mainnet --clr_pks=CLR-ID-1,CLR-ID-1 --clr_round=<roundNumber>

# If sufficent funds are present -> you'd see the below message on the console
# Contract balance of {dai_balance} DAI is exactly equal to the required amount

• Head over to contract's write tab

• Select enablePayouts and sign the transaction

• contributions are created and saved in DB based on CLRMatch

• emails are sent out to the grant owners

• activity are created

• Uploaded the distribution (make sure you have the final chunks txn ID) (step 6)

• Contract has been finalized (step 8)

• Funds have been transferred into the contract (step 9)

• Verify that the contract has enough funds to payout (step 10)

• Payouts have been enabled (step 11)

# notify_users
./manage.py payout_round_noncustodial notify_users mainnet --clr_pks=CLR-ID-1,CLR-ID-1 --clr_round=<roundNumber>

# enter a txn id -> Enter the last txn id after uploading the chunk in step 6

• Do ensure you drop this on the channel and update the progress so that folks are aware.

• Keep track of all the transactions / contract addresses

• Having the chunks in a file makes it easier as opposed to copy pasting it from the console for each chunk