So the question is...

When making a gate that simply says "Anyone holding the token can access it", how do you set up the minimum and maximum numbers?

The answer, actually, is in the statement above.

Simply put, when anyone holding a token can access it, there is only a minimum, and no maximum.

And by looking at how Paragraph has this set up, we learned that that is indeed true.

They only have an option for "Minimum".

And when we think about it, this makes sense.

Because usually, the value of an entity falls on "how much of it" one has.

Or in other words, "What's the minimum one should have to be considered valuable".

Value is never portrayed by "Everyone who owns this number or less..."

But rather value is portrayed by saying "Everyone who owns more than this amount"

Because between the lines, it says "Anyone who doesn't own this amount isn't valuable enough to..."

The context is we were looking for one solution to answer both these questions:

• How do you let someone token gate something depending on how much a user has

• But also, how do you token gate something, no matter how much anyone has

In other words, how do you make a user interface that looks pretty, but also accomplishes both those goals?

And as it turns out, instead of worrying about check boxes, or drop downs, or multiple text entry fields, or a few of those combined, you simply need one:

Minimum.

Do you want everyone to have access as long as they hold the token?

• Put in a minimum of 1, or fractions of 1

Do you want only people with a certain amount to have access?

• Put the minimum at the amount necessary for access