Protocol authority

Nockchain Protocol

A protocol-source trace for activation state, consensus-critical rules, release-track lineage, and the 014 Aletheia status drift that receipts must preserve instead of flattening.

Protocol API Docs Atlas Zorp Map

Commit

33ba97b1e206

Sources

Nous

Consensus

Aletheia

Priority Authority Sources

protocol-index

path

PROTOCOL.md

authority

tier-0-protocol-index

role

Canonical protocol index and active-upgrade selector.

evidence

If protocol guidance conflicts with workflow or crate docs, PROTOCOL.md and the linked upgrade specs win.

aletheia-014

path

changelog/protocol/014-aletheia.md

authority

specific-upgrade-spec

role

Consensus-critical ASERT, block-time, emissions, and coinbase split activation spec.

evidence

Frontmatter records status activated, consensus_critical true, and activation_height 65500.

status-drift-014

path

PROTOCOL.md

authority

consistency-alert

role

Visible status drift between the protocol index and 014 Aletheia spec frontmatter.

evidence

PROTOCOL.md lists 014 Aletheia as draft while changelog/protocol/014-aletheia.md frontmatter lists activated.

Release Track

nextScheduled

013 Nous final

latestConsensusCritical

014 Aletheia index=draft spec=activated

statusDrift

true

activationHeight

65500

Lifecycle Contract

statuses

draft, final, activated, superseded

activationHeightZero

activation_height = 0 means no consensus height trigger is recorded: usually a historical gap or rollout-gated operational activation.

maintenanceRule

When adding or updating any file in changelog/protocol/, PROTOCOL.md must be updated in the same change.

Summary

Motivation

Technical Specification

Activation

Migration

Backward Compatibility

Security Considerations

Operational Impact

Testing and Validation

Reference Implementation

Receipt Fields

docsAuthority

protocolSpec

protocolIndexStatus

specFrontmatterStatus

activationHeight

activationTarget

activationMode

consensusCritical

consensusRuleSurface

nodeUpgradeRequired

networkPartitionRisk

validationEvidence

upstreamCommit

upstreamRelease

zorpSource

Additional Sources

spec-format

path

changelog/protocol/SPECIFICATION.md

authority

protocol-spec-schema

role

Schema, lifecycle, and required-section contract for protocol upgrade specs.

evidence

Defines TOML frontmatter, lifecycle states, required sections, activation semantics, and maintenance expectations.

nous-013

path

changelog/protocol/013-nous.md

authority

specific-upgrade-spec

role

Next scheduled release-track upgrade: libp2p request-response generation 2.

evidence

Frontmatter records status final, consensus_critical false, activation_height 0, and activation_target 2026-Q2.

Operator Checklist

Do not flatten 014 Aletheia status until PROTOCOL.md and spec frontmatter agree.

Treat activation_height = 0 as rollout-gated or historical-gap context, not proof of no upgrade.

Attach the exact protocol spec path and upstream commit to any protocol-sensitive fakenet, Nockup, or VESL receipt.

Record consensusCritical, activationHeight, and networkPartitionRisk before interpreting post-activation mining or balance evidence.

Use crate READMEs only as scoped runtime/operator evidence after the Tier 0 protocol source is recorded.

docsAtlas

https://nocksperimental.com/api/nockchain/docs-atlas

syncGossipTrace

https://nocksperimental.com/api/nockchain/sync-gossip

zorpMap

https://nocksperimental.com/api/nockchain/zorp