Issued, listed, or made?

A scarce digital object is easy to mistake for another scarce digital object. A numbered token from a fixed mint and an account from a registrar both look scarce. A made object can look like both of those. It is not in that category.

Someone gave you the first two. Nobody gave you the third.

Look at anything that lets you in somewhere. A passport, a ticket, a key card, the account you use to read your email. Every one of them was given to you by someone, and that someone is still out there, maintaining a list, and able to take you off it.

Being let in, and someone else letting you in, have become the same idea. The reliable way to make something hard to get has usually been to put a person in charge of handing it out. Scarcity by permission. It works. It also charges rent: the office has to keep existing, stay honest, still be there in ten years, and still be willing. Because everything downstream depends on it, it is the first place anyone hostile will go.

Permission is not the only way a thing becomes hard to get. A tree ring is scarce. You cannot have a hundred in a year, and nobody issues them. The hollow worn into a stone step is scarce the same way. These are limited by what it took to produce them rather than by anyone controlling supply. Nobody hands them out. Nobody can take them back.

So the question is whether something digital could be scarce like that. Copies are free, so the cost has to sit inside the thing. How that cost is put there is How do you make a digital thing scarce? The when is How do you prove when the work happened?

What comes out is a record that was expensive to produce, checkable by anyone, and more expensive the more of them you want. No office issued it. No office can revoke it. There is nothing to shut down. A gate creates an arms race between passer and stopper. Cost creates no gate to get past. Producing the thing and arriving with it are the same act.

Whether to accept the object, once it can be hard to obtain on its own, is Why can saying no be cheap when saying yes cannot?

Two faces of the same office

Digital scarcity usually arrives in one of two costumes.

Allocated. A cap exists. A fixed mint, a finite collection, a namespace with so many slots. Someone wrote the number. Someone creates the units. The scarce step is the rule that said how many.

Admitted. You approach a registrar. Policy, puzzles, waitlists, a photograph of a document. After listing, the object itself is cheap. The scarce step is getting on the list.

They feel like opposites. One sells you a numbered unit. One lists you. Both are given. In both cases an office creates the controllable thing, and that office - or whoever can change its rule - can refuse the next one, or take this one back.

A made object has no such office. There is no cap to run out of. There is no list to join. The scarce step is producing this one, and the next one starts at zero.

That is why a hard-capped token is the usual mix-up. It is a scarce digital object. It is still issued.

A shared rule is still a rule

Open networks have limited things without a single doorman. That does not move the limit out of policy. A network that agrees a rule and applies it on many machines still decides who counts by that rule. Membership is something the network agrees on. Spreading enforcement does not take the criteria out.

Bitcoin, used as money, is this kind of limit: a supply rule, applied jointly, for as long as participants keep that rule. Control sits with whoever can keep or change the rule.

Bitcoin, used here as a clock, is a different use of the same network. What that clock is, is How do you prove when the work happened? It does not issue the object, allocate a slot, or decide that a producer deserved one.

A post box is not a mint. It is not a registrar.

Every other common limit also leaves control somewhere you can point to: the participants who keep a rule, the allocator of a cap, a door that must stay staffed, a party that can take a stake, a scorekeeper, a federation that must stay willing. Making has a dependency of its own. The work has to reach a public tick while it is underway. That tick cannot judge the object, allocate scarcity, or reach back and remove a mark once it is in the sequence. Whatever was needed during making is finished being needed when the making is done.

Afterwards the making can be confirmed from the file. Can you check a stranger without asking anyone? is that check.

What making does not do

Making will not tell you which of two histories is real. It cannot slash. It does not prove a person. It does not cap a population. It does not stop a funded adversary.

It answers one question: could there be very many of these, cheaply. The claim is never that you cannot make many. It is that many costs many times what one costs. Whether that constrains a particular adversary is a fact about their budget.

Flooding is possible when arriving costs nothing. A gate tries to stop the wrong arrivals. Making prices the arrivals. Those are different jobs.

Ordinary hardware is deliberate. A system only the wealthy can enter has reinvented the office. Why that still bites when someone wants many at once is What kind of cost refuses to divide?