docs: document initializerless accounts (v5-next backport of #24512) - #24598
Merged
Conversation
AztecBot
added
ci-draft
alejoamiras
marked this pull request as ready for review
July 8, 2026 14:12
AztecBot
force-pushed
the
cb/backport-24512-v5-next
branch
from
July 8, 2026 14:22
2afa421 to
c9f794c
Compare
AztecBot
enabled auto-merge
July 8, 2026 14:22
Backport of #24512 ("docs: document initializerless accounts") into `v5-next`, requested by Alejo in Slack. ## What this adds (same as the original PR) - **New concept page** `foundational-topics/accounts/deployment.md` ("Account Deployment"): the standard initialize-and-deploy flow vs the initializerless flow, how the signing key is committed into the address via `immutables_hash`, and the trade-offs (no deploy cost/delay; signing key fixed forever; per-PXE local setup; `getDeployMethod()` throws). - **New "Create an initializerless account" section** in `aztec-js/how_to_create_account.md` with the `createSchnorrInitializerlessAccount` snippet and caveats. - **Cross-links** from `fees.md`, `wallets.md`, `contract_creation.md`, and `aztec-nr/framework-description/immutables.md`. ## How the backport differs from the original - The original PR mirrored all changes into `developer_versioned_docs/version-v5.0.0-rc.2/`. That snapshot does not exist on `v5-next` (the only snapshot here is `version-v4.3.0`, which documents the v4 line and must not describe a v5-only feature), so this backport touches **only the current docs** under `docs/docs-developers/`. Git's directory-rename detection tried to remap the mirrored copies into the v4.3.0 snapshot during the cherry-pick; those were dropped deliberately. - Everything else is the original commit cherry-picked verbatim; the only diff-vs-original differences are context lines where `v5-next` prose already diverged from `next`. ## Notes - Unlike `next`, `createSchnorrInitializerlessAccount` **does** exist in this branch's `yarn-project` (verified), so the fenced snippet could be converted to an `#include_code` example here as a follow-up. Kept as a fenced block for a faithful backport. - Verified all new internal links resolve to files present on `v5-next`, and `initializerless` is already in `docs-words.txt` on this branch. Refs #24512. --- *Created by [claudebox](https://claudebox.work/v2/sessions/045227c21dcc966b) · group: `slackbot`*
AztecBot
force-pushed
the
cb/backport-24512-v5-next
branch
from
July 8, 2026 14:25
c9f794c to
7534604
Compare
nchamo
approved these changes
Jul 8, 2026
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.
Backport of #24512 ("docs: document initializerless accounts") into
v5-next, requested by Alejo in Slack.What this adds (same as the original PR)
foundational-topics/accounts/deployment.md("Account Deployment"): the standard initialize-and-deploy flow vs the initializerless flow, how the signing key is committed into the address viaimmutables_hash, and the trade-offs (no deploy cost/delay; signing key fixed forever; per-PXE local setup;getDeployMethod()throws).aztec-js/how_to_create_account.mdwith thecreateSchnorrInitializerlessAccountsnippet and caveats.fees.md,wallets.md,contract_creation.md, andaztec-nr/framework-description/immutables.md.How the backport differs from the original
developer_versioned_docs/version-v5.0.0-rc.2/. That snapshot does not exist onv5-next(the only snapshot here isversion-v4.3.0, which documents the v4 line and must not describe a v5-only feature), so this backport touches only the current docs underdocs/docs-developers/. Git's directory-rename detection tried to remap the mirrored copies into the v4.3.0 snapshot during the cherry-pick; those were dropped deliberately.v5-nextprose already diverged fromnext.Notes
next,createSchnorrInitializerlessAccountdoes exist in this branch'syarn-project(verified), so the fenced snippet could be converted to an#include_codeexample here as a follow-up. Kept as a fenced block for a faithful backport.v5-next, andinitializerlessis already indocs-words.txton this branch.Refs #24512.
Created by claudebox · group:
slackbot