Skip to content

Commit 1572653

Browse files
authored
fix links & folder names (#71)
1 parent a54db40 commit 1572653

File tree

4 files changed

+1
-1
lines changed

4 files changed

+1
-1
lines changed

posts/2024-01-26_bgl-poc-2/README.md renamed to posts/2024-01-26_bgl-poc2/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ PoC solves this problem, ensuring the network becomes increasingly decentralized
2828

2929
PoC is thus slower to bootstrap than PoS and harder to achieve. You can think of PoC versus PoS as a marathon versus a sprint, whereby PoC starts slowly but then gains momentum over time, and PoS starts quickly but loses momentum over time (the graph below provides a visual representation of PoC versus PoS).
3030

31-
[![Graph](https://gnolang.github.io/blog/2024-01-26_poc-2/src/thumbs/graph-container.png)](https://gnolang.github.io/blog/2024-01-26_poc-2/src/graph-container.png)
31+
[![Graph](https://gnolang.github.io/blog/2024-01-26_bgl-poc2/src/thumbs/graph-container.png)](https://gnolang.github.io/blog/2024-01-26_bgl-poc2/src/graph-container.png)
3232

3333
The GovDAO that owns the chain has a mandate to scale (to grow and decentralize) continuously as it adds more contributors. This means it becomes progressively larger over time, achieving high decentralization efficiency way beyond the initial fast sprint of PoS chains. Once established as a proven consensus mechanism and alternative to PoS, GovDAO can benefit from by any blockchain project (through an evolution of ICS) wanting to achieve decentralization and sustainability—PoC can secure Gno.land and the web3 industry at large.
3434

0 commit comments

Comments
 (0)