Established foundations.
Evaluate standardized hash-based signatures, beginning with SLH-DSA, alongside Ethereum smart-account architecture.
Explore the studio
ETHEREUM / POST-QUANTUM ACCOUNTS
Stronger authorization. Considered recovery.
A clear path to what comes next.
Protocol in development · Interactive planning preview
01 / THE APPROACH
SECURITY THAT CAN EVOLVEOwning an asset means controlling what happens next. That control should survive a change in the mathematics behind it.
Aftercurve is being designed to help Ethereum accounts adopt hash-based authorization, keep recovery deliberate, and make every step of migration inspectable.
Explore the foundations ↗02 / THE SYSTEM
Architecture notes ↗Four connected capabilities.
One considered security lifecycle.

Map the paths that can move assets or change account rules. The planned explorer distinguishes observed permissions from dependencies that still need review.
04 / FIRST PRINCIPLES
THE DETAILS ARE THE DIFFERENCEThe work is in the authorization paths, the recovery rules, and the assumptions that remain.
Read the security boundaries ↗Evaluate standardized hash-based signatures, beginning with SLH-DSA, alongside Ethereum smart-account architecture.
Transfers, recovery, and upgrades belong in the same threat model. Protection is only as strong as the permissions around it.
Prove destination control. Rehearse recovery. Review supported assets. Start with a small transfer.
05 / THE PATH FORWARD
BUILT IN THE OPEN, STEP BY STEPEach stage has a clear purpose.
Security claims follow the evidence.
Brand, architecture notes, and an interactive planning studio. Establish the account model and its security boundaries.
FOUNDATIONS ↗Implement a testnet account, signing flow, recovery rehearsal, and verifier benchmarks against known test vectors.
TESTNET ↗Independent cryptographic and contract review, published limitations, and a controlled path to mainnet use.
REVIEWED RELEASE ↗A FEW IMPORTANT QUESTIONS
The intended scope is authorization inside dedicated Ethereum smart accounts: who may transfer assets, recover access, or change account rules. Contract implementation and independent review are still ahead.
No. This release introduces the brand, architecture, and a local planning studio. It does not deploy an account, sign transactions, or accept deposits.
No. Account authorization is one layer. Ethereum consensus, data commitments, application contracts, and asset issuers have their own dependencies. Aftercurve's scope must remain explicit.
You can plan for an existing address in the studio. Actual protection would require moving supported assets or control to a dedicated account with verified authorization rules. Merely connecting a wallet would not change its security.
OWNERSHIP, BEYOND THE CURVE.