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
Recommend a decentralized and full P2P ID provider, and enable it on official sites #1646
Comments
I did make a PR on ZeroTalk. One of the things that's really needed before very wide acceptance of KxoId is that I need a better computer because the one that I use right now freezes after a few days. |
Instead of a better computer, more trusted nodes. |
I'll get to that, I think I just need to figure a few things out for that first. Like, do I trust other client's with my zite's private key (which is different from the private key used to give out signatures for users) in order to add to the index, or should I have some system where there may be a delay for a user to be added to the index (note that you don't need to be on the index to be able to use your new id, but it'll let people search for you), or I could have a thing where each trusted node/peer can add to the index using their own user, etc. As I'm currently a little busy with school work, I've been thinking about how to fix these issues. When I find the time, then I'll work on this. |
The POW based ZeroID providers are still planned and would be relatively easy to add. I started to generate a "1ZeroiD[0-9]", but it never finished, I will fire it up again. |
@shortcutme |
Not sure if it's possible |
If you use trusted nodes like KxoID |
well it still relies in something to keep everything in order.. a truly serverless nodeless system can: of course we lose the ability to pick handlers but it's the price we pay but for truly self maintained ID(id that can be generated without connection to any servers or approval by any server yet maintains uniqueness) will take more work and probably should be in another issue |
@Thunder33345
Why the need for something else ? |
i mean i am assuming our endgoal is to have a trustless and decentralized system with always unique username
what you meant by? we could also use namecoin for usernames but who want to pay every time for a username but using raw bitcoin address as username would be somewhat customisable yet 100% unique and decentralized yet trustless |
No my bad I though we were talking about DNS (I still had my head on an other issue). Namecoin doesn't fill the unique id purpose. You are right current system is centralized and it is not great.
I say pick the less worst solution 😄 |
re POW: we can have something like POWless but use bitcoin crypto so it's just impossible or financially unviable to create the same bitcoin address but free to create an user we can also somehow create our own crypto(sounds bad but lets just assume it on paper) drawbacks: which also reminds me of some self singing cert providers why not just use them, they already can customise the username display, and the auth address is always unique, we can derive an identifier based off the auth address to each user so they cant be impersonated and afterthought: there's not much differences other then the fact of the ladder already existed... now by that said it's a step from finally stop needing clearnet request to get an ID so that's an improvement i will take, |
No description provided.
The text was updated successfully, but these errors were encountered: