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.
LifeHashTool is a command line tool written in Swift that generates LifeHash images as PNG files.
version1The Original. DEPRECATED
version2Bug fixes and CMYK-friendly.
detailedNow with twice the resolution, and CMYK-friendly.
fiducialFiducials are symbols specifically optimized for recognition by machine vision algorithms like those in Apple's ARKit. Now CMYK-friendly.
grayscaleFiducialHighest 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!
"LifeHash Example" 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
"LifeHash Gallery" shows an elegant, artistic presentation of various collections of LifeHashes that automatically change every ten seconds. The latest version shows
⚠️ NOTE: The Mathematica implementation currently only generates
layer.magnificationFilter = .neareston a
UIImageView. Under SwiftUI you call
myImage.interpolation(.none). The iOS LifeHash library already does this for you.
LifeHash is available under the BSD-2-Clause license. See LICENSE.md for more info.
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.
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.
The best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.
Wallet Standard Discussions. For standards and open-source developers who want to talk about wallet standards, please use the Discussions area of the Airgapped Signing repo. This is where you can talk about projects like our LetheKit and command line tools such as seedtool, both of which are intended to testbed wallet technologies, plus the libraries that we've built to support your own deployment of wallet technology such as bc-bip39, bc-slip39, bc-shamir, Shamir Secret Key Recovery, bc-ur, and the bc-crypto-base. If it's a wallet-focused technology or a more general discussion of wallet standards,discuss it here.
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 the Gordian System or the wallet standards, each of which have their own discussion areas.
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.
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.
|Wolf McNally||Originator, Project Lead||@WolfMcNally||<Wolf@WolfMcNally.com>||9436 52EE 3844 1760 C3DC 3536 4B6C 2FCF 8947 80AE|
|Christopher Allen||Principal Architect||@ChristopherA||<ChristopherA@LifeWithAlacrity.com>||FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED|
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.
Please report suspected security vulnerabilities in private via email to ChristopherA@BlockchainCommons.com (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:
|Christopher Allen||FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED|
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.