-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Registering domains freely. #2189
Comments
ZeroID is the official service for that, which is centralized.
That's a bit difficult to implement because you can never be sure that there are no seeds anymore. A minute of advertisement: there's Name.YO that you can use to register a domain for free. Not everyone will be able to use it, only those who have Name.YO plugin, but I believe many people have it (and your service would be another reason to promote it). |
I meant, expiry due to non-seeding by the user who registered the domain. For example, failing to seed for at least N days in a period of M days, would result in loss of domain, where N, M - some reasonable numbers. |
Define "reasonable". Balancer's domain are still hosted by lots of people even though he passed away. (RIP) |
Kinda naive, but ZeroNet's centralized namecoin mirror is almost nonsense though |
@imachug Maybe domain could be active until a certain number of people use/seed it. For example, the domain is deactivated if less then 15 people seed it for more than 30 days. Also, if the domain has subdomains, it may be deleted only if all of its subdomain websites are seeded by less than 15 people. But yes, this is a difficult topic as many things need to be considered here. |
Sybil attack
…________________________________
From: Filip Š <[email protected]>
Sent: Tuesday, September 17, 2019 1:29:01 AM
To: HelloZeroNet/ZeroNet <[email protected]>
Cc: blurHY <[email protected]>; Comment <[email protected]>
Subject: Re: [HelloZeroNet/ZeroNet] Registering domains freely. (#2189)
@imachug<https://github.com/imachug> Maybe domain could be active until a certain number of people use/seed it.
For example, the domain is deactivated if less then 15 people seed it for more than 30 days. Also, if the domain has subdomains, it may be deleted only if all of its subdomain websites are seeded by less than 15 people.
But yes, this is a difficult topic as many things need to be considered here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#2189?email_source=notifications&email_token=AH5CPREJLOIJDOWUZO3V733QJ6653A5CNFSM4IU4VQZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Z4WKA#issuecomment-531876648>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AH5CPRAMKNTXLBY5HIJFCNLQJ6653ANCNFSM4IU4VQZQ>.
|
checking for seeder count is futile, like blurhy mentioned: who knows what if i just add bunch of bot peers to my own site to keep it alive? you cant tell, without invasive of advance measures we havent address the name claiming problem i mean making a namecoin but POS clone seems most doable, even might be most realistic over observing updates/seeders/peers(basically same pay coins(but staked) to keep sites alive) |
I have an interesting idea for domain names... I'm going to make a separate issue for it. |
Registering domain.
Right now, to register a domain, I seem to need NameCoins, but namecoin miner is not embedded in the ZeroNet, so I can't simply mine a little bit of it in order to be able to register a domain. Mining NameCoin separately is a hassle, and buying it is also a hassle. How can we simplify this, and make it free like seeding is.
Describe the solution you'd like
I suppose, ideal solution would be some kind of PoS-based chain, that's embedded in the ZeroNet, perhaps a version of NameCoin itself, with proof-of-stake scheme.
Describe alternatives you've considered
I've considered, that it could happen in a similar way that users register their usernames, perhaps with expiry due to non-seeding.
Additional context
In the context of launching a website on ZeroNet.
The text was updated successfully, but these errors were encountered: