We could write this blog post in my favorite Windows text editor, Notepad++.  And I bet millions of other users would agree with me when I say: this Notepad++ project is simply amazing.

The open source project Notepad++ has been used for over a decade by developers, system administrators, support engineers and many more people who want to edit all kinds of text knowing that Notepad++ will support all their formats and file types.

Github shows more than 7000 stars and over 2100 forks for this great project.

However, a few days ago the following message hit our twitter stream:

Then the following news made it clear:

“When you install Notepad++ version 7.6.4, You might notice there’s no more blue-trusted UAC popup. Here’s the explanation for the reason that we remove code signing from Notepad++ : 3 years ago DigiCert donated a 3 years code signing certificate to the project, and every good thing has its end, the certificate has been expired since the beginning of this year.

NotePad-plus-plus code-signing digital-certiticates

I was trying to purchase another certificate with reasonable price. However, I cannot use "Notepad++" as CN to sign because Notepad++ doesn’t exist as a company or organization. I wasted hours and hours for getting one suitable certificate instead of working on essential thing – Notepad++ project. I realize that code signing certificate is just an overpriced masturbating toy for FOSS authors –

Notepad++ has done without a certificate for more than 10 years, I don’t see why I should add the dependency now (and be an accomplice of this overpricing industry). I decide to do without it.

It doesn’t mean there’s no more security in Notepad++, but it will be less flexible for sure: SHA256 hash of Installer and other packages will be provided for every release as usual. Too bad for ugly yellow-orange UAC popup while installation.

Notepad++ will check the SHA256 of all the components (SciLexer.dll, GUP.exe, and nppPluginList.dll) used by the program.”

Actually, we at are in total agreement! That is exactly the reason why vChain created and released CodeNotary. To provide a valid alternative to the old-fashioned and cumbersome code signing certificates!

Digital Certificates and Certificate Authorities were never meant for code signing. While they might be a nice add-on feature for a large software vendor like Microsoft, smaller software companies need to pay a Digital Certificate tax, just to avoid the MS Windows message popping up. That’s not fair to the smaller software publishers, but more importantly, digital certificates don’t’ make the software more secure, while wrongly giving to users the impression that they do.

As an alternative to code signing certificates, some developers create their own verification pages for MD5, SHA-1, and SHA-256. Others use GnuPG (GPG) scheme for signing. However, that is just a check-the-box thing, because users downloading the software, still need to manually check and compare the hashes or signatures. Most users never even bother doing that or have any idea how that works.

We at believe that developers and publishers work hard,  create hugely popular software for free, in their spare time. It’s a shame that they get charged a lot of money by digital certificate authorities, only because there are no better alternatives to code signing certificates.

Every software developer who offers free software should get an autonomously sign their own builds and binaries… for free! allows software developers to sign their open source software for free and independently of any authority, due to our use of our blockchain-protected, code-signing product, and best of all, with CodeNotary it’s a simple 1 step process.

Sign up for a free Open Source and Freeware developer and publisher:

Let’s see how simple it is:

# vcn login

# vcn sign notepad_binary.exe

Boom, done! Check your signed assets in a nice and elegant dashboard.

Want to verify?

# vcn verify notepad_binary.exe

Or just download and your chrome extension checks the integrity automatically.

Did we mention, that we have some amazing features coming?

Granular revocation and recall of your binaries and applications in 1 simple step! No need to ask a digital Certificate Authority to revoke for you: a process that can take up to a week! With CodeNotary you can revoke the single software file, leaving any other signed software valid. With digital certificates, you revoke the certificate itself, invalidating all the software that you signed with it.

Moreover, with CodeNotary the integrity file signature is not attached to the file, like certificates do, but stored in a tamper-proof blockchain. This way you can always checked what assets were signed. Try that with a code signing certificate…

Gone are the times of cumbersome process of acquiring a code signing certificate, signing the code and managing the certificate renewal, revoking, etc.

CodeNotary is the first solution that offers a valid alternative to code signing certificates and makes the whole process intuitive and fast (just 1 step). Developers unite against code signing certificate and start using CodeNotary to make sure that none of your users uses fake or tampered software!

Get started today.

Get Your Free CodeNotary Trial Account Here

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

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.