How to move unsupported assets?

bytesun · December 27, 2023, 8:51pm

As I understand, if users send an asset(NFT/token) to a dApp(e.g. DSCVR), and the dApp doesn’t integrate with the asset(e.g. transfer), then the asset will be stuck in the dApp forever, right?

The is no any issue on other blockchains, no matter what kind of assets, users always can move it with wallet.

Is there a solution to address this issue?

What I am thinking is to export identity as PEM from dApp, then use dfx to call the asset canister, is it possible?

bytesun · January 3, 2024, 5:44pm

works on

github.com

dfinity/wg-identity-authentication/blob/main/topics/signer_standards_overview.md

# IC Signer Standards: Overview

This document gives an overview over the ICRC standards related to signer interactions and transaction approval flows.
It explains the motivation behind the standards and how they relate to each other.

The following ICRC standards are relevant in this context:
* The [Internet Computer Interface Specification](https://internetcomputer.org/docs/current/references/ic-interface-spec/), specifically the [HTTPs interface](https://internetcomputer.org/docs/current/references/ic-interface-spec/#http-interface)
* [ICRC-21](https://github.com/dfinity/wg-identity-authentication/blob/main/topics/icrc_21_consent_msg.md): Canister Call Consent Messages
* [ICRC-25](https://github.com/dfinity/wg-identity-authentication/blob/main/topics/icrc_25_signer_interaction_standard.md): Signer Interaction Standard
* ICRC-27: ICRC-25 Extension for ICRC-1 ledger subaccounts
* [ICRC-29](https://github.com/dfinity/wg-identity-authentication/blob/main/topics/icrc_29_window_post_message_transport.md): PostMessage Transport Standard for ICRC-25
* [ICRC-31](https://github.com/dfinity/wg-identity-authentication/blob/main/topics/icrc_31_get_principals.md): Get Principals (ICRC-25 Extension)
* [ICRC-32](https://github.com/dfinity/wg-identity-authentication/blob/main/topics/icrc_32_sign_challenge.md): Sign Challenge (ICRC-25 Extension)
* [ICRC-33](https://github.com/dfinity/wg-identity-authentication/blob/main/topics/icrc_33_call_canister.md): Call Canister (ICRC-25 Extension)

The following diagram presents the interactions between the different components (see [terminology](#terminology)) and shows which standards cover the respective parts of the interactions:

![Visalization showing which part of the interactions between relying party, signer and target canister are covered by which standard.](../diagrams/signer_standards_overview.svg "Signer Standards Overview")

## Terminology

This file has been truncated. show original

Topic		Replies	Views
ICRC-1 Token Standard Ledger Developers	128	6298	September 22, 2022
ckBTC Approve, Allowance and Transfer - ICRC1 to ICRC2 Developers ckBTC	2	295	December 12, 2023
Call for Feedback: IC Wallet Standards General Discussing	12	891	September 4, 2023
Has anyone created an ICRC cycle token? Developers	10	621	July 28, 2023
Proposal to add security for IC wallet users Developers	5	745	August 2, 2023

How to move unsupported assets?

Related Topics