Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
WalletKit enables mobile applications to use World ID.
Part of the World ID SDK.
WalletKit can be used as a Rust crate, or directly as a Swift or Android package. WalletKit includes foreign bindings for direct usage in Swift/Kotlin through UniFFI.
Installation
To use WalletKit in another Rust project:
To use WalletKit in an iOS app:
WalletKit is distributed through a separate repo specifically for Swift bindings. This repo contains all the binaries required and is a mirror of @worldcoin/walletkit.
- Navigate to File > Swift Packages > Add Package Dependency in Xcode.
- Enter the WalletKit repo URL (note this is not the same repo):
https://github.com/worldcoin/walletkit-swift
To use WalletKit in an Android app:
WalletKit's bindings for Kotlin are distributed through GitHub packages.
- Update
build.gradle(App Level)
dependencies {
/// ...
implementation "org.world:walletkit:VERSION"
}
Replace VERSION with the desired WalletKit version.
- Sync Gradle.
Local development (Android/Kotlin)
Prerequisites
-
Docker Desktop: Required for cross-compilation
- The build uses
crosswhich runs builds in Docker containers with all necessary toolchains - Install via Homebrew:
- Launch Docker Desktop and ensure it's running before building
- The build uses
-
Android SDK + NDK: Required for Gradle Android tasks
- Install via Android Studio > Settings > Android SDK (ensure the NDK is installed)
- Set
sdk.dir(andndk.dirif needed) inkotlin/local.properties
-
Protocol Buffers compiler:
Building and publishing
To test local changes before publishing a release, use the build script to compile the Rust library, generate UniFFI bindings, and publish a SNAPSHOT to Maven Local:
Example with custom Rust locations:
RUSTUP_HOME=/.rustup CARGO_HOME=/.cargo
Note: The script can be run from any working directory (it resolves its own location). It sets
RUSTUP_HOMEandCARGO_HOMEto/tmpby default to avoid Docker permission issues when usingcross. You can override them by exporting your own values.
This will:
- Build the Rust library for all Android architectures (arm64-v8a, armeabi-v7a, x86_64, x86)
- Generate Kotlin UniFFI bindings
- Publish to
~/.m2/repository/org/world/walletkit/
In your consuming project, ensure mavenLocal() is included in your repositories and update your dependency version to the SNAPSHOT version (e.g., 0.3.1).
Development
Linting
WalletKit uses feature flags (e.g. semaphore, storage) that gate code paths with #[cfg]. To catch warnings across all configurations, run clippy three ways:
CI runs all three checks. Formatting:
Overview
WalletKit is broken down into separate crates, offering the following functionality.
walletkit-core- Enables basic usage of a World ID to generate ZKPs using different credentials.
World ID Secret
- Each World ID requires a secret. The secret is used in ZKPs to prove ownership over a World ID.
- Each host app is responsible for generating, storing and backing up a World ID secret.
- A World ID secret is a 32-byte secret generated with a cryptographically secure random function.
- The World ID secret must never be exposed to third-parties and must not leave the holder's device. //TODO: Additional guidelines for secret generation and storage.
Getting Started
WalletKit is generally centered around a World ID. The most basic usage requires initializing a WorldId.
A World ID can then be used to generate Zero-Knowledge Proofs.
A ZKP is analogous to presenting a credential.
use ;
async
🛠️ Logging
WalletKit uses tracing internally for all first-party logging and instrumentation.
To integrate with iOS/Android logging systems, initialize WalletKit logging with a
foreign Logger bridge.
Logger is intentionally minimal and level-aware:
log(level, message)receives all log messages.levelis one of:Trace,Debug,Info,Warn,Error.
This preserves severity semantics for native apps while still allowing
forwarding to Datadog, Crashlytics, os_log, Android Log, or any custom sink.
Basic Usage
Implement the Logger trait and initialize logging once at app startup:
use ;
use Arc;
;
init_logging;
Swift Integration
class WalletKitLoggerBridge: WalletKit.Logger {
static let shared = WalletKitLoggerBridge()
func log(level: WalletKit.LogLevel, message: String) {
switch level {
case .trace, .debug:
Log.debug(message)
case .info:
Log.info(message)
case .warn:
Log.warn(message)
case .error:
Log.error(message)
@unknown default:
Log.error(message)
}
}
}
public func setupWalletKitLogging() {
WalletKit.initLogging(logger: WalletKitLoggerBridge.shared, level: .debug)
}
Kotlin Integration
class WalletKitLoggerBridge : WalletKit.Logger {
companion object {
val shared = WalletKitLoggerBridge()
}
override fun log(level: WalletKit.LogLevel, message: String) {
when (level) {
WalletKit.LogLevel.TRACE, WalletKit.LogLevel.DEBUG ->
Log.d("WalletKit", message)
WalletKit.LogLevel.INFO ->
Log.i("WalletKit", message)
WalletKit.LogLevel.WARN ->
Log.w("WalletKit", message)
WalletKit.LogLevel.ERROR ->
Log.e("WalletKit", message)
}
}
}
fun setupWalletKitLogging() {
WalletKit.initLogging(WalletKitLoggerBridge.shared, WalletKit.LogLevel.DEBUG)
}