-
Notifications
You must be signed in to change notification settings - Fork 18
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
5G1LVy9K5uapJE9uzG1NbMN4bTKJEyKLMtKGAtqdgbLDegNF #75
Conversation
Hey, the PR appears to be empty. Haven't you forgotten to attach the files? |
Yes
Przemysław Paczoski ***@***.***> schrieb am Di. 13. Aug. 2024
um 13:10:
… Hey, the PR appears to be empty. Haven't you forgotten to attach the files?
—
Reply to this email directly, view it on GitHub
<#75 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKOLPXIG566ME6QVZ3VL46TZRHSRPAVCNFSM6AAAAABMKC6E3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBVHE4DGOJTHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Dont now how to add this 2 things
Lukas Schreiber ***@***.***> schrieb am Di. 13. Aug. 2024
um 14:43:
… Yes
Przemysław Paczoski ***@***.***> schrieb am Di. 13. Aug.
2024 um 13:10:
> Hey, the PR appears to be empty. Haven't you forgotten to attach the
> files?
>
> —
> Reply to this email directly, view it on GitHub
> <#75 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BKOLPXIG566ME6QVZ3VL46TZRHSRPAVCNFSM6AAAAABMKC6E3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBVHE4DGOJTHE>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
where can i find the metadata from my token? i create it on inkwhale |
okay metadata are ready and uploaded |
Pleas check if it is ok |
You're missing the link to the source code. I believe if it's InkWhale, it should be this one:
What's more:
|
Sorry, my bad. Please fill also the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Source code address is slightly wrong, but otherwise LGTM
Co-authored-by: Grzegorz Gawryał <31205678+ggawryal@users.noreply.github.com>
okay, done. please check :) when will the token be verified? Thanks. |
ASCAN Token Submission
Introduction
Before submitting this PR, ensure you have followed all the requirements below and filled out all necessary details about your token.
Checklist
Please review the checklist below and check each item before submitting your token information:
Asset Details
General Information
Logo
logo.png
Metadata File
metadata.json
Token Information File
info.json
Required Content in
info.json
:Note on Custom Tags
The
customTags
field in the info.json file is optional. This field can be used to include specific tags that describe unique characteristics or features of the token, such as burner wallet. Include custom tags only if they are relevant to the token’s functionality or usage.Note on Owner and Minter
The owner and minter fields should include the addresses of the accounts that hold these capabilities within the token's smart contract. The owner is typically the account that has administrative rights over the entire contract, while the minter might be an account with the capability to issue new tokens.
Note on Warnings
Please do not fill out the warnings field in the info.json file. This field is reserved for use by our auditing team, who will add relevant warnings such as "Mintable" or "Burnable" after thoroughly reviewing the token's smart contract. This ensures that all warnings are accurate and based on a comprehensive technical assessment.