Research Edge
Pages grouped by this topic tag.
DAGKnight Research EdgeConsensusDAGKnight belongs in research edge unless current implementation and release evidence supports stronger status.Integration Readiness ChecklistDeveloper IntegrationReadiness is a checklist of evidence: fields preserved, network selected, source current, tests run, accepted evidence captured, and recovery paths tested.Open Research GapsOpen Research GapsVisible unresolved source checking work that blocks a final authoritative release.Tooling Readiness And Production CaveatsToccataTooling readiness pages keep moving APIs, pre-check tools, wallet support, and mainnet safety gates visible.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.Testnets And Production ReadinessReadinessTeach network selection, release checks, explorer/API observations, wallet signing, broadcast safety, and production gates with explicit freshness labels.API And Explorer Observation ChecksReadinessExplorer/API pages explain observation value and limits.Broadcast SafetyReadinessBroadcast safety separates local transaction construction from mempool admission and accepted network state.Production ReadinessReadinessProduction readiness is an evidence gate, not a confidence word.Readiness TroubleshootingReadinessReadiness troubleshooting maps symptoms to likely layers before making claims.Release And Version ChecksReadinessVersion checks prevent stale guide prose from turning into unsafe operation.TestnetsReadinessTestnets are environments for testing network behavior, not proof of mainnet behavior.TN10, TN11, And Historical Testnet ContextReadinessHistorical testnet pages preserve context without turning old network behavior into current instructions.TN10, TN11, And TN12 ReadinessReadinessTN readiness pages keep TN10, TN11, and TN12 evidence from blending.TN12 Covenant TestnetReadinessTN12 covenant-testnet guidance is source-sensitive and must name network selection, branch or release assumptions, and evidence checks.Verification And EvidenceReadinessVerification pages define which observations support which claim and what still needs source review.Wallet Signing ReadinessReadinessWallet signing readiness checks that a wallet preserves intent through build, sign, decode, submit, and observe.ZK, Groth16, And RISC Zero SuccinctToccataTeach inline ZK as a covenant-adjacent proof verification path, while separating proof validity from whole state-transition validity.ZK First Contact And VocabularyToccataZK pages begin by defining proof, statement, prover, verifier, public input, witness, circuit, zkVM program, receipt, journal, tag, and precompile.Inline ZK Covenant ModelToccataInline ZK is best taught inside the covenant loop: current UTXO, proof, script verification, successor output.OpZkPrecompile Tags And CostsToccataTags and costs are high-risk source claims because they decide which verifier runs and whether the transaction has enough budget.Groth16 OverviewToccataGroth16 background explains circuits, witnesses, proving keys, verifying keys, proof bytes, public inputs, and trusted setup context.RISC Zero Succinct OverviewToccataRISC Zero Succinct pages explain zkVM receipts, image IDs, journal commitments, seals, and the difference between upstream concepts and Kaspa stack expectations.Proof Binding To Covenant StateToccataProof binding connects verifier success to the covenant state transition the app actually cares about.Negative Cases And Failure MatrixToccataA failure matrix makes ZK safer by naming what must fail.Groth16 Transition StarterToccataThe Groth16 starter is a draft implementation checklist for binding proof output to a covenant transition without citing local lab files as authority.RISC Zero Succinct Transition StarterToccataThe RISC Zero starter is a conceptual checklist until a concrete public upstream recipe is verified, and it makes image ID, journal digest, receipt/seal, and verifier boundaries explicit.Testing Evidence And ReadinessToccataReadiness labels prevent local proof output from being mistaken for production evidence.ZK FAQ And MisreadingsToccataThe ZK FAQ answers the mistakes that cause unsafe designs: valid proof is not whole transition validity, local proof output is not network readiness, and zkVM verification is not on-chain program execution.