✅Verifying Abilities

Once you find a potential ability, you'll want to make a few checks before submitting it. Abilities should be:

• New

• Relevant

• Actionable

• For allowlists, sourced

• For token-gates, on Ethereum and not trait-based

If an ability can pass all of these checks, it’ll have a high chance of being accepted. Let’s go through each of these checks in detail:

New

Potential abilities should not be duplicates of abilities already in Daylight's database. The easiest way to check if an ability already exists is to visit:

• https://www.daylight.xyz/community/[Community’s Contract Address] for a community that would qualify for a token-gated ability.

• https://www.daylight.xyz/preview/[User's Wallet Address]/abilities for a wallet address that would qualify for an allowlist-gated ability.

Also, don't submit abilities covered by one of Daylight's suppliers – if a supplier ability doesn't show up, it's likely still in moderation.

Relevant

The ability should only apply to holders of a token or to addresses on an allowlist that target a specific community or communities. Targeting >10 large communities or >100k addresses is considered spammy. Also, the ability itself should be something that a reasonable user would find interesting, otherwise, it could be considered spam. A relevant ability will make you feel:

• Belonging, like when you join a token-gated Discord channel of other like-minded individuals,

• Pride, like when you mint an on-chain credential showing how OG you are in a specific community,

• Hope, like when you submit your vote for a proposal that could propel your community forward,

• Excitement, like when you claim an airdrop worth thousands of dollars, or

• Comfort, like when you renew your ENS or revoke access for an old contract

On the other hand, bad abilities are boring or spammy. Some examples:

• A raffle to enter a prize, but the prize is so small it’s not worth entering (say, $250 per 10k potential entrants). This ability is boring.

• A derivative mint of a blue-chip NFT, but holders only get a small discount from the public sale price. This ability is a cash-grab, and most users won’t find it interesting.

• An unofficial token-gated merch shop, but the merch uses copyrighted images. This ability promotes illegal activity, which is unacceptable.

Ecommerce Abilities

Ecommerce abilities (abilities that offer non-token goods or services) are more likely to be seen as spam than other abilities, so we have a few rules that will help you determine whether or not an ability belongs on Daylight:

• Free stuff: Abilities that allow you to claim free goods or services are always okay! This includes goods where the user has to pay for shipping and handling only.

• Discounts: An ability that offers a discount is acceptable only if:

  • The discount is at least 10% off the regular price, and

  • The goods/services feature the NFT or community logo/branding

• Regular price: An ability with no discount is acceptable only if:

  • The goods/services are offered by the token's official store, or

  • The goods/services are customized to the holder's specific token

In all cases, if community logos/branding are used, the store has to have the right to use it. That is, it either must be the official store, have an agreement with the community that allows them to use the logo/branding, or the logo/branding must have a permissive license like CC0.

KYC

To complete certain abilities, you may need to provide some personal information, but overly intrusive abilities don't belong on Daylight. Here is the information that an ability is able to require:

• Ecommerce abilities: Wallet address, signed messages to verify ownership, email address, name, shipping address, and payment info as needed to pay for and receive goods

• All other abilities: Wallet address, signed messages to verify ownership, and email address only

While these are clear-cut rules, each ability is unique, so we can't guarantee that an ability that meets these rules will be accepted, but it will have a much better chance of being accepted than an ability that doesn't.

Actionable

The ability should be something people can do with their wallet, and there should be a specific web page where the ability can be done, even if it's just a contract interaction on Etherscan. Also, while some tokens have features that modify the token when it's transferred or sold, if it doesn't benefit the original holder, it shouldn't be submitted as an ability.

For Allowlists, Sourced

If the requirement is an allowlist, it's best to include a link to the allowlist if one is available. This makes it more likely for the ability to be accepted, and helps reduce spam.

For Token-gates, On Ethereum and Not Trait-Based

Currently, Daylight only accepts token-gated abilities for tokens on Ethereum Mainnet. The requirement should either be the whole token contract or specific token IDs, as trait-based ability requirements aren't supported. This means that required tokens should not use a shared contract (OpenSea Shared Storefront, Rarible, etc.), unless you have a list of token IDs that this ability is applicable to - in this case, you can use the “Hold specific NFT ID” requirement type.