-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support single-use-lock
script
#759
Labels
Comments
Keith-CY
added a commit
to nervosnetwork/ckb-explorer-frontend
that referenced
this issue
Jul 26, 2024
|
PR: nervosnetwork/ckb-explorer#2122 |
Verified. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
A new pattern named
single use lock
(https://talk.nervos.org/t/en-cn-misc-single-use-seals/8279/2), which is inspired byRGB++
, was introduced on CKB.They are now deployed on
The source code can be found at https://github.com/ckb-ecofund/ckb-proxy-locks
When an xUDT was issued by a
single-use-lock
, the token cannot be minted more because the owner is ephemeral, works as xUDT issued by an RGB++ Lock.On-chain cases:
Mainnet: https://explorer.nervos.org/xudt/0x27ab2471d79c4953a614a7d60d0ad1d376e8110a6ac6046f4bd6b012533bdf2d
Testnet: https://pudge.explorer.nervos.org/xudt/0xcef135ddca02a931e5b21235fe42f81fe93b01a2161699db4b3a1ae0ac795ec8
Describe the solution you'd like
limited supply
when a token(xudt, xudt-compatible, inscription, dob/spore) is issued withsingle-use
lock`single-use-lock
in script infoAdditional context
Issue xudt with single-use-lock on testnet: https://ckbccc-demo.vercel.app/
The text was updated successfully, but these errors were encountered: