|
| 1 | +--- |
| 2 | +cover: false |
| 3 | +header: |
| 4 | + overlay_color: "#000" |
| 5 | + overlay_filter: "0.25" |
| 6 | + overlay_image: /assets/images/dev-data-background.jpg |
| 7 | + og_image: /assets/images/bc-card.jpg |
| 8 | +title: Gordian Clubs |
| 9 | +hide_description: true |
| 10 | +classes: |
| 11 | + - wide |
| 12 | +permalink: /clubs/ |
| 13 | +sidebar: |
| 14 | + nav: clubs |
| 15 | +--- |
| 16 | + |
| 17 | +## Overview |
| 18 | + |
| 19 | +Gordian Clubs are **autonomous cryptographic objects** that provide read and write access to data using [permits](/envelope/features/#encryption-support). Gordian Clubs publish individual Editions, which are updated data files verified by the publisher (or some publishing group). |
| 20 | + |
| 21 | +Here's a bit more on the major elements: |
| 22 | + |
| 23 | +* **Autonomous.** Gordian Clubs are wholly self-contained. There's no phoning home and no verification with an external source. |
| 24 | +* **Cryptographic.** Access to Gordian Clubs is determined by mathematical means such as private keys and [SSKR](/sskr/) shares. |
| 25 | +* **Object.** A Gordian Club is a [Gordian Envelope](/envelope/) containing content, permits, and a [provenance mark](/provemark/). |
| 26 | +* **Envelope.** Gordian Envelope allows for the "smart" storage of information as a recursive set of semantic triplet. |
| 27 | +* **Permit.** Envelopes can be encrypted, and permits allow for the decryption of that data in a variety of ways. |
| 28 | +* **Edition.** A Gordian Club publishes Editions, which are linked by [provenance marks](/provemark/) and signed by publishers. |
| 29 | +* **Publishing Group.** Though an edition can be signed by an individual, it can also be signed by a [FROST threshold](/frost/). |
| 30 | + |
| 31 | +You may want to read more on the specific [technologies](/clubs/technology/) used to create Gordian Clubs, as well as their [history](/clubs/history/). |
| 32 | + |
| 33 | +## Why Are Gordian Clubs Important? |
| 34 | + |
| 35 | +Gordian Clubs allows for the distribution and storage of information when network infrastructure can't be trusted. Use cases include: |
| 36 | + |
| 37 | +* Dissidents organizing without surveillance |
| 38 | +* Long-term archival that outlives companies |
| 39 | +* Emergency coordination during outages |
| 40 | + |
| 41 | +The focus on cryptography ensures that the data remains decentralized and self-sovereign. This is in contrast to access that was [historically](/clubs/history/) controlled by centralized administration, introducing the possibility of corruption or censorship. Gordian Clubs avoid\ these issues. |
| 42 | + |
| 43 | +## Links |
| 44 | + |
| 45 | +**Gordian Clubs:** |
| 46 | + |
| 47 | +* [History](/clubs/history/) |
| 48 | +* [Gordian Technology](/clubs/technology/) |
| 49 | + |
| 50 | +**Demos:** |
| 51 | + |
| 52 | +* [Gordian Clubs Meeting (10/25)](https://developer.blockchaincommons.com/meetings/2025-10-clubs/) |
| 53 | +* [Demo Script](https://github.com/BlockchainCommons/clubs-cli-rust?tab=readme-ov-file#demonstration-script) |
| 54 | +* [Demo Log](https://github.com/BlockchainCommons/clubs-cli-rust/blob/master/demo-log.md) |
| 55 | + |
| 56 | +**Software:** |
| 57 | + |
| 58 | +* [clubs-rust library](https://github.com/BlockchainCommons/clubs-rust) |
| 59 | +* [clubs-cli-rust](https://github.com/BlockchainCommons/clubs-cli-rust) |
0 commit comments