Currently, BC Wallet needs to be deployed every time a new use case using the mobile verifier requires a different proof request. This is not scaleable.
As a developer, I want to update the proof request templates without having to deploy the wallet so that use cases are not delayed until a release is available
NOT IN SCOPE
As a verifier, I want to be able to create my own templates so that I don't need to rely on a different team/organizations to create my templates and I have more control.
Acceptance Criteria
proof request templates can be updated and accessed in BC Wallet without having to release a new version
Description of feature / user story
Currently, BC Wallet needs to be deployed every time a new use case using the mobile verifier requires a different proof request. This is not scaleable.
As a developer, I want to update the proof request templates without having to deploy the wallet so that use cases are not delayed until a release is available
NOT IN SCOPE As a verifier, I want to be able to create my own templates so that I don't need to rely on a different team/organizations to create my templates and I have more control.
Acceptance Criteria
Wireframes or relevant image assets / links