Skip to content
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

Open
phroi opened this issue Apr 6, 2024 · 3 comments
Open

[Question] Deployment status of CKB-Auth #46

phroi opened this issue Apr 6, 2024 · 3 comments

Comments

@phroi
Copy link

phroi commented Apr 6, 2024

Hello Cryptape, iCKB here 👋

I'm exploring the possibility on developing on top of CKB-Auth, so I'm wondering:

  • What's CKB-Auth deployment status on testnet and mainnet?
  • If any, please could you document the deployed cells?

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

@XuJiandong
Copy link
Collaborator

The deployment on mainnet has not occurred due to following reasons:

  1. It has yet to undergo an audit due to resource constraints.
  2. The authentication implementation, such as Solana, varies across different wallets. Consequently, its compatibility with various projects remains subject to potential changes.

@phroi
Copy link
Author

phroi commented Apr 7, 2024

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 secp256k1_blake160 signatures), I would really like to integrate with CKB-Auth as it provides nice Rust abstractions for both:

  • Signature validation logic.
  • Transforming the context into the message.
  1. It has yet to undergo an audit due to resource constraints.

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?

  1. The authentication implementation, such as Solana, varies across different wallets. Consequently, its compatibility with various projects remains subject to potential changes.

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?

@phroi
Copy link
Author

phroi commented Apr 9, 2024

As suggested by @homura, it could be sensible to switch from secp256k1 to ed25519, which may be in contrast with your previous reply:

The authentication implementation, such as Solana, varies across different wallets. Consequently, its compatibility with various projects remains subject to potential changes.

From CKB-Auth code I see that ed25519 is used by Solana, but also many other blockchains.

I'm no cryptographer, so let me ask a question: @XuJiandong is it correct to say that multiple blockchains use ed25519, but everyone uses slightly different parameters for ed25519? So while Solana implementation may be subject to changes, other ed25519 blockchains are considered stable, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants