A New Chapter! .bit has successfully completed the RGB++ and DOBs compatibility upgrade.

Transitioning to the most powerful Bitcoin Layer 1 DID!

In April, d.id announced the plan for the RGB++ and DOBs compatibility upgrade of .bit, receiving enthusiastic feedback from both the .bit community and CKB ecosystem users. Since then, we have been flooded with inquiries about when the upgrade would be completed, demonstrating the high expectations for this upgrade.

Today, we are delighted to share that after two months of hard work, the .bit RGB++ and DOBs compatibility upgrade have both been successfully completed and is opened for all .bit holders (click to go upgrade now).

As many of you know, .bit was created in the early days of the CKB ecosystem, and its underlying asset type significantly differed from the recently proposed RGB++ and DOBs protocols. However, we chose to invest considerable effort into a complete overhaul, leading the largest community on CKB to actively embrace CKB's new development direction and accelerate the adoption and implementation of these two protocol standards within the CKB ecosystem.

Becoming a Bitcoin Layer 1 DID through the isomorphic binding feature of the RGB++ protocol is a significant step forward for .bit's future development, allowing us to advance towards the goal of becoming the biggest Bitcoin DID protocol with greater confidence.

The Next Chapter of the Grand Voyage

From its inception, .bit has always believed that the key to making a DID protocol stand out is breaking down barriers and lowering entry thresholds. Enabling users from different blockchains, or even those with no understanding of blockchain technology, to use a unified DID system without obstacles is the only way to achieve mass adoption.

Over the past few years, .bit has adhered to this path, leveraging CKB's unique features to achieve technical advantages not found in other DID protocols, such as multi-chain address minting and management, and the use of DID without seed phrases or gas fees. This approach has allowed .bit to carve out a niche in the highly competitive DID field. We have been fortunate to find a group of users who recognize the value of .bit, building a united and dedicated community together.

Our technical advantages have merely realized the first step of our vision. The next question is, how can .bit reach the next hundred thousand, million, or even billion users? This may sound like a pipe dream, as this scale far exceeds the total number of users of all current DID protocols. However, when we return to the starting point of the DID concept—to build the next generation of secure, reliable, and decentralized identity systems for humanity—this becomes a goal we must achieve.

A few months ago, with the introduction of the RGB++ concept, CKB began transitioning towards being a Bitcoin Layer 2 network, which also pointed .bit in the right direction: through isomorphic binding, making .bit a Bitcoin Layer 1 DID, leveraging Bitcoin's strong consensus to achieve .bit's next growth phase.

It seems the .bit team realized, perhaps even before this, that only Bitcoin has the sufficient influence to unify everyone’s consensus on DID. And only through Bitcoin does .bit have the chance to achieve the dream of building decentralized identities for all humanity. RGB++ appeared at this perfect moment, unlocking the door to our next map.

The choice of "bit" as the suffix for .bit was never a coincidence. Our founder Tim once wrote in an article explaining why .bit was built on CKB:

"...Our core team members left their jobs in internet companies to enter the Web3 industry largely because they identified with Bitcoin's foundational narrative and admired its elegant design. We are drawn to things closer to Bitcoin..."

The innate faith of being Bitcoin maximalists, the intuitive choice of CKB, and an unintentional tribute have planted the seeds for today, guiding us almost fatefully onto this path toward Bitcoin.

The new round of competition will be fiercer, and we will face many competitors on Bitcoin with different solutions but the same vision. When we win this round, .bit will dominate the entire game.

What Will the Upgrade Bring to .bit?

From a practical perspective, what benefits will the .bit upgrade bring to users?

Firstly, once users complete the upgrade, the new .bit will fully qualify as a Bitcoin DID through the RGB++ protocol, becoming a genuine Bitcoin Layer 1 DID.

Currently, .bit uses CKB's wallet connectivity library Common Chains Connector (CCC) to help users transfer .bit ownership using BTC or EVM wallets. CCC currently supports JoyID, Unisat, Metamask, and OKX Wallets.

After the upgrade, users can continue to manage .bit with EVM or BTC addresses, enjoying .bit's multi-chain features. Users can also use JoyID to perform the leap operation once JoyID supports the upgraded .bit assets. JoyID’s .bit integration will be completed around mid July.

The upgraded .bit also conforms to the DOBs (Digital Object) standard. In simple terms, DOBs are encrypted assets issued through the Spore protocol on the CKB blockchain. Minting .bit DOBs requires new storage space, occupying additional CKB tokens, which enhances .bit's underlying value.

Each .bit will not only have its unique name and value based on its length but will also have an additional value boost from the underlying CKB. Simply put, it becomes more valuable. Of course, these CKB tokens are not permanently charged. When a .bit DOBs expires, users can melt their .bit DOBs, and the occupied CKB will be refunded to the user.

Adhering to the DOBs standard significantly enhances .bit's trading liquidity. Previously, .bit used its own asset protocol, so users could only buy or sell .bit on specific secondary markets, limiting .bit's circulation beyond existing holders, which hindered the full realization of .bit's asset value potential. In the future, any trading platform supporting DOBs and RGB++ standards can list .bit, helping .bit traders achieve sufficient liquidity. Omiga has already added .bit trading, Dobby will soon support .bit trading as well.

With the development and expansion of the RGB++ protocol, you might soon be able to trade .bit on other popular Bitcoin ecosystem NFT markets. Whether you are a user of the CKB ecosystem or the broader Bitcoin ecosystem, you will have more convenient ways to acquire your first beloved .bit.

DOBs also opens up more exciting possibilities for .bit. For example, Nervape, which is also a DOBs, will be combinable with upgraded .bit. Imagine Nervape clothing, weapons, and accessories with your .bit identity, fully integrating your identity with your digital object image! This collaboration is already in progress, and the first batch of gear airdrops will be released soon. In the future, .bit will collide with more digital objects to create other exciting possibilities.

The true significance of this upgrade for .bit may only become more apparent over time.

How to Complete the .bit Upgrade

The new My DID management page will have two tabs: legacy .bit and DOBs compatible .bit, corresponding to pre-upgrade and post-upgrade .bit, respectively.

Step 1: First, connect the current .bit owner wallet address, which could be Ethereum, BNB, Tron address, or your Passkey. After logging in, you can find all the .bits you want to upgrade in the legacy .bit tab.

Step 2: Switch to the DOBs Compatible .bit tab in the upper left corner. At this point, you will be prompted to connect your JoyID, Metamask, Unisat, or OKX Wallet. After logging in, you will see a CKB address displayed in the top right corner. This address is generated by Common Chains Connector (CCC) and will become the owner of your .bit after the upgrade. You can continue to manage this .bit using your Ethereum or Bitcoin address in the future via CCC.

Click "Upgrade now," then select the .bit you want to upgrade and click the upgrade button. Please note that this operation is irreversible.

Step 3: First select your payment method to pay the CKB fees required for the upgrade (which will be refunded upon expiration). Then you transfer .bit ownership to the newly generated CKB address.

The upgrade process takes about 5 minutes. During this time, you can continue to upgrade other .bits.

At this point, the upgrade is complete. You can find all the upgraded .bits in the DOBs compatible .bit tab. In the details of each .bit, you can see that the owner has become the newly generated CKB address. You can also transfer the upgraded .bit to other CKB addresses, but note that currently, it only supports transfers to other CKB addresses generated by CCC.

Next, you can follow a similar process to set .bit aliases or renewals.

---

A new chapter is unfolding before .bit and all our holders. It is filled with treasures waiting to be discovered and challenges to be conquered. More Dapp integrations, more ecosystem partners, stronger identity symbols, and more cohesive community consensus...

Display your .bit identity anytime, anywhere. The magnificent next chapter is on the horizon.