Kuira Bring On-Device ZK Proving come Midnight Android Apps

Kuira Labs don release Android SDK wey go help build Midnight applications wey fit generate zero-knowledge proofs directly for user phone. Version 0.1.0-alpha05 dey publicly available through Maven Central and e package wallet, identity, contract runtime and proving components under one single Gradle dependency.

Dem showcase the stack during the August 5 Fireside Dev Hang. Midnight, Cardano privacy-focused partner chain, still list Kuira inside their official developer documentation as community-maintained mobile and embedded-wallet option.

Kuira Dey Generate Midnight ZK Proofs for Android

By default, Kuira dey generate zero-knowledge proofs locally for Android. Application go build the transaction, produce the proof and prepare am to submit without sending private proving inputs go any external service.

According to the technical documentation, the SDK dey use Midnight Rust-based midnight-zkir proving engine, wey dem compile as native Android code and access through JNI instead of WebAssembly environment.

Developers fit manually choose remote proof server when circuit too heavy for the target device. The SDK no dey switch automatically. If local proving dey selected and the required keys no dey available, the process go fail instead of sending private inputs go server.

Wallet proving keys need about 33 MB and dem fit bundle am with the application or download and cache am during setup. Once e don store, proofs fit generate without connecting to proof server, although to submit the completed transaction still need network access.

Kuira never publish universal proving-time or memory benchmarks. Performance dey vary by circuit and Android hardware, so the current documentation no support single verified speed figure across devices.

Embedded Wallet Support $NIGHT, DUST and Passkeys

The SDK include self-custodial wallet inside the application own process. Users fit interact with Midnight application without first installing separate wallet.

Kuira support shielded and unshielded balances, transaction synchronization, DUST regeneration and $NIGHT transfers. E still include the Compact runtime wey you need to deploy and call Midnight smart contracts from Android application.

Wallet access dey use passkey-based system wey dem call Sigil. Biometric confirmation or device credential go unlock the passkey, wey dey protect identity and wallet setup process without needing recovery phrase during initial onboarding.

Users fit later reveal optional 24-word recovery phrase. The current Sigil architecture fit also restore access through synchronized passkey, but that route depend on the same Google account and application domain.

Kuira get plans to address wallet portability between applications and recovery across different Google accounts through Sigil V2. That architecture still dey project roadmap and e no dey inside the current alpha.

Developers fit test the stack with runnable examples, including basic counter application and Midnight Kicks, one commit-reveal game wey moves dey proven for the phone.

Kuira Alpha Public but E Never Ready for Production

The July 14 alpha05 release add typed Compact contract reads, constructor arguments, support for multiple contracts and end-to-end path to move unshielded funds.

The SDK dey distributed through Maven Central under Apache 2.0 license. Their public GitHub repository get documentation and release infrastructure, while the primary SDK repository still private. Kotlin source packages dey accompany the compiled Android artifacts, so developers fit inspect and debug the published implementation through Android Studio or IntelliJ.

Kuira release documentation classify the SDK as alpha. E APIs fit change between releases, production use no dey recommended and security fixes dey applied only to the latest alpha version.

Android na the only supported platform for now. Kuira list iOS and React Native integrations as planned additions, but none dey publicly available yet.

Alpha05 don change immediate workflow for Midnight mobile development: teams fit now test local proving and embedded wallet functionality through published Android dependency instead of assembling custom mobile stack. Production deployment still no dey inside Kuira current recommendation until the SDK pass the alpha release line.