Closed sea-snake closed 7 months ago
After the last ICRC-27 meeting there was some feedback:
In this PR I've tried to update the ICRC-27 to address above points.
Regarding interactivity, I've opted for a required method argument over having separate methods for the following reasons:
Edit regarding interactivity, I've opted to make the get accounts method always interactive (prompt user to select accounts) as discussed in https://github.com/dfinity/wg-identity-authentication/issues/131.
After the last ICRC-27 meeting there was some feedback:
In this PR I've tried to update the ICRC-27 to address above points.
Regarding interactivity, I've opted for a required method argument over having separate methods for the following reasons:With two methods, you would need to ask permission for bothWith two methods, you would need to unnecessarily implement the same method signature twiceSome signers might not support interactive account selection, this is more clear with a single methodFor the relying party the single method would behave same as long the signer supports the non interactive argument as requiredEdit regarding interactivity, I've opted to make the get accounts method always interactive (prompt user to select accounts) as discussed in https://github.com/dfinity/wg-identity-authentication/issues/131.