OpenZeppelin · ericnordelo · Aug 7, 2026 · Aug 7, 2026 · Aug 10, 2026 · Aug 10, 2026
diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml
@@ -44,12 +44,25 @@ jobs:
             *.md
             !PULL_REQUEST_TEMPLATE.md
 
+      - name: Verify generated Falcon NTT sources
+        run: |
+          python3 scripts/falcon_512/generate_ntt.py --write
+          git diff --exit-code -- packages/account/src/falcon_512/ntt
+
       - name: Cairo lint
         run: scarb fmt --check --workspace
 
       - name: Run tests
         run: snforge test --workspace --features fuzzing --fuzzer-runs 200
 
+      - name: Run Falcon release-profile tests
+        run: |
+          snforge test -p openzeppelin_account --release --features falcon_fast_tests falcon_512 --max-n-steps 100000000
+          snforge test -p openzeppelin_presets --release --features falcon_presets_tests falcon_512 --max-n-steps 100000000
+
+      - name: Build release-profile presets
+        run: scarb --release build -p openzeppelin_presets
+
       - name: Run tests and generate coverage report
         run: snforge test --workspace --coverage
 

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -11,6 +11,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
+- `Falcon512AccountComponent`, SHAKE-256 hint and direct verifier strategies,
+  `Falcon512ShakeAccountUpgradeable` and `Falcon512ShakeDirectAccountUpgradeable` presets with SRC9
+  and class upgrades, and felt-array deployment and public-key interfaces for Falcon-512 accounts
+  (#1730)
 - `SafeERC20DispatcherTrait` in `openzeppelin_token::erc20::utils` with `assert_transfer`, `assert_transfer_from`, `assert_increase_allowance`, and `assert_decrease_allowance` (#1683)
 
 ### Changed (Breaking)

diff --git a/Scarb.lock b/Scarb.lock
@@ -39,6 +39,7 @@ dependencies = [
 name = "openzeppelin_account"
 version = "4.0.0-alpha.1"
 dependencies = [
+ "openzeppelin_corelib_imports",
  "openzeppelin_interfaces",
  "openzeppelin_introspection",
  "openzeppelin_test_common",
@@ -47,6 +48,10 @@ dependencies = [
  "snforge_std",
 ]
 
+[[package]]
+name = "openzeppelin_corelib_imports"
+version = "4.0.0-alpha.1"
+
 [[package]]
 name = "openzeppelin_finance"
 version = "4.0.0-alpha.1"

diff --git a/Scarb.toml b/Scarb.toml
@@ -2,6 +2,7 @@
 members = [
     "packages/access",
     "packages/account",
+    "packages/corelib_imports",
     "packages/finance",
     "packages/interfaces",
     "packages/governance",

diff --git a/packages/account/README.md b/packages/account/README.md
@@ -2,21 +2,71 @@
 
 > **NOTE:** This document is better viewed at [https://docs.openzeppelin.com/contracts-cairo/api/account](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account)
 
-This crate provides components to implement account contracts that can be used for interacting with the network.
+This crate provides components for building account contracts that interact with the network.
 
-- `Account` validates transactions from signatures over the
-[STARK Curve](https://docs.starknet.io/architecture-and-concepts/cryptography/#the_stark_curve).
+- `AccountComponent` validates transactions from signatures over the
+  [STARK Curve](https://docs.starknet.io/architecture-and-concepts/cryptography/#the_stark_curve).
 
-- `EthAccount` validates transactions from signatures over the
-[Secp256k1 curve](https://en.bitcoin.it/wiki/Secp256k1).
+- `EthAccountComponent` validates transactions from signatures over the
+  [Secp256k1 curve](https://en.bitcoin.it/wiki/Secp256k1).
+
+- `Falcon512AccountComponent` provides felt-array public-key management and account behavior for
+  canonical Falcon-512 public keys. It is generic over `Falcon512SignatureVerifier` and supports
+  two supplied SHAKE-256 strategies:
+
+  - `Falcon512ShakeVerifier` validates a 60-felt signature containing a verifier-checked
+    polynomial-product hint to reduce on-chain execution cost.
+
+  - `Falcon512ShakeDirectVerifier` validates a 31-felt signature and recomputes the polynomial
+    product on-chain.
+
+> **WARNING:** The supplied Falcon verifiers target the verification relation and SHAKE-256
+> hash-to-point from the FALCON submission selected by NIST. Their public-key and signature
+> encodings are contract-specific, and they are not FN-DSA (FIPS 206) implementations.
+
+The Falcon component implements invoke, declare, and deploy-account validation,
+signature validation, and owner-authorized felt-array public-key management. Contracts embed it
+with `SRC5Component` and one of the supplied verifier strategies. Ready-to-deploy variants with
+SRC9 outside execution and class upgrades are provided by the `openzeppelin_presets` package.
+
+Falcon accounts support owner-authorized key rotation by executing a self-call to
+`set_public_key` or `setPublicKey`. As with the STARK-curve and Secp256k1 accounts, the
+current key authorizes the outer account transaction and the new key signs a
+domain-separated ownership-acceptance message. Rotation keeps the same account address.
+Because the current key authorizes the outer transaction, rotating a lost or unavailable key
+requires an independent recovery mechanism. The upgradeable presets can adopt verifier changes at
+the same account address through a self-authorized class upgrade.
+
+### Build profile
+
+Build deployable Falcon preset artifacts from this repository with
+`scarb --release build -p openzeppelin_presets`. The workspace dev profile produces Falcon Sierra
+artifacts that cannot be lowered to CASM. Only the workspace's `target/release` Falcon preset
+artifacts are suitable for declaration. A consuming project that embeds the component must
+likewise use a declaration profile with inlining enabled.
+
+### Maintainer workflow: generated Falcon NTT sources
+
+The Falcon root tables, bit-reversal table, and unrolled production transform are derived and
+checked by `scripts/falcon_512/generate_ntt.py`. Regenerate them from the repository root and verify
+the checked-in output with:
+
+```sh
+python3 scripts/falcon_512/generate_ntt.py --write
+git diff --exit-code -- packages/account/src/falcon_512/ntt
+```
 
 ### Interfaces
 
 - [`ISRC6`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#ISRC6)
+- [`IFeltArrayDeployable`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#IFeltArrayDeployable)
+- [`IFeltArrayPublicKey`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#IFeltArrayPublicKey)
+- [`IFeltArrayPublicKeyCamel`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#IFeltArrayPublicKeyCamel)
 - [`ISRC9_V2`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#ISRC9_V2)
 
 ### Components
 
 - [`AccountComponent`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#AccountComponent)
 - [`EthAccountComponent`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#EthAccountComponent)
+- [`Falcon512AccountComponent`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#Falcon512AccountComponent)
 - [`SRC9Component`](https://docs.openzeppelin.com/contracts-cairo/3.x/api/account#SRC9Component)
diff --git a/packages/account/Scarb.toml b/packages/account/Scarb.toml
@@ -24,6 +24,7 @@ scarb.workspace = true
 
 [dependencies]
 starknet.workspace = true
+openzeppelin_corelib_imports = { path = "../corelib_imports" }
 openzeppelin_introspection = { path = "../introspection" }
 openzeppelin_interfaces = { path = "../interfaces" }
 openzeppelin_utils = { path = "../utils" }
@@ -36,6 +37,8 @@ openzeppelin_test_common = { path = "../test_common" }
 
 [features]
 fuzzing = []
+# Enables tests for the generated production NTT path; requires the release compiler profile.
+falcon_fast_tests = []
 
 [lib]
 

diff --git a/packages/account/src/falcon_512.cairo b/packages/account/src/falcon_512.cairo
@@ -0,0 +1,26 @@
+// SPDX-License-Identifier: MIT
+// OpenZeppelin Contracts for Cairo v4.0.0-alpha.1 (account/src/falcon_512.cairo)
+
+//! Falcon-512 SHAKE account component and verifier strategies.
+//!
+//! `Falcon512ShakeVerifier` validates the FALCON submission relation with a verifier-checked
+//! polynomial-product hint that reduces on-chain execution cost. `Falcon512ShakeDirectVerifier`
+//! recomputes the product on-chain. Both strategies use SHAKE-256 hash-to-point and
+//! contract-specific felt encodings; they are not FN-DSA (FIPS 206) implementations.
+//!
+//! `Falcon512AccountComponent` provides SRC6 account behavior and owner-authorized key rotation
+//! for canonical packed Falcon-512 public keys. Ready-to-deploy compositions are provided by the
+//! `openzeppelin_presets` package.
+
+pub mod account;
+pub(crate) mod falcon;
+pub(crate) mod hashing;
+pub(crate) mod ntt;
+pub(crate) mod packing;
+pub mod verifier;
+pub mod verifier_impls;
+pub(crate) mod zq;
+
+pub use account::Falcon512AccountComponent;
+pub use verifier::Falcon512SignatureVerifier;
+pub use verifier_impls::{Falcon512ShakeDirectVerifier, Falcon512ShakeVerifier};