📤Submitting Abilities

It's important to make high quality submissions. This step-by-step guide to submitting will help.

Link

This should be a URL that takes the user directly to the page where they can do the ability. Oftentimes, this will be a website with a "Connect Wallet" button, where the user can mint an NFT, for example. For Discord/Telegram access, this link should be an invite link, as the user might not have joined the Discord or Telegram channel yet. If the ability is a contract interaction and there is no better web app link, this should be an Etherscan link to the contract's Write or Write As Proxy page – you'll be able to add an explanation of how to interact with the contract later.

If you get a warning that “we automatically detect abilities” from your link, it’s likely that your ability has already been submitted by a Supplier, though it may still be under review. If you submit it, the ability will most likely be rejected as a duplicate.

If you’ve typed in the link, but you can’t continue, be sure you’ve added “https://” to the front of the link.

Is this action completed on-chain?

This box is used to state whether the ability involves an Ethereum contract interaction, such as minting an NFT or claiming tokens. This information is used to find whether a user has already completed the ability, so that the ability can be automatically marked as completed for these users. For most abilities, you'll set this to No, but if the ability involves spending gas, it's Yes! If you're not sure which contract function corresponds to the ability, that's ok! Moderators will help track it down.

Ability type

Select the ability type that best matches your ability – the descriptions should be self-explanatory. If none of these seem to fit, don't be afraid to select Other.

Title

Give the ability a short title under 80 characters that tells the user exactly what the ability is. Try starting the title with a verb, like "Mint", "Access", or "Claim".

Description (Optional)

This is optional, but helpful if the title doesn't completely describe the ability. Write a short, 1-3 sentence description for the ability. Put the most important / most interesting details first. Focus on what's appealing about the ability. If possible, answer these questions:

• What are people getting?

• Why would they want it, and what can they do with it?

• How is this offering unique to community members?

• What do I have to do to get it?

• What is the urgency?

Also, if completing the ability could be confusing, you can add instructions right in the description.

Image (Optional)

Also optional. Add an image related to the ability, not just to the community or the related service. For example, if an ability is access to a Discord channel, it's better not to have an image than to use the Discord logo or the community's logo. On the other hand, if the ability is a mint, you should add an image showing what the minted NFT looks like. The image should be a JPG or PNG under 3 MB in size.

Open Date and Close Date (Optional)

Enter in the times when the ability becomes available, and stops being available. Be sure to set the correct time zone. If the ability is already available, you can leave the Open Date blank, and if there is no end date, leave the Close Date blank. Lastly, if there are dates but not times, you can just enter in dates and leave the time boxes blank.

Requirements

Here we add the token or allowlist requirements for the ability. This is the token a wallet needs to hold or the allowlist that the address needs to be on to do the ability.

Token Requirements

It's not unusual for an ability to have more than one token as a requirement. For example, a mint might allowlist a few different NFT communities. To handle this, you can add multiple token addresses with "Any requirement" logic. If the ability already exists for other tokens, and you want to add more token requirements, don't create a new ability! Instead, post in the #scouts channel and a mod will update the existing ability for you.

For now, the only requirements logic available for multiple requirements is “OR”. Soon, the submit form will also have “ALL” logic, where many different tokens are all required to do an ability. For example, a community might have various "seasons", each on different contracts, with some abilities only open to holders from various seasons. Here, you can use "And" logic. One exception is when an ability requires both a "base" NFT and a "consumable" NFT, where the ability involves burning the consumable. In this case, list only the base NFT as a requirement, so holders can see that they can do the ability by getting the consumable.

Lastly, sometimes an ability only applies to certain token IDs. For example, an ERC1155 NFT contract might have three different IDs representing different membership tiers, and an ability only applies to the highest tier. In these cases, you can use the "Hold specific NFT ID" requirement type. If an ability applies to more than one ID, you can submit the IDs separated by commas.

Allowlists

Unlike token requirements, abilities with allowlists typically only have a single allowlist. Sometimes, the allowlist is public, however, it usually isn't in a txt or csv file with one address per line, which you need to submit. In those cases, you'll need to download the allowlist and reformat it before uploading. Also, duplicate addresses will cause an error when uploading, so if you encounter an error, try checking for duplicates.

Unfortunately, allowlists often aren't public. In those cases, you may need to reach out to someone providing the ability to get access to the allowlist. Be sure to mention that you're scouting for Daylight and that you won't be posting the allowlist publically, as Daylight will only alert people on the allowlist. That way, they'll be more likely to share the allowlist with you. Of course, please respect their wishes if they choose not to share their allowlist.

In some cases, a token holder snapshot is used as an allowlist, and yet the project continues to add addresses to the allowlist on request from token holders who missed the snapshot. In those cases, it's clear that the intended audience is the token holders. In these cases, it's best to submit the ability as a token requirement, and to add who the holder can contact to get on the allowlist to the description.

Preview

Congrats, you've added all the necessary info for submitting an ability! The last step is to make sure the ability looks good before you submit. This is a good opportunity to check your spelling and make sure you added the right image. If everything looks good, submit!