immudb-release-0-9-0-rc2

v0.9.0 Release Candidate 2 is out. The next release candidate of immudb 0.9.0 that integrates our new embeddable cryptographic-proof storage engine is available.

v0.9.0 is 7 times faster data writes than the former version 0.8.0 and instant cryptographic proof!

immudb v0.9.0 Release Candidate 2

Here are the changes since Release Candidate 1:

Changelog

Bug Fixes

  • cmd/immuadmin/command: fix unit tests
  • cmd/immuclient: fix unit tests
  • embedded/tbtree: sync GetTs to prevent data races
  • pkg/api: change order of validations when checking state signature

Changes

  • adapt coverage to the new server implementation
  • fix immuserver mock
  • cmd/immuadmin: disable stats and removed print tree command
  • cmd/immuclient: print verified label when executing safereference
  • pkg/client: update service mock to new API
  • pkg/database: add input validations during verifiable set
  • pkg/database: implements History using lock-based operation

Code Refactoring

  • uniform server and client tests
  • improving buffconn server with splitting start method in initialization and start

Features

  • embedded/store: implements lock-based History without requiring snapshot creation
  • pkg/client: update auditor implementation to new server API
  • pkg/client: implementation of client-side verifiedZAdd
  • pkg/client: implements VerifiedSetReference
  • pkg/database: implementation of verifiableZAdd
  • pkg/database: implementation of VerifiableSetReference

Release Source:
https://github.com/codenotary/immudb/tree/v0.9.0-RC2

Downloads

Docker image
https://hub.docker.com/r/codenotary/immudb

Immudb Binaries

File SHA256
immudb-v0.9.0-RC2-darwin-amd64 c16f1a762c7460fe66df2490a5ac5f1e4eb662584b63334eddf78e90fe4147b4
immudb-v0.9.0-RC2-linux-amd64 45fc2fe6407d63f35dfa7a7d9b864acb9b0fe81e3ca684b20f50be1809830e06
immudb-v0.9.0-RC2-linux-amd64-static 2f5b895d1ca745ec1ff57bb238ba9420891f1c1201c29b8efef1e203d86623ab
immudb-v0.9.0-RC2-linux-s390x c2c78756fc701627e46735a2fc7c5c1afbc99e5a26e7b9a60e763ec7115ea422
immudb-v0.9.0-RC2-windows-amd64.exe 26ab5c6d267e9f71d79b3ea2633cfa103084e56d2f5da1987e3dca417f8564e7

Immuclient Binaries

File SHA256
immuclient-v0.9.0-RC2-darwin-amd64 473050e446741a6147ef365192f3599a70e8b4d176e9068be5c6d5895f086110
immuclient-v0.9.0-RC2-linux-amd64 2d0c18ef6f827ffe0bb28350618f890260997334dc3fba50040af9fdd14f0375
immuclient-v0.9.0-RC2-linux-amd64-static 504365eeb2cec1349f56fe9a64ba4c0bb052a7eaf3574d488fbfb9c0708846bc
immuclient-v0.9.0-RC2-linux-s390x 2832f468cf951adf030401f436338b067f8c4d6dab043d4cf7e850d2e74e7b19
immuclient-v0.9.0-RC2-windows-amd64.exe 11c3611410ada6b823759b3fe1ff71e3318901d5d9d903606a62ec5357bf8616

Immuadmin Binaries

File SHA256
immuadmin-v0.9.0-RC2-darwin-amd64 51302ba08a291a384a0b966cd7bcc6dbb29f94546888e105db0771ec1d19389c
immuadmin-v0.9.0-RC2-linux-amd64 223248531930710721933df915821b230bfd1de0f25ff32a3dfbb3259b782095
immuadmin-v0.9.0-RC2-linux-amd64-static 3fb1a05ad1a73e46fa9804ffa541e3d93f8f6beaff485fdb1a7bf3dd53fe1b3a
immuadmin-v0.9.0-RC2-linux-s390x 0332f5fc773eb93478facf02641dbfcbf51f0a5a73146288d42fa6f77b7e1d3a
immuadmin-v0.9.0-RC2-windows-amd64.exe fac79bad8285e0167a06c2a7a5ae8e5e8543ddd431d75a67179fe2cc1b6cd658

immudb

BUILT ON THE FASTEST
IMMUTABLE LEDGER
TECHNOLOGY

Open Source and easy to use in new applications and easy to integrate into existing application.

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.