From 1f8b502e031c5b8d03a40df13dc0ac8b633fb200 Mon Sep 17 00:00:00 2001 From: Hassan Mohammed <84959188+zx0509080209@users.noreply.github.com> Date: Tue, 3 Dec 2024 17:13:46 +0300 Subject: [PATCH 1/3] Rename README.md to BLu2000 NFT GOLD --- README.md => BLu2000 | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename README.md => BLu2000 (100%) diff --git a/README.md b/BLu2000 similarity index 100% rename from README.md rename to BLu2000 From f05f02375ce5b4d7b349a616564fe258d8f74ace Mon Sep 17 00:00:00 2001 From: Hassan Mohammed <84959188+zx0509080209@users.noreply.github.com> Date: Mon, 9 Dec 2024 22:25:07 +0300 Subject: [PATCH 2/3] Create README.md --- README.md | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 0000000..54bc9c0 --- /dev/null +++ b/README.md @@ -0,0 +1,54 @@ +# OpenSea Drop - Instructions for Media and Metadata files + + + +## Media file instructions + +Supported files include JPG, PNG, SVG, and GIF. The per file size limit is 50 MB. + +All files should have the same extension (e.g. all of them should be .png). + + + +### When there is no metadata file + +Media file naming can be anything you want. The tokenID will be set based on order of submission. + + + +### When there is a metadata file + +The name of the media file should be matched in the column 'file_name' in the metadata file. + + + + + +## Metadata file instructions + + + +On the metadata file, make sure that the tokenIDs are consecutive numbers. So if you have 1000 items, you must have tokenIDs consecutive from 1 to 1000 without missing any numbers. + + + +Mandatory columns are: + +- 'tokenID' -- identification of the item, which is a number between 1 and the number of files you have, consecutively + +- 'name' -- name of your item (max 200 characters) + +- 'file_name' -- name of your media file, including the extension + + + +Optional columns are: + +- 'description' -- description of your item + +- 'external_url' -- URL shown on your item (can be an external URL to provide more information about your item) + +You can add trait columns, which must follow the convention 'attributes[name_of_trait]'. For example, if you wanted eye color to be a trait, you can have a column named 'attributes[eye color]'. + + + From b7d43fbd4edb18262671d3761a065523c60e9688 Mon Sep 17 00:00:00 2001 From: Hassan Mohammed <84959188+zx0509080209@users.noreply.github.com> Date: Mon, 9 Dec 2024 22:28:37 +0300 Subject: [PATCH 3/3] Create DRAWING DRAWING --- DRAWING | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 DRAWING diff --git a/DRAWING b/DRAWING new file mode 100644 index 0000000..5e75788 --- /dev/null +++ b/DRAWING @@ -0,0 +1,54 @@ +# OpenSea Drop - Instructions for Media and Metadata files + + + +## Media file instructions + +Supported files include JPG, PNG, SVG, and GIF. The per file size limit is 50000000000 MB. + +All files should have the same extension (e.g. all of them should be .png). + + + +### When there is no metadata file + +Media file naming can be anything you want. The tokenID will be set based on order of submission. + + + +### When there is a metadata file + +The name of the media file should be matched in the column 'file_name' in the metadata file. + + + + + +## Metadata file instructions + + + +On the metadata file, make sure that the tokenIDs are consecutive numbers. So if you have 1000 items, you must have tokenIDs consecutive from 1 to 1000 without missing any numbers. + + + +Mandatory columns are: + +- 'tokenID' -- identification of the item, which is a number between 1 and the number of files you have, consecutively + +- 'name' -- name of your item (max 200 characters) + +- 'file_name' -- name of your media file, including the extension + + + +Optional columns are: + +- 'description' -- description of your item + +- 'external_url' -- URL shown on your item (can be an external URL to provide more information about your item) + +You can add trait columns, which must follow the convention 'attributes[name_of_trait]'. For example, if you wanted eye color to be a trait, you can have a column named 'attributes[eye color]'. + + +