SwiftUI application structure
Native views and view models organize the wallet interface. RPC services connect application screens to the selected Sigil network.
Native mobile identity
A wallet built for iOS.
Sigil’s iOS implementation uses SwiftUI and native signing code. Its integration connects protocol-compatible messages to a mobile approval experience.
iOS WalletIllustrated study
Signer → signature → record
Identity establishes attribution. Trust needs context.
01 / Built for a purpose
Signing is one part of the experience.
A mobile wallet needs a compatible message format, a secure key lifecycle, a clear approval screen, and a reliable return path to the requesting application. A signing implementation alone does not establish that entire journey.
Native signing implementation
The documented signer uses CryptoKit for Ed25519 and shares canonical-message and digest fixtures with other Sigil wallets.
Explicit request approval
A mobile sign-in or transaction flow needs to identify its origin and requested action before producing a response. Follow the supported integration for the distributed release.
Device custody is specific
App permissions, local key storage, backup, and recovery must be documented for the release. The presence of CryptoKit does not by itself imply a Secure Enclave-backed Ed25519 key.
Keep exploringOne capability.