# Benefits

Chains

* Liquidity and users can be onboarded to any chain within Composium in a single block, allowing chains to grow users and liquidity more easily.

Applications

* By utilizing Javelin, apps can aggregate liquidity across chains and enable composability across different instances of their apps. This provides a solution that is faster than existing cross-chain solutions and atomic, providing a better user experience and better guarantees for app developers than any other solution on the market.

Users

* Users benefit from a better experience where they can easily leverage:
  * Instant Bridging
    * By leveraging Javelin, bridges can unlock single block verification making bridging faster than ever before.&#x20;
  * Intents
    * By utilizing the composability of NodeKit, solvers can get repaid within a single block, increasing the capital efficiency of cross-chain intents.
  * DEX/Yield Aggregation
    * Cross-chain composability dramatically decreases liquidity fragmentation across chains, allowing for a better trading experience and better prices.
  * Oracles
    * An oracle chain developed on top of a composable network of chains allows for better distribution for the oracle without leaking revenue to large bridging providers. Oracles internalize some of the cross-chain transaction revenue without requiring complex infrastructure to be set up and maintained.
  * Lending
    * Cross-chain lending allows for higher capital utilization and a greater TAM for lending markets, enabling them to grow faster.
  * Margin
    * Capital efficiency can be improved by borrowing against assets on one chain and utilizing the leverage on another.


---

# 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://nodekit.gitbook.io/nodekit-documentation/core-advantages/benefits.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.
