This repository was archived by the owner on Jan 22, 2025. It is now read-only.
Validators aren't incentivized to provide timestamps #7485
Labels
stale
[bot only] Added to stale content; results in auto-close after a week.
Milestone
Comments
garious
added a commit
to garious/solana
that referenced
this issue
Dec 20, 2019
@CriesofCarrots says meh about the first concern, and has moved the second concern into a GitHub issue solana-labs#7485.
garious
added a commit
to garious/solana
that referenced
this issue
Dec 20, 2019
@CriesofCarrots says meh about the first concern, and has moved the second concern into a GitHub issue solana-labs#7485.
garious
added a commit
that referenced
this issue
Dec 20, 2019
…7591) * Move implemented proposals to implemented section of the book Leave "Slashing" commentary in a new proposal. * Remove considered considerations @CriesofCarrots says meh about the first concern, and has moved the second concern into a GitHub issue #7485.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
|
Timestamps are now expected with every vote. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
Some downstream users need access to reliable clock times for blocks. We have implemented a timestamp reporting system for validators (https://github.com/solana-labs/solana/blob/master/book/src/proposals/validator-timestamp-oracle.md), but there is no economic incentive for them to participate.
Proposed Solution
Incorporate timestamp expectations in validator uptime calculations to provide social pressure to participate in a timestamp oracle.
This might require storing more information about historical timestamps in the vote account.
The text was updated successfully, but these errors were encountered: