Kotlin and Compose
Native application code separates domain models, network clients, and the wallet interface so the signing flow can carry context into the approval screen.
Native mobile identity
A wallet built for Android.
Sigil’s Android implementation uses Kotlin and Jetpack Compose with a protocol-compatible signing layer and network-aware RPC clients.
Android WalletIllustrated study
Signer → signature → record
Identity establishes attribution. Trust needs context.
01 / Built for a purpose
Bring the whole approval flow to mobile.
A mobile integration includes more than a signature: receiving a request, showing its origin and contents, obtaining approval, and returning the result. Those steps need to work together for the actual distributed app.
A compatible signing transcript
The documented signer uses Ed25519, BLAKE3, and canonical message encoding. Shared fixtures compare the message and signature behavior with reference implementations.
Application-to-wallet handoff
Custom Tabs, links, and callbacks are integration surfaces that require validation. A callback should remain bound to the original request and relying party.
Platform-specific key handling
The Android release must document its actual storage, unlock, and recovery behavior. A cryptographic library does not establish hardware-backed key custody on its own.
Keep exploringOne capability.