# Metaverse Package

## Lowering the barrier to entry <a href="#lowering-the-barrier-to-entry" id="lowering-the-barrier-to-entry"></a>

![Klaytn offers end-to-end integration including a built-in L2 solution](https://2361259531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo8dCjygb765jszAbMUcT%2Fuploads%2Fgit-blob-22fa7b5687d322f718c73f954e492dd9ddef0555%2Fmainnet-integration.png?alt=media\&token=b67b22a7-e061-416b-8f1e-16c1bd75781f)

It is clear that blockchain technology will serve as the critical trust layer for the metaverse.

However, between the fledgling state of blockchain tech and the difficulty of selecting the right tools and components, blockchain development is still filled with hurdles.

That’s why we put together an end-to-end package that’s designed to help builders of metaverse enter the blockchain world as smoothly as possible.

## Klaytn’s ‘Metaverse Package’ <a href="#klaytns-metaverse-package" id="klaytns-metaverse-package"></a>

Primary Infrastructure: Tool sets for end-to-end blockchain integration and building Customized L2 solution SDKs and smart contract libraries Wallets and chain explorers Distributed storage solutions Oracle support Bridges

Secondary Infrastructure: Ecosystem for supporting products and services Integration/abstraction services Stablecoin integrations DAOs NFT Marketplaces DEX and DeFi Traditional finance interfaces

• This package will be managed by our dedicated package manager.

• Builders can easily build and customize Layer 2 as well as create/transfer assets.

With our metaverse package, the complexity of blockchain will no longer get in the way of realizing your aspirations.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://archive-docs.klaytn.foundation/misc/klaytn2/metaverse-package.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.