Issuing Documents

[SP-INDT-OpenCert]

Hi,

I was looking at this site that allow issuing documents via https://www.openattestation.com/docs/ethereum-section/issue-document

Few questions on the above link:

1. Is this preferred way to go or still use the Metamask/Hardware Token approach?
2. Is this fully automated without human interraction? or the wallet password still require someone to enter to complete the publishing/issuing cert?
3. Read about the wallet password is generated upon creation of that wallet. Is it applicable to us? We already have the wallet and was generated back then via the web app. We deployed our cert store way back in 2020 and already issued certs for it.

[HJunyuan]

Hi @SP-INDT-OpenCert,

1. You can continue to use Metamask or the hardware wallet approach. The example mentioned in the article is mostly for demonstration purposes where the user generates a virtual wallet and has access to the private key (which is less secure).
2. Issuance can be entirely done programmatically. You may utilise the OpenAttestation library.
3. You can continue using the same wallet you previously generated. Whether you want to rotate (generate a new wallet) is entirely at your discretion.

[SP-INDT-OpenCert]

Thanks, speaking of generating new wallet.. based on the very old meeting from GovTech all the way from the initial implementation before, they stressed out there should be 1 cert store addr for each institutions. So generating a new wallet institutions can have multiple cert store address now?