Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Skein hash function for Erlang, via NIFs
C Erlang
Latest commit cd531f8 @dizzyd dizzyd Merge pull request #5 from basho/adt-bsd-support
Support for NetBSD, DragonFlyBSD and OpenBSD



skerl is a NIF wrapper around Skein hashing functions

Quick Start

You must have Erlang/OTP R13B04 or later and a GNU-style build system to compile and run skerl.

git clone git://
cd skerl

Start up an Erlang shell with the path to skerl included.

cd path/to/skerl/ebin

Hash a binary by calling skerl:hash/2 with the desired number of bits for the resulting hash:

1> Bits = 256.
2> Data = <<"foobarbazquux">>.
3> {ok, Hash} = skerl:hash(Bits, Data).
4> bit_size(Hash).

You may find skerl:hexhash/2 more useful, as it returns a hexadecimal-encoded string representing the hash:

5> HexHash = skerl:hexhash(Bits, Data).      

The Skein Hash

The underlying hashing code in Skerl is the reference implementation of Skein from the official NIST submission.

Skein is a finalist candidate in the NIST competition to become SHA-3.

It is a hash function designed by Niels Ferguson, Stefan Lucks, Bruce Schneier, Doug Whiting, Mihir Bellare, Tadayoshi Kohno, Jon Callas, and Jesse Walker.

Details on the algorithm as submitted and known analysis can be found at ecrypt.

A full paper on Skein by the designers has been published.

The official Skein page uses the headline:

Fast, Secure, Simple, Flexible, Efficient. And it rhymes with “rain.”


We encourage contributions to skerl from the community.

  1. Fork the skerl repository on Github.
  2. Clone your fork or add the remote if you already have a clone of the repository.
git clone
# or
git remote add mine
  1. Create a topic branch for your change.
git checkout -b some-topic-branch
  1. Make your change and commit. Use a clear and descriptive commit message, spanning multiple lines if detailed explanation is needed.
  2. Push to your fork of the repository and then send a pull-request through Github.
git push mine some-topic-branch
  1. A Basho engineer or community maintainer will review your patch and merge it into the main repository or send you feedback.
Something went wrong with that request. Please try again.