cryptoconditions: Interledger Crypto-Conditions

[ bsd3, crypto, finance, library, network ] [ Propose Tags ]

Please see

[Skip to Readme]


Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


  • No Candidates
Versions [RSS],,,, 0.2.4, 0.2.5
Dependencies aeson, asn1-encoding, asn1-parse, asn1-types, base (>=4.7 && <5), base64-bytestring, bytestring, containers, cryptonite, memory, text [details]
License BSD-3-Clause
Copyright Copyright (C) 2017 Scott Sadler
Author Scott Sadler
Maintainer Scott Sadler <>
Category Crypto, Finance, Network
Home page
Source repo head: git clone
Uploaded by ssadler at 2020-03-26T01:01:41Z
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 3299 total (14 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2020-03-26 [all 1 reports]

Readme for cryptoconditions-0.2.5

[back to package description]

Crypto Conditions

Targeting spec: draft-thomas-crypto-conditions-02 of December 20, 2016

Current status

Supports all standard condition types except RSA.

Needs more testing. Some tests exist.


This approach to Crypto Conditions in Haskell has the goals:

  • Simple to understand and work with
  • Easily extensible

The bottleneck to achieving these goals is extensibility; Haskell does not support dynamic dispatch like OOP languages, and runtime type casting in Haskell is very unnatural and somewhat unsafe.

The solution is to decouple the condition type from the implementation, such that the core algorithms and serialization can work with instances of an "IsCondition" class, and a polymorphic data type can be implemented separately to support the desired condition types and behaviours.

The module Network.CryptoConditions supports the standard condition types, library authors wishing to extend CryptoConditions should copy and paste this file into their own project and define their own Condition type.