---
# System prepended metadata

title: Quarterly

---

---
robots: noindex, nofollow
---

# Quarterly

![](https://www.blockchaincommons.com/images/2025-Q1-Report-linkedin.jpg)

Blockchain Commons focused on the ZeWIF project for the Zcash blockchain during the first quarter of 2025, but that didn't stopped us from also advancing a few other priorities, including the initial release of our long-incubating Open Integrity project. Here's what all we've been working on.

---
**ZeWIF Specification:**

* Why It's Important
* The ZeWIF Meetings
* What We've Released So Far
* What's Still to Come

**Post-Quantum Commons:**

* Why It's Important
* PQC Meeting
* QuantumLink
* What We've Released So Far

**Open Integrity:**

* Why It's Important
* What We've Released So Far

---

**New Articles:**

* The Right to Transact
* SSI Orbit Podcast

**New Dev Docs:**

* SSKR Pages
* UR Pages
* Meetings Pages
* Improved Crate Docs

**New Ports:**

* Lifehash to Rust

**New Research:**

* Provenance Marks
* Provenance References

---

## ZeWIF Specification

<img src="https://www.blockchaincommons.com/images/zcash.png" style="float: right" width=200px>

_The Zcash extensible Wallet Interchange Format (ZeWIF) has been Blockchain Commons' main priority since the Zcash Community Grants program approved our proposal at the end of the year._

**Why It's Important.** Blockchain Commons talks a lot about interoperability, and that's what ZeWIF is: it's a way to freely exchange data between Zcash wallets in a standardized form. What we don't talk about as often is why interoperability is important.

It goes back to our [Gordian principles](https://developer.blockchaincommons.com/principles/). Interoperability supports at least three of them. 

* It supports ***independence*** because any user can freely move their data among the interoperable software systems. 
* It supports ___openness___ because any developer can easily join the ecosystem by adopting a mature, well-understood specification. This creates an environment of _coopetition_ (cooperative competition) that leads to advances in technology and usability.
* It supports ***resilience*** because the interoperable format makes data less likely to be lost: it'll be in a form that will be understood and therefore accessible, well in the future.

For a wallet ecosystem, interoperability means that users will have the freedom to move their digital assets among Zcash wallets. That's the precise independence we want users to have, which is why it's been worth spending a few months of time on this project.

**The ZeWIF Meetings.** To support the ZeWIF project, Blockchain Commons held [three meetings](https://developer.blockchaincommons.com/chains/zcash/zewif/#meetings) in the first quarter: on the [initial wallet survey](https://developer.blockchaincommons.com/chains/zcash/zewif/meeting1/), on the [first demo of the zmigrate tool](https://developer.blockchaincommons.com/chains/zcash/zewif/meeting2/), and on [ZeWIF data abstractions](https://developer.blockchaincommons.com/chains/zcash/zewif/meeting3/). Meeting with developers to ensure that specifications serve everyone's needs has always been a bedrock policy for Blockchain Commons, so we've of course extended it here. (At least one more meeting is planned, for April 16th, to demo the data file format.)

<table width="100%">
  <tr>
    <td width="640px">
      <b>#1: Wallet Survey:</b>

{% include video id="wy06xxpJy-M" provider="youtube" %}

    </td>
    <td width="640px">
      <b>#2: Zmigrate demo:</b>

{% include video id="wSeAdx6oZLw" provider="youtube" %}

    </td>
    <td width="640px">
      <b>#3: Abstraction Discussion:</b>

{% include video id="qptTRJP_K2U" provider="youtube" %}

    </td>
  </tr>
</table>

**What We've Released So Far.** The ZeWIF project is built around the [zewif library](https://github.com/BlockchainCommons/zewif), which stores Zcash wallet data in an in-memory format. We've also written [zewif-zcashd](https://github.com/BlockchainCommons/zewif-zcashd) and [zewif-zingo](https://github.com/BlockchainCommons/zewif-zingo) to demonstrate the import of data from those wallets to ZeWIF, while our partners at [Zingo Labs](https://zingolabs.org/) have produced "zewif-zecwallet" for importing zecwallet data (though that PR hasn't been merged yet). Finally, we authored [zmigrate](https://github.com/BlockchainCommons/zmigrate), which is a demo CLI for importing zcashd content. With these demos and libraries in hand, other wallet developers can start working to interchange their own data via the ZeWIF format.

**What's Still to Come.** With our releases so far, data can be interchanged between different Zcash wallets as long as it's all done on the same machine: you just import into the in-memory ZeWIF format from one wallet, then export to another. But we expect most use cases will instead involve at least two different machines. That's where the ZeWIF file format comes into play. Building on [Gordian Envelope](https://developer.blockchaincommons.com/envelope/), it translates the ZeWIF in-memory storage into a fixed file that can then be moved to a different machine. We expect to demo the Envelope ZeWIF format at that upcoming April 16th meeeting.

## Post-Quantum Commons

<img src="https://www.blockchaincommons.com/images/pqc-bitcoin.png" style="float: right" width=200px>

_Is Post-Quantum Cryptography (PQC) the next big thing? We were able to support our friends at Foundation with some PQC work just as we got the ZeWIF project going at the start of the year._

**Why It's Important.** Quantum Computers are starting to appear, and though they're far, far from what would be needed to break cryptography at the moment, there's no telling when there's going to be a sudden "quantum" leap. Though today's cryptography might not need PQC, if you're working on something that might be around for 5 or 10 years, you should be thinking about it!

**PQC Meeting.** Our [March Gordian meeting](https://developer.blockchaincommons.com/meetings/2025-03-pqc/) contained all the details of our PQC work, including what Quantum Computing is.

{% include video id="ZfsH2fIHCIA" provider="youtube" %}

**QuantumLink.** The highlight of the meeting was a discussion of [QuantumLink](https://developer.blockchaincommons.com/assets/pdfs/202503-quantumlink.pdf) from our friends at [Foundation](https://foundation.xyz/). This is a  quantum-resistant protocol for Bluetooth communication that is a critical component of their new [Passport Prime](https://foundation.xyz/buy-passport-prime/) wallet. It allows them to use Bluetooth with high security and for that security to remain strong 5 or 10 years in the future, in case Quantum Computing does make those big strides forward.

**What We've Released So Far.** The QuantumLink technology was enabled by new PQC support that Blockchain Commons incorporated into its libraries. You can now use the PQC algorithms [ML-DSA and ML-KEM](https://hackmd.io/@bc-community/rJ8DOmCd1e) in our Rust stack, from [bc-componenents](https://github.com/BlockchainCommons/bc-components-rust) on up.

## Open Integrity

<img src="https://www.blockchaincommons.com/images/openintegrity.png" style="float: right" width=200px>

_We had one other big release in Q1: [Open Integrity](https://github.com/openintegrityproject), a system for increasing the trust of software being developed in Git. Well, technically it was released on April 7th, the 20th anniversary of Git's release, but this is something that Blockchain Commons Architect Christopher Allen has been working on for about a year, so we're thrilled to get the word out._

**Why It's Important.** We wrote [a whole article](https://www.blockchaincommons.com/musings/open-integrity/) discussing why Open Integrity is important. But, in short: Git repos are growing increasingly important for the deployment of critical software, and Git doesn't actually provide a high-level of trust for those repos, despite the ability to sign commits. Open Integrity bridges the gap betwen what Git offers and what online software distribution needs.

**What We've Released So Far.** The Open Integrity project is now available in an early form at [GitHub](https://github.com/openintegrityproject). A [Problem Statement](https://github.com/OpenIntegrityProject/core/blob/main/docs/Open_Integrity_Problem_Statement.md) offers  details on the issues we're trying to solve and our solutions. We've also got a number of tools and scripts, the most import of which creates an [inception commit on a repo](https://github.com/OpenIntegrityProject/core/blob/main/src/setup_git_inception_repo.sh). This inception commit is the root of trust that lays the foundation for ensuring that you always know who's in control of a repo.

If you want to try out Open Integrity, see the [Open Integrity Snippets file](https://github.com/OpenIntegrityProject/core/blob/main/docs/Open_Integrity_Script_Snippets.md), which has complete instructions on how to get that inception-commit script running, plus many examples that will allow you to experiment with Open Integrity.

---

> _That's it for our big Q1 projects, but we had a number of smaller releases over the course of the quarter as well._

---

## New Articles

**The Right to Transact.** We think the right to transact should be an international freedom. Read more in Christopher's recent article, ["The Case for an International Right to Freedom to Transact"](https://www.blockchaincommons.com/musings/RightToTransact/), which builds on his 2024 musing, ["How My Values Inform Design"](https://www.blockchaincommons.com/musings/ValuesDesign/).

**SSI Orbit Podcast.** Christopher also was interviewed for the [SSI Orbit Podcast](https://www.blockchaincommons.com/videos/SSI-Podcast/). It's been nine years since he wrote the foundational ["Path to Self-Sovereign Identity"](https://www.lifewithalacrity.com/article/the-path-to-self-soverereign-identity/). Where do things stand today?

## New Dev Docs

**SSKR Pages.** We updated our [SSKR dev pages](https://developer.blockchaincommons.com/sskr/) with the big focus being differentiating [SSKR URs](https://developer.blockchaincommons.com/sskr/#what-are-sskr-urs) (where you split up a key) and [SSKR Envelopes](https://developer.blockchaincommons.com/sskr/#what-are-sskr-envelopes) (where you protect the entire contents of an Envelope by creating and splitting up a key). The [test vectors](https://developer.blockchaincommons.com/sskr/vectors/) also now demonstrate both cases.

**UR Pages.** We similarly did some big updates to our [UR dev pages](https://developer.blockchaincommons.com/ur/). Here the issue was that URs had seen some changes over the years, especially as we locked down CBOR tag registration, and our examples were no longer up-to-date. Now, every page and every test vector should be correct. There's also a new page on [URs for Gordian Envelope](https://developer.blockchaincommons.com/ur/envelope/).

**Meetings Pages.** All of Blockchain Commons' meetings are now documented on a new [meetings page](https://developer.blockchaincommons.com/meetings/), which also includes subpages with videos and slides (and usually transcripts) of everything from the last few years!

**Improved Crate Docs.** Finally, we've used some lessons learned from the documentation of ZeWIF to improve the documentation of our Rust stack. As a result, docs.rs now has improved docs for [bc-dcbor](https://docs.rs/dcbor/0.16.5/dcbor/), [bc-components](https://docs.rs/bc-components/0.18.2/bc_components/), and [bc-envelope](https://docs.rs/bc-envelope/latest/bc_envelope/)

## New Ports

**Lifehash to Rust.** Lifehash is now available in a new [Rust Implementation](https://github.com/GalactechsLLC/lifehash-rs) courtesy of Ken Griggs. Lifehash is a critical element of the [object identity block](https://developer.blockchaincommons.com/oib/), which can help users to recognize seeds and keys. We hope this will allow for more deployment.

## New Research

<img src="https://www.blockchaincommons.com/images/provenance-mark-symbol-white.svg" style="float: right" width=200px>

**Provenance Marks.** One of our newest innovations, courtesy of Blockchain Commons Lead Researcher Wolf McNally, is the [provenance mark](https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2025-001-provenance-mark.md). The provenance mark is a cryptographically secure chain of marks that facilitates the easy verification of authenticity. We'll have more on them in the months ahead, but in the meantime, you can read Wolf's [research paper](https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2025-001-provenance-mark.md) on the topic! 

**Provenance References.** If you want to start playing with provenance marks right now, 
we've already released a series of reference apps and libraries. They include our original [Swift implementation](https://github.com/BlockchainCommons/Provenance), our newer [Rust implementation](https://github.com/BlockchainCommons/provenance-mark-rust), and a [CLI](https://github.com/BlockchainCommons/provenance-mark-cli-rust) that can be used to create and manage marks!

---

_That's it for the moment. For the next quarter, we'll be closing out our initial work on ZeWIF in April, and we'll be offering more looks at Provenance Marks in the months ahead._

_If you'd like to work with us on these or other topics, [drop us a line](mailto:team@blockchaincommons.com) about becoming a Blockchain Commons partner._