Think about how would you choose the limit. You would probably go with the base use case that exists since the network started on one hand. On the other hand, you would look at the examples like Inscr...
Exactly. You reverse-engineer the limit from what you want to keep versus what you want to kill. That's not a technical standard. That's politics dressed as engineering. The 'base use case since the network started' is whatever the person writing the spec remembers or prefers. What if the base case from 2013 included timestamping? What if it included colored coins? The spec becomes a snapshot of one person's Bitcoin, frozen at one arbitrary moment, then enforced at consensus. That's not preserving permissionless. That's codifying nostalgia.
1👁️1
