Activation, Releases, And Parameters

What this page explains#

Activation pages teach how to verify Toccata status without blending mainnet, testnet, and history. This page sits in Toccata. It gives the topic a plain-language handle first, then shows the working idea, the mechanism, the source trail, and any limits that still matter. This category treats Toccata as a cluster of related changes rather than one feature. Transaction v1, compute budget, script pricing, lanes, sequencing commitments, covenants, and ZK have to be read together when an application depends on them.

The writing follows a simple Kaspa documentation pattern: answer the practical question first, then link outward for details. The closest public sources for this page are RK-RELEASE-V2-0-0, RK-RELEASE-V2-0-1, RK-PARAMS, RK-CONSTANTS, DOC-TOCCATA. Local notes can help choose what to explain, but public-facing references resolve to upstream websites, repositories, papers, release pages, or docs.

How to think about it#

The practical model starts by naming the layer that owns the topic: wallet use, node operation, consensus, transaction validation, Toccata script behavior, tooling, or research. From there, the page shows which public source can support the explanation and where the explanation becomes incomplete.

For Activation, Releases, And Parameters, the model is built around these anchors: release notes show rollout evidence; params and constants show source behavior; docs orient but may need source refresh; testnets are not mainnet evidence; Open Questions record conflicts rather than publishing guesses. This model is useful, but it does not encode every constant, branch, error type, or edge case. Those details belong in the source path and the source notes.

How it works#

1. release notes show rollout evidence. Toccata status is settled by source, params, release notes, and network scope together. Docs can introduce the feature cluster, but rollout wording needs release evidence and source paths. KIP or PR-shaped details remain proposed until they are merged, implemented, and tied to the relevant network.

2. params and constants show source behavior. Toccata status is settled by source, params, release notes, and network scope together. Docs can introduce the feature cluster, but rollout wording needs release evidence and source paths. KIP or PR-shaped details remain proposed until they are merged, implemented, and tied to the relevant network.

3. docs orient but may need source refresh. Source-review pages are practical maps. They start from one claim, identify the owning subsystem, inspect data structures and serialization, follow validation or execution, check tests and release context, and then write down what remains unresolved. The page is useful only if it says both what a source proves and what it does not prove.

4. testnets are not mainnet evidence. Readiness pages are evidence gates. A testnet result is useful only with network name, date, release or branch, node/wallet/tool versions, and accepted evidence. Release notes and source paths support stronger claims; old testnet observations remain historical unless refreshed.

5. Open Questions record conflicts rather than publishing guesses. Toccata pages explain how transaction v1, compute budget, lanes, script pricing, sequencing commitments, covenants, and ZK fit together. The page marks which part is source behavior, which part is docs orientation, and which part is readiness-sensitive.

This mechanism section separates current release/source details from proposal-shaped KIP text. Transaction v1, script pricing, lanes, sequencing commitments, covenants, and ZK are related, but each has its own source boundary.

How to check it#

When using this page for Toccata material, separate deployed release/source details from open KIP or PR-shaped details. Transaction v1, lanes, sequencing commitments, script pricing, covenants, and ZK each need their own source boundary before the page presents them as current behavior.

Related Pages#

• sequencing-commitments
• toccata
• toccata-decision-guide