docs: document ML-DSA-65 post-quantum access keys#3061
Draft
r-near wants to merge 4 commits into
Draft
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Resolve access-keys.mdx: keep both the new 'Limited Access Key Caveats' (from master) and 'Signature Schemes' (this branch) sections.
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.
What
Documents the ML-DSA-65 (FIPS 204) post-quantum signature scheme as a third access-key / transaction-signing option alongside
ed25519andsecp256k1.Covers the feature added in nearcore#15731, the SDK support in near-sdk-rs#1557, and the CLI support in near-cli-rs#605.
Changes
protocol/accounts-contracts/access-keys.mdx— new Signature Schemes section (a canonical comparison of the three schemes) plus a Post-Quantum Keys (ML-DSA-65) subsection covering FIPS 204, key/signature sizes, on-chain hash storage (48-byte SHA3-384), and theml-dsa-65-hash:view behavior.api/rpc/contracts.mdx— documentsview_access_keyandview_access_key_list(previously undocumented) and howml-dsa-65keys surface asml-dsa-65-hash:in key lists.tools/cli.mdx— new Generate a key pair section (generate-keypair),--signature-scheme ml-dsa-65examples on theadd-keyautogenerate flow, and a note on thedelete-keypicker limitation for hash-only PQ keys.smart-contracts/anatomy/actions.mdx— note thatadd_access_key/add_full_access_keyacceptml-dsa-65public keys with no code changes.smart-contracts/anatomy/environment.mdx— note thatsigner_account_pkmay return anml-dsa-65key.Notes for reviewers
PostQuantumSignaturesprotocol feature, stabilized at protocol version 85 (the nearcore 2.13 stable version). The CLI support (near-cli-rs#605) is itself a draft pending 2.13 crate publication, so this stays a draft until the release is live. Content is written GA-style, as agreed.ed25519/secp256k1. PQ keys are random-only (no seed phrase) and have no implicit-account form.near-api-jsstill pending: noml-dsa-65support in the JS client yet, so the JS key examples intools/near-api.mdxare unchanged — a follow-up for when it lands.core/crypto/src/signature.rs: sizes 1952 / 3309 / 4032 B, 48-byte SHA3-384 trie hash, domain tagnear:ml-dsa-65-pubkey-hash:v1.