Juncta.Where liquidity never sleeps.

LPs set static price ranges, wait, and watch their capital sit idle the moment price drifts outside them. The architecture has no idea which bins are working and which aren't.

Juncta went DLMM instead, for architectural reasons rather than cosmetic ones. Liquidity lives in discrete price bins, and the protocol knows which bin is active at every moment. That awareness is what makes the core mechanic clean: liquidity in inactive bins is routed into the lending market automatically.

Every screen had to translate a deeply technical engine into something a newcomer could trust, without hiding what a professional needs to see.

1. 01Passive LPs consistently lose.Once impermanent loss and missed rebalancing are priced in, the average retail LP underperforms simply holding the tokens. Concentrated liquidity has become an institutional product wearing retail clothing.
2. 02DEX liquidity and lending are disconnected.LP capital and lending deposits live in separate pools with no relationship to each other, so LP capital sits idle when it's inactive. Nobody had brought unified liquidity to a Move chain.
3. 03Impermanent loss is treated as inevitable.Every AMM design treats IL as the cost of providing liquidity. No protocol had built IL mitigation into its core fee economics instead of leaving it as the LP's problem.
4. 04Lending parameters adapt too slowly.Aave and Compound use static utilisation curves that only change through slow governance. No lending market adapts continuously to live on-chain conditions.
5. 05Collateral sits idle.When a trader or borrower deposits margin, that capital earns nothing while it waits. Pure capital inefficiency that no protocol had resolved at the protocol level.

• User 01

  Passive LP

  “Yield, not a second job.”

  Deposits once, and expects the protocol to rebalance and route idle capital automatically.

• User 02

  Active / Pro LP

  “Control and live data.”

  Manages positions across bins directly. Needs real-time bin state and fine-grained controls.

• User 03

  Borrower

  “Liquidity without unwinding a position.”

  Borrows against an LP position as collateral, instead of exiting it to raise cash.

The three-layer architecture wasn't the first idea. It's what survived testing two liquidity models, and cutting a version that showed users too much.

1. 01Mapped where capital actually sits idleTraced a position through both the DEX and the lending market and found two silos that never talk. The DEX knows a bin is inactive; the lending market has no idea.
2. 02Tested static range against DLMM, head to headStatic range was simpler to build and explain, but couldn't tell the lending layer which capital was actually idle. DLMM's bin-level tracking could. That data decided it, not visual preference.
3. 03Found the gap wasn't a missing featureThe DEX already knew which capital wasn't earning fees. The fix was routing that signal to the lending layer, not inventing a new primitive.

Juncta's edge is tying three layers that update at the same time into a single surface, so the user never has to connect what the protocol is already doing.

1. Layer 01DLMM

   Concentrated liquidity, in discrete bins.

   The protocol tracks exactly which price bin is active at every moment. No static range, no guessing.

2. Layer 02Debt

   Lending that reacts to the DEX in real time.

   Idle capital on either side of a position is automatically eligible as lending collateral.

3. Layer 03Signal

   Rebalancing logic the user never has to trigger.

   The layer that decides when a position needs attention, before the user has to notice.

1234

Creating a pool and providing its first liquidity are two decisions, so they're two steps on one screen. The step you're not on stays visible but dimmed, so the whole flow is always in view.

01 Define the pool02 Seed the first position

123

1. 1A starting price, suggested

   The initial price shows the estimated market price underneath, so a new pool doesn't open mispriced.

2. 2The economics, up front

   Base fee, the fee ceiling at peak volatility, bin step, the LP share of fees and IL compensation, before anything is created.

3. 3One step at a time

   Seeding the pool waits, dimmed, until the pool is defined.

A swap can route through several pools. Instead of hiding the route, the confirmation breaks it down hop by hop: each pool's type, fee and active bin, what went in, what came out, and the price impact at every step.

Settings speak in consequences, not just numbers. Slippage says exactly what happens at the chosen tolerance, and Auto shows the tolerance it picks for each route length. Expiry explains its own trade-off: more time to sign means more price risk.

• 

  Expiry, with its trade-off spelled out.

• 

  Slippage at 0.1%: what reverts, and the minimum you'll receive.

• 

  Auto, set by route length: 1.0% for this three-hop route.

Spot concentrates liquidity around the active bin. Wide spreads it across a broad range, with lower impermanent-loss risk.

The live bin state is where the strategy becomes visible. With Spot, liquidity crowds the active bin and earns more in fees. With Wide, more bins sit away from price, and those are lent out (blue) instead of left idle. Yield is broken into trading fees and lending yield before it's combined, so the user knows where the number comes from.

⟷

← SpotWide →

Two states of the same surface. A first-time borrower is asked how they'd like to start, and can deposit collateral directly, with no LP position needed. Someone with an active position sees the lending market beside their account: health factor, borrow power, active borrows and LP collateral, in one view.

⟷

← First-time borrowerActive position →

Liquidation is where users lose money, so it's where vagueness costs the most. Each stage has an explicit threshold, so users can see what will trigger each action before it happens.

Trading fees, lending yield and borrow cost are reported separately, then reconciled, so an LP can see exactly where their return comes from and what each position is doing.

Every tabular layout had to stay legible at 12px, and every chart had to read at a glance. The palette is deliberately narrow, because in a product about money, colour is a signal.

The first version of the Signal layer told users everything. Testing showed that more information wasn't more trust.

1. 04Overbuilt the signal layerThe first version surfaced every bin-rebalance event to the user. Early testers ignored most of it.
2. 05Cut it back, then locked the splitTrimmed to the one trigger that mattered. DLMM, Debt and Signal became separate architectural layers with one shared surface: the version that shipped.

• 35/3535/35

  Screens delivered

  Pools, New Pool, Swap, Provide Liquidity, Borrow, Monitor and Portfolio, all production-ready.

• 6×6×

  Empty-state variants

  Every surface has a first-use empty state with shimmer skeletons, so a new LP never sees a broken-feeling dashboard before connecting a wallet.

• 1st

  DLMM on Move

  The first DLMM designed for a Move chain, with lending yield natively integrated into inactive bins.