Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Discussion for the proposal of Fungible token Standard #7 #9

Closed
KimKyungup opened this issue Feb 21, 2020 · 5 comments
Closed

Discussion for the proposal of Fungible token Standard #7 #9

KimKyungup opened this issue Feb 21, 2020 · 5 comments

Comments

@KimKyungup
Copy link
Contributor

I proposed Fungible token standard in #7 and want to discuss about new token standard here.

@KimKyungup KimKyungup changed the title Discussion for [Proposal] Fungible token Standard #7 Discussion for the proposal of Fungible token Standard #7 Feb 21, 2020
@kjhman21
Copy link
Collaborator

kjhman21 commented Mar 3, 2020

What about applying KIP-13 to this proposal?

If we do that, we can easily recognize the contract is KIP-7 compliant or not via calling of supportsInterface().

So, what I am proposing is to define KIP-7's interface ID here.

@KimKyungup
Copy link
Contributor Author

I think it's good idea. :)

@kjhman21
Copy link
Collaborator

kjhman21 commented Jul 3, 2020

Finalized.

@kjhman21 kjhman21 closed this as completed Jul 3, 2020
@Halejandrostm
Copy link

Hi, i made a transfer to my ETH wallet. I can see right now in the klaytnscope blockchain that the transaction is completed and i'm a holder of these KIP-7 Tokens in the Holders list. but i don't have access to them.

How can I recover these tokens?
thanks for ur help

regards.

@kjhman21
Copy link
Collaborator

kjhman21 commented Mar 8, 2021

@Halejandrostm You can import your private key in the ETH wallet to KLAY wallet. Then you can have access to those tokens in Klaytn. ETH and KLAY has same address scheme. Hope this helps.

By the way, this repository is to propose a new feature or enhancement of Klaytn. The question is not appropriate for this repo. Please file a question to https://forum.klaytn.com/ later. Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants