polish-artist-uses-codenotary

We’re excited to share the news that we support Aleksandra Jozefow, a sculptor from Poland. From now on, all of her artworks will be immutably authenticated using CodeNotary, so that everyone can verify the certificate and the origin.

Aleksandra Jozefow, Gdansk (Poland) based Sculptor

The year is 2021 and the Fourth Industrial Revolution is in full swing.

Within the European Artistic community, there is a growing sense that, across artistic disciplines, dramatic events are unfolding; that ultimately, only the artists who will have understood the importance of the fourth industrial revolution's technological stack, and will have done something about it, will remain relevant.

Artists, clinging to Traditionalism (as can be shown, for example, by their very vocal opposition to Non-Fungible Tokens) are hesitant to fully embrace Industry 4.0.

As a sculptor, I have been looking for creative ways to integrate a very promising Industry 4.0 technology in my workflow: Blockchain Technology.

When a sculpture is completed and sold, a paper-based certificate of authenticity is issued by me and given to the buyer. This certificate states that only one copy of this work exists, that it is authentic.

But, I thought, don't Blockchain or similar technologies provide a better way to do this? Why not authenticate sculptures cryptographically from everywhere in the world?

As soon as I saw and tried CodeNotary's solution (www.codenotary.com), I understood this was a powerful tool, and one I wanted to integrate in my workflow.

A sculpture's characteristics such as: name, materials used, year, specifications such as size and weight, etc. can be stored tamperproof thanks to CodeNotary's CLI tool and within a few minutes, all of this information can be viewed and shared with customers, curators and collectors around the world and its authenticity is cryptographically verifiable.

Using CodeNotary was truly eye-opening for me.

Not only does it drastically reduce my paper-trail, but this information about my works, stored in an immutable platform, can be easily queried and leveraged by applications. My current focus is to build – with some help! – simple, proprietary applications that will leverage this information, applications that will be used in the context of exhibitions.

CNIL Metrics & Logs

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

immudb

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

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.