I’m glad you’ve been using the Blockcerts tools! I’m sorry for the delayed response.
To add yourself as an issuer, the wallet is expecting an issuer profile (URL). This schema of the content it expects at that URL is defined here: https://github.com/blockchain-certificates/cert-schema/blob/master/docs/issuer_schema-2.md
And here is an example of a sample testnet issuer profile: https://www.blockcerts.org/samples/2.0/issuer-testnet.json
Note that if you are already successfully verifying Blockcerts, then, you would have had to generate this issuer profile already (since that’s looked up during verification).
But first I should back up and provide more context:
The issuer adding process is used to “introduce” a recipient to an issuer. The full flow looks like this:
It’s assumed that the issuer already has a way of identifying recipients, e.g. their email address. In this case, the issuer would email the recipient letting them know to add the issuer in their Blockcerts wallet. At this time, the issuer can (optionally) provide a nonce that the recipient would use during this introduction. (This is equivalent to a one-time link for resetting a password).
During the introduction phase, the recipient’s wallet is sending the next public Bitcoin address in the wallet’s key chain, so if you are using wallets for this purpose, note that you’d need to host that endpoint. If provided, that endpoint would be specified in the issuer profile field
introductionURL (also in the issuer profile schema).
This “collecting addresses” functionality is not part of the supported open-source because the desired implementation choices vary wildly across issuers, but you can experiment with this via a sample docker service. It is not part of the standard installation, but these configuration options are described in the cert-viewer README
So the effort increases if you actually want to be an issuer and allow recipients to introduce themselves to you through the wallet, because you have to actually host a service to collect the recipient addresses. But the expected interface is pretty simple, and defined in the issuer profile schema above.
Let us know if you have any questions!