P2pKit is a Kotlin Multiplatform library for authenticated peer discovery, messaging, and durable file transfer over a reachable local network. It supports Android, JVM/Desktop, and iOS through one transport-independent API.

Development version: 0.7.0-SNAPSHOT. Latest published version: 0.7.0-rc3.

0.7.0-rc3 is available from Maven Central under io.github.apdelrahman1911. It is a release candidate: the automated release gates are extensive, but the external validation areas listed below remain pending.

The immutable RC3 tag and published artifacts are the candidate for the pending physical-device, hostile-network, independent-interoperability, and professional-review campaigns. Results from later main snapshots must not be reported as RC3 evidence.

• Android API 24+, JVM 17, and iOS/iPadOS 14+ through iosArm64, iosSimulatorArm64, and iosX64.
• Android/JVM JmDNS and Apple Bonjour discovery with TCP transport.
• Authenticated protocol v2 by default using Noise_XX_25519_ChaChaPoly_SHA256 and persistent X25519 identities.
• Independent advertising/discovery states, typed failures, bounded framing, keepalive, and outgoing-session reconnect.
• Authenticated metadata envelopes and streaming file transfer with negotiated SHA-256 verification and receiver durable-commit acknowledgement.
• Coroutine/Flow APIs and explicit host ownership of lifecycle and permission presentation.

P2pKit does not provide internet signaling, NAT traversal, relays, accounts, rooms, or application-level authorization. Both peers must already be mutually reachable on the LAN. Guest/enterprise Wi-Fi may block multicast or peer TCP.

Use mavenCentral() and keep all P2pKit modules on the same version.

kotlin {
    sourceSets {
        commonMain.dependencies {
            implementation("io.github.apdelrahman1911:p2p-core:0.7.0-rc3")
            implementation("io.github.apdelrahman1911:p2p-transport-lan:0.7.0-rc3")
        }
    }
}

dependencies {
    implementation("io.github.apdelrahman1911:p2p-transport-lan-android:0.7.0-rc3")
    // Optional hotspot/Wi-Fi provisioning:
    implementation("io.github.apdelrahman1911:p2p-network-provisioning-android-android:0.7.0-rc3")
}

dependencies {
    implementation("io.github.apdelrahman1911:p2p-transport-lan-jvm:0.7.0-rc3")
    // Optional manual-endpoint provisioning:
    implementation("io.github.apdelrahman1911:p2p-network-provisioning-desktop:0.7.0-rc3")
}

Kotlin Multiplatform root coordinates select their platform variants. The complete 15-coordinate publication set is recorded in the 0.7.0-rc3 release record.

The Maven publications serve Kotlin Multiplatform consumers. A direct Swift application builds P2pKitShared.xcframework from this repository:

./gradlew :p2p-transport-lan:assembleP2pKitSharedReleaseXCFramework

The maintained Swift sample and provenance-checked integration live under samples/iosApp.

Current development builds with Kotlin 2.4.10 while retaining the iOS 14 library floor explicitly. Kotlin Multiplatform applications that link their own Apple binary must apply the iOS 14 Kotlin/Native override documented in the compatibility policy; repository-built XCFrameworks apply it and verify every Mach-O slice automatically.

Authenticated v2 is the default and fails closed. Exchange the full pairing QR or fingerprint through a trusted channel, then pin the expected identity:

import dev.p2pkit.core.AppId
import dev.p2pkit.core.P2pKit
import dev.p2pkit.core.P2pMessage
import dev.p2pkit.transport.lan.lan
import kotlinx.coroutines.flow.first

val kit = P2pKit.create {
    appId = AppId("com.example.transfer")
    deviceName = "My device"
    transports { lan() } // Android: lan(applicationContext)
}

kit.start()
kit.startAdvertising()
kit.startDiscovery()

val expectedFingerprint =
    requireNotNull(kit.parsePeerPairingQr(qrFromTrustedChannel))
val peer = kit.peers.first { it.isNotEmpty() }.first()
val session = kit.connect(peer, expectedFingerprint)
session.send(P2pMessage.Text("hello"))

Subscribe to incomingSessions before advertising and attach each session.incoming collector promptly; these are hot event streams. send() confirms a local transport write, not remote application processing. Add domain-level IDs, ordering, deduplication, acknowledgements, and repair where your application requires them.

Initialize secure identity storage once from Application.onCreate() before constructing a kit:

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        P2pKitAndroid.initialize(this)
    }
}

Declare the base LAN permissions:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_MULTICAST_STATE" />

The optional network-provisioning sidecar has separate runtime permission and system-state requirements. Query its permission manager immediately before a provisioning operation; do not gate the base LAN transport on those permissions.

The final application Info.plist must contain a nonblank local-network reason and the secure-v2 Bonjour service:

<key>NSLocalNetworkUsageDescription</key>
<string>Find and connect to nearby devices on your local network.</string>
<key>NSBonjourServices</key>
<array>
    <string>_p2pkit2._tcp</string>
</array>

Keep these values in the source that generates the final plist. The sample uses samples/iosApp/project.yml. Add the legacy _p2pkit._tcp service only for an explicitly configured deprecated plaintext-v1 build; v1 and v2 do not interoperate or downgrade.

Core intentionally has no plaintext secure-identity default. Install a durable, confidential, integrity-protected operating-system-backed store:

val kit = P2pKit.create {
    appId = AppId("com.example.transfer")
    deviceName = "Desktop"
    jvmSecureIdentityStore(protectedIdentityStore)
    transports { lan() }
}

putIfAbsent must be atomic across processes and durable before returning. The samples' in-memory stores are development-only.

See the architecture overview and current specification.

Discovery TXT records, names, peer IDs, and AppId are untrusted. The default RejectUnknown policy requires an exact trusted identity. The explicit-risk AcceptAnyAuthenticatedSameApp policy encrypts and authenticates key possession but does not identify a person/device; it requires application-level admission. There is no automatic fallback to plaintext.

Public collection models are snapshot values. Text/binary messages are capped at 4 MiB. File transfer is streaming and completes only after the authenticated receiver verifies the sender's prepared SHA-256 snapshot and durably commits the destination.

Read the security model, compatibility policy, and 0.6-to-0.7 migration guide.

The automated module/platform, ABI, strict Dokka, publication-shape, isolated consumer, SBOM, signing, provenance, Swift warnings-as-errors, and XCFramework gates passed for the published 0.7.0-rc3 commit. This does not replace external evidence.

These areas remain explicitly pending:

1. Android physical-device validation.
2. Apple device, AWDL, path-rotation, background, and restart validation.
3. Two-machine hostile-network validation.
4. CLI fault injection and headful Desktop observation.
5. Independent secure-v2 interoperability validation.
6. Professional cryptographic audit.

See validation status and the operational real-world validation handbook. Do not treat this release candidate as fully production validated or independently audited.

• Documentation index
• Contributing
• Security reporting
• Support policy
• Changelog

P2pKit is licensed under the Apache License 2.0.