docs(v5-next): backport v5 testnet connection details + evergreen doc fixes#24246
Draft
AztecBot wants to merge 3 commits into
Draft
docs(v5-next): backport v5 testnet connection details + evergreen doc fixes#24246AztecBot wants to merge 3 commits into
AztecBot wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v5-next docs backport covering the remaining survey candidates, the partial-notes docs from #23564, and the slashing-configuration rewrite from #24005 (now adapted to v5). Complements #24242 and #24243.
Files
v5 testnet connection details
getting_started_on_testnet.md—NODE_URL→https://v5.testnet.rpc.aztec-labs.com,SPONSORED_FPC_ADDRESS→0x261366…7880, dropped the stale "~36 seconds" block-time row.docs/docs/networks.md— testnet column →v5.0.0-rc.1(rollup4239416255, RPC, all L1/L2 addresses), verified against the live node'snode_getNodeInfo. Mainnet column unchanged except4.3.0→4.3.1.slashing-configuration.md (from #24005, adapted to the v5 testnet)
Brings in #24005's structural rewrite (correct ejection mechanism, 72s slot math, grace period) and corrects the network-specific numbers to the v5 testnet config sourced from
l1-contracts/script/deploy/DeployRollupForUpgradeV5.s.sol(Sepolia branch):The old v5-next page was materially wrong for v5 (36s slots, 1%/3-strikes model). Caveat: these figures come from the v5 deploy config in-branch, not an on-chain read — the session's RPC proxy only serves mainnet, so I could not query the Sepolia rollup directly. Worth a confirmation against the live rollup before this merges.
Partial notes (from #23564, still open on
next)partial_notes.md(expanded),partial_notes_as_payment_endpoints.md(new),docs-words.txt(unlinkable). All cross-links and the#include_code/referencespaths verified present on v5-next; v5-next'saip-20.mdalready documents the referenced API.Evergreen
community_calls.md— refreshed meeting times / links / calendar.ai_tooling.md— "never callbbdirectly" agent guidance (doc prose only).Sources: v5 release-docs flow (
7d6b320,f5fadef,8bfd77d,b84af54,80830d0),8aed7c5/22393fe,9ebff63, #24005 (slashing), #23564 (partial notes). No tracked issue is closed by this backport.