Sixty seconds in a row is a minute. That is arithmetic, and it is also the smallest way to own something here that feels bigger than a single number. If you claim seconds 3,600 through 3,659, you are holding the full 01:00:00 to 01:00:59, the whole first minute of the second hour. A block. A run.
I want to think about what that actually is, because it is easy to talk yourself into believing a run is more than it is, and also easy to miss the part that genuinely does feel different.
The chain sees sixty tokens. Not a minute. Not a block. Sixty separate ERC-721 rows that happen to carry consecutive second numbers, each with its own owner field and its own editable URL. There is no object in the contract called "a minute," no wrapper that binds 3,600 through 3,659 into a single thing. If you sold thirty of them tomorrow, the other thirty would not notice. The run only exists as a run because you are looking at the numbers and seeing an order in them.
You can claim them together in one transaction, which is what mintBatch is for: hand it the list of sixty seconds and their sixty URLs, sign once, and they land as a group. But that is a convenience of the claiming, not a property of the tokens afterward. The morning after, they are sixty ordinary seconds that share a neighborhood.
Because memory does not store in scatter. When you think about a moment, you think about its edges too: the second before the thing happened, the second after. A run gives you those edges. One second is a pin. A minute is a window you can stand inside.
There is a plainer version of this that has nothing to do with sentiment. A run is legible. "I have 03:00:00 through 03:00:59" is a sentence anyone can hold in their head. "I have seconds 10,801 and 44,209 and 61,540 and 288" is just a list, and a list resists being a set. The human mind rounds a contiguous block up into a single idea and rounds a scatter down into noise. That rounding is doing real work on how the thing feels to own, even though the tokens are identical either way.
So the difference is not onchain. It is in the framing, and framing is not nothing. A collection has always been partly a story the collector tells about a pile of objects. The objects sit there being objects; the set is the sentence you wrap around them.
A scatter has its own logic, and I do not want to sell it short. If you claimed the top of every hour, 00:00:00, 01:00:00, 02:00:00, all the way up, you would hold twenty-four seconds that are nowhere near each other and yet form a tighter concept than a random minute ever could. The through-line is not adjacency, it is rule. Every second that ends a workday. Every second a specific song hits its chorus. The scatter is a set because you can state the rule that generates it.
The run's rule is the simplest possible one: next. That is its charm and its limit. It is instantly readable and it says almost nothing. A rule-based scatter is harder to read and can mean much more. Neither is better; they are answers to different questions. A run asks "what surrounded this moment?" A scatter asks "what do these moments have in common?"
None of this makes a run worth more, and I would be doing the opposite of my job if I implied it did. Sixty adjacent seconds cost the same as sixty scattered ones, sixty times the single price, and a block is not a discount on the concept or a promise that anyone else will ever care about the same window you do. Scarcity by adjacency is not a real form of scarcity; there are exactly as many possible minutes as there are minutes in a day, and any of them can be assembled by anyone willing to claim the slots.
A set here is a private matter. The chain will confirm you own sixty specific tokens. It will not confirm they are a minute, because it does not have that concept. Whether they add up to something is a decision you make and keep, and it holds exactly as long as you keep telling it.
This is not financial advice and a second is not an investment, alone or in a run. The usual caveats do not soften just because you are buying more of them at once: a real fee on Base, transactions that cannot be undone, keys that cannot be recovered if lost, and phishing pages that imitate the real contract. A batch multiplies every one of those by however many seconds are in your list, so read the run twice before you sign it once.
→ Claiming several seconds in one transaction · Rarity by construction · Whose midnight is second 0?
0 to 86399 (0 = 00:00:00, 86399 = 23:59:59); the page converts a second number to an HH:MM:SS label, so a run of sixty consecutive seconds is one clock minute. Contract ABI declares mintBatch(uint256[] _seconds, string[] _urls, address _referrer) payable for claiming a list of seconds in a single transaction, alongside single mint; each second is a distinct ERC-721 with its own editable URL.