docs(stack): add cryptographic primitives section to security page - #1687
Merged
Conversation
Signed-off-by: Othryades <Othryades@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Signed-off-by: Othryades <Othryades@users.noreply.github.com>
Othryades
requested review from
Soleimani193,
alexandratran,
bgravenorst and
eloi010
August 25, 2026 13:13
eloi010
previously approved these changes
Aug 25, 2026
alexandratran
previously approved these changes
Aug 25, 2026
Co-authored-by: Alexandra Carrillo <12214231+alexandratran@users.noreply.github.com>
Signed-off-by: Othryades <Othryades@users.noreply.github.com>
| | Key custody | Remote signing through [Web3Signer](../../protocol/architecture/index.mdx#web3signer), with optional AWS KMS-backed secp256k1 signing | AWS KMS uses FIPS 140-2 and FIPS 140-3 validated HSMs (validations held by AWS). Key custody is a deployment choice. | | ||
|
|
||
| All signing and hashing go through established libraries (Besu, web3j, Tuweni, | ||
| BouncyCastle) or AWS KMS. The stack does not implement custom cryptographic primitives. |
Contributor
There was a problem hiding this comment.
The stack does not implement custom cryptographic primitives.
You mainly mentioned the cryptography for the infrastructure, so the phrase is correct for those.
The ZK proof system uses additional primitives—including proof-system-specific hash functions and polynomial commitment or encoding schemes—that are only industry-standard within the ZK ecosystem, or custom.
But I guess they are outside the scope of this table.
So maybe better remove the phase.
Signed-off-by: Othryades <Othryades@users.noreply.github.com>
Soleimani193
approved these changes
Aug 26, 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
4 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.
Adds a "Cryptographic primitives" section to docs/stack/evaluate/security.mdx. The section lists the cryptographic primitives the Lineth stack relies on (secp256k1, secp256r1 via the P256VERIFY precompile, Keccak-256, TLS, and signing key custody) and flags the published standard for each where one applies, with canonical links to RIP-7212, FIPS 186-5, and FIPS 202.
The section is descriptive only. It makes no compliance, alignment, or certification claims.
Verified: npm run build passes (no broken links). No other files changed.
Note
Low Risk
Documentation-only change with no runtime, configuration, or security logic impact.
Overview
Adds a Cryptographic primitives section on the stack security evaluation page, placed before Available evidence. It documents what crypto Lineth uses in a three-column table: primitive, stack usage, and applicable standard or note.
The table covers secp256k1 signing, P-256 via
P256VERIFY(with RIP-7212 and FIPS 186-5 links), Keccak-256 (including the Ethereum vs FIPS SHA3-256 distinction), TLS, and key custody via Web3Signer and optional AWS KMS (FIPS 140-2/140-3). The text is descriptive only and does not assert compliance or certification.Reviewed by Cursor Bugbot for commit b7e2f88. Bugbot is set up for automated code reviews on this repo. Configure here.