Engineering

The major engineering efforts inside Kogany: what each one changes, why it matters, and where it stands.

  1. 01
    Consensus · in testing

    Three Node Lines, One State Hash

    Two C++ nodes and one Rust node must compute the same vault and Yellowback state at every block. The Rust traps that threaten it are map order, overflow, concurrency and checkpoints, and each has a rule. Kogany is not yet a qualified Ycash node line.

    Read about three node lines, one state hash
  2. 02
    Consensus · in testing

    Applying Vault Acts in Order on a Concurrent Verifier

    Zakura verifies the transactions in a block in parallel. Vault acts read and change shared state, so Kogany runs them in sequence during contextual validation, against a snapshot of the parent block's state.

    Read about applying vault acts in order
  3. 03
    Cryptography · in testing

    Post-Quantum Signatures in Script

    One opcode, OP_CHECKPQSIG, verifies two schemes: SLH-DSA-SHA2-128s and FN-DSA-512 (Falcon-512). Vault owners sign with SLH-DSA by default, YED holders with FN-DSA-512, and plain YEC can sit at a post-quantum address of either scheme, whose third character names it (sqf…, sqs…). Signatures and keys are pushed in canonical 520-byte chunks, and Kogany verifies with byte copies of the C++ nodes' vendored C.

    Read about post-quantum signatures
  4. 04
    Wallet · in testing

    A Wallet Beside the Node

    ycashd keeps its wallet inside the node; Kogany doesn't. yewd serves ycashd's wallet RPCs from the YEW wallet core, apart from a few listed exceptions such as the watch-only imports, and waits until it has caught up with the node before it answers. It has no release yet: it is built from source.

    Read about yewd