docs: add Alpha Network page and update privacy/limitations docs#22515
Merged
critesjosh merged 5 commits intoApr 21, 2026
Merged
Conversation
Add a dedicated Alpha Network page explaining what Alpha is, known limitations, proving system expectations, state migration challenges, security disclosure process, path to Beta milestones, and per-role expectations. Update privacy_considerations.md and limitations.md to reflect current state: document enqueue_incognito for hiding msg_sender, update side-effect padding status, remove stale Decoder.sol link and duplicate msg_sender section.
- Replace "local network/sandbox" framing with language reflecting Alpha is live on mainnet - Update bytecode validation section: protocol-level validation now exists in Contract Class Registry, but client-side (PXE/wallet) validation is still missing - Update key derivation section: scheme is stable within current rollup version, may change in future upgrades - Remove dismissive "sandbox" language from private data auth and hash sections - Update WARNING to say "networks" instead of "testnets"
The PXE has a scopes parameter for restricting note access, but it's caller-specified not protocol-enforced. Update the section to reflect this nuance instead of claiming no authorization exists at all.
The developer docs are served under /developers/docs/ not /developers/. Fix three links to limitations and privacy_considerations pages.
ciaranightingale
requested changes
Apr 18, 2026
| Migrating application state from one rollup version to another is a hard problem for any ZK rollup, and Aztec is no exception. You should expect that: | ||
|
|
||
| - **State does not carry over automatically.** Application data, deployed contracts, and notes on the current rollup will not be directly accessible on a new rollup version without explicit migration steps. | ||
| - **Migration tooling is still being developed.** There are no mature, battle-tested tools for migrating L2 state across rollup upgrades yet. |
Contributor
There was a problem hiding this comment.
should we link to the ones being developed?
ciaranightingale
approved these changes
Apr 21, 2026
ciaranightingale
left a comment
ciaranightingale
left a comment
Contributor
There was a problem hiding this comment.
lgtm, lets mergeeeeee
critesjosh
deleted the
josh/ecodr-948-docs-add-a-page-that-explains-detials-of-alpha
branch
Collaborator
|
❌ Failed to cherry-pick to |
critesjosh
added a commit
that referenced
this pull request
Apr 22, 2026
…tes (v4-next) (#22714) Backport of #22515 to v4-next. ## Summary - New Alpha Network page at `/participate/alpha` (`docs/docs-participate/alpha.md`): known limitations, state-migration expectations across rollup upgrades, security disclosure, path-to-Beta, per-role expectations. - `limitations.md` + `privacy_considerations.md`: document `enqueue_incognito` for hiding `msg_sender`, note that hashes/nullifiers/private logs are now padded, drop stale `Decoder.sol` link, remove duplicate `msg_sender` section. - Caution banner in Participate index, sidebar entry, and pointer from `networks.md` to the new page. ## Conflict resolution Two files conflicted on auto-cherry-pick: 1. **`docs/CLAUDE.md`** — trivial timestamp/version block. Took newer values from the PR (`2026-04-21` / `1.7`). 2. **`docs/docs/networks.md`** — terminology mismatch. On `next`, the mainnet phase is called "Alpha"; on v4-next it's called "Ignition" (Phase 1 — gas limit 0, no user tx, governance/staking active). The PR's replacement paragraph described "transaction processing fully active" which is `next`-accurate but not v4-next-accurate. Resolution: kept v4-next's Ignition description of Phase 1 specifics, but appended the pointer to the new Alpha Network page so it's still linked from the networks guide. Full analysis: https://gist.github.com/AztecBot/9076276b1dc2e239f25e3f3983abb53a ## Commit structure Per `CLAUDE.md` backport protocol: 1. `cherry-pick: …` — conflicted files staged AS-IS with markers. 2. `fix: resolve cherry-pick conflicts` — resolves the two markers. No build-fix commit needed (docs-only). ClaudeBox log: https://claudebox.work/s/6d396637e42fb57b?run=1
danielntmd
pushed a commit
to danielntmd/aztec-packages
that referenced
this pull request
Jun 19, 2026
…ons docs (AztecProtocol#22515) Original PR: AztecProtocol#22515 Merge commit: 63c67a0 Conflicts (left AS-IS with markers, resolved in next commit): docs/CLAUDE.md docs/docs/networks.md
danielntmd
pushed a commit
to danielntmd/aztec-packages
that referenced
this pull request
Jun 19, 2026
docs/CLAUDE.md: take newer timestamp/version from PR AztecProtocol#22515 docs/docs/networks.md: keep v4-next Ignition wording for Phase 1, add pointer to new Alpha Network page
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
3 participants
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.
Summary
/participate/alphaexplaining what Alpha is, known limitations (proving system bugs, unaudited software, privacy gaps), state migration challenges for rollup upgrades, security disclosure process, path-to-Beta performance milestones, and per-role expectationsprivacy_considerations.mdto documentenqueue_incognitofor hidingmsg_sender, update side-effect padding status (note hashes/nullifiers/private logs are now padded), and remove staleDecoder.sollinklimitations.mdwith the samemsg_senderand side-effect corrections, remove duplicatemsg_sendersectionnetworks.md, and add caution banner to Participate indexTest plan
yarn startin docs/ serves the new page at/participate/alpha🤖 Generated with Claude Code