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

[doc] testnet node liveness criteria #951

Merged
merged 1 commit into from May 13, 2022

Conversation

rustielin
Copy link
Contributor

Start the doc that informs node operators the conditions upon which they are incentivized for AIT1.

@aptos-bot aptos-bot added this to In Review in bors May 12, 2022
Copy link
Contributor

@davidiw davidiw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs to land asap, please follow all the feedback or ask questions if there's any ambiguity and land quickly

slug: " node_liveness_criteria"
---

When you participate in the [Aptos Incentivized Testnet](https://medium.com/aptoslabs/aptos-incentivized-testnet-update-abcfcd94d54c), your validator node must pass liveness checks within 24 hours of being deployed, and at a regular cadence onwards. This is required to ensure that your validator node contributes to the health of the overall network and that you become eligible for incentivized testnet rewards.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

within 24 hours of the start of the notification process

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

notification process?

Copy link
Contributor Author

@rustielin rustielin May 13, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changing to "your validator node must pass liveness checks within 24 hours of being selected to participate in the testnet"

@davidiw davidiw dismissed rajkaramchedu’s stale review May 13, 2022 05:22

due to the timeliness -- -- ...

@rustielin rustielin force-pushed the doc-liveness branch 2 times, most recently from d458b91 to ba82f8b Compare May 13, 2022 06:01
@rustielin
Copy link
Contributor Author

/land

@aptos-bot aptos-bot moved this from In Review to Queued in bors May 13, 2022
@aptos-bot aptos-bot moved this from Queued to Testing in bors May 13, 2022
@aptos-bot
Copy link
Contributor

Forge run: https://circleci.com/gh/aptos-labs/aptos-core/19503
Forge test result: all up : 1283 TPS, 3451 ms latency, 5300 ms p99 latency,no expired txns

@aptos-bot aptos-bot removed this from Testing in bors May 13, 2022
@aptos-bot aptos-bot closed this in a17b536 May 13, 2022
@aptos-bot aptos-bot merged commit a17b536 into aptos-labs:main May 13, 2022
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

Successfully merging this pull request may close these issues.

None yet

4 participants