Sparkling
It has often been asked why there is such little specification in the sUDT (simple user-defined token) token standard on Nervos. sUDT specifies a mechanism for issuing and governing a token and creates an “amount” field in token holder cells.
With the sophisticated and varied token models out there, we can understand why some might be concerned!
Actually there is sound reasoning that underlies this minimalistic approach, the sUDT type script has been audited and its simplicity offers safety. It ensures the most basic requirements for tokens (users can hold tokens, issuers can mint and govern) and provides a foundation for a world of interoperable extensions on top of it.
And this brings us to xUDT! xUDT (or Extensible UDT) allows for definition of more functionality and rules that a user-defined token may need. The first use case of xUDT we are seeing is for regulatory-compliance purposes, in the RCE extension. RCE enables an allow list/ban list of holders, emergency shutdown and other governance features required by issuers of digital assets.
xUDT extensions can continue to be stacked on top of each other (similar to the relationship of sUDT to xUDT) and token functionality can be customized as needed.
While this first usage of xUDT may just seem like another day in crypto to the passive reader, the CKB enthusiast will recognize that this is yet another example of the unique capabilities of CKB beginning to show their power.
Check out the Nervos talk post for xUDT details and the full specification.
A Lay2 CKB bounty and a successful bounty hunter
Last week, Lay2 launched a bounty to develop a minimal back-end for pw-core. Three submissions were received and the bounty was successfully claimed. Check out this link on Github for more information. We look forward to more of these kinds of activities in the future, as the Nervos community continues its trajectory of explosive growth!
The Nervos Foundation is seeking builders, if you have ideas and ambition, check out the wish list and let them know what you are interested in building!
RFC
Nervos applies the RFC (Request for Comments) process for implementing every building block of the protocol. There were 27 Previous RFCs, which can be found here.
If you are curious about the design decisions of aspects of CKB or anything built on it, please post your questions in this repository.
Dev Updates
Core
CKB
(#2604) allow miner http basic authorization
(#2509) metricize network traffic
(#2594) add EpochProvider trait and refactor dao calculation
(#2602) waiting for tx pool in integration tests
(#2598) bump serde_json from 1.0.61 to 1.0.64
(#2599) bump once_cell from 1.6.0 to 1.7.2
(#2600) bump atty from 0.2.11 to 0.2.13
(#2597) bump libc from 0.2.86 to 0.2.87
Dev Tools
Neuron
CKB Explorer
(#792) bump elliptic from 6.5.3 to 6.5.4
Layer 2
Muta [Layer2 framework on CKB]
SECBIT Labs [Zero knowledge proof toolkit for CKB]
Godwoken [A framework to build rollup solutions upon Nervos CKB]
Cross-chain
force-bridge-btc [maps BTC on Bitcoin to cBTC on CKB in a trustless way]
force-bridge-eth [maps ETH on Ethereum to cETH on CKB in a trustless way]
(#217) relayer only relay confirmed blocks
Ecosystem
Tocial [cosplayers’ photo sharing app]
Lay2 [pw-sdk, build dApp on CKB and run them everywhere]
Obsidian Labs [developer IDE]
Synapse [browser wallet and keyper agency]
BlockABC [onechain CKB and web auth]
GrowFi [token swap functionality]
Obsidian Systems [[CKB integration with ledger wallets]
Summa One [BTC/CKB interoperability] (completed)
LeapDAO [Sidechain Framework]
The Nervos Foundation currently runs a grants program for builders. check out the scope and how to apply.
CKB Weekly is curated by a group of people who witnessed Lina’s birth and started this to record her growth. Any views expressed are personal and do not represent an official position of the Nervos project. Got updates or articles you would like to include? Any feedback or other suggestions? Let us know by replying to the email.
If you are interested in contributing, we welcome you to join the review group on Telegram.
Meanwhile, there are links below if you want to learn more about the project and community.