indy.error.IndyError: ErrorCode.WalletNotFoundError about greenlight HOT 5 CLOSED

The docs are a bit out of date. We're working on a method to ensure that development machines use a unique version number.

In the short term, try changing that to something unique like 0.0.123123. Do the same in proof.py.

from greenlight.

That worked; thanks. It still seems like an odd step to require.

from greenlight.

Indy SDK requires that claim definitions be published by the issuer and thus stored in the issuer's wallet. If the claim definition exists on the ledger already, the issuer can either skip the publish step or clobber the last person to issue a claim def with that schema version number.

The solution will be to generate a unique version number for every dev machine so that developers don't clobber each other's ledger state while working against the same indy node pool.

We hope to implement a better solution to this in the next few days using some unique information derived from the machine.

from greenlight.

How about referring to the schema by its hash in development mode? Then if the schema is already present on the ledger, it doesn't need to be registered again, and we don't end up with lots of identical clones. If it does change, so will the hash, so they won't clobber each other.

In production, it may still be a good idea to have a version number; I don't think full semver is a good idea, but it might be useful to be more human readable and provide some indication of sequence. That or a date, so that it would have more meaning.

from greenlight.

Agreed on the semver issue. We've since found out that creating a Cred Def creates a keypair and you can't control the seed for it. As a result, you can't regenerate a full wallet from seeds if you have a Cred Def. We're working on a developer approach for that and will be handling that in a separate issue.

from greenlight.