Coffer

Cubee.ee interface updates 👀

We’ve redesigned the portfolio page – making it more intuitive and easier to track your positions and overall pools activity

We’ve added a stats block to the pools page. You can now quickly evaluate key metrics directly in the pool list:
• TVL
• 24h volume
• APY
• fees

We’ve also redesigned the portfolio page – making it more intuitive and easier to track your positions and overall pools activity

More useful data on screen – no need to navigate between pages

Continuing to improve the interface and make cubee.ee simpler and more efficient to use

App | X | Telegram | Chat | Docs

Today someone asked me:
“How does it differ from other multitoken pools? For example, in comparison to Balancer?”

I replied:
We added concentrated liquidity to the Balancer multitoken pool model
Balancer’s multitoken pools ≈ Uniswap V2
Cube’s multitoken pools ≈ Uniswap V3

The result:
more stable than Curve
more profitable than Uniswap V3
more elastic than Balancer

We’ve applied to the Colosseum hackathon – check out our project and support us👇
https://arena.colosseum.org/projects/explore/cube-dex

App | X | Telegram | Chat | Docs

Gm, cubee.ee documentation is now live!

In the docs, you’ll find full and detailed information about every smart contract function and its parameters, a complete explanation of the protocol’s math, as well as comprehensive API documentation – including endpoints, parameters, and logic.

The API is open to everyone. Anyone can access pool data and request swap routes – a major step towards integrations

This unlocks:
• market makers – full visibility into pools and the ability to build strategies, and after mainnet, the ability to connect to Cubee pools and interact with them directly
• solvers – access to routing
• partners – seamless integrations via a fully open and documented API

We have a powerful API from day one. You can query our API to get any data about pools, tokens, and stats, as well as request the optimal swap route across Cubee pools

You can now explore how the protocol works in more detail:
• core concepts
• architecture
• FAQ
• technical information about smart contracts and backend API
• and more

The protocol is now more open to the market than ever → https://docs.cubee.ee/

App | X | Telegram | Chat | Docs

Cubee.ee just got an update

We’ve completed a full redesign of key interface pages:
• pools page
• pool page
• add liquidity
• withdraw liquidity

We made the interface simpler, clearer, and easier to use

Also:
• slightly updated the landing page
• shipped multiple UI improvements and fixes

We keep improving cubee.ee – more to come

App | X | Telegram | Chat | Docs

Solana curve killer with new amm primitive

Curve has a ceiling.

Beyond A = 5,000, the protocol becomes fragile

Virtual balance has no such ceiling.

Let’s break down why this matters with real numbers.

What is A in Curve?

It’s a parameter that makes the price curve flatter (lower slippage in stable pools).

A = 100 → standard stable pool
A = 500 → aggressive tuning, lower slippage
A = 5,000 → extremely risky. Pools have been drained at this level

Beyond that, no serious protocol goes further.

$100 swap against $1,000 real liquidity:

Curve A=100 → 0.100% slippage
Curve A=500 → 0.020% (best it can safely do)

Cubee:
1,000× → 0.020% (like Uniswap V2 with $1M liquidity)
10,000× → 0.002%
1,000,000× → 0.00002%

Curve can’t reach that scale safely.

Cubee can.

Why?

Curve uses a hybrid formula that only behaves safely near 1:1 (stable assets).

Pushing amplification too far increases depeg risk and arbitrage attack surface.

Virtual balance uses the same formula as Uniswap V2, but with scaled reserves.

No new math. No ceiling. Works across any assets.

$1,000 of real capital.
$1,000,000,000 of virtual depth.

Near-zero slippage on any retail swap.

This is already live on Solana.

Set your leverage. Any pair. Any multiplier.

cubee.ee

App | X | Telegram | Chat

pt2 – FOR LP PROVIDERS

1. Range problem

Problem:
In V3, your liquidity only works within a set range

You define:
• min price – the lower bound of the pair price
• max price – the upper bound of the pair price

As long as the price stays within the range → you earn fees

Once the price moves out of range:
• your liquidity stops participating in swaps
• your income = 0

Your earnings depend heavily on market movement

Solution:
In cubee.ee, liquidity isn’t tied to a single pair

• one pool can include up to 10 tokens
• liquidity is used across multiple pairs
• even if one pair is out of range, others continue to work

liquidity is utilized more frequently and more consistently

2. Liquidity leverage (via virtual balance)

Problem:
In traditional pools, your earnings are directly limited by the amount of liquidity you provide

Less liquidity:
• price moves more aggressively
• less volume goes through the pool
• lower fees earned

Solution:
cubee.ee uses virtual balance

This creates a leverage effect on your liquidity

Example:
you deposit $10 → but for pricing, the pool behaves as if there is more liquidity

What this gives you:
• smoother price movement
• more volume flowing through the pool
• higher fee generation

Simply put, you get the effect of more liquidity without increasing capital

Important:
the pool cannot use more funds than actually exist

3. Pair limitation

Problem:
In most DEXs:
1 pool = 2 tokens

At first glance, it seems simple – but this is also the limitation

This means:
• liquidity is tied to a single pair
• it cannot be used in other swaps
• a significant portion of liquidity sits idle

If there’s low activity in the pair → your earnings drop

Solution:
In multi-token pools:

• you can add up to 10 tokens(=45 pairs)
• liquidity is used more frequently
• more swap paths = more utilization

Based on testing in a mainnet environment, some pools have achieved 50%+ APY

App | X | Telegram | Chat | Docs

pt1 – FOR END USERS

1. Slippage

Problem:
You can get a worse price – even if the market is calm
Slippage is the difference between the expected price and the actual execution price

Why it happens:
• your trade size is too large relative to available liquidity
• your trade itself moves the price
• the price changes during execution

The larger the trade relative to available liquidity – the bigger the deviation.

Solution:
In cubee.ee, slippage is reduced through virtual balance:
• the pool behaves as if it has more tokens → your trade puts less pressure on the price
• you get the effect of higher liquidity without increasing actual capital
• if a swap is split across multiple pools, the load is distributed and the price moves less → this also reduces slippage

+You can set your own slippage tolerance when making a swap

2. Routing losses

Problem:
You don’t see how your swap is executed – and this is where value is often lost

There are two scenarios:
1. swap goes through a single pool
2. swap is split across multiple pools

In the second case, usually:
• better price
• less market impact
• more efficient use of liquidity

The issue is that users don’t see or control this process, so part of the value is lost due to inefficient routing

Solution:
In cubee.ee:
• the best route is selected automatically
• but you can also adjust it manually

This feature is still in beta – we’re working on making routing as efficient as possible by default

App | X | Telegram | Chat | Docs

Which is better? 😁

Redesign on cubee.ee

We’ve updated the homepage and swap page – the interface is now cleaner, sharper, and more minimal

All technical details are now hidden in a single dropdown under the Swap button:
• route (can be adjusted manually)
• price impact
• other swap details

Nothing extra on the screen – everything you need is just one click away

This is a major milestone for cubee.ee

It’s no longer just a project, but a serious product built by a team(yes, there’s a whole team behind this now)

And you can already see it in the interface

Check it out: Main page & Swap

App | X | Telegram | Chat | Docs

In a regular V3 DEX, liquidity only works for a single pair

Add liquidity to SOL/USDC – you earn fees only from swaps in that pair

If the price moves out of your range,
your liquidity stops participating in swaps and stops earning fees

cubee.ee’s pools (multi-token pools) work differently

One pool combines multiple tokens, and your liquidity participates in several pairs at once

More available pairs → more swaps → more fees

Example:

You add liquidity to the SOL/BTC/USDT pool

Now it can be used for swaps in:
• SOL/BTC
• SOL/USDT
• BTC/USDT

Even if one pair temporarily goes out of range, the others continue generating fees

Simply put: At cubee.ee, liquidity never sits idle – it works 24/7

App | X | Telegram | Chat | Docs

Slippage is the difference between the expected and actual swap price

Low liquidity → high slippage
High liquidity → low slippage

Cubee solves this with leverage (via virtual balance) – Liquidity works as if it were larger than it actually is

Example:

Without leverage:
Real balance: 10 SOL
Virtual balance: 10 SOL
If your swap volume is 5 SOL → the price moves significantly

With 10x leverage:
Real balance: 10 SOL
Virtual balance: 100 SOL
Same 5 SOL volume → the price moves less

Important: if the real balance is depleted, the pool simply stops executing swaps for that token

App | X | Telegram | Chat | Docs

GN! Cubee.ee insight:

Swap routing (beta version)

What it does:
• Finds the optimal route between pools
• Splits the swap amount across multiple pools for a better effective price

One swap can can be splitted through multiple (e.g. 3 or 6 pools) to get a better result

Currently in beta – we’re still working on it

App | X | Telegram | Chat | Docs