-
Notifications
You must be signed in to change notification settings - Fork 94
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
[Frontend] Adding option for "about" & icon/image when deploying memecoins #216
Comments
Would love to give this a go myself but may take some time |
@Jet-Gill-Lee I feel this is going to be a bigger task and probably we should divide and conquer. We need to smartly plan out whether these info (socials, images) should be saved in our db or smart contract (I won't recommend this). We'll also have to provide edit functionality so, a separate effort on UI might be requireds as well (though we will try to reuse as much as possible) |
up for any help needed in contribution! |
@Jet-Gill-Lee Hello, i would love to work on this, please could you assign it to me? |
@Jet-Gill-Lee Hello good day My name is Ugo and I would love to contribute to this effort, as it is something that piques my interest, please can I be assigned this task to immediately tackle it? |
|
Haven't had the time I expected to work on this - reach out to devs/admin if you wish to be assigned |
Hi i would love to work on this |
Please how do i go about this? |
Hi @Jet-Gill-Lee , @0xChqrles & @ugur-eren , please can I be assigned this issue? |
@od-hunter This issue would take too much resources and planning to develop, it would require to edit the contracts to store the informations, edit the frontend for setting and updating the informations. For this reason this issue is not going to be implemented yet. |
Noted ser!🫡 I’m open to other issues please. |
Description
Create the ability for memecoin deployers to add an about section, image and socials when deploying their coin, and then have this show up when viewing tokens on /token[addr] and /tokens[addr]
Requirements
Notes
Imagine this would be implemented as optional rather than forcing users to include them when deploying.
Users might also want to update this at a later date via /tokens or /manage once implemented.
Devs have stated desire for this functionality to be on-chain
The text was updated successfully, but these errors were encountered: