> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inkwell.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Protocol Onboarding

> How to become a Leviathan Embedded integration partner — from application through go-live.

> **CONFIDENTIAL & PROPRIETARY © 2026 Inkwell Finance, Inc. All Rights Reserved.**
>
> This document is for informational purposes only and does not constitute legal, tax, or investment advice, nor an offer to sell or a solicitation to buy any security or other financial instrument. Any examples, structures, or flows described here are design intent only and may change.

## Overview

Becoming an Embedded integration partner involves a structured onboarding process. This page covers what protocols need, what Leviathan provides, and the steps from initial application through go-live.

## Onboarding Steps

<Steps>
  <Step title="Apply">
    Submit a partnership application describing your protocol, revenue model, user base, and integration goals. The Inkwell team reviews applications on a rolling basis.

    **What to include:**

    * Protocol name, chain(s), and contract addresses
    * Monthly active users and transaction volume
    * Revenue model and fee structure
    * Intended use case for Embedded Lending (margin trading, leveraged yield, working capital, etc.)
  </Step>

  <Step title="Due Diligence">
    Leviathan's team evaluates the protocol across several dimensions:

    * **Revenue verification** — confirming that the protocol generates verifiable on-chain revenue
    * **Contract review** — reviewing the protocol's smart contracts for compatibility with function gating
    * **Risk assessment** — evaluating the risk profile of lending within the protocol's specific context
    * **Legal review** — ensuring the integration structure fits within both parties' compliance frameworks
  </Step>

  <Step title="Whitelist Approval">
    Upon successful due diligence, the protocol is approved and its on-chain configuration is established:

    * **Protocol whitelist** — the set of contract addresses and program IDs that borrowed capital can interact with
    * **Function gate** — the specific functions on those contracts that are permitted
    * **Revenue split** — the configuration for how revenue flows between borrower, protocol, and loan repayment
    * **Agreement template** — the legal agreement template for users borrowing through the protocol
  </Step>

  <Step title="Technical Integration">
    The protocol's engineering team integrates the Leviathan Embedded SDK into their frontend:

    * Install `@leviathan/sdk` and set up the `EmbeddedLendingClient`
    * Implement eligibility checks, agreement flows, and loan origination in the UI
    * Add loan state display and repayment progress tracking
    * Configure wallet signing for Leviathan transactions

    See the [Integration Guide](/leviathan/embedded/integration-guide) for detailed technical instructions.
  </Step>

  <Step title="Testing">
    Before go-live, both teams validate the integration on testnet:

    * **End-to-end flow** — verify the full path from eligibility check through loan completion
    * **Policy enforcement** — confirm that function gating correctly restricts capital usage
    * **Revenue splits** — validate that splitter contracts route funds correctly
    * **Error handling** — test edge cases and ensure the UI handles failures gracefully
  </Step>

  <Step title="Go Live">
    Once testing is complete:

    * Mainnet whitelist configuration is deployed
    * Revenue oracle monitoring is activated
    * The protocol enables lending features for users
    * Leviathan's team provides ongoing integration support
  </Step>
</Steps>

## What Protocols Need

### Verifiable On-Chain Revenue

The core requirement for Embedded Lending is that user activity within your protocol generates **verifiable, on-chain revenue**. This revenue serves as the basis for loan repayment through automated splitters.

Examples of qualifying revenue:

* Trading fees from DEX activity
* Yield from lending or staking operations
* Royalties from marketplace transactions
* Protocol fees from any on-chain service

### Technical Team

A development team capable of:

* Integrating a TypeScript SDK into your existing frontend
* Working with Solana wallet adapters for transaction signing
* Testing and maintaining the integration over time

### Legal Entity

A legal entity that can enter into a partnership agreement with Inkwell Finance. The agreement covers:

* Revenue share terms
* Liability and risk allocation
* Data sharing and privacy
* Termination conditions

## What Leviathan Provides

### SDK and Documentation

* `@leviathan/sdk/embedded` — the TypeScript SDK for all integration operations
* Technical documentation and integration guides
* Code examples and reference implementations

### On-Chain Infrastructure

* Whitelist configuration and function gate setup
* Revenue splitter deployment and configuration
* Credit scoring integration for your user base
* Policy enforcement and transaction verification

### Integration Support

* Dedicated technical contact during integration
* Testnet environment for development and QA
* Revenue oracle setup and monitoring
* Ongoing maintenance and upgrade support

### Risk Management

* Credit assessment of your user base
* Policy parameter tuning based on protocol-specific risk factors
* Health monitoring and enforcement automation
* Default resolution through standard Leviathan mechanisms

## Timeline

Typical onboarding follows this timeline:

| Phase                 | Duration          | Notes                                                |
| --------------------- | ----------------- | ---------------------------------------------------- |
| Application review    | 3–5 business days | Faster for protocols with public, verifiable revenue |
| Due diligence         | 1–2 weeks         | Depends on contract complexity and legal review      |
| Whitelist setup       | 2–3 business days | On-chain configuration and testing                   |
| Technical integration | 1–2 weeks         | Depends on protocol's engineering capacity           |
| Testing               | 3–5 business days | Joint testnet validation                             |
| **Total**             | **2–4 weeks**     | End-to-end from application to go-live               |

<Note>
  Timelines vary based on protocol complexity, engineering availability, and legal review requirements. Protocols with existing Solana wallet integration and clean contract architectures typically onboard faster.
</Note>

## Partnership Inquiries

Ready to explore Embedded Lending for your protocol?

<Card title="Contact Us" icon="envelope" href="mailto:partnerships@inkwell.finance">
  Reach out to [partnerships@inkwell.finance](mailto:partnerships@inkwell.finance) with your protocol details and integration goals.
</Card>

**Include in your email:**

* Protocol name and website
* Chain(s) deployed on
* Monthly active users and volume
* Intended use case for Embedded Lending
* Technical team size and availability

You can also reach us on [Discord](https://discord.gg/ggGfKnDwXQ) for informal discussions before submitting a formal application.