Skip to content

Commit 36ded99

Browse files
authored
Update PoS FAQ link to direct "Nothing at Stake" section (#2341)
## Overview Replaced the outdated Ethereum Proof-of-Stake FAQ link with the current, direct link to the "What is the 'nothing at stake' problem and how can it be fixed?" section in Vitalik Buterin's Proof of Stake FAQ. This ensures readers are directed to the most relevant and up-to-date explanation of the concept. Reference: https://vitalik.eth.limo/general/2017/12/31/pos_faq.html#what-is-the-nothing-at-stake-problem-and-how-can-it-be-fixed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Updated the reference link for the "Nothing-At-Stake" problem to a more current source. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
1 parent 6b509c0 commit 36ded99

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

specs/lazy-adr/adr-004-core-types.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ type EvidenceParams struct {
171171
//
172172
// It should correspond with an app's "unbonding period" or other similar
173173
// mechanism for handling [Nothing-At-Stake
174-
// attacks](https://github.com/ethereum/wiki/wiki/Proof-of-Stake-FAQ#what-is-the-nothing-at-stake-problem-and-how-can-it-be-fixed).
174+
// attacks](https://vitalik.eth.limo/general/2017/12/31/pos_faq.html#what-is-the-nothing-at-stake-problem-and-how-can-it-be-fixed).
175175
MaxAgeDuration time.Duration
176176
// This sets the maximum size of total evidence in bytes that can be committed in a single block.
177177
// and should fall comfortably under the max block bytes.

0 commit comments

Comments
 (0)