Transitioning HotorNot SNS to a Multi-Subnet Architecture: Proposal for User-Index Ownership Transfer #16
diksha-yadav-yral
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear HotorNot Community,
We are excited to announce a significant milestone in the evolution of our platform. As part of our commitment to innovation and scalability, we are transitioning from a single-subnet architecture to a multi-subnet architecture on the Internet Computer blockchain.
Setting a new standard with MULTI-SUBNET architecture on the Internet Computer blockchain, we are introducing dynamic canister provisioning across subnets - a FIRST in IC history!
1. Background:
HotorNot has been built upon the Internet Computer Protocol (ICP) blockchain with a unique architecture where each user is allocated a dedicated canister, managed within a single subnet. This architecture has served us well in our initial stages of growth, providing stability and reliability to our users.
2. Moving Towards Multi-Subnet Architecture:
To accommodate our expanding user base and enhance the resilience of our platform, we are now moving towards a multi-subnet architecture. In this new setup, user-canisters will be distributed across multiple subnets, with each subnet having its own set of user-indexes.
3. Introducing the Platform Orchestrator:
To efficiently manage the allocation and maintenance of user-canisters across multiple subnets, we have developed a Platform Orchestrator. This orchestrator will be responsible for assigning new users to subnets based on the availability of user-indexes within each subnet.
4. Proposal: Transferring Ownership of User-Indexes:
In line with our transition to a multi-subnet architecture, we are submitting a proposal to transfer the ownership of user-indexes from the HotorNot SNS DAO to the Platform Orchestrator canister. This transfer of ownership will empower the Platform Orchestrator to effectively manage user allocation and ensure the seamless operation of the platform in the new architecture.
5. Next Steps: Once we have thoroughly tested the multi-subnet architecture and addressed any bugs or issues, and once we are confident that the Platform Orchestrator is performing as expected, the ownership of the Platform Orchestrator will be transferred to the HotorNot SNS DAO.
Community Participation:
We value the input and participation of our community members in this critical decision-making process. Your insights and feedback are essential as we navigate this transition and shape the future of HotorNot. We encourage you to review the proposal and share your thoughts with us.
Proposal: https://nns.ic0.app/proposal/?u=67bll-riaaa-aaaaq-aaauq-cai&proposal=85
As we embark on this exciting journey towards a multi-subnet architecture, we remain steadfast in our commitment to innovation, scalability, and the continued growth of HotorNot. Your support and active engagement are invaluable as we work together to build a more resilient and vibrant social media platform on the Internet Computer blockchain.
Thank you for being part of the HotorNot community.
Warm regards,
HotorNot Team
Beta Was this translation helpful? Give feedback.
All reactions