awesome-repositories.com
Blog
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

5 repositorios

Awesome GitHub RepositoriesCryptographic Commit Logs

Commit logs that use cryptographic hashing to ensure the immutability and verifiability of the record history.

Distinct from Distributed Commit Logs: Adds the requirement of cryptographic verifiability to the standard distributed commit log concept.

Explore 5 awesome GitHub repositories matching data & databases · Cryptographic Commit Logs. Refine with filters or upvote what's useful.

Awesome Cryptographic Commit Logs GitHub Repositories

Encuentra los mejores repositorios con IA.Buscaremos los repositorios que mejor coincidan usando IA.
  • codenotary/immudbAvatar de codenotary

    codenotary/immudb

    8,982Ver en GitHub↗

    immudb is a tamperproof database that maintains an immutable record of entries using cryptographic commit logging. It ensures verifiable database integrity by utilizing Merkle trees to generate membership and consistency proofs that detect unauthorized data alterations. The system employs a multi-model storage engine that unifies key-value, document, and relational data structures within a single immutable backend. It provides compatibility with the PostgreSQL wire protocol, allowing it to integrate with standard SQL clients, ORMs, and database tools. The project covers broad capabilities in

    Maintains an immutable record of data using a cryptographic commit log to ensure a verifiable history.

    Goauditablecompliancecryptographic
    Ver en GitHub↗8,982
  • orbitdb/orbit-dbAvatar de orbitdb

    orbitdb/orbit-db

    8,791Ver en GitHub↗

    Orbit DB is a decentralized NoSQL database that utilizes conflict-free replicated data types to ensure eventual consistency across a network of nodes. It functions as a peer-to-peer data store that uses IPFS for content-addressing and synchronization, allowing for the maintenance of application state without a central server or authority. The system is built upon a cryptographically verifiable, immutable operation log, which serves as the foundation for custom decentralized data models. This architecture enables the implementation of various data storage patterns, including JSON document stor

    Uses a cryptographically verifiable append-only commit log as the foundation for all data models.

    JavaScript
    Ver en GitHub↗8,791
  • orbitdb/orbitdbAvatar de orbitdb

    orbitdb/orbitdb

    8,737Ver en GitHub↗

    OrbitDB is a decentralized data storage system that enables the creation of serverless databases residing across a network of peers. It functions as a peer-to-peer database that integrates with a content-addressed storage layer to distribute and replicate data without a central server. The system utilizes conflict-free replicated data types to ensure eventual consistency and state convergence across distributed nodes. It maintains an immutable record of updates using a directed acyclic graph to preserve causal ordering and cryptographic integrity. Access is managed through a decentralized ide

    Uses a Merkle-DAG as a cryptographic commit log to maintain a verified causal order of updates.

    JavaScriptcrdtdatabasedecentralized
    Ver en GitHub↗8,737
  • spaceandtimefdn/sxt-proof-of-sqlAvatar de spaceandtimefdn

    spaceandtimefdn/sxt-proof-of-sql

    5,423Ver en GitHub↗

    Este proyecto es un motor de base de datos verificable que proporciona un sistema de prueba criptográfica SQL para asegurar la integridad de la información almacenada y su recuperación. Funciona como un almacén de datos que lleva pruebas y utiliza compromisos criptográficos para prevenir la manipulación de datos y garantizar que los resultados de las consultas sean precisos. El sistema genera pruebas de conocimiento cero para proporcionar evidencia matemática de que una consulta SQL se ejecutó correctamente sin requerir una re-ejecución completa del proceso. Estas pruebas criptográficas pueden exportarse para validación on-chain, permitiendo que contratos inteligentes o terceros verifiquen los resultados de la base de datos de forma confiable. El motor incluye un procesador de consultas SQL analíticas de alto rendimiento capaz de ejecutar agregaciones y filtros complejos sobre millones de filas con tiempos de respuesta inferiores a un segundo. Mantiene un pipeline de ingesta de datos seguro que crea hashes a prueba de manipulaciones durante la entrada para asegurar la integridad del estado de la base de datos.

    Creates tamper-proof hashes during data entry to ensure the integrity of the database state.

    Rust
    Ver en GitHub↗5,423
  • google/trillianAvatar de google

    google/trillian

    3,736Ver en GitHub↗

    Trillian is a distributed, multi-tenant verifiable data store that maintains cryptographically verifiable logs and maps using Merkle tree structures. It functions as a scalable backend for transparency logs, providing a system where data integrity is ensured through append-only records and mathematical proofs of inclusion and consistency. The system distinguishes itself by decoupling core storage from application-specific logic through a personality layer, which handles admission criteria and data canonicalization. It employs a consensus-based leader election mechanism for high availability a

    Creates append-only data stores using Merkle trees to ensure records cannot be altered or deleted without detection.

    Gocertificate-transparencymerkle-tree
    Ver en GitHub↗3,736
  1. Home
  2. Data & Databases
  3. Distributed Commit Logs
  4. Cryptographic Commit Logs

Explorar subetiquetas

  • Append-Only Consistency ProofsProofs demonstrating that a new version of a cryptographic log is a valid extension of a previous version. **Distinct from Cryptographic Commit Logs:** Specializes cryptographic commit logs by focusing specifically on the consistency proof between different log versions.
  • Commitment-Based IngestionProcesses for generating cryptographic commitments during data entry to secure database state. **Distinct from Cryptographic Commit Logs:** Focuses on the ingestion phase creating commitments rather than the log of changes itself.