Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add multi-ledger support #39

Open
KimEbert42 opened this issue Dec 18, 2023 · 1 comment
Open

Add multi-ledger support #39

KimEbert42 opened this issue Dec 18, 2023 · 1 comment

Comments

@KimEbert42
Copy link
Contributor

Add multi-ledger support to aries-akrida

@KimEbert42
Copy link
Contributor Author

There are a few outstanding issues with adding multi-ledger support to aries-akrida.

The first, is that aries-akrida currently only supports a single issuer and a single verifier. I could see value in being able to add additional issuers and verifiers in a test. The biggest question is how to manage the configuration of each of the issuer and verifiers? It is possible that we move the configuration of the issuers and verifiers into Locust instead of using environment variables? The question is does this exist as a locust config file, or does each test specify its own definition of the agents?

The second issue, is that if aries-akrida uses a single issuer to use multi-ledger support is that the issuer cannot use two ledgers at once for writing. This means that when attempting to use write to two separate ledgers using the same Aca-Py agent, the agent can only write to ledger A, or ledger B at the same time. When the Locust test X and Locust test Y are at different stages of testing, Locust X and Locust Y may be attempting to write to different ledgers at the same time. This would likely cause one of the writes to fail. I don't recommend configuring a single Aca-Py agent to write to two ledgers at the same time, so we would need to use more than one issuer agent.

Next steps:

  1. Add support for more than one issuer agent.
  2. Add support for more than one ledger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant