Core Protocol
Pages grouped by this topic tag.
Rusty Kaspa Source ListContributionThe Source List groups Rusty Kaspa by responsibility: consensus, transaction validation, mining/mempool, P2P, RPC, indexes, wallet, database, txscript, and tests.Core Protocol Source PathCore ProtocolCreate the code-reading path for validation, proof of work, constants, difficulty, pruning, reachability, storage, and upgrade behavior.Activation, KIPs, And Release EvidenceCore ProtocolKIPs and upgrades are a status map, not an automatic statement of deployed behavior.DAA, Difficulty, And ActivationCore ProtocolDifficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs.Header, Body, And Virtual PipelineCore ProtocolThe consensus pipeline explains where headers, bodies, transactions, and virtual state are processed.P2P And IBDCore ProtocolP2P and initial block download connect a local node to the network and determine whether local evidence is useful.Proof Of Work And kHeavyHashCore ProtocolProof of work gives blocks an objective work signal; kHeavyHash and header checks belong to source-backed mining and validation pages.Pruning And Pruning ProofsCore ProtocolPruning is about keeping enough evidence for security and synchronization while bounding stored history.ReachabilityCore ProtocolReachability answers ancestry questions in a DAG and supports GHOSTDAG, pruning, and validation work.Rusty Kaspa Consensus MapCore ProtocolRusty Kaspa is the primary current implementation authority, but readers need a map before treating the repository as a flat list of files.Source Walkthrough ExercisesCore ProtocolExercises turn the Source List into contributor practice: trace one behavior from wiki claim to module to test evidence.Storage, Indexes, And State SurfacesCore ProtocolStorage and indexes expose state to tools, but indexer observation is not itself consensus authority.Supply And Emission Source PathContextSupply source paths map public claims to source constants and Kaspa documentation orientation.vProgs ZK PipelineToccataThe vProgs ZK pipeline connects transaction processing, batch aggregation, proof generation, journal/state transition, and settlement as tooling or architecture material, not as base-protocol authority.Source PathsSource PathsPublic source-path map for implementation, KIPs, docs, tooling, and research sources.Source RegistrySource PathsA compact public registry of the source classes used by the source-linked reference.Operations Source PathReadinessThe readiness operations source path maps public claims about wallets, nodes, mining, broadcast, and accepted evidence to the upstream files that can support them.Activation, Releases, And ParametersToccataActivation pages teach how to verify Toccata status without blending mainnet, testnet, and history.Source Path For Transaction ContributorsTransactionsTransaction contributors need a guided source order so a change does not silently break hashing, signing, mempool policy, RPC, or accepted evidence.Operations Source PathOperationsThe operations source path maps user symptoms to the files and tests that can support a current claim.Groth16 Kaspa Verifier Source PathToccataThe Kaspa Groth16 source path explains verifying key/proof data, public input arity, metering, parsing, and verification failure cases.RISC Zero Succinct Kaspa Verifier Source PathToccataThe RISC Zero Succinct source path is a verifier-specific review of image IDs, journal digest, seal, control proof, claim, and supported hash assumptions.ZK Source Path And Review PlaybookToccataThe ZK review playbook turns a claim into source work: docs, KIP, tags, costs, verifier source, tests, releases, and claim labels.