💻Creating Contract using UI
Guardian instance out of the box contains implementations for ‘Wiping’ and ‘Retirement’ contracts which can be deployed/enabled from the UI.
Each SR has its own contract permissions. Since contracts are deployed on Hedera and their methods can be called independently via 3rd party systems but the status of these contracts can change without Guardian’s knowledge. SRs can action a ‘refresh’ of their permissions by clicking on the refresh sign (chargeable Hedera operation, costs < 1 hbar)
Contract Roles:
1. Wiping Contract Roles:
2. Retirement Contract Roles:
4) At the token creation the system can be configured to delegate all permissions for wiping tokens to a specific wiping contract
5) SRs can add pools with tokens which have a wipe contract (Set pool operation in retire contract).
Also you can check “without approval” to set retirement tokens as immediate operation (without approval).\
6) SRs can check/delete/refresh pools (Pools operation in retirement contract). Not enabled means that the retirement contract has no wiper permissions in the appropriate wipe contract. It will be changed to enabled automatically when the SR approves a request for a wiper role from this retirement contract. If the wipe contract is not in Guardian a manual refresh is required to update the instance permissions status.
7) SRs can check/approve/reject/ban requests for the wiper role in the wipe contract (Requests operation in wipe contract).
8) To execute the retirement Guardian users which hold USER role navigate to the ‘Retire’ tab and click on ‘Retire’ button, choose appropriate pool and set token count/serials
9) If a token retirement requires approval, users which hold USER role can see their requests by clicking on the ‘Requests’ button.
10) Contract owners can also see these requests and approve or reject (Requests operation on retirement contract).
11) After approval or rejection of the requests users which hold USER role can see retire VCs on ‘Retire’ tab
Last updated
