The rise of global social media giants allows centralized technology cartels to misuse user data, violating user privacy and imposing censorship. A study by Cambridge Analytica revealed that Facebook harvested the social graphs and personal profiles of millions of users without their consent to facilitate political ads, improperly capitalizing on personal data. The current landscape of centralized Web 2.0 social networks has deviated from the World Wide Web's principles of decentralizing information on a large scale.

As a solution, we want to offer a decentralized, censorship-free and self-sovereign social network that most closely matches the thesis of the Web 3.0 revolution. At the dawn of Web 3.0, CyberConnect emerged to create a decentralized social graph protocol that powers the Web3 and Metaverse social networks. Our mission is to return ownership and use of social graph data to the users, while providing an integration and development infrastructure for all Web3.0 developers.

The breakthrough innovation of the Ethereum blockchain lies in the execution of smart contracts in a decentralized way, opening a chapter of decentralized applications that interact with digital assets. We saw the success of the DeFi summer and the NFT summer. Numerous Dapps have emerged to facilitate the trading of digital assets.

On the other hand, we are happy to see the growing popularity of decentralized UGC (user generated content) platforms such as mirror.xyz and blockchain-based games such as Axie Infinity. We believe that the next major step in the Web 3.0 roadmap will be the rise of decentralized social networks and the blockchain-based metaverse. A decentralized social graph protocol will be an integral part of it.

In the absence of a decentralized social graph protocol, current games and social applications centrally store user connection data. Users must go through the process of creating connections multiple times each time they sign in to a new application. Imagine how amazing it can be when you enter Decentraland, Dark Forest or even Opensea and you can immediately recognize your friends from your address book who are also using this app. With CyberConnect, users can surf the various Web 3.0 Dapps and games with their digital assets, on-chain identities and social graphs without giving control over them to any centralized party.

We offer CyberConnect, a decentralized protocol for building social graphs based on blockchain addresses. The CyberConnect protocol will have the following features:

• Publicly accessible : Decentralized social graph data will be publicly available to all Dapps as an additional feature for developers to use user connections to reach beyond the existing user base.

• Self-sovereign : while social graph data is public, only users have full control over their own social graphs, i.e. adding, deleting and updating links.

• Blockchain-agnostic : Instead of being tied to a single blockchain, the protocol is being built for a multi-chain ecosystem. The function, independent of the blockchain, will support connections from all blockchains.

• Decentralized governance : Inspired by the Ethereum vision, we will embrace the ideals of security, permissionlessness, and decentralized governance. The long-term development of the protocol will depend on decentralized governance.

• Token-incentivized : To support the long-term development of the CyberConnect protocol, we are introducing a token-incentivized model at an early stage to fairly reward all participants who help build the social graph.

Privacy Options: We know that some users care more about their connection data than others. We are actively investigating technical solutions for future privacy features.

At the heart of CyberConnect is a tamper-proof data structure that effectively facilitates the creation, updating, querying, and validation of user-centric data.

Each piece of user-facing data is represented as a data stream, which can only be updated by the owner of the data. Each data update is added to the data stream in the form of an append-only commit log, and the resulting data structure becomes a hash-linked data structure called Mercle DAG. To ensure data authenticity, we use a codec dag-jose IPLDso that every piece of data, whether file creation or individual updates, is signed and possibly encrypted by the owner of the data. Before a new commit log is added to the data stream, an authorization check is performed to ensure that only the owner of the data can add new updates. After custom IPLD encoding, data is stored securely in IPFS to ensure lookup by address and data integrity. With this design, each user's social graph can only be modified by the user, is readable by applications with proper decryption permission granted by the user, and can be verified against the attached signature.

We are partnering with Ceramic for our first release based on their implementation of such a resizable streaming storage system on top of IPFS. Further performance improvements will be achieved by writing a heavy data model.

The availability of data between nodes is achieved using libp2p pubsub, so as long as one node subscribed to the pubsub topic has the required commit log, the data will be available to query across all nodes.

Long-term data retention is guaranteed with Ceramic's blockchain anchoring and our custom data anchoring service.

To fully reclaim ownership of user data, we must first deal with authentication and authorization. Authenticating a user simply means that he is who he is and is easily achieved by signing using the user's private key. Authorizing user data means that only the user has access to write their own data, and no other centralized party, such as Facebook, can change anyone else's data. Authorization is performed using pre-commit checks and dag-jose IPLDto ensure proper signature after commit.

Given these two requirements for authentication and authorization, we have developed a secure keychain scheme for authentication and authorization based on a public key system (asymmetric key pairs). First, users are not required to sign any non-transactional data with their blockchain private key. Signing with the private key of the blockchain creates additional barriers to user interaction and expands the attack surface. Thus, we need to generate key pairs with a curve ed25519from the entropy of the blockchain wallet signature on the client side. The private key is generated inside the protected iframeand is only provided to applications via rpc to prevent XSS attacks.

The key pairs are then encrypted with the existing private key from the user's keychain (the blockchain private key if the keychain private key does not exist) and stored in a specific keychain data stream. The keychain data flow is authorized and secured using a key rotation scheme combined with blockchain anchoring to resolve conflicts.

IPFS storage has a common centralization issue when CIDs are stored on a centralized server. This raises the problem of data authenticity, where the central server can replace real user data with fake ones by changing the CID. As mentioned above, we apply data signing with a codec dag-joseto ensure the authenticity of the data.

To find the social graph of a particular user, we first need to find the user's keychain via their blockchain address. We could then find the user table through the public key of the keyring. Unlike the application-centric design in Web2, where each application stores some information about the user, and information such as name and avatar is duplicated between applications, in our design, a single user table for each user contains all the necessary information and can be used in all applications. By putting all the social graph information in one user table, only that user has permission to update any data involved, and only parties who have been given a decryption key can read the data inside by decrypting it.

Similar to thegraphindexes transactional data in Ethereum, all social graph data on top of CyberConnect is processed by data indexers. CyberConnect stores social media data as one-way connections. For example, if Alice subscribes to Bob, Alice will add Bob to her following list. However, Alice cannot change Bob's friends list due to limited access. Thus, we save in the users table only the list of those to whom they are subscribed, but not the list of their subscribers. Any indexer can easily obtain such a list and regenerate the list of third party subscribers and provide such data to facilitate application queries. We would first deploy an indexer for the above use case for a list of subscribers (stored in a computed index) and welcome other interesting possibilities for community data indexing. Any user with some technical skill can verify the validity of the computed index, and a more sophisticated system involving slashing may be developed in the future.

A node should provide the following functionality to maintain a decentralized social graph.

1. A Ceramic node that includes a custom IPFS daemon with dag-jose IPLDencoding. It handles the creation and updating of a stream of authenticated keychain data. It also supports the desired data availability with a data pinning service. libp2pand IPFS, as well as streaming data consensus through blockchain anchoring.

2. The RPC endpoint that provides the data flow.

3. A data indexer that provides reverse lookup and data aggregation to create a reverse "follower list" based on a unidirectional connection of subscribers.

According to our concept, a decentralized social graph is represented as a set of one-way paths between different blockchain addresses. This simple framework is flexible and has the potential to support many interesting Web 3.0 use cases.

Social media decentralized applications can integrate an open social graph based on the CyberConnect protocol to download Medium, LinkedIn and Twitter Web 3.0 versions.

Web 3.0-based instant messaging applications can use a bidirectional subgraph (meaning that two users follow each other) as a contact list to expand the user base.

Blockchain games can import the social graph to improve their social features. Players will be able to easily chat and play with their online friends.

As users collaboratively contribute to the decentralized social graph, the growing adoption of the social graph leads to an increased network effect. A new connection created in one Dapp will benefit all Dapps using the CyberConnect protocol.

Below we present the concept of a Web 3.0-based instant messaging application that we are particularly interested in: CyberChat. CyberChat is expected to become an example of a Web 3.0 application matrix based on CyberConnect in the future.

Enabling messaging between blockchain addresses and enabling users to socialize their crypto assets natively will be the next step to complete the social ecosystem on Web 3.0. CyberChat is a secure Web3.0 messaging application for all blockchain users. More information about CyberChat will be available soon.

Decentralized Identifiers (DIDs) are a new type of identifier that provides a verifiable decentralized digital identity. This is a standard created by the W3C for users to identify themselves without centralized registries, to identify vendors and CAs.

In the future, we may use the DID as a globally unique identifier for each Web3 user, each DID contains a private and public key pair for secure user interaction with services and data. Each DID is also associated with one or more blockchain addresses, and these addresses may even be on different blockchains.

There are several advantages to the DID approach. Users are uniquely identified without a centralized authority, and the integrity of user data is maintained by the DID signature. Users can associate different blockchain addresses with a single DID, which is in line with the ever-growing Layer-1 blockchain landscape. Users will not use their private key to sign any non-transactional information such as sending a message or updating their avatar.

Each DID is an abstract, key-independent and blockchain-independent interface used to uniquely identify, sign and encrypt information and delegate access control to services.

The CyberConnect protocol is managed by the CyberConenctDAO, which consists of $CYBER token holders. The management proposals will go through two phases. The first step is a consensus check done with Snapshot. A minimum threshold of tokens is required to pass any offer. The second stage is the implementation of proposals. Only proposals that pass the first stage can be finally implemented in the protocol. The code must be reviewed by professionals before implementation, and the audit fee will be reimbursed by the community back-up pool.

$CYBER is the native token of CyberConnectDAO. The DAO is the owner of the CyberConnect protocol. $CYBER holders are members of the CyberConenctDAO and share ownership of the CyberConnect protocol through the DAO. As a native token, $CYBER serves as an incentive to facilitate governance. The CyberConnect team will continue to actively participate in the best Web 3.0 projects to expand the use cases for the $CYBER token.

The $CYBER token will only be used for early stage governance purposes. Functionality related applications such as staking rewards will be introduced later along with the increasing adoption of the protocol. The total supply of $CYBER tokens is 100,000,000. More information about tokenomics will be provided in the future.

The rise of global social media giants allows centralized technology cartels to misuse user data, violating user privacy and imposing censorship. A study by Cambridge Analytica revealed that Facebook harvested the social graphs and personal profiles of millions of users without their consent to facilitate political ads, improperly capitalizing on personal data. The current landscape of centralized Web 2.0 social networks has deviated from the World Wide Web's principles of decentralizing information on a large scale.

As a solution, we want to offer a decentralized, censorship-free and self-sovereign social network that most closely matches the thesis of the Web 3.0 revolution. At the dawn of Web 3.0, CyberConnect emerged to create a decentralized social graph protocol that powers the Web3 and Metaverse social networks. Our mission is to return ownership and use of social graph data to the users, while providing an integration and development infrastructure for all Web3.0 developers.

The breakthrough innovation of the Ethereum blockchain lies in the execution of smart contracts in a decentralized way, opening a chapter of decentralized applications that interact with digital assets. We saw the success of the DeFi summer and the NFT summer. Numerous Dapps have emerged to facilitate the trading of digital assets.

On the other hand, we are happy to see the growing popularity of decentralized UGC (user generated content) platforms such as mirror.xyz and blockchain-based games such as Axie Infinity. We believe that the next major step in the Web 3.0 roadmap will be the rise of decentralized social networks and the blockchain-based metaverse. A decentralized social graph protocol will be an integral part of it.

In the absence of a decentralized social graph protocol, current games and social applications centrally store user connection data. Users must go through the process of creating connections multiple times each time they sign in to a new application. Imagine how amazing it can be when you enter Decentraland, Dark Forest or even Opensea and you can immediately recognize your friends from your address book who are also using this app. With CyberConnect, users can surf the various Web 3.0 Dapps and games with their digital assets, on-chain identities and social graphs without giving control over them to any centralized party.

We offer CyberConnect, a decentralized protocol for building social graphs based on blockchain addresses. The CyberConnect protocol will have the following features:

• Publicly accessible : Decentralized social graph data will be publicly available to all Dapps as an additional feature for developers to use user connections to reach beyond the existing user base.

• Self-sovereign : while social graph data is public, only users have full control over their own social graphs, i.e. adding, deleting and updating links.

• Blockchain-agnostic : Instead of being tied to a single blockchain, the protocol is being built for a multi-chain ecosystem. The function, independent of the blockchain, will support connections from all blockchains.

• Decentralized governance : Inspired by the Ethereum vision, we will embrace the ideals of security, permissionlessness, and decentralized governance. The long-term development of the protocol will depend on decentralized governance.

• Token-incentivized : To support the long-term development of the CyberConnect protocol, we are introducing a token-incentivized model at an early stage to fairly reward all participants who help build the social graph.

Privacy Options: We know that some users care more about their connection data than others. We are actively investigating technical solutions for future privacy features.

At the heart of CyberConnect is a tamper-proof data structure that effectively facilitates the creation, updating, querying, and validation of user-centric data.

Each piece of user-facing data is represented as a data stream, which can only be updated by the owner of the data. Each data update is added to the data stream in the form of an append-only commit log, and the resulting data structure becomes a hash-linked data structure called Mercle DAG. To ensure data authenticity, we use a codec dag-jose IPLDso that every piece of data, whether file creation or individual updates, is signed and possibly encrypted by the owner of the data. Before a new commit log is added to the data stream, an authorization check is performed to ensure that only the owner of the data can add new updates. After custom IPLD encoding, data is stored securely in IPFS to ensure lookup by address and data integrity. With this design, each user's social graph can only be modified by the user, is readable by applications with proper decryption permission granted by the user, and can be verified against the attached signature.

We are partnering with Ceramic for our first release based on their implementation of such a resizable streaming storage system on top of IPFS. Further performance improvements will be achieved by writing a heavy data model.

The availability of data between nodes is achieved using libp2p pubsub, so as long as one node subscribed to the pubsub topic has the required commit log, the data will be available to query across all nodes.

Long-term data retention is guaranteed with Ceramic's blockchain anchoring and our custom data anchoring service.

To fully reclaim ownership of user data, we must first deal with authentication and authorization. Authenticating a user simply means that he is who he is and is easily achieved by signing using the user's private key. Authorizing user data means that only the user has access to write their own data, and no other centralized party, such as Facebook, can change anyone else's data. Authorization is performed using pre-commit checks and dag-jose IPLDto ensure proper signature after commit.

Given these two requirements for authentication and authorization, we have developed a secure keychain scheme for authentication and authorization based on a public key system (asymmetric key pairs). First, users are not required to sign any non-transactional data with their blockchain private key. Signing with the private key of the blockchain creates additional barriers to user interaction and expands the attack surface. Thus, we need to generate key pairs with a curve ed25519from the entropy of the blockchain wallet signature on the client side. The private key is generated inside the protected iframeand is only provided to applications via rpc to prevent XSS attacks.

The key pairs are then encrypted with the existing private key from the user's keychain (the blockchain private key if the keychain private key does not exist) and stored in a specific keychain data stream. The keychain data flow is authorized and secured using a key rotation scheme combined with blockchain anchoring to resolve conflicts.

IPFS storage has a common centralization issue when CIDs are stored on a centralized server. This raises the problem of data authenticity, where the central server can replace real user data with fake ones by changing the CID. As mentioned above, we apply data signing with a codec dag-joseto ensure the authenticity of the data.

To find the social graph of a particular user, we first need to find the user's keychain via their blockchain address. We could then find the user table through the public key of the keyring. Unlike the application-centric design in Web2, where each application stores some information about the user, and information such as name and avatar is duplicated between applications, in our design, a single user table for each user contains all the necessary information and can be used in all applications. By putting all the social graph information in one user table, only that user has permission to update any data involved, and only parties who have been given a decryption key can read the data inside by decrypting it.

Similar to thegraphindexes transactional data in Ethereum, all social graph data on top of CyberConnect is processed by data indexers. CyberConnect stores social media data as one-way connections. For example, if Alice subscribes to Bob, Alice will add Bob to her following list. However, Alice cannot change Bob's friends list due to limited access. Thus, we save in the users table only the list of those to whom they are subscribed, but not the list of their subscribers. Any indexer can easily obtain such a list and regenerate the list of third party subscribers and provide such data to facilitate application queries. We would first deploy an indexer for the above use case for a list of subscribers (stored in a computed index) and welcome other interesting possibilities for community data indexing. Any user with some technical skill can verify the validity of the computed index, and a more sophisticated system involving slashing may be developed in the future.

A node should provide the following functionality to maintain a decentralized social graph.

1. A Ceramic node that includes a custom IPFS daemon with dag-jose IPLDencoding. It handles the creation and updating of a stream of authenticated keychain data. It also supports the desired data availability with a data pinning service. libp2pand IPFS, as well as streaming data consensus through blockchain anchoring.

2. The RPC endpoint that provides the data flow.

3. A data indexer that provides reverse lookup and data aggregation to create a reverse "follower list" based on a unidirectional connection of subscribers.

According to our concept, a decentralized social graph is represented as a set of one-way paths between different blockchain addresses. This simple framework is flexible and has the potential to support many interesting Web 3.0 use cases.

Social media decentralized applications can integrate an open social graph based on the CyberConnect protocol to download Medium, LinkedIn and Twitter Web 3.0 versions.

Web 3.0-based instant messaging applications can use a bidirectional subgraph (meaning that two users follow each other) as a contact list to expand the user base.

Blockchain games can import the social graph to improve their social features. Players will be able to easily chat and play with their online friends.

As users collaboratively contribute to the decentralized social graph, the growing adoption of the social graph leads to an increased network effect. A new connection created in one Dapp will benefit all Dapps using the CyberConnect protocol.

Below we present the concept of a Web 3.0-based instant messaging application that we are particularly interested in: CyberChat. CyberChat is expected to become an example of a Web 3.0 application matrix based on CyberConnect in the future.

Enabling messaging between blockchain addresses and enabling users to socialize their crypto assets natively will be the next step to complete the social ecosystem on Web 3.0. CyberChat is a secure Web3.0 messaging application for all blockchain users. More information about CyberChat will be available soon.

Decentralized Identifiers (DIDs) are a new type of identifier that provides a verifiable decentralized digital identity. This is a standard created by the W3C for users to identify themselves without centralized registries, to identify vendors and CAs.

In the future, we may use the DID as a globally unique identifier for each Web3 user, each DID contains a private and public key pair for secure user interaction with services and data. Each DID is also associated with one or more blockchain addresses, and these addresses may even be on different blockchains.

There are several advantages to the DID approach. Users are uniquely identified without a centralized authority, and the integrity of user data is maintained by the DID signature. Users can associate different blockchain addresses with a single DID, which is in line with the ever-growing Layer-1 blockchain landscape. Users will not use their private key to sign any non-transactional information such as sending a message or updating their avatar.

Each DID is an abstract, key-independent and blockchain-independent interface used to uniquely identify, sign and encrypt information and delegate access control to services.

The CyberConnect protocol is managed by the CyberConenctDAO, which consists of $CYBER token holders. The management proposals will go through two phases. The first step is a consensus check done with Snapshot. A minimum threshold of tokens is required to pass any offer. The second stage is the implementation of proposals. Only proposals that pass the first stage can be finally implemented in the protocol. The code must be reviewed by professionals before implementation, and the audit fee will be reimbursed by the community back-up pool.

$CYBER is the native token of CyberConnectDAO. The DAO is the owner of the CyberConnect protocol. $CYBER holders are members of the CyberConenctDAO and share ownership of the CyberConnect protocol through the DAO. As a native token, $CYBER serves as an incentive to facilitate governance. The CyberConnect team will continue to actively participate in the best Web 3.0 projects to expand the use cases for the $CYBER token.

The $CYBER token will only be used for early stage governance purposes. Functionality related applications such as staking rewards will be introduced later along with the increasing adoption of the protocol. The total supply of $CYBER tokens is 100,000,000. More information about tokenomics will be provided in the future.