Skip to content

How does blockchain ID balance squat-resistance with seizure-resistance? #4

@paulkernfeld

Description

@paulkernfeld

Blockchain ID seems like a really cool concept. I'm thinking about using it, but I have this question about its mechanics.

Resistance to squatting and resistance to seizure seem to be two opposing sides in the problem of name registration. If names are too easy to hold onto, squatting becomes a problem. Conversely, if they are too easy to take over, seizure becomes a problem.

So, how does blockchain ID balance these two concerns? As I understand it, this is done by correctly choosing the cost of registering a new name as well as the cost of renewing a name (in the id namespace). If my understanding is correct, then I guess my questions are: what are these costs, and how do you know that you have chosen them correctly?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions