Claimable collections

Let holders of one of your collections claim from another. How the proof works, what the cap really counts, and when the setting takes effect.

You can tie two of your collections together: owning a piece from one of them gives the right to claim from the other. It is how you reward the people who were already there, without asking them to pay twice.

How the relation works

One of your already published collections is the proof. The collection you are creating now is the target: whoever holds a piece from the proof can claim from it.

The direction only goes that way — an existing collection unlocks a new one, never the reverse. That is what makes it a reward rather than a promise.

And this is what your holders end up seeing on the piece that proves it — the gift, with how many claims they have left:

The claim button on the proof piece. Real button, inert here.

You configure it while creating the collection

The setting lives in step 1 of the wizard, in the same form as everything else, saved by the same button. There is no separate save.

It has to be there because this is the only moment when it makes sense: the target collection does not have a drop yet. Your choice is kept pending and applied when the collection is approved — you do not have to come back afterwards to set it up.

Turning it on is explicit

The switch starts off unless the collection already had a configuration. Saving step 1 with it off also clears any previous setting rather than leaving it alone.

This is deliberate, and it protects you from something invisible: a dropdown always has something selected. Without an explicit switch, saving step 1 with no intention of setting anything up would have quietly enabled a claim using whichever collection happened to be first in the list.

What you need

An active subscription, checked on the server when the configuration is saved. If you do not have one you still see the controls and what they do — disabled, with the reason — because you cannot want a feature nobody explained to you.

Claiming is not gated. Whoever holds a proof piece can claim, subscription or not. The requirement is on you configuring it, not on them using it.

The cap counts per collection, not per campaign

You set a maximum number of claimable pieces. That maximum is that collection's own: if you later link a second target collection to the same proof, one filling up does not block the other.

Set it to zero for no cap — then the only limit is the supply you uploaded.

One proof piece can claim from several collections

A holder who used their piece to claim from one of your target collections can still claim from a different one. What is blocked is using the same piece twice on the same collection.

So a proof piece is a standing membership across the campaign, not a single-use ticket. Plan supply with that in mind.