yeah, my name service consensus design doesn't include a mechanism for slowing down initial registrations, i need to think about how that should work.

the challenge is how to do it without mixing a binding to bitcoin with it and polluting the chain with anchors. i'd prefer not to do that. could just be a consensus rule that nodes will only accept the first one they see, and then they wait some period, disregarding all submissions until a new epoch for registration. something like rate limiting using a distributed consensus.

squatting is already handled in the protocol i designed in a similar way. names are just registered for a year only, and in the last 30 days of the registration the registrant has the right to extend it, so they are forced to be active in maintaining their squats, in a way that requires a lower time preference. there could be better methods to avoid this, but this is a simple one that doesn't involve monetary tokens.