This section explains how to deploy and operate custom smart contracts on EBSI using the Trusted Contracts Registry (TCR) and the CLI.
General Description
Custom smart contracts can be deployed on EBSI through the Trusted Contracts Registry, which contains templates of audited and trusted contracts. Only contracts listed in this registry can be deployed. Additionally, the deployer requires an authorisation in the Trusted Policies Registry (TPR).
The process involves multiple roles and steps:
- Support Office & Development Team: Register new contract templates
- Entity: Deploy proxies of approved templates and issue invocation authorisations
- User: Interact with the contract using an access token and VC-based authorisation
Follow the guides in order.
1. Register a new template
This step is performed by the Support Office and the Development Team of EBSI.
2. Deploy a new proxy
This step is performed by the Entity that wants to manage this use case.
3. Issue VC to invoke
This step is performed by the Entity that manages the use case.
4. Interact with the contract
This step is performed by the User that wants to interact with the contract.