8930d292bf
Fast-forwards the submodule 8 commits, 2478403 -> e67fe17. The pinned commit is an ancestor of upstream master -- the local "align with AGP 9.1.1 / Kotlin 2.4.10" commit had already been pushed there -- so this is a clean advance with nothing to rebase or re-apply. What it brings, all of it PR #1 (ac-cord-ac/latest-greatest): 6775d51 Fix stale trusted-dealer path in KNOWN_ISSUES.md 880d57a Document the ChillDKG module in the READMEs ed5f7f4 Add ChillDKG test vectors and ported test suite 4345dc0 Add ChillDKG port: public API (chilldkg.py) 94686be Add ChillDKG port: SimplPedPop and EncPedPop sub-protocols cf13e22 Add ChillDKG port: crypto primitives, error hierarchy, and VSS 0b7223f Move trusted-dealer keygen into the dkg package +7,817 lines, almost all of it a Kotlin port of ChillDKG -- distributed key generation for FROST, ported from BlockstreamResearch/bip-frost-dkg @ a918968 (BIP draft 0.3.0-dev) -- plus its sub-protocols (SimplPedPop, EncPedPop), Feldman VSS, the BIP DKG tagged-hash primitives, and all 10 official vector files exercised by 249 vector cases. This is the piece the group work has been blocked on. A threshold that actually means something needs a FROST key no single member holds, and until now the library only offered FrostTrustedDealer, which requires one party to know the whole secret -- fine for tests, wrong for a group whose entire premise is that nobody is privileged. ChillDKG generates that key among the participants with no dealer at all. One breaking change rides along: frost/trusted_dealer_keygen/ moved to frost/dkg/trusted/. It costs nothing here -- the app declares the library as a dependency but does not yet call any of its API, so there is nothing to update. (The ac.cord.auxiliary.compose packages under jvmMain are the app's own leftover naming, unrelated to the library.) Verified against the bumped submodule, with the composite build recompiling the library from source: ./gradlew :composeApp:compileCommonMainKotlinMetadata ./gradlew :composeApp:compileDebugKotlinAndroid Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform…