Skip to content

docs(stack): add cryptographic primitives section to security page #1687

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Othryades merged 6 commits into from
Aug 26, 2026
Merged

docs(stack): add cryptographic primitives section to security page #1687

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
054129a
docs(stack): add cryptographic primitives section to security page
Othryades Aug 25, 2026
bdd70b8
docs(stack): drop NIST-approval note from secp256k1 row
Othryades Aug 25, 2026
eeb5702
Update docs/stack/evaluate/security.mdx
Othryades Aug 25, 2026
ba9d30e
docs(stack): fix library list serial comma
Othryades Aug 25, 2026
286959c
docs(stack): drop overbroad no-custom-crypto claim per crypto review
Othryades Aug 25, 2026
b7e2f88
Merge branch 'main' into docs/cryptographic-primitives-security-page
Soleimani193 Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/stack/evaluate/security.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,18 @@ response, or control upgrade authority depending on the deployment. For upgrade
mechanics, see the
[OpenZeppelin Transparent Upgradeable Proxy pattern](../../protocol/architecture/smart-contracts.mdx#contract-versioning).

## Cryptographic primitives

The following table outlines the cryptographic primitives Lineth relies on, where they are used in the stack, and what standards they correspond to.

| Primitive | Where the stack uses it | Standard |
| --- | --- | --- |
| ECDSA over secp256k1 | Transaction signing and validator signing | Ethereum-standard curve. |
| ECDSA over secp256r1 (P-256) | Available to smart contracts through the `P256VERIFY` precompile ([RIP-7212](https://github.com/ethereum/RIPs/blob/master/RIPS/rip-7212.md)) | Curve approved under [FIPS 186-5](https://csrc.nist.gov/pubs/fips/186-5/final) |
| Keccak-256 | EVM hashing, state commitments, and role identifiers | Based on the Keccak permutation standardized in [FIPS 202](https://csrc.nist.gov/pubs/fips/202/final) (SHA-3 family). Ethereum uses the pre-standardization Keccak-256 padding, not the FIPS 202 SHA3-256 output. |
| TLS | Service-to-service and RPC endpoints | Standard TLS. Configuration is per deployment. |
| 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. |

## Available evidence

The following public materials are the available assurance evidence for the Lineth stack:
Expand Down
Loading