bc-lifehash - The C++/C Implementation

🟨🟨🟨🟨🟨
🟨🟨🟥🟨🟨
🟨🟨🟨🟥🟨
🟨🟥🟥🟥🟨
🟨🟨🟨🟨🟨

•    part of the crypto commons technology family

by Wolf McNally and Christopher Allen

Watch the LifeHash explainer video!

LifeHash is a method of hash visualization based on Conway’s Game of Life that creates beautiful icons that are deterministic, yet distinct and unique given the input data.

The basic concept is to take a SHA256 hash of the input data (which can be any data including another hash) and then use the 256-bit digest as a 16x16 pixel "seed" for running the cellular automata known as Conway’s Game of Life.

After the pattern becomes stable (or begins repeating) the resulting history is used to compile a grayscale image of all the states from the first to last generation. Using Game of Life provides visual structure to the resulting image, even though it was seeded with entropy.

Some bits of the initial hash are then used to deterministically apply symmetry and color to the icon to add beauty and quick recognizability.

See a LifeHash demo at LifeHash.info.

Notes on This Implementation

We intend this C++/C implementation to become the "canonical" implementation, and to be suitable for binding to other languages such as Java, Python, and cross-compilation into WebAssembly. In order to work from a single main codebase, we also expect this implementation to eventually replace the pure Swift implementation.

Implementations

Command-Line Tools

bc-lifehash-cli is a command line tool written in C++ that generates LifeHash images as PNG files.

Dependencies

The LifeHash library is self-contained and has no dependencies.

Installation Instructions

$ ./build.sh
$ sudo make install

Note: If on Linux, you'll have to install zsh beforehand:

$ sudo apt-get install zsh

Usage Instructions

1. Link against liblifehash.a.
2. Include the umbrella header in your code:

For C:

#include <lifehash/lifehash.h>

For C++

#include <lifehash/lifehash.hpp>

The output image structure contains the image width and height, and an array of RGB byte tuples in row-major order starting from the upper-left corner. The caller is responsible for translating this structure into a displayable format.

LifeHashes In Five Flavors

• version1 The Original. DEPRECATED
• version2 Bug fixes and CMYK-friendly.
• detailed Now with twice the resolution, and CMYK-friendly.
• fiducial Fiducials are symbols specifically optimized for recognition by machine vision algorithms like those in Apple's ARKit. Now CMYK-friendly.
• grayscaleFiducial Highest contrast for low-light situations.

⚠️ NOTE: The images generated by LifeHash from a given seed will not be recognizably similar between each of these versions. So pick the one you want to use for your application and stick with it!

Version 1 (DEPRECATED)

Version 2

Detailed

Fiducial

Grayscale Fiducial

From the "LifeHash Example" demo app:

"LifeHash Example" (part of the Swift implementation) lets you scroll through an endless table of LifeHashes generated from sequential integers, and tap on any of them to get a closer look. The selector at the top lets you choose to browse .version2, .detailed, .fiducial, and .grayscaleFiducial LifeHashes.

From the "LifeHash Gallery" demo app:

"LifeHash Gallery" shows an elegant, artistic presentation of various collections of LifeHashes that automatically change every ten seconds. The latest version shows .version2, .detailed, and .fiducial LifeHashes.

From the Mathematica implementation:

⚠️ NOTE: The Mathematica implementation currently only generates version1 LifeHashes.

Tips for Presenting LifeHash Images

• Don't vignette or round the corners of a LifeHash image, every pixel contributes to the security of the image, so show the image as a square. If you really want to round the corners, make the radius small enough to still show the corner pixels.
• Don't interpolate or blur a LifeHash image: show every pixel crisply. On iOS UIKit this is accomplished by setting layer.magnificationFilter = .nearest on a UIImageView. Under SwiftUI you call myImage.interpolation(.none). The iOS LifeHash library already does this for you.
• The iOS/Mac LifeHash library renders LifeHash images asynchronously and caches the result, so if you pass in the same Fingerprint you'll get the same image back right away. But if LifeHash rendering seems slow, be sure you're compiling the Release configuration of your target: LifeHash is really fast when compiled for Release.

License

LifeHash is available under the BSD-2-Clause license. See LICENSE.md for more info.

Financial Support

LifeHash is a project of Blockchain Commons. We are proudly a "not-for-profit" social benefit corporation committed to open source & open development. Our work is funded entirely by donations and collaborative partnerships with people like you. Every contribution will be spent on building open tools, technologies, and techniques that sustain and advance blockchain and internet security infrastructure and promote an open web.

To financially support further development of LifeHash and other projects, please consider becoming a Patron of Blockchain Commons through ongoing monthly patronage as a GitHub Sponsor. You can also support Blockchain Commons with bitcoins at our BTCPay Server.

Contributing

We encourage public contributions through issues and pull-requests! Please review CONTRIBUTING.md for details on our development process. All contributions to this repository require a GPG signed Contributor License Agreement.

Discussions

The best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.

Gordian Developer Community. For standards and open-source developers who want to talk about interoperable wallet specifications, please use the Discussions area of the Gordian Developer Community repo. This is where you talk about Gordian specifications such as Gordian Envelope, bc-shamir, Sharded Secret Key Reconstruction, and bc-ur as well as the larger Gordian Architecture, its Principles of independence, privacy, resilience, and openness, and its macro-architectural ideas such as functional partition (including airgapping, the original name of this community).

Blockchain Commons Discussions. For developers, interns, and patrons of Blockchain Commons, please use the discussions area of the Community repo to talk about general Blockchain Commons issues, the intern program, or topics other than those covered by the Gordian Developer Community or the Gordian User Community.

Other Questions & Problems

As an open-source, open-development community, Blockchain Commons does not have the resources to provide direct support of our projects. Please consider the discussions area as a locale where you might get answers to questions. Alternatively, please use this repository's issues feature. Unfortunately, we can not make any promises on response time.

If your company requires support to use our projects, please feel free to contact us directly about options. We may be able to offer you a contract for support from one of our contributors, or we might be able to point you to another entity who can offer the contractual support that you need.

Credits

The following people directly contributed to this repository. You can add your name here by getting involved — the first step is to learn how to contribute from our CONTRIBUTING.md documentation.

Responsible Disclosure

We want to keep all our software safe for everyone. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. We are unfortunately not able to offer bug bounties at this time.

We do ask that you offer us good faith and use best efforts not to leak information or harm any user, their data, or our developer community. Please give us a reasonable amount of time to fix the issue before you publish it. Do not defraud our users or us in the process of discovery. We promise not to bring legal action against researchers who point out a problem provided they do their best to follow the these guidelines.

Reporting a Vulnerability

Please report suspected security vulnerabilities in private via email to [email protected] (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.

The following keys may be used to communicate sensitive information to developers:

You can import a key by running the following command with that individual’s fingerprint: gpg --recv-keys "<fingerprint>" Ensure that you put quotes around fingerprints that contain spaces.