Salkutsan Certified Continuity Protocol Candidate

SCCP v0.1 is an independent research package for admissibility-certified state continuity. It combines established cryptographic primitives with a machine-checkable transition predicate and an authenticated continuity transcript.

It is not a new cipher and is not production-ready cryptography.

One-line model

standard AEAD + standard key derivation + signed admissibility certificate
+ parent-bound transcript = locally verifiable continuity record

The candidate state is:

Sigma_n = (id, n, q_n, K_n, h_n)

Every accepted successor binds the same identity, the next epoch, the observed parent head, a commitment to the next state and a domain-specific Admit result. Two different certified heads with the same (id, parent, epoch) are explicit fork evidence once both views are observed.

What this repository contains

• formal/CertifiedContinuity.lean: a small Lean 4 model proving strict epoch growth and rollback rejection under the successor relation.
• src/sccp.mjs: dependency-free Node.js reference code using Ed25519, HKDF-SHA-256 and AES-256-GCM from node:crypto.
• src/physical-anchor.mjs: CR-03 provider contract, receipt verification, rollback rejection and physical-fork evidence, plus an explicitly non-production software simulator.
• test/sccp.test.mjs: happy-path, mutation, rollback, fork and admissibility tests.
• test/physical-anchor.test.mjs: receipt, rollback, tamper and cloned-anchor fork tests.
• docs/THREAT_MODEL.md: the security boundary.
• docs/PRIOR_ART.md: standards and repositories on whose shoulders this candidate stands.
• docs/PROTOCOL.md: wire-level reference model.
• docs/PHYSICAL_ANCHOR.md: CR-03 mapping from the abstract continuity record to a TPM-class hardware root and independent witnesses.

Run

npm test
cd formal
lean -o CertifiedContinuity.olean CertifiedContinuity.lean
LEAN_PATH=. lean CertifiedContinuityAudit.lean

Research status

The reference implementation demonstrates binding and evidence semantics. It does not establish forward secrecy, post-compromise security, side-channel resistance, secure erasure, distributed fork discovery or production suitability. Those properties must come from reviewed protocols, implementations and independent cryptanalysis.

CR-03 adds a narrow hardware-provider boundary. A conforming provider must advance its protected epoch and sign the bound payload as one atomic operation. The included SoftwareAnchorSimulator is for deterministic development and attack tests only; it is not a hardware root of trust.

Русское чтение

SCCP v0.1 — независимый исследовательский пакет для сертифицированной непрерывности состояния. Он не заменяет стандартную криптографию, а связывает переход цифровой личности с проверяемым предикатом допустимости, родительской вершиной и аутентифицированным журналом.

Это не новый шифр и не готовый продукт защиты. Lean-срез доказывает только логические свойства заданного отношения наследования. Node.js-реализация показывает проверяемый протокол записи, но не доказывает криптографическую стойкость всей системы.

CR-03 добавляет узкий контракт физического якоря. Провайдер обязан атомарно увеличить защищённую эпоху и подписать связанный payload. Встроенный SoftwareAnchorSimulator предназначен только для разработки и моделирования атак и не является аппаратным корнем доверия.

Public reader: https://chertogi-razuma-research.kernelpanic888.chatgpt.site/readers/certified-continuity-protocol/

Author: Salkutsan Aleksey Anatolievich
ORCID: https://orcid.org/0009-0006-8717-0492