Links
🗺️

Roadmap

Timeline

2022 Q1
  • Project Establishment [COMPLETED]
2022 Q2
  • Proof of Concept [COMPLETED]
  • Protocol Establishment [COMPLETED]
2022 Q3
  • Draft of the Whitepaper [COMPLETED]
  • Development & Marketing Launch [COMPLETED]
2022 Q4
  • Official Website Launch [COMPLETED]
  • Official Litepaper Release [COMPLETED]
2023 Q1
  • GitHub Repos Release [COMPLETED]
  • Testnet Release [COMPLETED]
  • Deployed on Arweave [COMPLETED]
2023 Q2
  • Deployed on BNB Greenfield [COMPLETED]
  • Deployed on Filecoin [COMPLETED]
2023 Q3
  • Incentivized Testnet Release [COMPLETED]
  • Multiple Storage Layers Upgrade [COMPLETED]
2023 Q4
  • ZK-rollup Integration Testnet
2024 Q1
  • ZK-rollup Integration Mainnet
2024 Q2
  • User Experience Improvement

Future Plan

🧊 Decentralized Identity
In Web3, the data is owned by an on-chain address that has the owner key of the related data. However, just the on-chain address isn’t enough to identify the profile or record the identity and social graph. What is worse is that everyone could easily set up hundreds of on-chain addresses in seconds. This means that someone is required to integrate all the on-chain data to form a one-chain Identity, which could be used in the logins, social connections, reputation system and credit finance of the Web3 space.
🧊 Data Cross-chain
Today, crypto assets are realized in cross-chain transfer between different blockchains. However, the Web3 data is still constrained in different blockchains and can not be transferred between them, significantly limiting the integration and potential of Web3 data. Therefore, Glacier will research how to achieve cross-chain transfer between different blockchains to make the data flow easily in the multichain era.
🧊 Graph Database for Web3 Social Graph
Web3's openness creates an excellent foundation for building a user social graph which has not been achieved in Web 2.0 due to the data barriers. When creating the social graph in Web3, developers have to deal with a great load of on-chain data which is not structurally stored on the blockchain nodes. In Web2.0, the graph database, which is one of the important NoSQL database types, is used to store the user's social connection data to create a social graph. Therefore, Glacier will consider releasing a dedicated Graph Database SDK to help Web3 developers create the social graph more easily.
🧊 Enhanced Log Security
The use of a single Read and Service Key for an entire Log means that, should either of these keys be leaked via malicious (or other possibly accidental) means, there is no way to prevent a node with the leaked keys from listening to Events or traversing the Log history. Glacier will explore the potential solutions which could deliver enhanced log security in the future.