A row said "waiting for 2 of 3 members to take part" on the day a proposal was made and on the day before it completed. That is the rule, not the progress. Now it says "1 of 3 members have offered to sign", and on the next stage "2 of 3 signatures are in" -- the fractions that actually move. Nothing is counted once it has ended, which is both endings and not only the happy one. A signed session has nothing left to gather; an abandoned one has counts frozen where they stopped, and "2 of 3" beside a failure invites the reader to wait for a third that is never coming. The failure reason is what that row has to say. The denominators are the ones the protocol gates on. `orderedNonces` returns nothing until `threshold` nonces have arrived and then takes the first `threshold` of them, so the threshold is both what is needed and what is used -- the room's size is a bigger number nothing waits for. Once the signer set exists it is the set being waited on, which is the same count from the other side. The numerator is the part that had to be got right. A nonce or a partial signature is recorded with no check on who sent it, unlike a refusal, and `orderedNonces` drops the ones from members holding no share when it aggregates. So the tally joins `DkgParticipantMessage` on HOST_KEY and counts members rather than rows: a count including strangers would have a row read ahead of the coordinator, saying the group has what it needs while the session sits still. That is the one direction a progress figure must never be wrong in, and there is a DAO test for it. A count that still runs ahead -- a nonce landing before this device runs `advance` -- is clamped, because a fraction over one reads as a bug rather than as a session about to move. The counts travel as their own `GROUP BY` flow, combined with the sessions in the view model. They change far more often than the rows do, and carrying the messages themselves would carry every nonce payload the room has ever exchanged to a screen that only wants to count them. The progress is its own line rather than a clause, so a reader scanning for the one that is nearly there does not have to read a sentence to find out. That left `statusOf` saying only who the reader is in the proposal, and since this adds user-facing text its remaining literals moved to the catalogue with it -- nine strings that had been raw in the screen since before the catalogue rule. 1367 jvm tests pass, the Android target compiles, all audit budgets met. 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…