Mining
Pages grouped by this topic tag.
Node Miner Template EvidenceWorking Model BridgesHow node operation, mempool policy, block templates, and miner work relate.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.Proof Of Work To blockDAG To GHOSTDAGFirst ContactA bridge from ordinary proof of work intuition into Kaspa's graph and ordering vocabulary.Wallet, Node, Miner, Developer PathsFirst ContactThe first practical branches through the guide and the evidence each branch needs.Minimal dApp TemplatesToccataTemplate pages organize counter, vault, ZK transition, based lane, and dice-style lessons into source-labeled starters.Block Templates And Transaction SelectionTransactionsBlock templates turn node state and mempool candidates into miner work.Wallets, Nodes, And MiningOperationsConnect user-facing operation with the node, wallet, mempool, P2P, and block-template paths that make a workflow real.Docker And Self-Hosted NodesOperationsSelf-hosted and Docker node pages explain deployment surfaces while keeping image tags and commands freshness-sensitive.Mempool And Block TemplatesOperationsThis page bridges operations and protocol source: a node may admit a transaction, but miners still need a valid block template and consensus still decides acceptance.Message Signing And KIP-0005OperationsMessage-signing support is treated as feature-specific wallet behavior that needs source and KIP evidence before current claims are made.MiningOperationsMining joins node state, block template construction, and proof of work search. It should be explained without profitability or hype framing.Mining Hardware And High-Staleness CatalogsOperationsMining hardware, hashrate tables, pools, and profitability references are volatile catalog material, not durable protocol education.Mining TroubleshootingOperationsMining troubleshooting separates node sync, template construction, miner connection, proof-of-work attempts, pool policy, and accepted block evidence.Node Sync, Logs, Ports, And IndexesOperationsNode sync, logs, ports, and indexes are the practical evidence surfaces operators inspect before trusting local state.NodesOperationsA node is the local participant that syncs, validates, communicates with peers, serves APIs, and provides the state surface wallets and miners depend on.Operational TroubleshootingOperationsTroubleshooting is symptom-led: the first job is to identify whether the failure lives in wallet, node, network, mempool, miner, indexer, or source freshness.P2P And IBDOperationsP2P and IBD explain how a node becomes useful by connecting to peers and catching up to network state.Setting Up A CLI NodeOperationsThe CLI node page turns Kaspa documentation operation flow into a source-checked checklist.Setting Up A CLI WalletOperationsThe CLI wallet guide follows an operation-guide shape: prepare, create or import, back up, connect to a node, build a transaction, sign, submit, and verify.Solo And Pool Mining FlowOperationsSolo and pool mining are explained as different operational routes from block templates to proof-of-work attempts and payout evidence.Operations Source PathOperationsThe operations source path maps user symptoms to the files and tests that can support a current claim.Wallet Roundtrip EvidenceOperationsWallet roundtrip evidence checks whether intent survives build, signing, decoding, submission, and accepted-state observation.Wallet Safety And BackupOperationsWallet safety pages focus on backup, seed handling, wallet files, network selection, and avoiding accidental loss of authority.Wallet TroubleshootingOperationsWallet troubleshooting maps symptoms to wallet file, daemon, node connection, network, UTXO index, signing, and broadcast layers.WalletsOperationsA wallet is best understood as key and transaction workflow software, not as the place where coins physically live.