cordn, MLS group messaging whose delivery service is an MCP coordinator reached
over Nostr, for Kotlin Multiplatform: JVM, Android, iOS, macOS and Linux. It implements the cordn
specs (coordinator tools, group metadata, envelopes, sealed payloads, group refs, encrypted media,
multi-device) on top of Quartz and the RFC 9420 engine
mls-kmp, and ships a headless client,
CordnGroupManager, that a front end drives to create, join, send to and sync groups.
It is the cordn layer of Amethyst, its desktop app and
the amy CLI, and is tested against ts-mls, the engine cordn's own client runs.
dependencies {
implementation("com.vitorpamplona.cordn:cordn:<version>")
}Releases are on Nostr + Blossom, through Magpie
(Maven Central up to 1.2.1), and so are the libraries it depends on. Add Magpie's settings
plugin in settings.gradle.kts: it serves these groups, trusting only the key
vitorpamplona.com/.well-known/nostr.json names as releases. Commit the gradle/magpie.lock
it writes; Gradle has to run on Java 21 or newer:
plugins {
id("com.vitorpamplona.magpie") version "0.2.3"
}
magpie {
group("com.vitorpamplona.cordn")
group("com.vitorpamplona.quartz")
group("com.vitorpamplona.crypto")
group("com.vitorpamplona.schnorr256k1")
group("com.vitorpamplona.negentropy")
group("com.vitorpamplona.mls")
}./gradlew installGitHook
./gradlew -PquartzDir=../quartz :cordn:jvmTest # -PquartzDir until the pinned Quartz is releasedAGENTS.md has the project rules, for people and coding agents alike.