Release v0.9.0 – parallel notarizations, wildcard support, Ledger Compliance support

We’re more than happy to announce the v0.9.0 release of vcn. The latest news around the Solarwinds hack and the addition of malicious code to software updates (incl. valid code signing) shows again the importance of solid alternatives to digital signatures.

This release adds:

  • parallel notarizations for the same account
  • wildcard support for files and directories
  • timestamp is always returned when authenticating
  • support for CodeNotary Ledger Compliance, the high-speed immutable ledger that runs in any cloud or on-premise.

Thanks again to the community for great feedback!


[v0.9.0] – 2020-12-08

Bug Fixes

  • restore verification with the highest level available when not logged
  • fix integration tests and add circleci job for go 1.15
  • fix dist release go1.15.6
  • fix ledger-compliance-go dependency
  • pkg/api: swap signerID position with the hash in the vcn lc key format
  • pkg/api: fix artifact status json unmarshall
  • pkg/cmd: don’t track untrusted verification
  • pkg/cmd/inspect: fix inspect ux, examples and errors
  • pkg/cmd/verify: fix empty signerid handling
  • pkg/meta: add apikey env var


  • bump sdk version, remove useless package
  • bump lc sdk version
  • add swagger.json
  • bumb version of go-ethereum and smart contracts
  • fix inspect full history message
  • upgrade go version to 1.15 and sdk
  • remove all whitespaces from otp
  • pkg/cmd: show status unknown if tamper is detected
  • pkg/cmd/serve: handle missing api key error
  • pkg/extractor: fix typo
  • pkg/extractor/wildcard: remove max notarization limit
  • pkg/extractor/wildcard: improve max notarized files number with wildcard

Code Refactoring

  • change api in order to make atomic indexing of notarized items in lc
  • pkg/extractor: handle array of artifacts instead of a single one in extractor


  • vcn accepts a certificate to setup a tls connection
  • if no limit or filter are submitted inspect return last 100 items
  • add multiple notarizations capability with wildcard
  • add wildcard extractor
  • add serve LC inspect
  • improve inspect result with timestamp for each element
  • add verify filter by LC signerID. fix #104
  • add vcn LC login. fix #103
  • partial parallel notarizations support
  • add inspect for ledger compliance
  • add otp_empty environment var
  • add LC operations for vcn server
  • add verify asset on ledger compliance
  • add ledger compliance authentication and notarization
  • Add otp support. close #87 close #88
  • pkg/cmd: add inspect api
  • pkg/cmd/inspect: improve inspect in lc
  • pkg/cmd/verify: manage verify by hash in lc mode


Docker image


File SHA256
codenotary_vcn_v0.9.0_setup.exe 638efd932aabc5770723eb844329983d64d8a2260976a6f9750a73003f8a34d5
vcn-v0.9.0-darwin-amd64 b34ea15a46565f3d5a88a12835c9ae8d56cc4999a1b99083f6783cffc5cf934b
vcn-v0.9.0-linux-amd64 90b07343c44980e8dbad1d59c2a7a2b9266ac94b31a5c5ad42abe47d0f9de3b6
vcn-v0.9.0-linux-amd64-static cd7acd10d271aab4c97bdd22ce3627f2030c10859fd1f1e82bbe49d8f1c2c140
vcn-v0.9.0-linux-arm64 7d9cd1292ac7756879cad902fad8510263746b5c32d5e2471bff540ad8c79a05
vcn-v0.9.0-linux-ppc64le 14d2f04625d2b37300713449bda80d107367ad664dbc8f074a59363985f4203c
vcn-v0.9.0-linux-s390x 8f7402ad58f8a03391992cd01806a839e1ec66007457970a8b7ca03064e5944e
vcn-v0.9.0-windows-amd64.exe efe63be40f7cfb688ebb4ce477bcc07d9641e6772d6ebea22133d233e9cbb6f1

CNIL Metrics & Logs

Self-Hosted performance monitoring and compliant log analysis for VMware vSphere, container and much more.


Built on the fastest immutable ledger technology. Open Source and easy to use and integrate into existing application.

Codenotary Cloud

Trusted CI/CD, SBOM and artifact
protection with cryptographic proof.
One CLI to manage all.

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


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.).


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


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.


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


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, …)


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


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.


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


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.


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.