πŸ’»Launching Guardian

Once http://localhost:3000 is launched, we need to first generate Operator ID and Operator Key by clicking on Generate button as shown below:

Note: If OPERATORID and OPERATOR KEY are added in .env file, we can click on Generate button directly without entering the details again in the UI.

Once you generated Operator ID and Operator Key, we can either click on Next or restore the Data, by selecting Restore Data from the Next button dropdown to setup Registry as shown below.

Note: Restore Data can be restored from Hedera if data is available for setting up the Registry.

Limitations on restoring the data: 1. The state of policy workflows is not persisted onto any decentralised storage used by Guardian (such as IPFS and/or Hedera blockchain), and therefore not available for restoring. This means that while all artifacts produced by projects and their respective Policy workflows will be discovered and made accessible through the restored Guardian, the policy execution state will not be restored.

2. Similarly, dynamic filled β€˜options’ from VCs is not available at restoration time. This results in the limitation that some document grids will not be restored.

If Next is clicked, we need to manually setup the Registry or if Restore Data is clicked, it is filled automatically.

Note: The above fields in UI are mandatory only for this default Schema.

The Format of the Standard Registry Hello World Message is as follows:

{
	'type': 'Standard Registry',
	'status':'ISSUE'
	'id': '35c5d340-1a93-475d-9659-818bb77d45df',
	'did': 'did:hedera:testnet:vzN41A2bMhvYGhg7oCMoo5UAzQ6PCTq4VTQaNPE1uPG;hedera:testnet:tid=0.0.3423402',
	'action': 'Init',
	'topicId': '0.0.34234020',
	'lang': 'en-US',
    'attributes' : {
    	'ISIC': '051 062',
    	'geography' : 'USA CAN EU AUS',
    	'law': 'USA',
    	'tags': 'VERRA iREC'
  }
}

Where the list of attributes is extendable, and all attributes in it are optional.

Standard Registry Message Parameters

INITIALIZATION_TOPIC_ID for different Hedera Networks

RETIRE_CONTRACT_FILE_ID and WIPE_CONTRACT_FILE_ID for different Hedera Networks

How to Deploy Contracts on Mainnet using your own account:

Note: If you wish you have an option to deploy your own instances (from an account that your organization controls - e.g. an β€˜official’ account of your organization). We have created scripts for easy deployment you can use. In this case the following procedure needs to be followed:

  1. Navigate to ./guardian-clifolder.

  2. Execute npm install followed by npm run build and npm i -g

  3. Now the scripts are ready, and you can execute at the level of the guardian-cli folder

  4. RETIRE contract deployment:

guardian-cli deploy-contract-file ../contracts/retire/Retire.sol Retire {account} {key} -n {network}

  1. WIPE contract deployment:

guardian-cli deploy-contract-file ../contracts/wipe/Wipe.sol Wipe {account} {key} -n {network}

Where:

  • account - accound ID in hedera

  • key - its private key

  • network - the target network (testnet, mainnet, previewnet), by default it uses testnet

The contract file identifier will be printed out in the terminal.

Last updated