riven

gistfile1.txt

# Cross-Chain Collateral Architecture Note

## Idea

We are exploring a private cross-chain collateral layer where a borrower can use native assets or positions from another chain as collateral without wrapping or bridging them.

The first narrow flow is:

> A borrower has native collateral controlled by an Ika dWallet. Solana coordinates the loan, refinancing, or liquidation flow. Encrypt keeps sensitive market inputs private. Ika signs the native settlement transaction when the Solana-side logic says it is valid.

This is not a claim that Ika solves external-chain state verification today. We understand Ika is the signing/control layer, while attestation is a separate layer.

## High-Level Architecture

```text
                    External Chain
              native asset / staked position
                         |
                         | controlled by
                         v
                    Ika dWallet
                         |
                         | future signature / approve_message
                         v
Solana ---------------------------------------------------------
                         |
                 Collateral Coordinator
                         |
        +----------------+----------------+
        |                                 |
        v                                 v
  Encrypt private logic              Attestation layer
  - private loan quotes              - proves collateral exists
  - sealed liquidation bids          - proves current balance/state
  - private refinancing offers       - proves position is still valid
        |                                 |
        +----------------+----------------+
                         |
                         v
              settlement decision on Solana
                         |
                         v
          Ika signs native transaction on source chain
```

## What Each Layer Does

### Solana Coordinator

Solana is the coordination layer. It stores the loan or collateral position, runs the state machine, and decides when a quote, refinance, margin call, or liquidation can move forward.

### Encrypt

Encrypt protects sensitive market inputs.

Examples:

- lenders submit private loan quotes
- liquidators submit sealed bids
- refinancing offers stay private until selected
- risk limits or thresholds can be hidden from public observers

The goal is not "everything is private." The goal is bounded privacy around the parts that create front-running, lowballing, or information leakage.

### Ika

Ika controls native assets through dWallet signing.

The asset does not need to be wrapped or bridged just to be used in a Solana-coordinated flow. When settlement is needed, Ika signs a native transaction on the asset's home chain.

### Attestation

Attestation is the open architecture piece.

The Solana program needs a way to know:

- the external collateral exists
- the dWallet currently controls it
- the amount is enough
- the position has not changed in a way that invalidates the loan or liquidation

Ika gives signing capacity. It does not currently prove this external state. So the full production version needs an attestation module.

## MVP Scope

For the hackathon version, we can avoid over-claiming by using pre-funded or pre-verified collateral.

MVP assumptions:

- one collateral type
- one dWallet
- one Solana-coordinated flow
- collateral state is pre-verified for the demo
- Encrypt is used for private quotes or sealed bids
- Ika is used for native settlement signing

This proves the composition:

```text
private market coordination on Solana
        +
native asset control through Ika
        +
clear place where attestation plugs in
```

## Production Version

The production version adds an attestation layer between the external chain and Solana.

Possible attestation paths:

- protocol-specific attestor for one chain or collateral type
- oracle/indexer-backed state feed with explicit trust assumptions
- light-client or proof-based verification
- Ika-exposed state primitive if that becomes part of the protocol later

We do not want to hide this. The architecture only becomes fully trust-minimized when the attestation layer is solved.

## First Use Case

The cleanest first use case is a private credit or liquidation flow for one native collateral type.

Example:

1. Borrower locks native collateral under an Ika dWallet.
2. Solana records the collateral position.
3. Lenders or liquidators submit private quotes/bids through Encrypt.
4. Solana selects the valid outcome.
5. Ika signs the native settlement transaction.
6. Attestation is pre-verified in the MVP and becomes a dedicated module in production.

## Summary

The core idea is not "Ika solves attestation."

The core idea is:

> Encrypt handles private market coordination. Ika handles native signing/control. A separate attestation layer proves external-chain collateral state.

For the MVP, we can demonstrate the first two layers cleanly and show exactly where the third layer belongs.