-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Question] Deployment status of CKB-Auth #46
Comments
The deployment on mainnet has not occurred due to following reasons:
|
Hey @XuJiandong 🤗 Thank you for taking your time to explain!! While my use case is really simple (as I just need a library that supports
If an iCKB script was to depend on CKB-Auth, would it be possible within a few months to allocate some resources for an audit of the core components?
Every day a new blockchain is born, so you can't really wait for all implementations to become stable... In my eyes the most reasonable approach would be to adopt a gradual deployment, so as authentication implementations become stable and audited, deploy them. Is there anything preventing this approach? |
As suggested by @homura, it could be sensible to switch from
From CKB-Auth code I see that I'm no cryptographer, so let me ask a question: @XuJiandong is it correct to say that multiple blockchains use |
Hello Cryptape, iCKB here 👋
I'm exploring the possibility on developing on top of CKB-Auth, so I'm wondering:
I'm asking here since GitHub issues are SEO friendly and very likely in the future there will be other L1 developers wondering the same 😉
Keep up the Great Work,
Phroi
The text was updated successfully, but these errors were encountered: