Sparkling
This week we saw Nervos researcher Cipher publish a new NFT specification proposal!
The flexibility of CKB allows for a wide array of functionality to be added to NFTs and has produced multiple standard proposals, you can check out two previous NFT specification proposals here and here. We are excited about the possibilities for NFTs on CKB!
This new CKB NFT specification offers:
Publicity of the issuer information for authentication
Class definition for multiple NFT items with the same attributes
Limited edition definition for pre-defined issuance count
Set definition for a group of collectibles that span different classes
Claim action supported, for ticket-like use cases scenarios
Bit configuration for exchangablility, permanent lock, and self destructibility
Extensible information definition
Like sUDT, NFT’s on CKB are first class assets and are held with the same security as the native CKB, allowing users to own their own assets and get maximum asset security.
We know that many NFT issuers are artists, who may have little prior experience using blockchains. With the Interoperability 2.0 components of Nervos, such as pw-core, we can ensure that these users can easily use existing authorization systems such as biometrics, FaceID, etc. on their laptops or mobile devices.
This will create more user-friendly NFT applications on Nervos with a seamless user experience, so that Nervos can serve more users beyond the existing blockchain ecosystem.
Power usage, environmentalism and PoW
PoW energy usage has always been a topic of debate, and we see a Nervos Talk post inquiring about Nervos and this topic. Nervos architect Jan shared his thoughts, including many links to further the discourse.
Given the attention this topic has garnered recently, this post is highly suggested reading! Click here for more.
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
(#2611) improvement: smaller block status map during IBD
(#2569) add rpc generate_block_with_template to IntegrationTest rpc module
(#2612) no timeout if the tx-pool still works
(#2608) add case about get block templae and conflict transactions
(#2595) refactor: set prepare_for_bulk_load option for migration
Dev Tools
Neuron
(#2006) bump elliptic from 6.5.3 to 6.5.4
CKB Explorer
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]
(#112) Fix v0.1.x testnet bug
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]
(#230) rm unused code
Ecosystem
Hxro [Gamified Crypto Trading Platform]
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.