Now picture a postal service that started with postcards. Open mail, every word readable by anyone who handles it, and that is how the mail works. Years later somebody adds an envelope option. Pay a little extra and seal your letter. A few people do.
Something shifts the moment that happens. The envelope stops being ordinary and starts being a statement. The clerk notices. The forty people who bought one become a list.
I keep running into that shape in networks. A network here means a shared set of rules that computers agree to follow, so strangers can send value to each other without a company sitting in the middle. The rules it launches with are the defaults. Everyone gets them without choosing, which is exactly why nobody stands out for having them.
My claim is one sentence. What a network is built with at the start is what it can defend later.
"We will add that later" sounds like a scheduling question. It lands as a category question. Later means optional, optional means a minority, and a minority is a list.
The strongest case against me is a fair one. Networks upgrade constantly, and plenty of good things arrived long after launch. Treating a launch document as sacred is conservatism wearing the clothes of principle, and it blocks improvements that would bring more people in.
I think that case is right about parameters and wrong about properties. You can change a number, a fee, a limit, a schedule, and the system still behaves the way people expect. Changing what the system reveals about the people using it is a different sort of edit, because everyone already inside built their habits on the old answer.
One result would show me wrong. A large network bolts on a foundational property after launch, privacy switched on for everyone by default would be the clean test, and most of its users are on it within a few years. If that happens I will say so.
This is why Bitcoin's oldest arguments keep coming back. Read them as the original design meeting an incentive that did not exist yet, and the shape of the fight makes sense. I am not picking a side in any of them today. I am saying the disagreements that never quite resolve tend to be the ones where something foundational is on the table, and that is worth knowing before you read the spec.
if this changed how you read a proposal, Zap ⚡
