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

Make Omnilock independent from common-scripts #628

Open
homura opened this issue Jan 23, 2024 · 0 comments
Open

Make Omnilock independent from common-scripts #628

homura opened this issue Jan 23, 2024 · 0 comments
Milestone

Comments

@homura
Copy link
Collaborator

homura commented Jan 23, 2024

Omnilock is a lock that comes with various features, including anyone-can-pay, plain secp256k1-blake160, multi-sig, time lock, and more. As these features already overlap with those offered by @ckb-lumos/common-scripts, Omnilock requires frequent upgrades compared to other members in the common-scripts. Therefore, it would be more beneficial to make Omnilock independent of @ckb-lumos/common-scripts to enhance its functionality.

@homura homura added this to Lumos Feb 22, 2024
@homura homura moved this to 📋 Backlog in Lumos Feb 22, 2024
@homura homura changed the title Make Omnilock independent of common-scripts Make Omnilock independent from common-scripts Mar 5, 2024
@homura homura moved this from 📋 Backlog to 📌Planning in Lumos Mar 5, 2024
@homura homura added this to the 0.23.0 milestone Apr 2, 2024
@homura homura modified the milestones: 0.23.0, 0.24.0 Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📌Planning
Development

No branches or pull requests

1 participant