You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the first ledger will always be used when writing an object to the ledger. It would be nice to select the ledger to use when writing objects to the ledger
This could be as simple as passing the pool id to the method, however a better approach would probably be to pass the did to use. This will remove the need for the publicDid property that we currently use (because you always pass it), and we could just require the dids to be did indy formatted dids so we can extract the ledger to write to from it. #965 adds the indyNamespace property to the pool configs. We could then match that against the namespace form the provided did and use that ledger.
E.g. agent.ledger.registerSchema() could take a publisherDid property of value did:indy:sovrin:xxx so we know it needs to be registered on mainnet. The advantage of this approach is that it will also work when we add support for other ledgers with anoncreds. You just pass e.g. did:cheqd:mainnet and we would write it to cheqd mainnet instead
The text was updated successfully, but these errors were encountered:
Currently the first ledger will always be used when writing an object to the ledger. It would be nice to select the ledger to use when writing objects to the ledger
This could be as simple as passing the pool id to the method, however a better approach would probably be to pass the did to use. This will remove the need for the publicDid property that we currently use (because you always pass it), and we could just require the dids to be did indy formatted dids so we can extract the ledger to write to from it. #965 adds the indyNamespace property to the pool configs. We could then match that against the namespace form the provided did and use that ledger.
E.g.
agent.ledger.registerSchema()
could take apublisherDid
property of valuedid:indy:sovrin:xxx
so we know it needs to be registered on mainnet. The advantage of this approach is that it will also work when we add support for other ledgers with anoncreds. You just pass e.g.did:cheqd:mainnet
and we would write it to cheqd mainnet insteadThe text was updated successfully, but these errors were encountered: