P2PSDK packages are not published to public npm, Maven Central, NuGet, or Swift package registries. Do not expect the package names below to resolve until your organization receives private registry or artifact access.
What onboarding provides
Section titled “What onboarding provides”- Registry URL or versioned artifact download for the selected platform.
- Authentication instructions for the package registry, if required.
- Application API key and non-production environment.
- Consent URL, revoke URL, consent version, and RS256 public verification key.
- Checksums or release metadata supplied with the artifact bundle.
- A support contact for package and eligibility questions.
Package identifiers
Section titled “Package identifiers”| Platform | Identifier | Version |
|---|---|---|
| Android | com.p2psdk:p2p-sdk-android | 1.0.0 |
| iOS | Swift product P2PSdk with P2PSdk.xcframework | 1.0.0 |
| Node.js | @p2psdk/node | 1.0.0 |
| Electron | @p2psdk/electron and matching Node package | 1.0.0 |
| Windows | P2PSdk.P2P, optionally P2PSdk.P2P.Wpf | 1.0.0 |
| Linux | libp2p_sdk.so.1, pkg-config p2p-sdk, CMake P2PSdk::p2p_sdk | ABI 1 |
Version integrity
Section titled “Version integrity”The wrapper and native library must come from the same SDK release. Do not combine a JavaScript, Java, Swift, or C# wrapper from one bundle with a native binary from another.
For native consumers, verify sdk_abi_version() == 1 before creating a handle. For managed packages, preserve the artifact layout so the wrapper can resolve the native library from its expected runtime directory.
Local artifact fallback
Section titled “Local artifact fallback”The onboarding team may provide a local Maven repository, npm tarball, NuGet package directory, XCFramework bundle, or Linux archive when private registry access is unavailable. Each platform guide documents the expected local layout.
Need access? Send an integration request with your application platforms, category, monthly active users, and target release window.