Existing e2e use cases that do not use AuthNext should not fail once new auth next interface changes in cli or rpc.
No coverage on AuthNext features of contract invocations.
What would you like to see?
existing system tests with no auth next still pass with latest auth next in cli and rpc
New Feature Test case:
As a Dapp Developer I configure secure auth next signatures for two identities and my contract function invocation from cli tool is able to verify those identities at function invocation time.
What problem does your feature solve?
What would you like to see?
What alternatives are there?