• Language

  • Non-English translations are machine-generated.

  • Language Preferences
  • Theme
Sign In

Knowledge Base

Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.

Tagged: standard

12
Library
Ed25519 Deep Dive Addendum (r/crypto) r/crypto discussion of Cendyne's Ed25519 Deep Dive Addendum, covering inconsistent signature-validation criteria across libraries, strong unforgeability, cofactored verification, non-canonical encodings, and the design history of EdDSA. EdDSA (Wikipedia) Wikipedia's overview of the Edwards-curve Digital Signature Algorithm: twisted Edwards curves, Schnorr variant, deterministic nonces, Ed25519 and Ed448, key and signature sizes, and standardization. Interoperable Randomness Beacons (NIST CSRC) NIST CSRC project defining an interoperable public randomness beacon that emits signed, hash-chained 512-bit full-entropy pulses every 60 seconds over a REST API, with the Beacon 2.0 format and NISTIR 8213 reference. Linked Timestamping (Wikipedia) Wikipedia overview of linked timestamping: hash chains and Merkle trees that link time-stamps into a tamper-evident order, avoiding private keys, with history, standards, and blockchain publication. Patents and Caveats as Priority Instruments How patent filings and confidential caveats used a neutral state office to record a dated priority for an invention: an institutional timestamp and proof-of-existence marker, ancestor to modern cryptographic timestamping. RFC 6962: Certificate Transparency IETF Experimental RFC defining Certificate Transparency: publicly auditable append-only Merkle Hash Tree logs of TLS certificates, with SHA-256 leaf/node domain separation, inclusion and consistency proofs, SCTs, and Signed Tree Heads. RFC 8032: Edwards-Curve Digital Signature Algorithm (EdDSA) IRTF/CFRG specification of EdDSA deterministic Schnorr signatures over twisted Edwards curves, defining Ed25519 (SHA-512) and Ed448 (SHAKE256), with encoding, verification, and test vectors. RFC 8785: JSON Canonicalization Scheme (JCS) RFC 8785 defines the JSON Canonicalization Scheme (JCS), a deterministic serialization of I-JSON data for reliable hashing and signing, using ECMAScript number formatting, UTF-16 property sorting, and UTF-8 output. RFC 9562: Universally Unique IDentifiers (UUIDs) IETF standard defining 128-bit UUIDs, obsoleting RFC 4122 and adding versions 6, 7, and 8 for time-ordered, database-friendly, sortable identifiers with CSPRNG and privacy guidance. Secure Hash Standard (SHS) FIPS PUB 180-4, the NIST Secure Hash Standard specifying SHA-1 and the SHA-2 family (SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, SHA-512/256) message-digest algorithms. Taproot: SegWit version 1 spending rules (BIP 341) BIP 341 defines Bitcoin Taproot: SegWit version 1 outputs using Schnorr signatures and a Merkle-branch script commitment (MAST) with key-path and script-path spending. Things that use Ed25519 - IANIX IANIX catalog tracking real-world deployment of the Ed25519 EdDSA signature scheme across protocols, operating systems, hardware security modules, and cryptographic libraries.