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

Presentation proposal: Proof of Stake vs. Proof of Work #62

Merged
merged 1 commit into from
Nov 16, 2023

Conversation

filippaleuckfeld
Copy link
Contributor

Assignment Proposal

Title

  • Comparative Analysis of Two Consensus Mechanisms: Proof of Stake (PoS) vs. Proof of Work (PoW)

Names and KTH ID

Deadline

  • Week 6

Category

  • Presentation

Description

This presentation will delve into two pivotal consensus mechanisms in blockchain technology: Proof of Stake (PoS) and Proof of Work (PoW). The focus will be on explaining how each mechanism functions and evaluating their respective advantages and drawbacks. Key aspects such as security, energy efficiency, scalability, and their impact on decentralization will be explored. Additionally, real-world applications and implications of both PoS and PoW in various blockchain networks will be discussed.

Relevance

Understanding consensus mechanisms is fundamental in the realm of blockchain technology. These mechanisms are critical for upholding the integrity, security, and seamless operation of blockchain networks.

@filippaleuckfeld filippaleuckfeld changed the title Create README.md Presentation proposal: Proof of Stake vs. Proof of Work Nov 16, 2023
@Deee92 Deee92 self-assigned this Nov 16, 2023
@Deee92 Deee92 added week6 Week6 related demos and presentations presentation Assignment proposal labels Nov 16, 2023
@Deee92 Deee92 merged commit 9ce8959 into KTH:2023 Nov 16, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
presentation Assignment proposal week6 Week6 related demos and presentations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants