In brief
This page is source-sensitive. Treat application, covenant, proof, and readiness wording as bounded by the listed public sources and Open Questions.
What this page explains#
User operation pages teach payload encoding, gas, lane namespace, and ordering evidence. This page sits in SilverScript, vProgs, And Based Apps. 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 distinguishes tooling convenience from protocol behavior. SilverScript can author or lower scripts, vProgs can organize based-app execution, and settlement/indexer responsibilities remain part of the application design.
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 DOC-TOCCATA-BASED-APPS, RK-SUBNETS, RK-TX-VALIDATION, RK-BODY-VALIDATION, KIP-0021. 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 User Ops, Payloads, And Lanes, the model is built around these anchors: lane choice is an application design decision; payload formats need deterministic decoding; gas and subnetwork fields must survive protocol and RPC paths before wallet or SDK claims are made; reserved lane claims need current source checks; observing lane order is evidence work. 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. lane choice is an application design decision. Toccata-era transaction fields are application surfaces, so the guide must trace them through structs, serialization, hashing, signing, RPC, wallet tooling, mempool policy, and accepted evidence. The risk is not only invalid construction; it is a tool silently dropping or misunderstanding a field that the application relies on.
2. payload formats need deterministic decoding. Toccata-era transaction fields are application surfaces, so the guide must trace them through structs, serialization, hashing, signing, RPC, wallet tooling, mempool policy, and accepted evidence. The risk is not only invalid construction; it is a tool silently dropping or misunderstanding a field that the application relies on.
3. gas and subnetwork fields must survive protocol and RPC paths before wallet or SDK claims are made. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
4. reserved lane claims need current source checks. Toccata-era transaction fields are application surfaces, so the guide must trace them through structs, serialization, hashing, signing, RPC, wallet tooling, mempool policy, and accepted evidence. The risk is not only invalid construction; it is a tool silently dropping or misunderstanding a field that the application relies on.
5. observing lane order is evidence work. Toccata-era transaction fields are application surfaces, so the guide must trace them through structs, serialization, hashing, signing, RPC, wallet tooling, mempool policy, and accepted evidence. The risk is not only invalid construction; it is a tool silently dropping or misunderstanding a field that the application relies on.
This mechanism section separates authoring tools, runtime organization, proof workflow, indexer replay, and L1 settlement. Tooling convenience does not become protocol behavior without upstream source support.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check lane choice is an application design decision. | Read DOC-TOCCATA-BASED-APPS, RK-SUBNETS, RK-TX-VALIDATION; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 2 | Check payload formats need deterministic decoding. | Read DOC-TOCCATA-BASED-APPS, RK-SUBNETS, RK-TX-VALIDATION; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 3 | Check gas and subnetwork fields must survive protocol and RPC paths before wallet or SDK claims are made. | Read DOC-TOCCATA-BASED-APPS, RK-SUBNETS, RK-TX-VALIDATION; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 4 | Check reserved lane claims need current source checks. | Read DOC-TOCCATA-BASED-APPS, RK-SUBNETS, RK-TX-VALIDATION; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 5 | Check observing lane order is evidence work. | Read DOC-TOCCATA-BASED-APPS, RK-SUBNETS, RK-TX-VALIDATION; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
When using this page for tooling or based-app work, identify which layer authors scripts, observes ordering, computes state, produces proof material, submits settlement, and recovers after restart. Tool output and runtime architecture need L1 source or settlement evidence before they become protocol claims.
Related Pages#
- based-apps
- silverscript-vprogs-based-apps
- based-lane-starter