Skip to main content

Lamina1 Distribution SDK

NOTE: The LAMINA1 Distribution SDK is only currently available on Betanet.

In Testnet/Betanet development, Lamina1 developed an SDK known as the L1 For Unity toolset, a simple, easy to use interface for developers seeking to integrate Lamina1 into their Unity projects. 

We tested this toolset to power one of our first metaverse demo Spaces, Space Lasers, which has since been retired from the Lamina1 Mainnet. 

With the launch of the Creator Studio and content publishing on Lamina1, we now need a way to enable content to be distributed and engaged with across various applications/Spaces. This need goes beyond Unity, and will require us to extend support of the toolkit to the web and other platforms.

To reflect this broader objective to facilitate integrations across multiple platforms, we’ve officially renamed L1 for Unity to the Lamina1 Distribution SDK. Its goal remains to enable the frictionless activation of content pipelines and unifying content experiences across apps powered by Lamina1. We also plan to add support for other client runtimes such as Unreal, Javascript as well as having direct access to the APIs.

The key capabilities of this new, broader Lamina1-developed SDK will be:

  • User Authentication: Securely verify users and session keys to access Lamina1 profiles and items
  • Item and Profile Data: Allow apps to import user profiles, items, collections while retaining key metadata and rights restrictions
  • Distribution: Register and distribute (push or pull) items into apps and metaverse Spaces
  • Analytics: Capture usage telemetry within apps to provide back to creators and feed personalized recommendations.

We are preparing to launch the Lamina1 Distribution SDK alongside future updates to identity and authentication on the Lamina1 Hub — which will further streamline how users login to upcoming Spaces and experiences on Lamina1.

Beyond the Lamina1 Distribution SDK, you can also expect SDKs from our ecosystem partners (like the Emergence SDK) to be updated to support our new capabilities in content distribution and user authentication post-launch.