feat(signer): support ledgers that do not implement ICRC-21 #4082
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We were requested to generate a consent message similar to the one used by the ledger for cases where the ICRC-21 implementation is missing. This if the targeted methods is either
icrc1_transfer
,icrc2_approve
, oricrc2_transfer_from
.Notes
The ICRC-49 standard specifies that a user should be warned when a consent message is interpreted on the frontend side instead of being retrieved through a canister.
See https://github.com/dfinity/wg-identity-authentication/blob/main/topics/icrc_49_call_canister.md#message-processing
Changes
@dfinity/[email protected]
which implements the requirement (see release notes v0.1.0 and v0.1.1)Tests
I did not test with OISY.
Screenshot