---
# System prepended metadata

title: Q3 Report
tags: [article / in process]

---

# Q3 Report
###### tags: `article / in process`

![](https://raw.githubusercontent.com/BlockchainCommons/www.blockchaincommons.com/master/images/2022-Q3-report.jpg)

It's been another busy quarter at Blockchain Commons, with a focus on new foundations, created in coordination with our community.

## Major Works

**New Foundations:**

* Hello to the Identity Community
* Gordian Envelope
* MVA Algorithm Suite
* Collaborative Seed Recovery
* CSR Use Cases

**Community Events:**

* Silicon Salon 2
* RWOT11
* Congrats to DIDs

**New & Updated Projects:**

* Beancount
* SpotBit

**Advocacy:**

* Law & Advocacy Repo
* Private Key Disclosure

**Web Site Updates:**

* Vision Page
* About Page
* Projects Page

**Doc Updates:**

* Revised Gordian Page
* New Test Vectors

## Firm Foundations

Much of our work in Q3 has been forward-thinking, focused on creating the next generation of specifications for blockchain interoperability.

**Hello to the Identity Community.** Being able to create the next generation of specifications depends on having a wide-spanning community, and we've been thrilled to see the Blockchain Commons community continue to grow. That includes not just cryptocurrency nowadays, but also digital identity thanks to sustaining sponsor Proxy. We also reached out to more digital-identity companies at this year's Rebooting the Web of Trust event, and hope to see that pay out in the near future.

<a href="https://www.youtube.com/watch?v=FVzTRsqcyMU"><img src="https://raw.githubusercontent.com/BlockchainCommons/www.blockchaincommons.com/master/images/2022-Q3-Envelope.jpeg" align="right" width="300"></a>

**Gordian Envelope.** Our specification work is intended to build firm foundations. Our newest foundational work of this sort has been on Gordian Envelope, a new sort of "Smart Container" that can be used to hold secrets and metadata of an arbitrary size and that can be opened by a variety of "permits", including SSKR shares and public-key cryptography keypairs. Extensive [docs](https://github.com/BlockchainCommons/BCSwiftSecureComponents/tree/master/Docs) are now available as part of our [BCSwiftSecureCompanents package](https://github.com/BlockchainCommons/BCSwiftSecureComponents). Also see our [Gordian Envelope videos](https://www.youtube.com/watch?v=FVzTRsqcyMU) on our [YouTube channel](https://www.youtube.com/channel/UCPQ9LtDWZAkfItMF4B5tztw).

**MVA Algorithm Suite.** The appendix of the Gordian Envelope docs contains our first [MVA ALgorithm Suite](https://github.com/BlockchainCommons/BCSwiftSecureComponents/blob/master/Docs/09-A-ALGORITHMS.md). This refers to the algorithmic suite we've decided to use in our [Minimal Viable Architecture](https://www.youtube.com/watch?v=S0deyIHXukk&t=7s): effectively a future-proofed Minimal Viable Product. It overviews current cryptographic algorithms and discusses our decisions about which to use. Gordian Envelope uses BLAKE3, IETF ChaChaPoly, the secp256k1 curve, and more. Our Appendix talks about why we think they're the best practices for this project.

**Collaborative Seed Recovery.** This new foundational work is largely in service to Collaborative Seed Recovery (CSR): we intend it to add independence, resilience, and openness to seed storage by allowing digital-asset holders to shard their seed and then store it with a variety of different steward services, making recovery painless and resilient. We are currently working with a companies such as Bitmark, Foundation, and Proxy in regular biweekly meetings to make CSR a reality this fall. For more, please see our [CSR Overview](https://github.com/BlockchainCommons/Gordian/blob/master/Docs/CSR.md). Our Gordian Envelope videos also lay out the whole foundation, so take a look at the combined [CSR playlist](https://www.youtube.com/watch?v=aciTNh402Co&list=PLCkrqxOY1Fbp-P1Yv-7gmu75i2QS2Z6vk).

**CSR Use Cases.** Why is CSR needed? We've written several sequences of [progressive use cases](https://hackmd.io/ZbRiwvUfQSy-1RKM15bM8Q#CSR-Focused-Use-Cases) in a preliminary document that discusses options both for CSR and its 2023 successor, Collaborative Key Management (CKM). It covers everything from simple protection of keys to future possibilities where no one actually holds a complete seed, despite its keys being in active use.

## Community Events


Preventing vendor lock-in via interoperability has been a Blockchain Commons goal from the beginning, but that requires bringing together multiple parties to buy into interoperable specifications. The growth of Blockchain Commons' community of developers, sponsors, and other interested parties in 2022 has truly made that possible, with those parties coming together in community events such as the biweekly CSR meetings and others. 

<a href="https://www.siliconsalon.info/salon2/"><img src="https://raw.githubusercontent.com/BlockchainCommons/siliconsalon.info/master/assets/silicon-salon-2/images/silicon-salon2.jpg" width=300 align="right"></a>

**Silicon Salon 2.** Our other ongoing get-together this year has been the [Silicon Salon](https://www.siliconsalon.info/), where we've facilitated wallet makers and semiconductor makers talking about the creation of the next generation of silicon design that is specialized for cryptography. Our [second Silicon Salon](https://www.siliconsalon.info/salon2/) was held on September 14th. Presenters included Bunnie Studios, Cramium Labs, Proxy Labs, Foundation, and the VLS team.

**RWOT11.** Blockchain Commons got its start with [Rebooting the Web of Trust](https://www.weboftrust.info/), where Christopher Allen first brought community members together to support the future of decentralized and self-sovereign technologies. Unfortunately, Rebooting the Web of Trust went on hiatus shortly after the foundation of Blockchain Commons, due to the COVID-19 pandemic, but it was back [this September](https://github.com/WebOfTrustInfo/rwot11-the-hague). 

Blockchain Commons submitted two papers for RWOT11, to bring some of our topics into the conversation in the Netherlands: [an introduction to CSR](https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/collaborative-seed-recovery-csr.md) and [Elision, Redaction, and Non-Correlation in Smart Documents](https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/elision-redaction-correlation-smart-documents.md). The elision topic paper led to a discussion of [Selection Disclosure](https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/draft-documents/selective-correlation.md) that we're looking forward to finishing in the coming months. We also participated in an article on [Identity Threats](https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/draft-documents/identity-threats.md), which returns to some of our early identity work in the field!

**Congrats to DIDs.** We can't talk about RWOT without congratulating everyone who worked on turning [DIDs into a standard](https://www.blockchaincommons.com/specifications/DIDs-Ratified/). This has been a long-running goal for both RWOT and Blockchain Commons, so we were thrilled to see [DIDs](https://www.w3.org/TR/did-core/) become a W3C Recommendation this July.

## New & Updated Projects

We have also continued work on some of our smaller projects:

<a href="https://github.com/BlockchainCommons/spotbit"><img src="https://raw.githubusercontent.com/BlockchainCommons/spotbit/master/static/images/spotbit-screen.jpg" align="right" width="300"></a>

**Beancount.** Beancount is a [simple program](https://github.com/beancount/beancount) that allows double-entry accounting from text files. Because of its textual foundation, it's very convenient to use in conjunction with command-line Bitcoin tools. As it happens, this type of tool is also crucial to Bitcoin because of regulatory decisions in the US treating Bitcoin as property, not currency, meaning that capital gains need to be calculated for every transaction(!). This requires careful accounting of your Bitcoin, and to support that, we've updated our [SpotBit server](https://github.com/BlockchainCommons/spotbit) to also include a script called `beancounter.py` that will take a descriptor, look up historical prices via SpotBit, and thus provide all of the data an accountant will need to properly report Bitcoin purchases, sales, and usages. We've iterated the software a few times during the quarter, and think we might have a final version; watch for some documentation on the process in the coming quarter.

**SpotBit.** We've actually had a few recent updates to SpotBit, primarily to improve the look, feel, and design of its [webpages](https://spotbit.info/spotbit/). Thanks to 2022 interns who supported in this upgrade.

## Advocacy

The work that Blockchain Commons does on specifications, leading to libraries and reference apps, is bottom-up: we work with developers to incorporate specifications that meet our vision of independence, privacy, resilience, and openness. However, we also do top-down work, where we advocate for this vision to lawmakers, agencies, and other organizations.

**Law & Advocacy Repo.** To better highlight this work, which was also well-supported by our 2022 interns, we've added a [Law & Advocacy repo](https://github.com/BlockchainCommons/law-and-advocacy) to GitHub, to report out much of our work. It includes a list of [Terminology & Definitions](https://hackmd.io/Eat2gnYqT56HQStI63JCNg) produced by this year's interns, and links to other work.

**Private Key Disclosure.** That work includes our new article advocating for [protection for private keys in courts](https://www.blockchaincommons.com/articles/Private-Key-Disclosure/), which was published by [Bitcoin Magazine](https://bitcoinmagazine.com/legal/saving-bitcoin-private-keys-from-courts). In recent years, courts have begun to request private keys as part of pre-trial discovery motions. It's dangerous and unnecessary and it needs to end, as is now being considered in Wyoming, where Christopher Allen continues to give regular testimony. Fortunately, the proposed law in Wyoming to protect private keys from disclosure has recently passed a select committee and moved on to others. It still has a ways to go though!

## Web Site Updates

Blockchain Commons' third birthday passed without mention this Spring. But, that span of time since our foundation is probably why we've been doing a bit of work cleaning up our web presence, to make sure it accurately reflects where we are today!

<a href="https://www.blockchaincommons.com"><img src="https://raw.githubusercontent.com/BlockchainCommons/www.blockchaincommons.com/master/images/2022-Q3-website.png" align="right" width="300"></a>

**About Page.** Didn't even know that Blockchain Commons had a birthday? It's referenced on our brand-new [About Page](https://www.blockchaincommons.com/about.html) which also highlights our three principals: Founder & Executive Director Christopher Allen; Lead Researcher Wolf McNally; and Lead Tech Writer Shannon Appelcline.

**Vision Page.** We've long known the goal of Blockchain Commons: to make it possible for people to control their own assets and information on the internet, using the decentralized power of blockchain technology. We slightly revised how we write about that vision this quarter. Our [newest statement](https://www.blockchaincommons.com/vision.html) combines two previous statements to say:

> "Blockchain Commons advocates for the creation of open, interoperable, secure & compassionate digital infrastructure to enable people to control their own digital destiny and to maintain their human dignity online."

**Projects Page.** You may also want to take a look at our updated [Projects Page](https://www.blockchaincommons.com/projects.html). We've done a lot of different work over the last three and a half years. Our updated projects page now highlights what we consider most important to our vision, beginning with the Gordian System.

## Doc Updates

As part of our web updating, we've also done some work on our docs.

**Revised Gordian Page.** How does the whole Gordian system fit together, from our air-gap and tor-gap overview to specifications such as Gordian Envelope? Our [updated Gordian page](https://github.com/BlockchainCommons/Gordian#readme) walks through the whole system from top to bottom, including new pages on topics such as the [Gordian Architecture](https://github.com/BlockchainCommons/Gordian/blob/master/Docs/Overview-Architecture.md) and [Gordian Architecture Roles](https://github.com/BlockchainCommons/Gordian/blob/master/Docs/Overview-Roles.md)

**New Test Vectors.** We've also produced some new test vectors, to help people who are implementing our specifications. These include [SSKR test vectors based on 256-bit seeds](https://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/sskr-test-vector.md#256-bit-seed) and [crypto-seed test vectors for both 128-bit and 256-bit seeds](https://github.com/BlockchainCommons/crypto-commons/blob/master/Docs/crypto-seed-test-vectors.md).

## Final Notes

Thank you as always for your support for Blockchain Commons. In 2022, we have truly become the commons that we imagined. Moving forward, we will continue to build firm foundations with our big focus on the architectural and reference work needed to release CSR by the end of the year.

If you're not already a sponsor of our work, you can become one through [GitHub](https://github.com/sponsors/BlockchainCommons). Now that we're back from RWOT11 in the Netherlands, we're looking forward to continuing to advance our work!