-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onewallet - add the option to import a list of predifined tokens, instead of doing it one by one #67
Comments
Another idea is to just whitelist/add these contracts into the One Wallet code for all users since they are legit contracts anyway. Some other wallets like Myetherwallet go even further and implement a logic that: If wallet has funds in any any of the whitelisted contracts, shows the token. The user has still the option to add it manually if he wants. Only worry is that this could be resource consuming. You would have to do this check every time you select the Token tab. |
I like this idea, seems much better. Do we have ENS names on Harmony already? I am not sure we have this yet, but i see it accepts lists via https and IPFS as well, so we could use these if we don´t have ENS. |
I think harmony doesn't have any official HRC20 Token lists yet. So I am not able to show the list like uniswap for now. @yelllowsin @mirrormirage0 @BrunoMarshall What do you think? Correct me if I am wrong |
@Raptor1001
|
The proposal is to add an option to import a list of tokens on the ONEWallet, instead of importing each token separately.
currently the team is developing several DEX ( SWOOP, SeeSwap, Unify,) that will work with several tokens.
The user need to import each one separately.
Proposal is that each platform has a list of tokens, that can be imported.
the format list need to be agreed and shared to everyone
(tokens syntetic names are just for the example):
Import:
USDs 0x5f089d2ea9008dada6f05b8c78f25233fd27f966
BTCs 0xea10a239c4fcaf31225efdb4dc634aeff42c585d
ETHs 0x7334d832bfc79f59df8bc092cba3ae687faed7fa
XRPs 0x33bA9Bf6cF19bCd91E2f745C0ac4c05A192c069F
BCHs 0x4a6B66F5B955cA3FB51c59c272554Ee45bDb2239
BNBs 0xbCf0038d69372773a966166d35Ac35B7B6914D33
DOTs 0x120aEeA98f391cBc7f1DCA79c5eDD8f329856258
LINKs 0x62D8fEacf66E39Ed9179dB4f68581dBBa159457A
ADAs 0xDD697498B26F135C5C331022F17BA368A89489c1
LTCs 0x10580fD9aB6DF1E836708C553165f1002D6ff2F9
EOSs 0xf54f91a34C0280a8F3c11819a5364E4A67181ECe
The text was updated successfully, but these errors were encountered: