EDC Interface

IPFS Setup

In order to pin content to the IPFS you must include your Pinata API credentials in the form of environment parameters:

1. Create a file in root directory called ".env"
2. Add your Pinata key as a variable (the JWT key):

   PINATA_KEY="<JWT key>"
   

3. Optionally: Add your own smart contract addresses as env variables
   • ASSET_ADDRESS
   • POLICY_ADDRESS
   • CONTRACT_ADDRESS
   • TRANSFER_ADDRESS
   • AGREEMENT_ADDRESS

Run the Tezos Client

First, make sure all dependencies are installed:

npm install

Run the server locally:

npm run serve

Swagger Documentation

The documentation can be viewed on http://localhost:3000/docs when server runs.

Contract Information

Metadata of FA2 contracts is generated with the support of @taqueria/plugin-metadata feature to comply with TZIP-16 standard.

Following smart contracts were originated and can be used for minting by default:

• FA2 Asset Contract: KT1N3iJne4jFnQz4tdHBz5q7Cd8Wmd6XtZSH
• FA2 Policy Contract: KT1J7FvNLo2yQSUm7jcm2wzNHDBhR19Y5dJ9
• FA2 Contract Contract : KT1QDheV2TkL3mitzYNKzunWYhSe6MmEPTh5
• EDC Transfer Logging Contract : KT18pEHAbmtGj9iYQAJNhN2CtzjBGf4zBxKX
• EDC Agreement Contract : KT19Jk6zvWfFjWMVSozPNm7VDMKSDVGrU6XD
• EDC Agreement Logging Contract: KT1CHo3f2eWcnT7zCYs1KD1ERVXwEPYacj3A

Tezos Account

Feel free to use the current tezos account included in ./.taq/config.json for testing.

You can easily create your own account and change it in the config file.

When originating new contracts, make sure to update the new addresses in ./contractConfig.js.

Contract Origination

Compile Asset Contract:

npm run compileAssetContract

Deploy Asset Contract:

npm run deployAssetContract

Alternatively:

~/smartpy-cli/SmartPy.sh originate-contract --code ./artifacts/contractContract/step_000_cont_0_contract.tz --storage ./artifacts/contractContract/step_000_cont_0_storage.tz --rpc https://rpc.ghostnet.teztnets.com/