Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Waku blog topics #5

Open
1 of 4 tasks
hackyguru opened this issue Jan 31, 2024 · 1 comment
Open
1 of 4 tasks

Waku blog topics #5

hackyguru opened this issue Jan 31, 2024 · 1 comment

Comments

@hackyguru
Copy link
Collaborator

hackyguru commented Jan 31, 2024

In an effort to advocate Waku to wider developer audience, the following topics are on the pipeline for publishing on various blogging platforms :

  • Building a TicTacToe game with Waku (Waku blog)
  • Unbiased comparison of web3 communication protocols (Personal article from @hackyguru )
  • The expected role of a communications protocol in a network state
  • From Whisper to Waku : the evolution of web3 messaging protocols
@CryptoMaryna
Copy link

CryptoMaryna commented Feb 6, 2024

Goals of the article:

  • educaiton
  • expose current decentralization level of Waku
  • can help new project undersand whether to use static sharding or autosharding

Description:
As the decentralized landscape evolves, choosing the right architecture becomes pivotal for new projects seeking to foster permissionless communities. This article delves into the intricacies of Waku's decentralization models, specifically comparing static sharding and autosharding, to empower project leaders with informed decisions.

Article Overview:
The rise of permissionless community creation has sparked interest in decentralized architectures capable of supporting these ecosystems. Waku, a prominent player in the decentralized communication realm, offers both static sharding and autosharding solutions for community scalability and resilience. This article dissects the nuances of these approaches, shedding light on their strengths, limitations, and suitability for fostering thriving decentralized communities.

Key Points:

  1. Understanding Waku's Decentralization Models:

Static Sharding: Examining the implications of shard allocation and its impact on community scalability and participation.
Autosharding: Unraveling the deterministic mapping of community IDs to shared shards, and its implications for scalability and network resilience.

  1. Analyzing Acid Test Compliance:

Criteria for passing the acid test, assessing permissionless community creation, operation, and participation without centralized intervention.
Evaluation of Waku's architectures against the acid test, highlighting strengths and areas for improvement.

  1. Pros and Cons Comparison:

Static Sharding: Benefits such as validation of assumptions, scalability potential, and identifiable limitations like reliance on centralized bootstrapping.
Autosharding: Advantages including passing the acid test, autoscalability, and identified risks such as dependence on new RLN technology.

  1. Navigating Decentralization Challenges:

Addressing bootstrapping, peer discovery, and peer-to-peer transport in decentralized systems, and how Waku's models fare against these challenges.
Insights into potential pathways for enhancing decentralization and mitigating identified risks in Waku's architectures.

  1. Future Perspectives and Recommendations:

Anticipating future developments in Waku's decentralization journey, including efforts to enhance bootstrapping, peer discovery, and scalability.
Recommendations for project leaders considering Waku for fostering permissionless communities, based on the current landscape and anticipated advancements.

By offering a comprehensive analysis of Waku's decentralization approaches, this article equips project leaders and developers with the knowledge needed to make informed decisions in navigating the evolving decentralized communication landscape.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants