toUuid(seed): 128-bit id from four 32-bit hashes≈SHA-256 / BLAKE3 cryptographic hashSame idea (content -> fixed-size id); the site hash is fast and deterministic but not collision/preimage resistant.
Crypto Compare — показан в пълни детайли, с неговото доказателство: детерминиран адрес по съдържание, преизчислим от името на компонента.
криптография · сравнение
toUuid(seed): 128-bit id from four 32-bit hashes≈SHA-256 / BLAKE3 cryptographic hashSame idea (content -> fixed-size id); the site hash is fast and deterministic but not collision/preimage resistant.
merge(a,b) = toUuid("a:b"), order-sensitive≈Merkle node H(left ‖ right)Order-sensitivity matches a real Merkle node; security still depends on the underlying hash, which here is non-cryptographic.
merkleFold(leaves): tree of merges≈Merkle tree (RFC 6962, Certificate Transparency)Identical structure and inclusion-proof idea; the site proves structure and recomputability, not cryptographic soundness.
foldBlockchain: hash-linked blocks≈Hash chain / blockchain (PoW or BFT consensus)Tamper-evident links, but no consensus, no proof-of-work, single-writer — a ledger shape, not a distributed ledger.
content-addressed UUID stream≈Git (SHA-1 -> SHA-256), IPFS multihashSame content-addressing principle as Git/IPFS; those use vetted hashes, the site uses a fast non-crypto one.
build-time model seal + git-history fold≈Reproducible builds, code signing, SigstoreReproducibility and tamper-evidence are real; there is no signing key or trusted authority, so it is evidence, not attestation.
Честно: сгъването тук споделя ФОРМИТЕ на криптографията (съдържателно адресиране, Merkle дървета, хеш вериги), но използва 128-битов НЕкриптографски хеш. Дава детерминирано адресиране и доказателство за подправяне — не устойчивост на колизии. За враждебна сигурност използвай SHA-256/BLAKE3.
✓ доказано · адрес по съдържание 22553704-897f-8a4f-b7ef-0075578e1475 — деклариран, поставен, монтиран и преизчислим от името на компонента.